How strange, it is executing the updated() function, but seems to think you already have child devices and hence doesnt go into the child devices section. You are pressing the cog at the top of the screen right? The Spanner/configure button sends config details to the Fibaro, but is only there as a fallback option - sometimes straight after pressing the spanner it might not create child devices if it is busy sending details to the Fibaro. After 5 minutes, try going into the cog at the top right, and then after changing something press Save.
You are right that they should appear in the device list - using the same name as the parent device but with (S1) and (S2) after the name. No other code/smartapp/devicehandler is needed. If that doesnt work I might ask for a couple of screenshots to try and understand a bit more!
In that case I expect ST have changed something on their end. I should be able to add a nice fix for it this evening as Ive just noticed that section uses some old code that I have since improved significantly for some of my other device handlers.
@TheCellMC and @chrisym
I have updated the device handler on Github, can you give it a quick check and it should be more reliable at creating the child devices. Thanks
Hi @cjcharles
I have been using your DH (thanks a lot for your work), for only 1 of the 2 switches. At this time I deleted the 2nd child device automaticaly created… and I am not sure how to restore it ?
Thanks a lot
Greg
If you delete the other it will auto create both again. It might (if youre lucky) create the second one anyway, when you go back to the configuration/settings screen.
Interested in the result here as the 223 DH is NOT creating the child devices if you go into the config page, at least for existing devices, I’m away from home so cannot remove and add them back from scratch. In fact all 6 of my my dual relays have been offline (unavailable) since the 3rd January and support at their usual helpful selves as they are not officially supported. They all went offline at the same time so it is definitely something they have done to the config or the cloud! I’m really pissed at the moment as having numerous issues over the last few weeks yet nothing has changed at my end at all!
They (the 222’s) all went offline on the same day and they all stopped working on the same day? (offline often doesnt mean a problem due to the way that ST works out offline/online status).
If the 223 is not doing anything then I can create a 223 handler that mimics the 222, but it should probably be Eric who does that, given it is his device handler to start with.
All my 223’s went offline at the same time. They are defo messing with config or the cloud somewhere.
Apologies, yes I do know it is Eirc’s DH, I replied from my phone whilst walking, two tasks I find hard enough to do on their own lol.
Wonder if it the same issue though as gregoiredore was unable to get the DH to re-create the Children via the config page also. Going to poke around a little more but think I will have to reset them all once home and add them back to see if that helps.
The strange thing is that the Parent devices report nothing in the logs but if I go to the child links under the parent then there is activity under them. Still, all was working fine until the 3rd so ST change something somewhere!
EDIT: OK, so I managed to get them all back online by removing the Second Child device from under each of them via the IDE. No idea why this worked and lucking I do not use S2 on these at the moment.
Appreciate this is not relevant to the thread (different device) but just wanted to close it off in case someone came across my previous post.
@cjcharles How easy would it be to create a DH for the 223 which acted as a single switch so no Child devices under it. I have a stack of these but only use the S1 (single channel) on all of them. Thanks!
Super easy, just remove the switch2 parts and rename all switch1 parts to switch. That should be easy, and then you just need to tweak the ZWave bits so that they update switch rather than switch1. Can then just disable child devices.
For the people with problematic child devices on the 222, have they started working now? Mine seem to be running smoothly across this and other device handlers I have written using child devices.
Thanks, I did do all that months back but could never get it to work properly. Will give it another go though as my have missed a few things as was on heavy medication back then.
As of yesterday or the day before they started to report back again, I am getting notifications again but have not checked it out thoroughly yet, still away from home.
The same response from ST though, no changes were made lol… So it is evident that they have not fixed the issue that they did not cause in the first place I really wish they would just come clean occasionally.
I dont currently have my Github setup for ST integration as I had so many issues when I first tried. I have been meaning to have another go for ages so will try and get it setup so I can send you the details. As it stands at the moment you can add it via the ‘Code’ link in the IDE, and it doesnt change very often, unless ST change something!!
hi cjcharles,
Actualy, your DH creat 2 child device + one is the master so we have 3 device
maybe it is possible to have the endpoint 1 with the master (with the conf) and the second with the endpoint 2.
In this cas, we can have just 2 device
It is what do vera control and zipato on his system
I really wish they would just come clean occasionally.
