Zemismart Zigbee PIR Motion sensor stays active and mostly sends active events

hey everyone, I recently bought some Zemismart curtain rails and impulse bought a zigbee Tuya PIR motion sensor from them as well.


All my other devices have been z-wave up til now and they all work fine, this is my first Zigbee device, inhind sight I should have checked the driver list.

So I was able to link the Zigbee device.
Data just reads

  • endpointId: 01
  • application: 40
  • model: TS0202
  • manufacturer: _TYZB01_jytabjkb

Most things seem to work , but I meanly get active events in in the logs, but since they never get an inactive HE doesn't react to it.
logs:
20:48:19.861 infoMotion is active
20:40:25.390 infoMotion is active
20:40:23.365 infoMotion is active
20:40:20.287 infoMotion is active
20:38:44.899 infoMotion is active
20:37:42.615 infoMotion is active
20:37:39.822 infoMotion is inactive

After some digging around it seems like this Motion detector is being used by other brands;
for Example the CR Smart Home TS0202,

And for example zigbee2mqtt having the same issue with it, they seem to reset the activity after x seconds.

Is there something similar I can do, with rules or a custom driver?

The Tuya made sensors I have only send active events and you need to reset them after the time out period (usually around 60 seconds) when they will send another event.
I modified a Xiaomi driver (which works the same way) to work with mine which you could try and see if it works.

1 Like

hey @at9 thanks for the quick reply.
On my first try, the motion sensor just stopped sending events all together.
Probably because fingerprint and clusters don't match up?
Whats the best approach here? Are there things I should try to change in the driver?

I'll try some more after work.

You need to see what the sensor sends on active adjust the driver to react to this.
My device sends a message starting with "catchall:" only for motion so that is what the driver looks for.

ok, after some testing , your driver needed more changes in the parsing to make it compatible with my device.
I stumbled on the following one

Decided to "borrow" it and change the clusters and info according to my device and it just worked fine. It might even work fine without the tweaks, I don't know.
I did have to tweak the configuration a bit. Now I have it working I might try to figure out what the other clusters do an play around with those.
In any case I have a working PIR motion sensor now.
Thanks for the help @at9 and thanks for the driver @muxa.

1 Like