Can we create child devices?

stephack · February 28, 2018, 1:57am

doing that now

bravenel · February 28, 2018, 1:58am

I just went through this today.

ogiewon · February 28, 2018, 2:01am

I noticed this when creating my HubDuino Service Manager App + Child Drivers. For me, I just saw the errors in the Logs which annoyed me enough to simply add an empty installed(){} routine in every child. I haven’t had any issues with my Parent App / Child Devices.

stephack · February 28, 2018, 2:02am

It created without an error…but the “In use by” is blank for the child device.
parent.childOn() generates:
errornull on line 36

It still seems like the link between parent and child is not fully formed.

stephack · February 28, 2018, 2:02am

hmmm…I’ll take a look at your code and see whats different.

bravenel · February 28, 2018, 2:03am

What’s on line 36 of the app; is there a line 36 in the driver?

ogiewon · February 28, 2018, 2:05am

My code auto creates child devices based on data received from the Arduino/ESP8266… So it always checks for the existence of a child to decide if is needs to create one. Not the prettiest code, but it seems to work well-enough.

github.com

DanielOgorchock/ST_Anything/blob/master/HubDuino/Apps/hubduino-service-manager.groovy

/**
 *  HubDuino Service Manager
 *
 *  Copyright 2018 Daniel Ogorchock
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 *  Change History:
 *
 *    Date        Who            What
 *    ----        ---            ----
 *    2018-02-08  Dan Ogorchock  Original Creation
 *    2018-02-15  Dan Ogorchock  Added @saif76's Ultrasonic Sensor *

This file has been truncated. show original

chuck.schwer · February 28, 2018, 2:07am

if the link was not there, i would expect to see a null pointer exception… can you try adding a try catch around your call to parent and see what exception you get? I just tried creating a child device and then calling parent from there and it seemed fine. what does parent.childOn() do? can you add a logger to it at the beginning to see if it is truly being called?

patrick · February 28, 2018, 2:08am

So just to clear up any confusion…

Apps can have child apps

Apps can have child devices

Devices can NOT have child devices (yet)

stephack · February 28, 2018, 2:09am

I commented out everything and just have it log.debug. I’ll try your suggestions and see what I get.
@bravenel, line 36 simply does “parent.childOn()”

chuck.schwer · February 28, 2018, 2:10am

can you post your child device and parent app code?

stephack · February 28, 2018, 2:17am

So I got it working by changing

childDevice = addChildDevice("stephack", "Http Switch", "HC_${app.id}", null,[completedSetup: true,
        label: app.label])

TO

childDevice = addChildDevice("stephack", "Http Switch", "HC_${app.id}")

Getting rid of the trailer code seems to work now. Thank you @ogiewon. I used your HubDuino as a template.
@bravenel, @chuck.schwer adding the empty installed method also removed the error in the logs…let me know if you need me to test anything further…but I think I’m good for now. Thanks for all the feedback guys.

ogiewon · February 28, 2018, 2:20am

You’re welcome! By any chance, are you working on an improved Harmony Hub integration?

stephack · February 28, 2018, 2:22am

yup…I was going to PM you once I had it working somewhat. Probably tomorrow because I’m pretty much done for the night.

chuck.schwer · February 28, 2018, 2:23am

I tried your:
childDevice = addChildDevice(“stephack”, “Http Switch”, “HC_${app.id}”, null,[completedSetup: true, label: app.label])

and i’m not seeing the problem… can you post an example of the failure?

stephack · April 15, 2018, 12:54pm

@patrick are there plans to allow this functionality in the near future. I was about to create a smartapp as a workaround for my fan driver...but you guys always seem to release an update that negates the need for my workarounds right after I create them.
Never had this "problem" on the ST platform

patrick · April 15, 2018, 1:22pm

Its in the works, but with anything software, it will be out when its ready.

I hate that problem, we will work hard to fix it

stephack · April 15, 2018, 1:48pm

Good enough for me. I understand you got a lot on your plate. I think I’ll wait a bit since it’s a “work in progress” and not a “last on the list of priorities” item.

BorrisTheCat · April 22, 2018, 8:59pm

any update on this yet? I have a driver that i have brought across from ST for the Fibaro UBS that creates the devices children. The DH used to grab the virtual DH from ST and use them as the children.

ogiewon · May 22, 2018, 7:41pm

Looks like Hubitat Firmware v 1.0.9 adds support for Composite Device Handlers! Thank you Hubitat team!