New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stopped communicating with Homey and can't include anymore #27
Comments
I'v opened a support-case with my supplier of z-lock/zwave. They will run a few tests on a in-house Homey system of their own. |
Ok, my supplier and ID Lock have now replicated and tested my problem. They confirmed to me that the issue is related to Homey update v3.1.0. |
My Homey log from IDLock fail inclusion, attached |
Thanks for sharing... Just checking... Can you try the following:
And share the Z-wave log afterwards |
Quote from my post last night in Homey Community: When you say:
Do you mean the ZWave module or the ID Lock it self (or both)? |
Hi Ted
(6. Tried to include yet again, and get “status.already.added” in the app.) At the end i did a new factory reset of ID Lock ZWave and removed the module until next time (or fix)... Appreciate your effort trying to solve this 👍 |
Hi Ted |
Hi Ted I am having the same issue as above so im adding some additional things for you in term of log and so on. I took out a zwave log from when i tried to include and got same error like above. I hope it helps you Ted i also sent a app diag in a pm for you from when i actualy managed to add the unit but nothing worked in term of actualy talking to the unit or getting event data from the unit to the app. Homey v3.1.1 |
Same issue here: "No device found" |
I updated to 3.2.0 rc3 today and tried to include my lock. and something else changed. before i only got one page on how to include and then when i do that it failes with no device. but now.... I get two green Icon bruttons and where it want to first exclude a lock and secodly when i have done a exclusion it check mark the first green and then moves over to a inclusion text. the lock behaves a lite different on inclusion when i have done it i get one of those bell sounds on the lock that say ok it went good. but the app get a text that first flash by that i dont get to read and then a something went wrong error message when adding the device. |
Any chance that this is fixed with Homey v3.2 ? |
I just updated mine to 3.2.0. So i will try it again in a moment. It need a moment to get the z-wave network to settle first. |
Nah, didn't work here. Just get an error message saying something went wrong.... basically telling; you should have bought a propper hub.. |
Bump @TedTolboom |
There is a rc release for fixing the walli. lets see if it helps us in any way. |
The user prj_84 has in the Slack thread confirmed that he can add the lock in version 3.2.1-rc.2, but he writes: |
Guys, apologies for providing an update so late. I am lacking the free time recently to actively address all topics in a proper manner. Brief update on the inclusion issue with the IDLock based on a recent 3.x release. Based on the logging you provided, the cause of the problem of not being able to include the IDLock has been determined. I’m in contact with both Athom and IDLock to get this issue resolved, since it is outside of my control from app space. Likely, it will require an update from either one of them. |
Thanks for looking into it @TedTolboom. It's clarifying and sobering to know that both idlock and athom needs to do some work. |
Ok @TedTolboom Awaiting fix from Athom/IDLock then... |
I can confirm that it works now with rc7 version. Thx Ted for your work on this with Athom. |
And rc8! First attempt failed though. On second inclusion everything was
OK. Thanks TED!
tor. 9. jan. 2020, 18:30 skrev Marlark <notifications@github.com>:
… I can confirm that it works now with rc7 version. Thx Ted for your work on
this with Athom.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#27?email_source=notifications&email_token=AIRXYJLYW4CICRB7TBBOK7DQ45NKLA5CNFSM4JRACSZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIRDQVQ#issuecomment-572667990>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRXYJJS4BQOSKXG64JVYQ3Q45NKLANCNFSM4JRACSZA>
.
|
Added rc8 after inclusion. Everything stil work but i had it included on rc7. |
Homey issue fixed |
Getting the same problem as described in this thread, not being able to connect id lock 150 z-wave to Homey. Have Homey version 7.2.1 and latest version from the id lock updater installed. Are able to get the first green checkbox, but then an error message due to time out. Any tips? |
Please update the inclusion page to say that you need to do the inclusion steps on the idlock 2 times in a row. One time for each number icon in the top. |
Hi
My ID Lock 150 suddenly stopped communicating with Homey yesterday. I have tried all the tricks around, but can’t get it to work again. Then tried excluding it from Homey and re-include.
-Success excluding from Homey, but NO success including again.
What i’v tried so far:
-Reinstalling ID Lock App - Then tried to include again with NO success
-Restarting Homey - Then tried to include again with NO success
-Reset ID Lock 150 and 3 x reset ZWave module - Then tried to include again with NO success
To verify if the ZWave modul was working, i tried to add it to my other ZWave hub (FutureHome). I had no problem including the device here. Everything working fine, so i’v concluded that it cant be a faulty ZWave-modul.
Finally tried again several times more to include in Homey, but still no success.
Homey v3.1.0
Id lock v1.4.49
Z wave module 01B/v1.6
(Diagnostic:
f9c75256-a1fc-412b-aa58-58b267334479)
The text was updated successfully, but these errors were encountered: