Zigbee Motion Sensors (Silvercrest) stuck in "motion detected" very often / SkyConnect / ZHA

[FlorianWilk]

The problem

I have 6 silvercrest motion sensors (TY0202) running for some weeks now. At first everything seemed to work fine, no problems at all. Then one of the sensors began to get stuck in "motion detected" state. I tried setting this state manually in dev-tools but it gets back to "motion detected" after seconds. Of course I also replaced all batteries with new ones. Sometimes i just have to pull batteries out / put then in again to have "normal/no motion"-state. But sometimes this didn't work and i had to reset/pair the sensor to get it working again.

At first i thought it could be an issue of this particular sensor, so i replaced it with another (also silvercrest). Worked fine for some days, then also got stuck in "motion detected" state.

Then i thought it could be an issue of signal-strength (-74dBm) - although i was wondering why it worked really reliable with DETECTING motion but not "undetecting" it.

Today i have two other silvercrest sensors with this "motion detected" issue, which are about 2 meters away from a gateway (Philips Hue and NOUS PowerPlug). -64dBm, so i guess it's not an issue of bad signal-strength.

Of course i googled this issue and there were plenty of similar issues with other devices/setups, so i am not even sure if it is ZHA related only. But i couldn't find any working solution or reason for this. Some people wrote scripts to reset the state after a while manually, but 1. this is hacky 2. i tried this by setting the value manually and it alway gets back to "motion detected" after seconds. Also, of course, the sensors might be the reason for this issue, but i have friends running exact the same sensors (we ordered them together) without any issues and also these issues seem to occur with other sensors, too (google says). I don't think its a "general problem" with these sensors as i worked fine for quite a while and detecting motion works also very reliable.

I have not tried Z2Mqtt yet because overall i am really happy with my setup - except of this issue.

My setup: Skyconnect with ZHA (channel 25) 28 Zigbee devices containing: Gateways: 4 Zigbee Power Plugs (NOUS) and 1 Philips HUE directly connected to the Zigbee Mesh Sensors: 6 Silvercrest Motion Sensors (TY0202 Firmware: 0x00000043) some Smoke/Fire sensors and a lot (~20) cheap Temperature/HumiditySensors from AliExpress

everything except motion sensors seems to work fine.

I also have some Philips Hues connected to the HUE Bridge on channel 11, so the channels shouldn't interfere.

What version of Home Assistant Core has the issue?

core-2024.3.0

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

[home-assistant[bot]]

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)}}

[TheJulianJES]

Provide the diagnostics information for the device. It can be downloaded on the device page.

[FlorianWilk]

Provide the diagnostics information for the device. It can be downloaded on the device page.

Device 1: Motion Büro zha-99c752e509b9aa4258f9face9251b55d-_TZ1800_fcdjzz3s TY0202-e3d04e9fa589eb84cf4471baaeea0792.json Device 2: Motion Treppenhaus OG 2 zha-99c752e509b9aa4258f9face9251b55d-_TZ1800_fcdjzz3s TY0202-5673fc46b3564f648cdba9df74e68758.json

I see there are no logs in the diagnostics. Would it help you if i activated debug logging in ZHA for the next time when this error occurs?

[FlorianWilk]

Not sure if this helps, but i just noticed something unexplainable in the Logbook of on of these sensors.

"became unavailable, then detected motion?, then identify changed to March 10? and then Firmware tuned off" seems strange to me, what do you think?

Now the sensor is stuck in "motion detected" for about one hour now. The Device is about 2 Meters from the next Zigbee Gateway. One main difference to the systems of my friends (which are working without any issues) is, that i have more gateways (5). Could this lead to some kind of "race condition of events" or any other problems with motion sensors? All my other zigbee devices provide data without any problems.

[9agladioli]

Following this. I have connected two EZVIZ CS-T1C-A0-BG motion sensors to a Sonoff Zigbee 3.0 USB Dongle Plus. Connects no problem but will only stay in "off" state for 1 minute, then will trigger motion to state "on" with sensors not triggered.

I put the sensors on my table face down, so they detect nothing. They will not reset back to "off" by themselves. If I force it to "off" through states in dev tools then it stays at "off" for 1 minute then changes state back to "on" with no operation of the sensor, the sensors face down on table and no lights on sensor.

They work fine through the EZVIZ A3 hub, but there is no EZVIZ integration for the hub. There are two EZVIS door sensors (also previously used with A3 hub) and they work fine.

zha-000bbca375f3ccd7fec740b35fc5c056-EZVIZ CS-T1C-A0-BG-d3ebe4872f0b7a66881d57d391d36b47.json

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.