rbswift

Something is publishing the "zigbee2mqtt/Leselampe-X" message. It's either your mqtt broker if zigbee2mqtt has told the broker to retain the message, or it's zigbee2mqtt itself publishing that message. A good...

Similar to #592 I just reported for HeaterCooler. Don't take your device offline while this happens as it will cause all the devices on your bridge to stop responding. Hopefully...

Where did you see `statusLowBatteryValue` documented or did you make it up? Try something like... ``` "getStatusLowBattery": { "topic": "security/sensors345/686604/status", "apply": "return (message == 'LOWBATT');" ```

Check your javascript in the apply setting will return an expected value. If you're using the `integerValue` setting then you might need to return something like `((message == 'LOWBATT') ?...

paste a copy of the relevant mqtt messages captured using `mosquitto_sub -t '#' -v`

I'd recommend dropping `integerValue` setting and just send boolean `true` / `false` values on more descriptive subjects instead of "status" because your current implementation cannot represent a status with both...

That config works fine for me. You may need to force close and reopen your Home app to see the change take effect immediately. That's an apple limitation I believe....

Me too. Works fine. The _Low Battery_ and _Status Tampered Yes_ elements in my screens above were produced by: `mosquitto_pub -t "security/sensors345/176014/status" -m "TAMPER"` or `mosquitto_pub -t "security/sensors345/176014/status" -m "LOWBATT"`...

I don't see anything obvious there that would cause a message to be sent on startup other than the power off message you have configured. I'd recommend removing `"retain": true`...

Thanks for replying. Yes in the example at step3 I am already inside geofence1. In my case geofence1 includes my whole street and the smaller geofence2 is my home (inside...