Zigbee Motion Sensor Firing every minute

[Martijnsx]

The problem

Since a week 2 of my 3 motion sensors keep firing every minute. I suspect this has something to do with home assistant itself.

The motion sensors are connected to ZHA by a Sonoff Zigbee 3.0 dongle.
The 2 motion sensors are RH3040 TUYATEC-zn9wyqtr. The other motion sensor which is not affected has the same hardware (from the outside) but has other serial numbers.

Last weekend the first began firing every minute. I took out the batteries (35% charge left) and put them back in. This did not work. Then i changed the batteries for charged ones (69% charge) and that stopped the firing.

A week later (now) the other motion sensor keeps firing every minute. This one has 40% charge. Will change batteries.

Because my home away alarm gets triggered when the motion sensor fires this has some unwanted side effects.

Does someone know what the problem might be? Is it HA related?

What version of Home Assistant Core has the issue?

core-2024.5.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[mib1185]

Hi @Martijnsx

At the moment this sounds like a request for support?
We use GitHub for tracking issues with Home Assistant Core itself, not for providing support.
If you are in need of support, you should try our Community Forum or join our Discord chat server.

Thanks! 👍

[Martijnsx]

Hi, Why do you think this is a support request? I suspect this has something to do with home assistant itself. Best regard Martijn Op zo 19 mei 2024 11:56 schreef Michael ***@***.***>:

…

Hi @Martijnsx <https://github.com/Martijnsx> At the moment this sounds like a request for support? We use GitHub for tracking issues with Home Assistant Core itself, not for providing support. If you are in need of support, you should try our Community Forum <https://community.home-assistant.io> or join our Discord chat server <https://www.home-assistant.io/join-chat>. Thanks! 👍 — Reply to this email directly, view it on GitHub <#117651 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXYSKIMZ4UOBZUMSABSJINDZDBZN7AVCNFSM6AAAAABH4QJ55KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGE3TKMZTGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[home-assistant]

Hey there @dmulcahey, @Adminiuga, @puddly, @TheJulianJES, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zha Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[mib1185]

I took out the batteries (35% charge left) and put them back in. This did not work. Then i changed the batteries for charged ones (69% charge) and that stopped the firing.

based on this, i think it is an issue with the device. If you would provide debug logs as described in the docs we might be able to check this further.

Does someone know what the problem might be? Is it HA related?

further this indicates on the first to be a request for support 😉

[Martijnsx]

Hi Michael, The motion sensors worked for many years without problems. The batteries have run down many times and i changed them after i got a low battery alarm. Now i did not get a low battery alarm. Also what are the odds that both suffer from the same problem almost at the same time? What should i do then? Best regards, Martijn Op zo 19 mei 2024 12:33 schreef Michael ***@***.***>:

…

I took out the batteries (35% charge left) and put them back in. This did not work. Then i changed the batteries for charged ones (69% charge) and that stopped the firing. based on this, i think it is an issue with the device. If you would provide debug logs as described in the docs <https://www.home-assistant.io/integrations/zha#reporting-issues> we might be able to check this further. Does someone know what the problem might be? Is it HA related? further this indicates on the first to be a request for support 😉 — Reply to this email directly, view it on GitHub <#117651 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXYSKIPQU2IEKXNT3WR3FQLZDB5WPAVCNFSM6AAAAABH4QJ55KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGE4DIOJXGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mib1185]

Hi @Martijnsx

first you could describe if you have lately updated HA in the questionable time frame? Further you could provide the requested debug logs, so we would be able to analyse your issue.

[iw1gfv]

I have the same issue with Ikea sensors.
Mine fires every 30 40 minutes.

[mib1185]

@iw1gfv do you mind do check #117651 (comment)? thx

[iw1gfv]

Hi
Looking at the register, i saw the "chekin event was fired" and after i have 1 or 2 movement.
I set the poll time to 0 and I don't have the issue anymore.