Skip to content
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

LIDL HG06336 Door sensor N/A contact, battery_low, tamper and LQI #12649

Closed
seederp2p opened this issue May 30, 2022 · 11 comments
Closed

LIDL HG06336 Door sensor N/A contact, battery_low, tamper and LQI #12649

seederp2p opened this issue May 30, 2022 · 11 comments
Labels
problem Something isn't working stale Stale issues

Comments

@seederp2p
Copy link

seederp2p commented May 30, 2022

What happened?

I'm using LIDL HG06336 Door sensor with HA 2022.5.5 and Zigbee2mqtt 1.18.1-1.

My coordinator is SONOFF Zigbee 3.0 firmware version 20220219

The sensor itself shows firmware version: 2019.12.12

The device is listed but

What did you expect to happen?

It should show real data and not "N/A" on contact, battery_low, tamper and LQI

How to reproduce it (minimal and precise)

I can remove the device and try again with the same result.

Zigbee2MQTT version

1.18.1-1

Adapter firmware version

20220219

Adapter

SONOFF Zigbee 3.0 firmware version 20220219

@seederp2p seederp2p added the problem Something isn't working label May 30, 2022
@seederp2p
Copy link
Author

Update:

Using ZHA works perfectly.

So, maybe, this is a Z2M bug?

@Koenkk
Copy link
Owner

Koenkk commented May 31, 2022

You are using a very old z2m version, try updating to the latest and wait 24 hours so that the sensor can report its data.

If you are still on 1.18.1 check first point of https://github.com/Koenkk/zigbee2mqtt/releases/tag/1.19.0

@seederp2p
Copy link
Author

seederp2p commented May 31, 2022

Hi ! @Koenkk

Ok. So I fresh installed my Z2M.

Right now is running version 1.25.1-2

Re-added my door contact sensor and got the same results:

contact
N/A

battery_low
N/A

tamper
N/A

battery
Remaining battery in %
100%

linkquality
145lqi

Zigbee2MQTT:warn 2022-05-31 16:27:26: Device '0x680ae2fffe0a2c21' left the network
Zigbee2MQTT:error 2022-05-31 16:34:02: Failed to configure '0x680ae2fffe0a2c21', attempt 1 (Error: Bind 0x680ae2fffe0a2c21/1 genPowerCfg from '0x00124b0024c116c0/1' failed (AREQ - ZDO - bindRsp after 10000ms)
at Timeout._onTimeout (/app/node_modules/zigbee-herdsman/src/utils/waitress.ts:64:35)
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7))

@Koenkk
Copy link
Owner

Koenkk commented Jun 1, 2022

Failed to configure '0x680ae2fffe0a2c21', attempt 1 (Error: Bind explains why it doesn't work. Try to reconfigure the device by pressing yellow refresh icon on the frontend after your paired the device. Right before reconfiguring wakeup the device by triggering the contact sensor on it.

@seederp2p
Copy link
Author

Hi there! Tried that with same results.

ZHA Works fine though :(

@Koenkk
Copy link
Owner

Koenkk commented Jun 2, 2022

Did the configure suceed now?

@seederp2p
Copy link
Author

Nop.

It remains with N/A

@Koenkk
Copy link
Owner

Koenkk commented Jun 2, 2022

Can you provide the data/database.db entry of this device?

@seederp2p
Copy link
Author

Hello,

After upgrading Z2M to 1.25.2-1 and today, HA to 2022.6.1, I re-added the device.

It looked like the same but I tried to reconfigure it as your said previously.

For some reason it now works.

Anyway, how can I retrieve the data/database.db inside HA?

@Koenkk
Copy link
Owner

Koenkk commented Jun 3, 2022

@seederp2p then I guess it was a hickup with the configuring part. As long as the configure succeeds I expect the device to report the battery % correctly.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 4, 2022

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Jul 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working stale Stale issues
Projects
None yet
Development

No branches or pull requests

2 participants