Integration with ID Lock 150

Configuration Z-Wave
125

Yepp

- binary_sensor:
  - name: Lock away mode
    state: "{% if 'Enable Away' in states('sensor.lock_lock_mode') %}on{% else %}off{% endif %}"

Then an automation to turn alarm on.

1 Like
126

Fantastic. Thank you!

127

Trying to add the binary sensor in my config. How do I reach ā€œsensor.lock_lock_modeā€, it does not seem like I have a sensor (alive, at least) in my list of entities for the lock.

128

Check if itā€™s disabled.

129

Cooling, lock statee, alarm level, alarm type, config parameter door lock mode and cover status is unavailable.

130

I got the same settings as: Integration with ID Lock 150 - #109 by mapeje

131

Since a few Zwave JS versions (?), my lock still change Door Lock Mode from ā€œDisable Away Manual Lockā€ to ā€œEnable Away Manual Lockā€ when I turn on the Away mode via code + [*] on the lock.

But it no longer change back to ā€œDisable Away Manual Lockā€ after unlock.
Temporarily, I handle that via an automation the set the Door Lock Mode parameter after unlock event, but it really shouldnā€™t be needed.

Does your lock still change back to ā€œDisable Away Manual Lockā€ after unlock?

132

Hello!

Sorry for the potential spam, but I didnā€™t find information regarding that.
I try to add my ID-Lock 150 to HA using the Zooz Zwave key. I changed batteries, tried non secure inclusion and reset the lock couple times, re-interviewed, nothing changes, I only get bare minimum entities. Anything I missed?
Here is a view of the device in HA:

image
image2302Ɨ1684 277 KB

133

Try moving your zwave stick close to your lock before starting inclusion.

134

Doesnā€™t look like you have added as a secure connection. Also check that you have updated the firmware to the latest version. There is an app for doing so. If I remember correctly it is android only.

135

Thanks @Minken and @Blixten .

firmware is updated to newest version. IƤll try to get the stick closer, itā€™s going to be a challenge though :sweat_smile:
I will update

136

Hi again!

I tried with the key next to the lock (litterally 1m away) and it doesnā€™t change much.
I did a factory reset of the lock and re-added it but it was added in unsecure mode for some reason and now it looks like that.

image
image1756Ɨ1794 349 KB

Any idea on how to fix it?

137

Updated ZWave JS UI, and now I canā€™t lock and unlock. Annoying! I have tried re-interviewing, but I think I remember that something has to be done to the lock first, to put it in a ā€œreceptableā€ mode. Does anybody know?

It shows a question mark for security, but I checked, and the S2 keys are still in there.

Never mind. Seems like holding in the * and the # key for a few seconds was it. :grin:

138

I upgraded my Idlock 101 with the 150 Z-wave module (which is backward compatible).
What I have noticed is that when it auto locks (set up in the lock before the module) the control and the sensor does not change state. Can take hours before it does.

  1. Do I have to configure something for the module settings via. AH (integration/Z-Wave/Idlock/Configure)?
  2. The module not updating (sending feedback) state for hours, anyone else experience this?
    image
    image679Ɨ713 40.9 KB
139

Try to reinterview the device.

140

I am tired of using motion sensors to unlock the door (in addition to my phone or my wifeā€™s phone having arrived at the house in the last minute, of course). The motion sensor eats battery. Is there anything that shows when the keypad is activated? So a signal thatā€™s sent when I lay two fingers on the keypad to activate that? I tried, and this is what I see in Z-Wave JS log:

