This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
The Homey Community has been moved to https://community.athom.com.
This forum is now read-only for archive purposes.
Closed Official Z-Wave SDK2
[App] ID Lock Z-wave - Main Discussion topic (v1.0.1)
This discussion has been closed.
Comments
When away mode is enabled, the inside button on the lock is disabled. Lock still works with code or remote/app.
The log file shows the notification reports... showing manual and keypad (un)locking, which could be used to send notifications to e.g. a mobile.
could you do three additional tests:
1) Can you check with this version, if the IDlock indeed reports (in the debug log) wether the door itself is open or closed??
2) remove Homey's ID (1) from association group and check if Notification reports are still showing up in the debug log
3) run the previous version of the app (athom project --run) and add Homey's ID (1) to association group 2 and check it the Notification reports are still showing up in the debug log.
On the battery reports;
the device is not announcing itself as battery device; so I don't expect it to start reporting:
On the state;
I am currently using the default door_lock capability... which also the Danalock app is using.
It is be possible to make (a seperate or the device) icon being black when locked and grey when unlocked...
I will ask Athom if it is possible to change icons based on a state: e.g. open lock when unlocked, closed lock when locked... and same for door if the IDlock reports also this state
Anyway, I am very thankful for Your work in making this app @TedTolboom !
1) Logfile first showing door left open (opened by inside button), and then door closed.
2) When Homey is removed from association group, there is no activity in the log when the lock is operated.
3) have not tested this yet. Do I have to uninstall latest app and exclude/include the lock again to do this test?
on 3) no, you can simple use “Athom project —run” from the folder where a different version is in over the previous version. In this case no need to de-install the app or to exclude and include the device.
Once you’re done, you can quite the debug mode (CTRL-c) and install the new version with “Athom project —install”
On the slack channel: you can request access to the Homey community via slack.athom.com.
When you are only, I’ll send you an invite for the beta channel.
Difference between current version and the next one is for the most part firmware/software capabilities.
Current version is probably not possible to upgrade.
i m german. So until they won’t Release it here the Risk is to high that it doesn‘t fit.
I am searching for a zwave lock. Danalock and nuki seem to be Slow and loud...
But saw this thread now, if you think this will work good with homey in the end I'll buy this right away and assist with what ever I can. I'm a quite incompetent programmer to be honest, but can contribute with beta testing, troubleshooting, donations, script kiddie programming.
I expect to have some time in two weeks from now to add the additional features (notifications and status) for the IDLock...
Please contact me on slack if you are willing to test this update.
Thanks to all who contributed in testing this app!
To keep the history, I requested the moderators to merge the old discussion topic into this new topic.
Let me know if I can be of any assistance!
BTW, can I donate a beer or so somehow?
https://apps.athom.com/app/no.idlock
@larza the updated app has a dedicated icon for door lock state and above link provides also the answer to your remaining questions
Is there a scheduled support of ID Lock 150 around the corner?
I got homey and the Idlock 150 with z-wave. Anyone who can add the support? I will gladly donate 50EUR.
So in the meant I will need your support in getting the required information.... Can you support here?
First step would be to get the ID’s of the 150. Can you included the 150 to Homey through the generic ‘add a Z-wave device’ option?
I should be added as a generic Z-wave device... can you post a screenshot of the ID info shown at devices > wrench symbol > device information?
Under download you have info about the z-wave and all the settings possible for the lock.
Reason to ask for the product ID’s from a retail product, is that it appears (based on above link) that ID lock re-used a product ID and product Type ID of an older version (of this one: https://products.z-wavealliance.org/products/1512)
Those should be a unique combination, but they appear not to be unique. Since manufacturers tend to make minor changes after certification, I always verify (myself) the ID’s as retrieved by Homey...
But since the combination was already known... it is already available in the ID Lock app, linked to the ID Lock 101 driver..
You can try to include the 150 based on this driver; majority is should work.
if someone would be able to run IDLock app (installed via CLI) with an included 150 in debug mode (Athom app run) and post the command class overview of the 150 here in the forum, I would greatly appreciate it. Again a verification of the command class versions... ;-P
bumped my head too many times trusting the provided documentation
Thank you for your help with Id lock 150. Here is the screen shot. Anything more I can help with?
https://products.z-wavealliance.org/products/2780
but apperantly they did change the manufacturers ID to 883 (instead of 560 for the 101)... which typically stays the same per vendor.
but that also explains why the device is included as an Unknown Z-wave device.
I will need to create a new driver for the 150; likely a duplicate of the 101. But first opportunity will be when I’m back from Norway (2 weeks from now)..
If someone with experience in installing an app trough the command line, is willing to help, I could explain how to make the changes to test the 150 with the 101 driver (and settings)...
Just let me know.