WOndering if anyone can shed some light on the subject of getting the UltraloqPro Zwave working with C5 or if I need to upgrade to a C7 to make it work?
I paired the lock successfully and it locked and unlocked a couple of times using a command direct from Hubitat but now there seems to be no communication between the hub and the lock??
I have the * zwaveSecurePairingComplete: true on the device page so looks like it's ocnencted using S0 but now I am lost as to why no commands or updates are working?
I have a Z-Wave repeater between the hub and the lock but not sure if it's being used for the routing or not??
I have done a Z-wave repair but still no joy.
Is it time to upgrade to C7? (I am scared of the migration if I'm honest. It looks very complicated!!)
I am using generic Zwave Lock driver. As I said it included and worked for a couple of lock/unlock commands and now it's totally unresponsive. Even when I lock or unlock the lock manually or via the keypad no updates happen in Hubitat. Zero comms between the two.
as @thebearmay requested, we need to see your Z-wave details. Go to Settings->Z-wave details.
EDIT- oops, nevermind the C5 doesn't have the level of detail that the C7 has. In any event there are a ton of people who have had lock issues, so much so that Hubitat removed multiple locks from their compatibility list. I don't know about the UltraLoq specifically, but even some of the largest in the industry failed with Z-wave locks(think Schlage)
So while I don't have a solution, you're in good company. Hopefully someone who owns an Ultraloq can chime in.
Many people prefer ZigBee for locks, but the only issue I've had with ZWave (and it would be the same for ZigBee) was when my mesh was relatively sparse and going through a plaster wall with metal lathe to get to the hub 12 feet away wasn't giving me the signal strength I was expecting.
You can determine if there are ghosts or stranded devices on a C-7 without a secondary zwave controller.
However, some stubborn ghosts and stranded devices will need a secondary controller to be removed. So it is always a good idea to keep a secondary controller around. Sticks from Zooz were about $20 a short time ago.
Quick update. I got impatient dug out a long ethernet cable and took the hub to the lock. I then excluded it which worked successfully and the included it again.
Moved the hub back to it's original position and it has been working since! Let's see how long it lasts?
The migration is pretty easy if you subscribe to hub protect. All your z-wave stuff will move over. Now the zigbee is interestinig. In most cases when you remove it from the old hubitat it will go into pairing mode on it's own. All you have to do is hit zigbee pairing on the new up and it should slot right in to it's own place. It will say, found previously connected device. Boom... You're done. When I did my migration I was worried because I have 36 window sensors. I have around 60 zigbee devices alltogether. I had to factory reset 2 of them... I was happy with that.
Just a quick additional question, why do I need hub protect? Can I not just download a saved back up and use that to restore from when I get the new hub?
Local backups don’t include the Z-wave radio database, but cloud backups do. So while it’s possible to migrate hubs with a local backup, it would require more work.
)
