TS0202 - false triggers

[manjh]

I have been using three ZIgbee PIR detectors, coming in on Zigbee as type TS0202.
Two of them work just great, but the third (and also oldest) tripped on regular intervals even when there was no movement.

So I ordered a new unit and installed that in place of the failing unit: works OK.

The failing unit has been in a closed box now for about a day, I left the battery in.
Since it was removed I can still see movement signals coming in at about 4-hour intervals.

Is this something I can fix? Is it a setting somewhere?

thanks in advance...

[waltervl]

Zigbee2MQTT or Zigbee for Domoticz plugin?
For Zigbee2MQTT you have to unpair the device or remove it from Zigbee22MQTT and also check MQTT retained messages to prevent it to be recreated in Domoticz.
For Zigbee for Domoticz plugin you have to remove the device from Domoticz and check what is left in the Z4D webUI and remove the device there too if it failed by first removal.

[manjh]

I know how to remove it, but am looking for a way to modify the setting so it stops sending fase triggers...

[waltervl]

These false triggers will probably come because the deletion/unpairing from the zigbee stick failed.
Or you remove the battery from the sensor in the box so it cannot send.....

[manjh]

Hmmmm... I doubt it. The device worked OK, except for the 4-hourly fase triggers.
But just to make sure, I will thoroughly remove the device from Z2D and Domoticz, and re-pair it.

[manjh]

Hmmmm... I doubt it. The device worked OK, except for the 4-hourly fase triggers.
But just to make sure, I will thoroughly remove the device from Z2D and Domoticz, and re-pair it.

[manjh]

OK, I thoroughly removed the device from both Z2D and Domoticz. Then reset it again and allowed it to pair.
After this I left it alone in a closed box in a cupboard, so no triggers should happen.
But sure enough, it trips at regular intervals.
Is there any further action I can take, apart from throwing the thing in the waste bin?

[heggink]

False triggers can happen for a number of reasons. Defective hardware, near empty battery, interference, aging hardware... I have thrown away devices that worked fine for years and, all of a sudden, gave caused triggers.

[manjh]

False triggers can happen for a number of reasons. Defective hardware, near empty battery, interference, aging hardware... I have thrown away devices that worked fine for years and, all of a sudden, gave caused triggers.

I'm not too worried about trhowing one out, theses sensors are about €5 or €6 a piece.
But the nature of the failure is interesting. I've kept it in a closed cardboard box for several days. The Domoticz log for the device shows "false" triggers at about 4 hour interval! So it is not random! It "feels" like a setting that causes the sensor to trip for some reason at the set interval.
So my question is really: is there someone who understands the firmware and can explain this?
Or is there a way to hard-reset the whole thing?

[waltervl]

I'm not too worried about trhowing one out, theses sensors are about €5 or €6 a piece.
But the nature of the failure is interesting. I've kept it in a closed paper for several days. The Domoticz log for the device shows "false" triggers at about 4 hour interval! So it is not random! It "feels" like a setting that causes the sensor to trip for some reason at the set interval.
So my question is really: is there someone who understands the firmware and can explain this?
Or is there a way to hard-reset the whole thing?

I am going to repeat myself:

These false triggers will probably come because the deletion/unpairing from the zigbee stick failed.
Or you remove the battery from the sensor in the box so it cannot send.....

So you have to be on the Zigbee coordinator. You did not tell how you connect your Zigbee stick with Domoticz? Zigbee2MQTT, Zigbee4Domoticz?
But you have to be sure that it is removed there too. Else the zigbee stick remembers the sensor.

[Kedi]

@waltervl It is not about pairing/removing etc.. The device triggers for no reason.
I think the device is defect, or like I found with similar devices from China origin: They might be perceptive for RF interference.
Is there something in your house that has a cycle of those 4 hours?

[habahabahaba]

Is it Tuya Motion&Lux sensor ? 2 in 1 ?

[waltervl]

It cannot trigger something if the coordinator is not listening to it. The Zigbee Coordinator (USB Stick or hub) should filter out those messages when it is not paired to the Coordinator.

But let us wait for manjh to respond on what zigbee integration he uses. Also curious to know what exactly those false triggers/messages are. In what application does he see this?

[manjh]

I use a Conbee stick, attached to a R-Pi 4 . I use ZIgbee2Domoticz.
After completely removing the device following the instructions for Z2D, I reset the device to connect it again. That works.
From that point on I kept the device in the box and left it alone.

I can then see the obviously false triggers in the log of the PIR device in Domotic, coming in at regular intervals of about 4 hours.
The triggers come in in a "normal" way, so the same as when the device actually detects movement..

[waltervl]

In the gui of Z4D do you see the Pir device in menu device? If so you have to remove it there too. Deleting the device from Domoticz sometimes does not completely rmove it from the coordinator. Then you have to remove it though the plugin Gui.

[manjh]

In the gui of Z4D do you see the Pir device in menu device? If so you have to remove it there too. Deleting the device from Domoticz sometimes does not completely rmove it from the coordinator. Then you have to remove it though the plugin Gui.

Yes. After going through the steps, at some point I can see the garbage can icon on the device in the GUI. After clicking that, it was removed.
After that I can see no trace of the device in both Domoticz and Z2D.
Is there a way to go into the Conbee device to check what's left there?

[waltervl]

I don know the conbee device, but the plugin interface should show this.