If that sounds like too much work, you might be able to join Hubitat as a secondary controller to HS, then "shift" it from your secondary to primary (I don't think Hubitat likes not being primary, but I think some people have done this short-term for this purpose). If you don't care about HomeSeer, you can also just reset the Z-Wave device (something you might need to try for troubleshooting anyway if it still doesn't pair after regular exclusion) or use any Z-Wave controller to exclude it, though HomeSeer will probably still think the device exists in that case, while not being able to do anything with it. If not, you can search this Community forum to see (and unofficially the SmartThings Community forum as it's normally easy to port code) or ask around for anything specific.Īs you may know, the most officially supported route would be to exclude the device with HomeSeer, then put the Hubitat hub into "discovery mode" for Z-Wave and ZigBee devices, then do an "include" on the device (varies from device to device, so see the manual, but usually pressing or holding a button on the device itself).
#Homeseer forum keeps shutting down drivers
If it doesn't pick one for you, it's likely one of the generic Z-Wave drivers for that type of device (motion sensor, contact sensor, switch, etc.) will work.
#Homeseer forum keeps shutting down driver
For popular devices, it's likely Hubitat has a built-in driver that will work to communicate with the device (not sure what the HomeSeer equivalent here is). Hubitat will pair with pretty much any Z-Wave device.
But since your devices are almost all Z-Wave, it should be pretty easy.
I haven't seen a lot of talk on this forum about HomeSeer migrations-there's definitely a lot of users migrating from SmartThings, and I've seen a few from Vera as well.
0 kommentar(er)
