On rare occasions, a sensor is left in triggered status. I guess this can happen if a sensor is tripped and when untripping it faces a communication timeout. So sensor value is not tripped, but Homey still think it is. If I’m still in the house, I can just manually tripp the sensor and it will most likely untripp as it should. But how can I remotely manipulate the trip status of a sensor when I’m not home and on the go?
You could try to send a “basic on/off” command or a “test frame” to the sensor via the developers page. No idea if that works, you never know. It might trigger a wake-up or refresh of the values.
Gr8 tip! However, I don’t think I need to manipulate the sensor. It’s the sensors state in Homey that need to be manipulated.
That is only valid for on/off status of witches etc. You can;t change a sensor’s value.
At least, as far as i know and to what my developer page shows.
The sensor state in Home is manipulated by the sensor’s reports. So if you trigger or wake-up the sensor (manually of maybe via the developer’s page), the current values will be sent to Homey.
For instance: if your tamper alarm is “stuck” in YES, triggering the alarm manually will send a new YES command, followed by the NO command after the value specified with the “cancel alarm after” setting.
Also most battery powered devices does not have a very frequent wake up interval, so I really can’t consider that to be an option. Also, manually triggering a sensor when away is not really an option
I had this issue the other day again:
Is HomeyScript able to manipulate sensor states?