Hi Ted and thanks a ton for making this app, even though you don’t have access to the lock itself.
I have the IDlock 150 with the z-wave module and want to report the following.
With the latest stable version, editing the the ManifacturerID to include 883, everything seems to work. Battery reports, locked state, door state etc works, as does locking/unlocking from homey. Did never test any flows.
The development app, where you’ve added support for IdLock 150, does NOT work as it should. Reporting of locked state, door state, battary, heat alarm shows noting, and I’m not able to lock/unlock the door from homey.
However, changing settings under “device specific” from homey DOES work!
@Baron it looks like something went wrong during the inclusion of the doorlock based on de GitHub Development branch…
Some critical command classes are not shown in the command class overview; COMMAND_CLASS_DOOR_LOCK, COMMAND_CLASS_USER_CODE and COMMAND_CLASS_NOTIFICATION, which are essential in the drivers functioning… that these command classes are missing, will result in Invalid commandClass: DOOR_LOCK error message and that the change of state is not shown on the mobile card…
Can you try to remove, reset and re-include the doorlock based on the development branch?
Preferably with Homey at close distance of the door lock…
@TedTolboom you where totally right. Tried removing and re-adding the lock as a device a few times without success. But after removing it, and rebooting the lock (resetting batteries) it seemed to add fine again.
Maybe woring after rebooting the lock was just a coincidence, don’t know fore sure.
Working fine now. Do you need any type of debuglog? Have it up and running with the console right now anyway
Yes, I would say you can release it. Here is the debug log, opened the door with both code, rfid and service code while logging. There should also be a few failed attempts with rfid as well as with code.
yes, IDLock 150. I Don’t have the spare z-wave-module in my hands yet, but should get it in the coming days.
Could not figure out how to send private messages here on the new forum. But send me your address to me and I’ll see what I can do
Hi and thanks for the development of the IDLock app for Homey! Very appreciated.
I have a IDLock 101 (Man. ID 560) and are struggling with rapid battery drainage, think 4 days now since a fresh set of batteries was inserted and today the lock started giving low battery tones. Homey still reports 100%, but i think they are low as the lock is playing the tunes.
I see that there have been some problems with this before as the newest update has a fix that may fix the drainage. In my case, unfortunately it has not worked. Is there anything i can contribute with to help fix this … ?
Unfortunately I have to draw the conclusion that I’m not able to solve it from app side…
@juw2 already provided an extensive logging showing that the IDLock is requesting a security handshake, but apparently gets an incorrect response from Homey… so the IDLock will keep requesting it depleting the batteries rapidly.
Security handshakes are handled outside control of the app / device driver; in Homey’s core (for security reasons)…
Hence my conclusion that I’m not able to solve it (myself).
Athom is currently (as I type) looking into the issue to see if they can find a solution for it. If I have more info, I’ll provide an update in this topic.
Hi TedTolboom and thanks for your extensive reply!
I will need to pull my Zwave module then to conserve the batteries in the mean time. I noticed that Homey reports the lock as Battery: No … so i thought that might be the issue like Homey polls more when it thinks its a non battery device.
I’ll follow your thread closely and thanks for you efforts.
I had a similar issue with my 101. Battery drain rapidly. solved this with taking out the Zwave module. Wait some minutes then put it back in. This was actually exactly same with Vera plus controller. Worth a shot.
Taking out the Z-wave module and putting it back in the lock will force a reinitialization…
Athom is looking into the security handshake, because this might also be the cause of the failing motion sensors…