2024-02-15 11:48:20.455 INFO Z-WAVE: [Node 009] Value updated: 98-0-currentMode 255 => 255
2024-02-15 11:48:20.462 INFO Z-WAVE: [Node 009] Value updated: 98-0-outsideHandlesCanOpenDoor false,false,false,false => false,false,false,false
2024-02-15 11:48:20.468 INFO Z-WAVE: [Node 009] Value updated: 98-0-insideHandlesCanOpenDoor false,false,false,false => false,false,false,false
2024-02-15 11:48:20.473 INFO Z-WAVE: [Node 009] Value updated: 98-0-doorStatus closed => closed
2024-02-15 11:48:20.477 INFO Z-WAVE: [Node 009] Value updated: 98-0-boltStatus locked => locked
2024-02-15 11:48:20.481 INFO Z-WAVE: [Node 009] Value updated: 98-0-latchStatus open => open
2024-02-15 11:48:34.997 INFO Z-WAVE: [Node 009] Value updated: 98-0-currentMode 255 => 255
2024-02-15 11:48:35.004 INFO Z-WAVE: [Node 009] Value updated: 98-0-outsideHandlesCanOpenDoor false,false,false,false => false,false,false,false
2024-02-15 11:48:35.016 INFO Z-WAVE: [Node 009] Value updated: 98-0-insideHandlesCanOpenDoor false,false,false,false => false,false,false,false
2024-02-15 11:48:35.022 INFO Z-WAVE: [Node 009] Value updated: 98-0-doorStatus closed => closed
2024-02-15 11:48:35.026 INFO Z-WAVE: [Node 009] Value updated: 98-0-boltStatus locked => locked
2024-02-15 11:48:35.030 INFO Z-WAVE: [Node 009] Value updated: 98-0-latchStatus open => open

To me that just looks like a set of parameters are refreshed when I activate the keypad. And that may happen if the lock wakes up unrelated to touching the pad, right? So is there something hidden that I could use?

141

Anyone had any issues with the ID Lock 150 lately? Some time ago my device node went dead and I readded it, but since then I canā€™t fetch the user_id anymore, no matter the keycode entered. The only thing I get correctly is the type, event and event_label:

event_type: zwave_js_notification
data:
  domain: zwave_js
  node_id: 26
  home_id: 3415330873
  endpoint: 0
  device_id: 6f180eb99b199bdb665ee28042f84d84
  command_class: 113
  command_class_name: Notification
  label: Access Control
  type: 6
  event: 2
  event_label: Manual unlock operation
  parameters: {}
origin: LOCAL
time_fired: "2024-03-02T11:11:21.201905+00:00"
context:
  id: 01HQZDS13HJ5RH21YFATGRP8SJ
  parent_id: null
  user_id: null

I have resetted the zwave in the ID Lock 150 multiple times, uploaded to latest firmware, removed and added the lock in HA multiple times. Even bought a zwave extender and put 1 meter away from the device. But no change. Iā€™m at loss.

Iā€™m using a Zooz 800 Series Long Range USB Controller with no issues with any other zwave devices. And it has worked in the past.

142

There are 6 different lock operations. Here are their events labels and event numbers.
Manual Lock(1), Manual Unlock(2)
RF Lock(3), RF Unlock(4)
Keypad Lock(5), Keypad Unlock(6)

The manual unlock event is generated when you unlock using a key or the inside knob and the keypad unlock event is generated when you unlock using the keypad. The user id is only displayed when performing a keypad lock or unlock.

Based off the event you provided this tells me 3 things. The lock events could be different from lock to lock, the lock is sending the wrong event, or you are not unlocking with the keypad so itā€™s not sending the keypad unlock event.

143

Thanks. Yes, I thought I pasted the event for when I opened the door via Keypad Unlock (6), but clearly not. (which makes sense if you continue reading)

After some testing now while scanning the event type zwave_js_notification I seem to have found the issue - but not how to fix it. Doesnā€™t matter what keypad number Iā€™m using to unlock, nothing is getting registered in the event log (but door works to unlock of course). So for some reason, the only things getting fetched is the event 1 and 2 (Manual Lock and Manual Unlock). Again, the others has worked in the past.

1 Like
146

Hi
User of one of these locks.
Since 1-2 months ago my lock is never going to sleep so it drains the batteries fast.
Using the latest firmware of the lock.
Using 2024.8.3 of Home Assistant Core and 0.6.2 of Z-wave JS.
Any ideas? Its getting quite expensive to feed the lock with fresh batteries