ZMS-102 Tuya status always on occupied

[deef88]

What happened?

I installed 2 ZMS-102 PIR sensors, but noticed that the occupied status is always on status TRUE.

What did you expect to happen?

After xxx seconds the status will switch to false (in case there isn't any motion.

How to reproduce it (minimal and precise)

Tried a few times and days always the same issue.

Zigbee2MQTT version

1.33.0

Adapter firmware version

20211217

Adapter

zStack3x0

Debug log

No response

[Anashost]

Kinda same issue with this sensor, seems unstable sometimes it won't clear and sometimes it stuck at occupied, and sometimes there's long delay.

• Model ZMS-102
• Vendor TuYa
• Device type EndDevice
• Zigbee Model TS0202
• Zigbee Manufacturer _TZ3000_msl6wxk9
• Description Motion sensor
• Support status Supported

This sensor looks the same as other tuya pir sensors i have, both working perfectly:

• TuYa IH012-RT01 _TZ3000_6ygjfyll
• TuYa 809WZT _TZ3040_bb6xaihh

[MoLiNaSa]

same issue here PIR sensor model ZMS-102 or manufacturer _TZ3000_msl6wxk9 was working well with some version < 1.28 under OpenHab (not sure which version) upgrade tool for zigbee2mqtt in OpenHab failed then PIR sensor didn't work anymore, after pairing occupancy remained TRUE so I installed manual extra Zigbee2MQTT server which has latest 1.33.1, behaving did not change device can be paired successfully, but then occupancy remains TRUE removing the device without force it starts to blink, connection seems to work, and re-pairs the linkquality is getting updated, keep_time and sensitivity can be adjusted, but occupancy stays TRUE even following the manual for troubleshooting issue with similar model did not help: https://www.zigbee2mqtt.io/devices/IH012-RT01.html

[Anashost]

@MoLiNaSa I've got mine to work better with changing the placement of my coordinator (sonoff model - P), i put it closer, higher and i had a usb 3.0 cable close to it, so it may caused some interference. It seems like this sensors has very bad signal which may cause this issue, 100% speculation here tho.

https://www.zigbee2mqtt.io/devices/IH012-RT01.html

The other model you mentioned here is one of a sensors i have (looks the same with blue lighting), which i consider to be one of the best small PIR tuya has, it works very very well.

[MoLiNaSa]

I can change values of keep_time and sensitivity compined with a movement shortly after, that means the trigger is recognized. Even after the set of keep_time when occupancy should go to FALSE a changed value of sensitivity is synchronized. Also when trigger for occupancy should be there the linkquality is updated, just the occupancy value is frozen

[Anashost]

just the occupancy value is frozen

Yes that was my issue too. This sensor may get better with some tweaks from the zigbee2mqtt devs. Try to mention them here, someone may help.

[MoLiNaSa]

simple things, big issues: after the device was reconnected for 100 times (at least it feels like), the battery showed for the first time a value not 100% so changing the battery with a new one makes life a lot easier devices is running smooth like it should

[jonathh21]

I've got a few of these and seem to have issues with them from time to time.

I currently have 2 of them in boxes and one report's ghosts the other doesn't.

I noticed that the battery was low (both in terms of voltage and percentage) on ghoater so I have switched it out for a Duracell one, we'll see if it helps.

I am particularly aware of this following well documented voltage issues with IKEA VALLHORN pirs.

[jonathh21]

Well it helped or rather the device was more reliable until today.

Today it has been stuck on 'occupied' for hours on 2 separate occasions.

Also, after I put in a brand new Duracell battery, the voltage and battery percentage never updated.

I am phasing in aqara sensors which seem more reliable..

Shame, I've got loads of these and the dome pirs - but what use is an unreliable PIR.

[xelemorf]

has been stuck on 'occupied' for hours on 2 separate occasions.

Also, after I put in a brand new Duracell battery, the voltage and battery percentage never updated.

I am phasing in aqara sensors wh

You might regret Aqara/Xiaomi (they're all Lumi actually) sensors on the long run (as do I), those devices are the most stubborn I have ever found straight up refusing to pair with anything except aqara routers. Even refusing to pair with their own smart plugs, accepting just smart wall switches in my case, won't pair to sonoff dongle-e routers or sonoff dongle-p coordinator, not to mention also refusing to pair any TuYa device (or in some case the'll pair if battery was removed but will drop off very quickly). And for the last my favorite, when pairing they tend to dissapear from Z2M inventory never joining back so you'll need to keep a tight record of your stuff, as they vanish.

However if you go that route, pairing can take multiple tries including battery removal and reinsert.

[dCypherNx]

Anyone know if it's possible to clear status sending a command to mqtt topic? In my case I know that if the sensor say it's occupied for more than 10 minutes it's a false positive, and I may clear it manually

[xelemorf]

Recently just stumbled upon a page on z2m device compatibility list for a very similar device which seems to work on all motion sensors having the same issue, the described method helped me to fix occupancy stuck issue, added a note into it aswell:

Troubleshooting: Occupancy stays on (or device "last seen" does not update): 

If the occupancy state stays on despite a lack of movement and regularly sent messages, it needs to be repaired. This can happen, e.g., when the power is interrupted by a battery change. 

1.    Remove from Zigbee2MQTT without force removal (this is the main point not to force). Device should start blinking upon successful removal (it might take some time to remove, trigger motion or power cycle if it's taking several minutes and then retry)
2.    Remove battery, wait a few seconds, reinsert. 
3.    Execute normal pairing procedure. 

Repairing without removal or power cut does not fix this issue. 
Note: If the above fails, retry a couple of times, or pair it with a TuYa plug / router.

Based on this article:
https://www.zigbee2mqtt.io/devices/IH012-RT01

[github-actions[bot]]

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