Yale Z-Wave Module 2 and USB Z Wave stick?

Hardware
223

No, not that I have noticed but it always was pretty instant response

1 Like
224

I created an automation to see who had unlocked the door by using Holdestmade’s code, but it doesn’t matter which tag I use to unlock the door with, it always comes up as AlarmType 21 - Manually Locked.

Any ideas why?

I am running the latest version of HA Core 2021.3.3, Supervisor 2021.3.4, HassOS 5.12 and Z-Wave JS to MQTT 0.6.2

225

Have you seen my post
I know who and when

226

Hey, are you able to tell which user unlocked the door. As my above post shows I use that a lot. Yet just moved over to Zwave us and can’t find it

227

Yes working fine now.
The entities didn’t appear for me at first but one day they just appeared !
Not sure if it was after an update or just a restart
They are named something else though and I think they were disabled

1 Like
228

I had issues the lock jammed, so I had to rebuild the lock and then I lost the Zwave connection.

I’ve reverted back to the old Zwave for now.

It currently reports the nfc tags like this “Unlocked by NFC Tag or Card by user 3”

229

Been lurking on this thread for a while.

I installed the lock about 3 weeks ago and the zwave module 2 weeks ago. Installed zwavejs-2-mqqt on a standalone Raspberry Pi so it is near the lock and thanks to all on here it is working quite well. Really happy with it.

I have noticed in 2 weeks (bear in mind to begin with I was using it a lot to test), the battery is reporting a 15% loss, does that sound right? I think it is ok, but just want to see others mileage.

I use Node Red for all my automations and have used the list from @lolouk44 for lock reason and it works a treat.

I can’t seem to get the tags working though by name - is this possible?

Thanks for all on here BTW - I was thinking about the lock for ages and you pushed me to it :slight_smile:

I do though still carry my back door key incase as I trust it 99.9% :slight_smile:

One last question - I go to the GUI for zwave probably every day to refresh status to get the battery - can this be done automatically, say once a day?

230

my batteries last ~6 months depending on usage.

Check my updated template sensor:

I don’t trust it that much so I will always keep the back door key. It got stuck twice already (once with OZW, once with Zwave-JS), requiring a rebuild. Never lost the Zwave connection though

I don’t understand. Battery Level should come to HA

1 Like
231

Thanks for getting back to me - I’ll take a look at the template sensor.

The battery doesn’t seem to update in HA unless i force an update on the zwavejs2mqtt server (I am running it standalone).

I have left it 2-3 days and nothing until I initiate the poll in the GUI. Strange. Is there a MQTT command to do the same? I could then poll from Node-Red or HA?

233

@lolouk44
thank you for sharing your sensor are you able to see the alarmtype track “24” I unlock my door via HA quite a lot and thought this is how it would track it, yet I only ever see “144”

234

I would almost never see the alarm type 24. but I see a lot of 25
unlock by zwave turns the deadbolt. You then can pull the handle down to fully open the door (multi lock).
Once you’ve pulled the handle down, you can’t lock unless you pull the handle all the way up.
All of this to say I’d only see alarm type 24 if I unlocked by zwave, didn’t touch the dooe, then locked by zwave.
the lock also has an automatic relock after 30 sec if I unlock but don’t pull the handle down

144 is for when I unlock with an RFID key tag

Hope it helps

235

Sorry I meant I thought using the unlock option within HA would trigger alarm type 24 (used z wave)

I can currently track when I or my wife unlock with our tags, but can’t if we use HA

Currently I can’t see a way to track which HA user unlocked the door via HA

236

no for that you’d need to check the entity’s history / log to see who tapped the button in the UI.
If it’s done via an automation you’ll need to know which user triggered the automation (if that’s even available)

237

I had resolved that issue but it broke again I think in a recent Z-Wave JS update, if you use the following code it would have told you which user locked the door in HA (and 25 for unlocked), as I say, the alarm type and alarm level sensors aren’t updating in my HA for the last few days

{% elif states("sensor.front_door_alarmtype") == "24" and states.lock.front_door.context.user_id == "ENTER USER ID FROM CONFIGURATION>USERS" %}Locked by HA (ENTER PERSONS NAME)
1 Like
238

@captain_daveman

Thank you for this, the only issue I have now is before when I was on the standard zwave intergration it logged in the history the user, now on JS Z Wave it doesn’t.

239

Yes, I had the same issue, I had to create the sensor @lolouk44 describes above (adding in the userID bit I shared with you) that way you have a sensor that always shows the status of the lock e.g. unlocked using RFID by x or locked manually. The necessary information actually comes from the alarm_type and alarm_level sensors, these have just recently stopped working for me, hoping I’ll resolve that though!

240

same here I see nothing has changed in a while. Not sure which update broke this, but I see my container updated on 22nd, 24th, 25th and 26th March…

241

Also I noticed battery sensor had not updated as I changed batteries thinking this may have caused it, if you use the Z-Wave JS: Refresh value(s) of a Z-Wave entity service call to update the battery it refreshed to 100%, tried the same service to update the alarm_type and alarm_level thinking this would be the same issue, sadly it wasn’t

242

Hi
This is a long shot, my lock has started malfunctioning to the point I can’t use it.

When I turn and unlock, it plays the power up sound, when I lift the handle to lock it the locks stops halfway.

The lock has been working fine for 2yrs has anyone else experienced this issue, or may know what might be the cause?

243

not experienced it, but maybe try to see if you can factory reset it:

1 Like