›
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.
Closed Official Z-Wave SDK2

[App] ID Lock Z-wave - Main Discussion topic (v1.0.1)

24

Comments

  • Kissa78Kissa78 Member
    This is great. I will try to test this myself also. There is alslo comming a new updated version of the IDlock very soon. 
  • TedTolboomTedTolboom Member
    Gents, I've updated the app and driver based on the new ZwaveLockDevice meshdriver (based on the Danaloc driver):
    https://github.com/TedTolboom/no.IDLock

    Can someone test this and send me the debug logging; please remove and re-include the lock after updating the app.
    I'm currious if this resolves the issues with notifications / battery reports not being received.... which is a similar issue Danaloc has / had...
  • MbenzNoMbenzNo Member
    Brilliant!

    I have included my lock without any problem, but it does not give status of locked/Unlocked, and it does not respond to lock/unlock command from Homey.  Battery level are not reported. It does however react to settings like away mode.

    I will gladly provide any logfiles, but I need som basic instruction on how to get it....
  • johnniemalmjohnniemalm Member
    TedTolboom said:
    @johnniemalm your effort is appreciated....
    is it possible to contact me on Slack (athomcommunity.slack.com, invite via athom.com)?
    That is possible, let me know how and when, I have connected my 2 locks now and lock/unlock and status working,
  • TedTolboomTedTolboom Member
    MbenzNo said:
    Brilliant!

    I have included my lock without any problem, but it does not give status of locked/Unlocked, and it does not respond to lock/unlock command from Homey.  Battery level are not reported. It does however react to settings like away mode.

    I will gladly provide any logfiles, but I need som basic instruction on how to get it....
    @MbenzNo did you use the latest version ("Change to ZwaveLockDevice")? If it is not working correctly, can you try the previous version: https://github.com/TedTolboom/no.IDLock/tree/14baa97b8260c6da5455b4307deb2e784ae2291e

    For getting the debug logging, use "athom project --run" instead of "athom project --install"
    the debug logging will be visible in the terminal
    @johnniemalm your effort is appreciated....
    is it possible to contact me on Slack (athomcommunity.slack.com, invite via athom.com)?
    That is possible, let me know how and when, I have connected my 2 locks now and lock/unlock and status working,
    @johnniemalm you can request access via https://slack.athom.com/
  • MbenzNoMbenzNo Member
    Jepp, I was using the latest version. Uninstalled and installed latest version again with same result. Uninstalled and installed previous version, and it is working now!
    I can unlock/lock the lock, and it reports correct status when unlocked from the lock itself. Battery level is not reported.

  • TedTolboomTedTolboom Member
    MbenzNo said:
    Jepp, I was using the latest version. Uninstalled and installed latest version again with same result. Uninstalled and installed previous version, and it is working now!
    I can unlock/lock the lock, and it reports correct status when unlocked from the lock itself. Battery level is not reported.
    Thanks for testing; so to be installed version (for now) is: https://github.com/TedTolboom/no.IDLock/tree/14baa97b8260c6da5455b4307deb2e784ae2291e

    I'll update the master branch to this version during the weekend.
  • MbenzNoMbenzNo Member
    TedTolboom said:
    Thanks for testing; so to be installed version (for now) is: https://github.com/TedTolboom/no.IDLock/tree/14baa97b8260c6da5455b4307deb2e784ae2291e

    I'll update the master branch to this version during the weekend.
    Yes, this is the version that works.
  • MbenzNoMbenzNo Member
    Many of my very simple flows have recently been very slow. During investigating of this I discovered that there is constantly a lot of Z-Wave traffic to the device ID that is my IDLock.
    The slow flow problem could be caused by something completely different, like the Fibaro app, but I guess it should not bee like this anyway.
    Every fourth second it is Polling commandClassId 'DOOR_LOCK' for capabilityId 'locked'
  • MbenzNoMbenzNo Member
    I had to exclude the lock and uninstall the app. The constant polling of the lock is causing the batteries to drain fast.
    But one last observation is that when the batteries goes low, it actually reports battery status (Red and 1%)
    I will be away from home this week, but will be happy to do some more testing when I am back.

  • TedTolboomTedTolboom Member
    @MbenzNo thanks for the feedback.
    Compared to the 'old' Zwavedriver where the polling interval was set in seconds unit, it was reverted back to millisecond unit in the new meshdriver... 

    I've updated the app and driver for IDLock 101 based on the last working version and disabled the polling interval:
    https://github.com/TedTolboom/no.IDLock/tree/master
  • johnniemalmjohnniemalm Member
    MbenzNo said:
    I had to exclude the lock and uninstall the app. The constant polling of the lock is causing the batteries to drain fast.
    But one last observation is that when the batteries goes low, it actually reports battery status (Red and 1%)
    I will be away from home this week, but will be happy to do some more testing when I am back.

    TedTolboom said:
    @MbenzNo thanks for the feedback.
    Compared to the 'old' Zwavedriver where the polling interval was set in seconds unit, it was reverted back to millisecond unit in the new meshdriver... 

    I've updated the app and driver for IDLock 101 based on the last working version and disabled the polling interval:
    https://github.com/TedTolboom/no.IDLock/tree/master
    ok, thats why i hade to exchange battery this morning <span>:smile:</span>

    I have possibility to test to if you like, thanks for the effort 
  • Kissa78Kissa78 Member
    Hi. I have added my lock to my Homey now. That works great. But it wont lock or unlock. Nothing happens when i press the switch in Homey. Any suggestions?



  • TedTolboomTedTolboom Member
    Kissa78 said:
    Hi. I have added my lock to my Homey now. That works great. But it wont lock or unlock. Nothing happens when i press the switch in Homey. Any suggestions?
    @Kissa78 did you install the app and if so when did you download the app from Github?
    Can you share more info? e.g. Node information (Devices > device settings (wrench symbol) > node information)
  • Kissa78Kissa78 Member
    Hi. I downloaded again the last version you linked here. The lock is now working. In the App it shows locked/unlocked. But here is no labeling in the APP so hard to know what is unlocked or locked unless you know it. And there is no battery status. I just installed the new version on top of the earlier one. 





  • TedTolboomTedTolboom Member
    Kissa78 said:
    Hi. I downloaded again the last version you linked here. The lock is now working. In the App it shows locked/unlocked. But here is no labeling in the APP so hard to know what is unlocked or locked unless you know it. And there is no battery status. I just installed the new version on top of the earlier one. 
    Hi @Kissa78 good to hear that the lock is functioning.
    Within this driver I’m using the default lock capability which is also used by Danock; I will check with Athom if it’s possible to add a status message to this capability.

    Battery status not being updated is a known issue; under clarification with IDLock development.
  • joleriusjolerius Member
    I tried installing my lock today.. at first it seemed to went ok.. but after a while of adding, exchanging security key, gather manufacture info.. my homey says "no zwave device found"????

    This is really strange because I had it Smartthings without any problem at all

    And yes, I did a proper removal before
  • MbenzNoMbenzNo Member
    jolerius said:
    I tried installing my lock today.. at first it seemed to went ok.. but after a while of adding, exchanging security key, gather manufacture info.. my homey says "no zwave device found"????

    Bring Homey close to the lock while including It may help.


  • joleriusjolerius Member
    MbenzNo said:
    jolerius said:
    I tried installing my lock today.. at first it seemed to went ok.. but after a while of adding, exchanging security key, gather manufacture info.. my homey says "no zwave device found"????

    Bring Homey close to the lock while including It may help.


    I was close, really close. In fact on my last try I basically held Homey to the lock.. it have done same thing several times.

    But something seems to happen because if I try again right after it says that the lock is already added to a controller and that I should remove it first.

    So I remove it and tried adding it.. but still the same.. tried about 5-7 times with the same result
  • casedacaseda Member
    @jolerius reboot your homey, and try again
  • TedTolboomTedTolboom Member
    Gents,

    what is your opinion: is the basic operation of the IDLock based on the current app (https://github.com/TedTolboom/no.IDLock/tree/master) good (stable) enough to release to the app store?
  • joleriusjolerius Member
    TedTolboom said:
    Gents,

    what is your opinion: is the basic operation of the IDLock based on the current app (https://github.com/TedTolboom/no.IDLock/tree/master) good (stable) enough to release to the app store?
    Since I couldn't even add the lock, I don't think it's ready yet
  • TedTolboomTedTolboom Member
    jolerius said:
    Gents,

    what is your opinion: is the basic operation of the IDLock based on the current app (https://github.com/TedTolboom/no.IDLock/tree/master) good (stable) enough to release to the app store?
    Since I couldn't even add the lock, I don't think it's ready yet
    @jolerius can you take the following steps (with Homey in proximity of the smart lock), it might be duplicate steps already executed, but in this way we exclude a number of factors:
    1. Download and install latest version of the IDLock app: https://github.com/TedTolboom/no.IDLock/tree/master
    2. Replace the batteries in the IDLock
    3. Go to Settings > Z-wave > 'remove a Device' and follow the "Exclusion" steps as mentioned in the manual (page 2).
      Feedback should be "device successfully removed"
    4. Reset the IDLock as per "reset Device" steps in the manual (page 2)
    5. Disconnect Homey and move to close proximity of the smart lock
    6. Make sure that Homey is ready:
      - Check in Settings > apps that all apps are loaded (no rotating wheels behind the apps)
      - Check in Z-wave > stuff for geeks > 'state' that Z-wave is ready and queue count is 0
        {"zw_state":{"stats":{"processmanager":{"processQueue":0},"commands":{"commandsQueue":0}}
    7. Try re-including the IDLock
    8. If not successfull, please send me the Z-wave log; Settings > Z-wave > log (unfiltered).
  • joleriusjolerius Member
    The battery trick did it. Now it's included and I can lock/unlock from the app
  • joleriusjolerius Member
    And I can see lock status.. but is there anyway to see closed door status? I know there is that sensor. And what about the fire alarm built in?
  • TedTolboomTedTolboom Member
    @jolerius good to hear the pairing worked out fine!

    As explained above, I don't have the IDLock myself and build this app / driver based on the available information (manual) to provide basic operation (lock / unlock.

    Could you check when running the app in debug mode "athom project --run" and provide me the entire debug log when (un-)locking the device manually, with rfid and user code, to see if notification reports are now visible.

    Debug mode can be terminated by CTRL-C, and app installed back with "athom project --install"

    I'm in discussion with IDLock to see if we can find a solution to extend the driver to support more features, but that will require having access to an IDLock for debugging purpose.
  • johnniemalmjohnniemalm Member
    jolerius said:
    TedTolboom said:
    Gents,

    what is your opinion: is the basic operation of the IDLock based on the current app (https://github.com/TedTolboom/no.IDLock/tree/master) good (stable) enough to release to the app store?
    Since I couldn't even add the lock, I don't think it's ready yet
    The problem you have, have nothing with the app do to, you need to reset the lock, before try again, the problem is with the lock, I have the same problem before and then i hade HC2, reset the lock, remove batteri and remove and insert the Z-Wave module, and it will work for you
  • TedTolboomTedTolboom Member
    Gents, just had an idea to see if I can get the notifications status updates (e.g. locked by RF) working (ie. showing in the debug logging)

    Is someone able to install and test this branch:
    https://github.com/TedTolboom/no.IDLock/tree/reportListener_Scene

    Please check the app in debug mode "athom project --run" to see if notification reports are now visible while unlocking / locking (manually, by RF etc) and send me (or post here) the entire debug log.
  • MbenzNoMbenzNo Member
    Installed https://github.com/TedTolboom/no.IDLock/tree/reportListener_Scene

    Had some difficulties installing, but got the same problem after reverting to last version. Installed OK after I removed and installed the batteries in the lock (Same batteries)
    It would have been nice with some text on the icon/action card indicating if it is locked or unlocked. The door is locked when the slider is to the right as indicated on attached screenshot:



    Still no battery indication.
    Debug logfile attached:
  • MbenzNoMbenzNo Member
    The door hinge position Mode setting does not seem to do anything. The door/lock works the same regardless of setting.
This discussion has been closed.