So, I have a Zwave 12724 dimmer. It was added to Hubitat days ago.
All of my Zwave devices dropped from ST a couple days before that, and I've been gradually excluding and re-adding them to ST because a simply rejoin wasn't working and ST Support was unable to help.
Last night, I was adding my CT101, and couldn't get it to pair. Then, a GE In-wall Dimmer appeared. Confused, since all should be pair to ST or HE already, I saved it to see what it was. It turns out that it was my Hall lights that are already on HE.
I could easily control the device from ST and it was working properly with HE Motion Lighting App and could be controlled from the HE portal.
Of course, wanting to glitch more devices this way, I started digging a bit to no avail. However, I noticed in ST IDE that the device registered with the manufacturer: Radio Thermostat Company of America (RTC). Hmmmm...
So, I changed the DTH to the CT100 driver in the IDE. I was now able to control the thermostat that I'd been trying to re-include in ST for 2 days.
How can one device control 2 devices and be associated with 2 controllers?
2 questions. 1. What driver is the ct100 in Hubitat and did you have hub link installed? You will likely see the virtual device in Hubitat from ST if hub link is installed or the other way around if other hub device installed.
The CT101 is not installed in Hubitat. Hublink has never been installed.
The GE dimmer is not a virtual device in either system.
One thing was noted on the ST forums. Because I did not power down my ST hub, Hubitat could have joined as a secondary controller, so they could both be sharing the same network.
Since the device could be controlled from both smartthings and hubitat at the same time, those two controllers have been joined to the same network. I donāt know which one is primary and which is secondary, but that has to have been what happened as far as that part goes.
As far as the DTH, there are a couple of different things that could end up with that result but itās not something I can troubleshoot on a forum. If the thermostat is still on SmartThings, run the Z wave tweaker over there and note all of the associations and parameter settings. And the same with the switch.
So, after having my dual device fun, I removed the device via the ST IDE. I then paired it properly for ST as the thermostat.
Immediately, a device appeared as discoverable in the Hubitat Zwave Info. I was able to apply the correct driver and control the thermostat with no issues.
So, they are both on the same Zwave network, and devices are only correctly shared from ST to Hubitat, since the one Hubitat->ST device control was some sort of glitch.
I currently have multiple ST Zwave devices being shared to Hubitat with full control on both systems.
NOTE: Events are not shared across hubs, and each must poll the device to be made aware of state changes made by the other hub. So, this is not advised as a way to integrate.
I am doing something similar with my old Intermatic HA-07 tabletop Z-Wave controller as well as a GE Z-Wave 45631 keypad; I was able to get it to transfer/learn/include (not sure which terminology applies) the Z-Wave network from Hubitat so that I have on/off/dim control of Z-Wave switches.
This was done by putting Hubitat into āAdd Deviceā mode and activating the devices āreceive allā replication funtion. Though Hubitat never produced a āfound deviceā message for the Intermatic (it did for the GE), there is an entry for it on the Z-Wave information page.
As you experienced, events from these devices arenāt sent to Hubitat and donāt get reflected until their state is refreshed. But as I run a periodic RM refresh rule, it finds out about them soon enough.
You added the Intermatic as a secondary controller.
