Has anyone’s zwave locks pooched since the last update? I have 2 kwikset locks that have been flawless since I’ve installed them a few years ago. Did an update about 3 days ago and since then my locks will not update status or lock/unlock from the device page. I know they were working as I use the status light on my inoveelli reds to tell me when a lock is open and since that last update the status light has been red. When I manually press the lock or unlock from the device page I can see the command come through on the session log but nothing actually moves.
I May roll back as I backed up prior to update but seems odd that the log shows the command but the lock doesn’t move. Incidentally I have 2 kwikset locks that are zigbee and they work properly since the update.
If you manually lock and unlock the lock do you see messages to the hub? Might try removing the batteries and reinserting them to force a communication from the lock, if that doesn’t work, maybe do a zwave repair on just on the errant lock.
Thanks for the reply.
Only the zigbee locks showed the status when manually operated. The zwave doesn’t.
I also factory reset one of the locks and re-paired it to the system. Same issue.
Trying a 5 min hard reset without power to the hub next.
Regards Mac
On May 4th - i decided to update as id seen a facebook post that indicated the beta hub app would allow you to connect directly to devices....cant recall exactly what version that was but i backed up 2.2.6.130 prior to updating.
Updated to 227 something. Tried the new app...love the ability to see all the devices. I dont believe my problem with the locks started right away, As noted in the previous email i use my Inovelli Red status lights to see lock status and i'm in a habit of looking at the light by the patio door when i manually lock it. So presuming that my locks worked after the upgrade on May 4th
May 10th..i couldn't get the Inovelli status light to turn green. Thats when i noticed that the patio lock ( Wave Kwikset 888) was not responding to a lock command form the device page.
May 11th. Noticed another update was available and updated to 2.2.7.125. Lock was unresponsive so i started to look deeper - thats when i found out that my other zwave lock was also unresponsive. Started a Wave repair...went to bed! Was no better after the zwave repair.
Here is what i know to date:
Both Wave Locks are displaying problems
Both Zigbee Locks operate normally
Completed a factory reset and restore on the lock
Re-paired it to the system
I can see lock / unlock and refresh commands on the session log as i press the options in the device page.
Manually locking / unlocking the lock does NOT refresh the status son the device page NOR show up on the session log.
One lock has responded to an unlock command....albeit with about 20 seconds lag. I was able to replicate that twice on 1 lock in about 30 different times i tried to lock unlock..so not consistent NOR able to replicate on the other zwave lock .
So...I tried to roll back to 2.2.6.130 using restore file. I save the backups in a folder. Selected that folder, selected the file, hit the restore button but it still shows 2,2,7,125 after the restore ( did it twice)
I do see an option to restore a previous platform version. I wanted to check that this option actually restores my database and not a clean 2.2.6
Appreciate any thoughts
Hoping my hub isn't pooched...Love my C5 and given the option...would rather keep it vs the C7
I know there were changes to the way the mesh identifies neighbors, and thus the routes, but for me all my routes improved. Might need to consult with the wizard (@bcopeland) on this one...
Do you have any beaming repeaters to throw into the mesh? When it comes to z-wave locks they're the best option to have one as close to the lock as possible (see the billion and one threads on the subject) While im sure you have mains powered devices they are likely enclosed in a metal box which will hinder signal. Repeaters like the aeotec 6 or 7 will strengthen your mesh.
As your question about platform, if you restore to a previous platform (think operating system version) it will continue to use the existing device database. That said, what's your main beef with the C7? It's a pretty solid performer. The only real issue is the s0 issue with certain devices not adhering to the z-wave specifications. Just curious.
The database will remain as is, it's just different software that is going to be using it.
We always keep database backwards compatible in case someone wants to roll back.
Appreciate the thoughts.
I'm pretty certain my mesh is strong. Next to the front door lock i have 2 zwave plus switches with in 2 feet. of the lock. Between that lock and my hub there are at least another 4 zwave plus switches.
Next to the patio lock i have about 6 zwave plus switches.
I think on the main floor, where both locks, and my hub is i have 12 zwave plus switches...and a couple of zwave repeaters. The switches in my home are all in plastic gang boxes as well.
My locks have been pretty solid up until recent so i'm looking for other things that have might have changed.
Now...i did find a new ZOOZ switch drop off recently. Discovered that a couple of nights ago too.... Wont even work at the switch...maybe thats causing some of 'noise " on the system and the lag i've seen on this lock issue. Going to force remove that today and try to factory reset that to see if it helps. Hard to believe that they are completely unrelated when they started acting up at the same time
Appreciate the replies and suggestions. will update after the roll back.
Forgot to add. I dont have anything specific against the C7...it's just when i read problem posts ...many many posts seem to be related to people who have C7s and i've never really had any issues with my C5 so was planning on keeping the C5 for as long as i could.
But open to upgrade if i cant sort the current issue.
Regards;
Mac
My experience has been the complete opposite. I had almost a year straight of problems with the C-5 and locks. I've yet to experience any lock problems with the C7. In fact one of my 3 locks that I could "on occasion" see accurate status updates from (on a metal building outside 50 ft from the house) but could never operate from HE. I now can "reliably" operate that lock and see accurate status updates now that it is on the C7, and according to the zwave mesh details it actually has better numbers than my closer locks.
As per your issue above, I would guess that if you have a device (zooz switch) that has went missing (not communicating) from your mesh, and your hub keeps trying to contact the device, that may cause some issues overall.
Not sure what really happened. Might have a red herring in the mix as a switch that fails to work on a manual push has more going on than just a loft of comms to the hub.
I rolled back the firmware to 2.26.130.
The front door lock worked immediately but a slightly longer lag than im used to..but at least it was more consistent for lock and unlock from the device page.
I factory reset the patio lock, re-paired it and it too started responding to the lock / unlock commands, as well as proper status updates on the session log.
I re-added the re-paired patio lock to the Switch Dashboard and my status light on the invvelli by the door worked properly.
However, the Inovelli status light in my bedroom wasn't updating with the lock / unlock status...which incidentally is in the same gang box as the Zooz that stopped working.
I had to power down the branch circuit at the breaker to get the ZOOZ to become responsive so i could do a factory reset, Did a factory reset on the Inovelli at the same time. Re-Paired both to the hub and everything is working.
It's possible that the patio lock was routing through one of the switches that were offline...but i'd be surprised as the lock is direct line of sight to the hub ( 15 feet tops) whereas the 2 switches in question are off at a right angle to the hub and further from the lock. I'd be extremely surprised if the front door lock was routing through the 2 switches in question as it's on the other side of the house away in the opposite direction from the switches and the hub is much closer than the switches.
If it was mesh related ( with 2 unresponsive switches) , i would have thought that the zwave repair i did a couple of night ago would have helped....but it didnt. And as the locks became responsive after the roll back...but before resetting both unresponsive switches....i still this its firmware related.
Anyway...going to make sure everything is working....download another hub backup and consider the firmware update again. I cant help but think something else happened over the last few days in conjunction with the firmware update. The power did blink a couple of days ago. those dont normally take out switches in my experience but who knows...might be a combination of a power glitch, 2 unresponsive switches and a firmware issue.
Appreciate all the replies and suggestions.
Solved for now!
If you have 2 switches which have no power going to them (as you stated above not manually turning on/off) but they are still included in your mesh, then your hub's radio is repeatedly trying to search for and contact those devices. Whether or not the locks are getting their commands from those switches isn't really the issue, the switches being offline is causing excessive traffic on your radio searching to communicate with those switches would more than likely be the issue.
Excessive traffic means much slower device response from the traffic being bottlenecked from repeated attempts to communicate with those switches. Even though the locks would more than likely re-route through different devices your network itself would be slower.
I'm leaning in the same direction as you indicate...too much traffic from unresponsive switches.
They were however powered......i only shut the power off to the circuit to be able to force a power cycle so i could factory reset...they were just nutted up.
I would say though that 2.2.6 handled the extra traffic better than 2.27.
Before i factory reset both the Zooz and Inovelli i had no control of my locks on 2.27. After i rolled back to 2.26...i could control both locks.
After i reset both switches...the lag time dropped yet again.
I think im going to systematically operate every switch manually and make sure the session log is updating and that i have control from the device page of each. who knows how many devices were affected form what ever nutted up the 2 that i know of.
