I'm running 2.2.0.125 . Since the last 2 updates to HE, my Alfred lock status (lock/unlock) isnt refreshing like it used too. I am manually refreshing it. I have a rule that looks like to see if it's LOCKED when someone hits a motion sensor. If it's LOCKED, then it UNLOCKS but now it's not reporting when the LOCK is actually locked or unlocked. Once i refresh manually it updates. Any help is greatly appreciated. @mike.maxwell
This is happening to me as well. This is also happening with my aeotec multi-sensors and my forbidden schlage lock. Things aren't updating correctly. Hit refresh and about 10 things happen in consecutive order. Poltergeist at the Brandt residence.
1 Like
Are these all Z-Wave devices? Just curious... 
No both meshes appear to be affected. I was just talking to someone about it yesterday, I'll copy and paste my description of the issue. In an edit to this post once I find it.
[EDIT]
It's hard to describe what things are doing around here. It's like they're "sleepy" if I lock the lock manually, and unlock it, then it starts communicating again. If I hit refresh on my sensors, they update. If I open the door and close it a few times, then other things associated with it start working. This is what's happening with lots of my devices on both mesh networks.
[another edit] About the sensors .. my aeotec multisensors are connected to mains and won't update unless I click refresh. I've confirmed that a zwave repair touches these sensors. This happens using the available built in driver and csteele's custom driver. All of my switches are zwave mains. They are all affected. When I start interacting with a lock/door - unlock manually open door/close door/open then everything that didn't fire hits in consecutive order for the next few minutes. Then the lock will lock again, even though it's locked. I have very little custom code on my hub. My second hub with sylvania's on it seems fine, but those lights are affected as well because the main hub is affected with this. The hub is super responsive when I go into the IDE and screens populate quickly. When this happens, I usually just reboot the hub.
1 Like
Lock that shall remain unnamed
2 Likes
The problem is that my lock has worked flawlessly until ... just recently. When I suddenly had to add repeaters move devices that had been working with no issue up until now.
It’s like discussing politics at family gatherings..
3 Likes
My lock is Zwave. And like the others, I haven't had issues with my Alfred lock DB2 until now.
1 Like
Any updates on this? I just installed a Alfred DB2. It paired to Hubitat really easily but now theres no status for locked or unlock. It also won't do anything when sending lock or unlock commands. I tried both the Alfred driver and the generic z wave lock driver.
I also installed a Yale YRD256 Z wave on another door at the same time and that lock is working great so far.
Does your lock have the updated firmware necessary for it work with the HE driver? Sounds like it does not.
Tagging @april.brandt - she knows what the current Alfred firmware is. Memory says that they had to ship her a brand new z-wave module with the latest firmware.
The firmware is about it working with lock code manager. If you're not getting communication, that's a mesh issue. Do you have a repeater that supports beaming?
I will check the firmware on the module and respond back.
here is the version report of my zwave lock
1 Like
Were you able to successfully pair the lock with the HE without issues in the logs? How far away is the lock for the hub?
Yes the locked paired first time no issues. The only event in the event log under the lock is a code length event which matches the only line listed under current states.
If there other logs I should be looking at?
Also, lock is directly beside a leviton decoa switch which does support beaming.
Both the Alfred lock and the Yale lock I installed are a floor above my hub and about 20ft away the hubs location. There is no other z wave units by the Yale unit and it works fine.
Based on how my device page looks I would think it’s a hubitat issue as the lock doesn’t show the same states as my Schlage and Yale locks I also have.
That might be the case. What version of firmware is it? Do you have any Zwave repeaters?
Not sure where to check the firmware status expect in the app? The says everything is up to date. Is there somewhere else I can look? I have no idea where April pull that version log from.
I moved my hub to directly in front of my door, did a exclusion, and then re joined everything. Still have the same issue and the device page is exactly the same.
I do have two aeotec 7 repeaters. One next to my hub and the other out in the garage.
I did just update my hub to the newest update.
I would think since the device page doesn’t even show me the status of lock/unlock it has to be a issue within hubitat. I’ve only be hubitat though for 2-3 months though so maybe I don’t know for sure.
In this thread there's a basic Zwave tool that I think Mike created. Install that driver, change your Alfred driver to the Zwave tool & from the device page, choose getversion, check the log & you'll see the firmware version. When you change it back, (the driver) don't forget to hit "configure".
Alright, I found Mike's tool. I installed it and clicked the "Get Version Report". I had the logs open and nothing happened. I have lines for other things they were happening (my Hue Light strip turned on because of the time of day). I never had any lines come across from the lock though. I tried a few other lights and switches and had log reports as well.
This lock just doesn't want to talk to anyone apparently......Any other ideas?
