ID LOCK Support

[matt (support)]

Indigo 7.0.2 is now available for download and includes some device parameter settings for the ID Lock. I'm not sure how useful it will be, but Indigo should be able to put it into RFID learning mode, for example.

ID Lock is working very well, except from one ting: Indigo receives '"ID Lock" status update is off' instead of '"ID Lock" status update is unlocked' after I unlock the 'ID Lock'.
(This gives me problems -I am not able to trigger an event when 'ID Lock' unlocks.)

Maybe there is a bug somewhere? I would be really glad if you have a look at this issue!


From the eventlog window:

Z-Wave Debug RCVD sceneActivateCmd2: 01 0B 00 04 00 09 05 5B 03 AC 00 08 00
Z-Wave Debug . . sceneActivateCmd2: node 009, type: 0, scene: 8
Z-Wave received "Multibryter" button 8 pressed
Trigger Button 8 - Unlock Door
Z-Wave Debug SENT nonceRequest: 01 09 00 13 17 02 98 40 25 3F 32
Z-Wave Debug RCVD nonceReport: node 023, nonce 5C B2 A9 40 F8 63 61 5C
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 09 03 80 03 64 1F
Z-Wave Debug . . requestBatteryLevel: node 009, level 100
Z-Wave received "009 - Multibryter" status update battery level 100%
Z-Wave Debug SENT setLockValue: 62 01 00 (encrypted)
Z-Wave sent "ID Lock" unlock
Z-Wave Debug RCVD nonceFetch: node 023
Z-Wave Debug SENT nonceReport: 01 11 00 13 17 0A 98 80 FB 7A 6B C5 11 7A F9 F1 25 41 D0
Z-Wave Debug RCVD encryptedPacket: 00 71 05 00 00 00 FF 06 06 01 00 00 (decrypted)
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 11 00 04 00 17 0B 71 05 00 00 00 FF 06 06 01 00 00 FF
Z-Wave Debug . . requestAlarmSensorStatus: node 023, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 6, valueExt 6, classSubKeyExt 7100000606
Z-Wave received "ID Lock" status update is off
Z-Wave Debug RCVD nonceFetch: node 023
Z-Wave Debug SENT nonceReport: 01 11 00 13 17 0A 98 80 FB 7A 6B C5 11 7A F9 F1 25 42 D3
Z-Wave Debug RCVD encryptedPacket: 00 62 03 00 00 03 FE FE (decrypted)
Z-Wave Debug RCVD requestLockStatus1: 01 0D 00 04 00 17 07 62 03 00 00 03 FE FE FF
Z-Wave Debug . . requestLockStatus1: node 023, endpoint None, value 0
Z-Wave Debug RCVD nonceFetch: node 023
Z-Wave Debug SENT nonceReport: 01 11 00 13 17 0A 98 80 14 7E 2F 4D C3 98 A1 EA 25 43 86
Z-Wave Debug RCVD encryptedPacket: 00 71 05 00 00 00 FF 06 01 00 00 (decrypted)
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 17 0A 71 05 00 00 00 FF 06 01 00 00 FF
Z-Wave Debug . . requestAlarmSensorStatus: node 023, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 6, valueExt 1, classSubKeyExt 7100000601
Z-Wave received "ID Lock" status update is off
Z-Wave Debug RCVD nonceFetch: node 023
Z-Wave Debug SENT nonceReport: 01 11 00 13 17 0A 98 80 14 7E 2F 4D C3 98 A1 EA 25 44 81
Z-Wave Debug RCVD encryptedPacket: 00 62 03 FF 00 01 FE FE (decrypted)
Z-Wave Debug RCVD requestLockStatus1: 01 0D 00 04 00 17 07 62 03 FF 00 01 FE FE FF
Z-Wave Debug . . requestLockStatus1: node 023, endpoint None, value 255
Z-Wave received "ID Lock" status update is locked

That's actually an Indigo bug.

However I can work around it.


Sent from my iPhone using Tapatalk

Sorry, just realised you're not using my plugin.

The ZWave lock manager plugin allows you to trigger on lock/unlock and by which user it is. (1 or 2 for the ID Lock)


Sent from my iPhone using Tapatalk

Thanks! I'm looking forward to install your plugin.

However, I hope the bug in Indigo will be fixed

[matt (support)]

ID Lock is working very well, except from one ting: Indigo receives '"ID Lock" status update is off' instead of '"ID Lock" status update is unlocked' after I unlock the 'ID Lock'.

Try this updated version of the Z-Wave plugin and let me know if it works better. Unzip it and then double-click to install it. No re-sync needed – just try lock/unlocking the door and check the Event Log window.

Thanks a lot! Now it works very well!

Hi

I hade my ID-Lock 150 connected and working but hade problems with heavy battery use one the decive.
I draind the batteries after about 14 days.
After recommendation from ID-Lock I exclude it and removed the z-wave module for testing.
After that my problems started.
I have spent many hours trying to include it again but have failed, failed and failed..
Please help!
I made a new test today but still no success..
One thing I also did with recomendation from ID-Lock was to uppgrade the z-wave firmware on the z-wave module.

CPV1-Internet Connection Check - Connected to internet
Z-Wave Optimizing - stopped
Z-Wave Syncing - started for "142 - Keypad Door Lock"
Z-Wave Syncing - retrieved module neighbors list: 4, 5, 6, 7, 8, 10, 11, 15, 18, 19, 25, 26, 30, 31, 53, 54, 59, 68, 73, 84, 87, 92, 97, 98, 110, 111, 114, 125, 129, 130, 132, 133
Z-Wave Syncing - assigning return route to "142 - Keypad Door Lock"
Z-Wave Syncing - assigned return route
Z-Wave Syncing - retrieved manufacture and model names: Unknown - 0373, Keypad Door Lock - 00030001

Sep 16, 2020 at 10:52:42 PM
Z-Wave Error Syncing - failed
Z-Wave Error Timeout waiting for "142 - Keypad Door Lock". Module might be asleep, or is unreachable.