Thanks for the replay again. No, I tried every available option before sending the last email because I thought the same thing. Can I just ask what you see when selecting an automation with yours? I assume you have one, since you’ve gone to the trouble of creating a handler…
What automation tool are you using? Webcore?
I’m just using the automation from within the ST app. I do use the Core app usually, but this wasn’t showing the children either.
I did try starting fresh over yet again - removed the device - waited a while for everything to update. After adding again and applying your device type - this time the children did not even appear in the device list (whereas before they did, but not in the automation selection).
At this point - If I could just get back to having the device - with children - with events showing for each, I’d be happy 
(automations can come later)
FWIW, I have been using this DTH with my Fibaro UBS for around 18 Months now. I included the module, change the DTH to this one and then went into the device on the app to create the child devices. If you look in the developer portal you can see that the child devices also have the parent ID in then, For me the Parent is 17 and the first contact is 17-ep1.
I have been using Webcore with the temp sensors for a while and also the Simple data Logger app. No issues. I just made the contact endpoints available to Webcore (via the app) and was able to create a piston no issue.
Maybe check the name of the contact device that shares the ID of the parent and make sure its selected in the webcore app?
@cjcharles any chance you can have another go a updating the DTH to work with the new app please? 
Sadly the new Smartthings app doesn’t work with custom device handlers if you have any custom tiles, which make the majority of custom device handlers. But surely the children devices show up fine since they are super simple, and then you can ignore the parent device
Please could you explain what you mean by “went into the device on the app to create the child devices” (I do understand about the Id’s)?
I have :
- Physically included the module .
- Added the parent device via the ST App.
- changed the DTH to the cjcharles one from within the ST portal.
- If I look at “My Devices” in the ST portal, under the parent device it shows “contact1” and “contact2”. Both of these have activity (from my home alarm in my case)- which is perfect. So far so good.
But if I then go to the ST app on my phone, I only see the Parent device. If I try to create an automation (with either ST automation or webCore) - both of these also only show the Parent and I cannot find how to target the child contacts. They do not appear regardless of what I select.
I seem to be missing the step where you said “went into the device on the app to create the child devices” (I do understand about the Id’s that each device has and where to find it).
Thank you for any help/advice
Mark
If you’ve got it working in the st app, then you just need to give the automation/webcore/… access to the new devices, normally in settings of the automation section in the app. No need to delete and recreate devices or children from this point
Yes, from the ST portal, I have a parent, with 2x children that are logging events. Perfect.
The problem is that in the ST App (on my phone), when trying to create an automation - with either the ST Automation - OR - the webCore automation (both of which I’m totally familar with), I still cannot see the children. All I see is the Parent device.
It Doesn’t matter what I select for an action/capability (switch/contact/motion Ive tried everything), there is nothing to select beyond the main parent.
I would expect to be able to select --> Parent --> Child - Action (open/close) or whatever, so that I can continue to create an automation/piston. (Or perhaps even just select the Child directly, without selecting parent first - but it’s just not there).
All I can select with webCore is --> Parent --> Temperature(why temperature?).
And with ST automation --> Parent (nothing else)
It’s great that the children are logging events in the ST Portal - but pointless if I can’t make use of them in the App.i hope that makes sense - i’m losing the will to care much for much longer
You have to add the child devices to webcore.
Thanks for trying to help everyone - I solved it by switching the handler to a different one ( [fuzzysb : Fibaro Universal Sensor ]). Children showed up straightaway and also appeared within automation and webCore. All working now, never, ever touching it again!!
The issue is all the child devices show as offline. Although, if you click on then you can see they are receiving events and the temp shows.
Curious, and that device handler works in exactly the same way from memory. Perhaps there is an ST bug again
Appearing offline is just an ST quirk, it doesn’t affect how the devices work, though admittedly annoying given it’s visibility in the new app. I’d suggest getting it set up in the old app first
NP. I have been using your DTH in the old app for over 18 months now. Works flawlessly. Its just with all the talk about migration to the new app I would like to get these quirks sorted if I can.
Well, I’m having a stack of problems here. I already have one existing ubs with temperature probes - been working for more than a year.
I have approx 7 spare DS1820s, two spare ubs, one implant.
Try as I might I cannot under any circumstances set up a new system here. Can’t get anything to get recognised, and it’s driving me insane.
I connect the PSU and the probes, reboot/reset, add using the triple-click, see it recognised as a zwave whatever, log into the dev portal and change the device type… cannot get this thing to recognise any of the sensors.
Same goes for both spare ubs’s and the implant. Which suggests the unlikely possibility that all of my unconnected sensors are broken ? I’m terrified to unplug anything from the existing working ubs as I’m not so sure I could get it working again.
Gah!!
I found the UBS to be the most problematic to include of all the Fibaro devices. When I had issues the best sequence was to b exclude the device, reset, confirm the probes are attached and then include again. Also look at the event to see how many end points were found. After setting the device in inclusion mode and doing the 3 clicks while the UBS is close to the hub, it pays to wait a while. I found it can take up to 20 seconds or more to show up.
Yup, absolute pain in the ass.
Finally got it working after a few reboots. Not the most intuitive. The smart implant by comparison, was a doddle.
Did you use the same DTH for the implant? Was looking at this for another use case.
Hi,
Oliver has written a fairly awesome DTH for the implant.
See here
Cheers. I missed that!