Koenkk
Onesti Products AS, EasyAccess doorlock , battery report
What happened?
After last update , the battery level was correctly changed from 200% to 100%, but it is stucked there, even if the doorlock warns of low battery....
What did you expect to happen?
Show a decline in battery level as time goes by...
How to reproduce it (minimal and precise)
Just look at the data each week
Zigbee2MQTT version
1.36.1-1
Adapter firmware version
Dont know
Adapter
Assistant SkyConnect
Setup
Addon Home Assistant
Debug log
No response
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days
Totally agree, I wonder why nobody that knows the code doesnt even leave a comment, is it the zigbee module or is it in the code....
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days
I finally bought a Nimly Connect module after seeing someone having success with it, and added it to my EasyAccess EasyFingerTouch door lock. It reports 37% battery, which sounds plausible:
I'll keep an eye on battery usage and report back if it's stuck.
My configuration:
- Sonoff Zigbee 3.0 USB Dongle Plus, model ZBDongle-E, running firmware version 8.0.2 (ember).
- zigbee2mqtt 1.42.0.
- zigbee-herdsman 2.1.9.
- Nimly Connect Zigbee module, firmware version 4.7.79, build date 20240625.
@stefancn: What is your configuration? Have you updated anything since creating this issue?
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days
I also have problem with a Nimly Touch Pro constantly reporting a battery level of 200% until the batteries are depleted.
The firmware version of my Connect module is 20220614.
The coordinator is a TI CC2652RB with zStack3x0.
I am currently running Z2M version 2.2.1, but this problem have been there for a year.
Too old firmware? Mine has working battery reporting.
Although, I changed batteries a week ago, when the level was about 12% (when it started beeping), and now the level is reported as 49%. That makes me think the battery levelig is wrongly getting divided by 2 somewhere.
Maybe, but the firmware cannot be updated, neither by me or by Nimly, so it is what it is. Unless I replace the module.
I have mailed with Nimly's support and they didn't recognize this issue.
I need to rule out if it is Z2M or the hardware/firmware that is to blame so that I can take the proper action.