I tried one last time (i have openhab on a big windows server for security, plex and more so alot of cable and stuff to have it 20 cm to the door)
What i did:
Removed all battery
Exluded one more time
Included
This made the idlock come up but not with secure (it had failed)
I tried to include one more time (without excluding) and another node was found (unknown) but secure completed.
It stayed unknown for 30 min so i deleted the first one restarted openhab and now it works
30 hours and sooo worth it, thanks for all the help and feedback!
So for anyone doing this it worth noting that it might take a few tries.
I believe the idlock sends some notification parameters (like code and rfid used). I havenât looked into it yet, but if you do please let me know if you are able to read it out!
Yes, i think personally it was the trick with taking out the battery after i had tried to many times that did it.
Will try to look more into that, i have talked with futurehome (in Norway) and they would be happy to help with documentation as i belive they do it in their hab solution.
Awesome. I think the magic dance has something to do with:
excluding
factory resetting
including (seeing unknown device)
deleting thing without excluding
including again.
One other note: For my lock, when the controller has marked it as failed & getting the âIs currently marked as failed by the controller!â message, the easiest way to reestablish comms is to do something on the device that will send a message TO the controller. In my case that was just opening the lock from the keypad.
Olav, did you read the battery and alarm correct? Battery is always 100 and i think its almost out of battery.
Also, do you door change the jingle? I think this is when battery is almost dead.
The jingle changes when the battery is low. I had problems with battery running out, but now it seems ok. Actually I have not checked if the battery indicator is correctâŠ
I have not gotten alarm to work yet, but havenât given too much effort into it either.
I was planning to look through the idlock zwave docs and see what I could get working, but havenât had the time yetâŠ
Ok, i hope it got drained before i manage to secure include it. Already changed 8 batteries 3 times now
With the alarm i see values, but dont think they are correct.
I have an id-lock and managed to get it securely included but the batteries drains in a couple of days
Anyone with a solution to this problem?
Almost forced to change back to manual lock
Did you get any further on this? Iâve been running all fine for some weeks now without any notable battery drain⊠Are you running a recent version of the dev binding? There was some discussion on battery with regards to usercodes in the «zwave security-thread» the last days, could be worth checking. If still a problem maybe some log files could be helpful for Chris to see if there is an issue with the bindingâŠ
Nope, no progress really. I had to remove the z-wave module since I had to change batteries every second day.
Iâll check the usercode issues to see if that gives me any hints, thanks!
Did some googling and found that it exists beta versions of z-wave modules that could have battery problems.
Havenât found a way of checking what version I have in my module or where to send it to get it upgraded.
Wrote a mail to idlock but havenât gotten any response yet.
btw Having major problems fitting the batteries, when I push in the last one the first one pops out.
Really annoying!!
Anyone else with that problem?
No change in the behavior for my lock. Still changing batteries every second/third day.
And still have major problems to insert them.
Changed parameter in âHABmin->Device Configurationâ for the lock to âPolling period: 12 Hoursâ.
Havenât seen any noticeable change though
I have written two emails do idlock asking questions but no response at all .
Iâve also written to âtrygghetsexpertenâ from which I bought the lock to see if I could get another or return the lock.
Letâs see what they say
Iâve not followed this thread at all, but it might be worth grabbing a debug log, and loading it into the log viewer to see how often the binding is communicating with the device - just in case thereâs something strange going on.
There should be very little communication, so if youâre seeing regular communication, then please send me the log (open a ticket on my website rather than posting logs with security here).
@TordYevl I took at look at the log you sent, and it looks ok. I guess it is from a restart as I see the binding request all the codes which does take quite a bit of time. This lock seems to have 190 of them and this takes a minute or so to complete. After this, thereâs only a few door status reports, so I donât think the binding isnât doing anything to impact the battery. These reports seem to be initiated by the door itself, so I guess someone opened itâŠ
The initialisation, and the downloading of the codes, will drain the battery a little, but unless youâre restarting many times per day, I doubt it will be an issue. I had a similar discussion elsewhere with someone who has a lock with 255 codes and he said it doesnât seem to impact battery life on his lock.
So, I guess letâs see what the supplier says, but I would say the binding probably isnât doing anything bad that would impact battery life (at least from what I see in this one log).
I was told by idlock that this lock uses 8 AA batterys a week (which corresponds with my observation). This document (sorry Iâd only got the norwegian version) should indicate that openhab then polls the lock every 30 sec ⊠The question then is : How can I change the polling intervals for the lock in openhab (im using 2.1 snapshot) ?
Clicking in PaperUI Configuration-Things-Idlock, and the the round blue icon with a pencil) throws me a ERROR: 500 - Internal Server Error âŠ
Im habmin I cannot seem to locate any usable settings for this ⊠Any eyeopening pointers would be welcome.
Polling period is normally a property on the device configuration of the thing in OH2. I am also not seeing this on my IDlock, but I think there are issues in the identification and discovery of the lock properties in OH2 Z-wave binding atm. I am running the latest snapshot of the Z-wave binding: OH2 Z-Wave refactoring and testing... and SECURITY.
If I understand correctly from the other thread, the device is being detected, so I would expect this to be available as an option. Do you have the Device Configuration selection in HABmin?
So according to ID Lock, their estimate would be around 3 months battery lifetime with a 30 minutes polling frequencyâŠ
Thatâs a bit short. Is it possible to customize that rate per device?
