Yikes. so sad.
1 Like
In a followup, they made it clear that parent/child devices are unsupported in the NEW app. No timeline on when they might restore that capability. Iâll be interested in your experience with Hubitat and multi channel devices
They do work, but you have to make some changes to the DTH. This issue has come up in about eight different threads with devices from different brands. You have to rewrite it so that they are no longer âcomponents,â but itâs only two or three lines of code. Then you have to delete the old child devices, and do anything with the parent device so that it will create new child devices.
Hereâs one example:
I know in Hubitat it is no problem. I have just been looking in their community just like
I am in the ST Community now.
My biggest reason for changing to Hubitat is that I need the MIMO and MIMOLite devices from FortrezZ to function. They are super cool devices with a Zwave dry contact that also has sensor input built in so in essence they are a dual zwave device. The MIMO actually is 4 inputs on one device . Two dry relays and two sensor inputs. I use it to turn my water on/off and water drain to turn on /off in a second home so cant do without it. But in two days I will be without it as it does not work with the new App. 
Itâs really an odd decision that ST chose to implement a breaking change to parent/child (including their stock handler) and no intention to fix(?)⌠
1 Like
Did the exclude/rejoin. Its working as a single channel device. Now onto step two, which is to try to find a DTH which will restore the dual channel functionality. Hows that Hubitat?
Started modifying the âZWave Device Multichannelâ DTH published by SmartThings based on the link @JDRoberts provided regarding modifications for adding child devices. TL;DR I have the child devices being added, but only partially works. Not sure how to get the child device switches both working.
First thing I noticed was they deprecated the multichannel functionality. Thanks SmartThings
So, on to debugging⌠I was able to piece together endpoint descriptions needed to add the child devices. â1001 20,25â Cool⌠child devices added, two switch endpoints⌠They show up as devices in the new ST App, but dont show up as children under the parent device in the app, but who cares at this point.
I go into the app, and the parent device doesnt look any different. I turn it on and nothing happens. Uh-oh. Then I noticed the child devices now show up in the app. Could it be that I figured this out? They both say on, but the lights are not actually on. Ok, maybe the state is just out of whack. I try turning each on or off EP1 and nothing. I try turning on or off EP2 and magic happens⌠lights on, lights off.
The logging output for each is slightly different. I dont know this stuff well enough yet to understand what I am looking at from the logs when the switch is turned on or off from the app (logging for each below). So, on to phase 3 now. Of course, any help is appreciated. Maybe @JDRoberts can provide another useful link to a piece of info I need to update my now custom DTH
Logging reported when turning on child device 1 from the app (which does not work)
[ffba3a62-f581-4ed7-882a-5b4da28ecfc5] 9:46:46 AM: debug 'zw device: 1E, command: 600D, payload: 01 00 20 03 FF â parsed to null
[ffba3a62-f581-4ed7-882a-5b4da28ecfc5] 9:46:46 AM: debug Got 2003FF for Switch Endpoint
[6272676c-cffd-49d3-b6d7-8bf28c78973e] 9:46:46 AM: debug 1E-ep1 handling BasicReport(value: 255)
[ffba3a62-f581-4ed7-882a-5b4da28ecfc5] 9:46:46 AM: debug 1E-ep1 cmd: [2001FF, delay 5000, 2502]
Logging reported when turning on child device 2 from the app (This works)
[ffba3a62-f581-4ed7-882a-5b4da28ecfc5] 9:58:44 AM: debug 'zw device: 1E, command: 600D, payload: 02 00 20 03 FF â parsed to null
[ffba3a62-f581-4ed7-882a-5b4da28ecfc5] 9:58:44 AM: debug Got 2003FF for Switch Endpoint
[7c02e3f1-59ed-4a54-ad15-d1d22c272aab] 9:58:44 AM: debug 1E-ep2 handling BasicReport(value: 255)
[ffba3a62-f581-4ed7-882a-5b4da28ecfc5] 9:58:43 AM: debug 1E-ep2 cmd: [2001FF, delay 5000, 2502]
Tagging @dckirker
Got the hub going. First thing I did was get the Zooz Zen16 3 relay device included. Works fine and has 3 child devices. I then moved the 3 closest switches to the hub over. I have not yet reached out any further in the house to move more over from ST. Now its getting cold so the mulitrelay that originally caused me issues in ST that runs the whole has fan has not been needed for over a week now and probably wont be run again until next summer so I will move it over at some point.
All my monoprice zwave dual-relays (about 30 of them) just stopped working yesterday. I guess Smartthings finally stopped supporting them as promises. This sucks!!! Going forward, Smartthings arenât getting anymore of my moneyâŚgonna convert everything back to Vera again.
I believe @Mariano_Colmenarejo âZ-Wave switch and Child Mcâ will work with these relays.
Thanks Paul, though I just searched âZ-Wave switch and Child Mcâ and it shows the topic about zwave temperature sensor and not the dual-relay switches that control light switches that I have.
Go to this link and you will find the driver. It is easy down on the list.
Thanks Paul, I actually just found a simple solution from the Reddit forum. Someone recommended using the âZooZ Sen52 dual relayâ driver and that works great. I just replaced the device driver and and the 2 daughter switches was generated immediately.
1 Like
Disregard, I found and installed the Zooz driver. Unfortunately when I attempt to select a new driver for one of my monoprice dual relay adapters in the app, no results are found.
The Z-Wave Switch and Child Mc Edge driver is currently installed but Iâm having issues with switch 2 sending Off values only.
How old are your Monoprice devices and do you use switch 2 to control other devices or automations?
Mine were installed around 2016, switch 1 functions as expected since the Edge migration, but switch 2 only sends OFF values to the app and IDE when turning the physical switch On or Off.
My monoprice dual-relays were installed since around 2015-2016 time frame. Iâve always used the Zwave device multichannel handler until recently when it stopped working. It was just a matter of me going into the database and selecting the Zooz Zen52 double relay device, after which two Zooz switches were instantly created.
Hello all, I ran into similar issue with my Mono price and Vision dual relays which I started added back in 2016. I was able to install @Mariano_Colmenarejo âZ-Wave switch and Child Mcâ for all dual relays. It works but status does not get updated.
I also tried using Zoom Zen52 driver but it does not allow me to add this driver. It complains to device fingerprint not matching. I would like to try ZooZ driver as well. Any suggestions?
Zooz drivers are NOT open sourced and generally only work with Zooz products.
Any luck here. Same story. Used Mariano_Colmenarejoâs âZ-Wave switch and Child MCâ driver but status does not get updated. Zen52 fails due to fingerprint mismatch. Any help will be appreciated.
Hi @rizy1976
Could you be a little more specific with the problem you have?
Can you publish the fingerprints of the device to be able to identify it in the driver?
You can switch to the zwave thing Mc driver to see all the information