David Miller

> Just wondering, @arachnetech, during your test, did you also have status messages being published? (i.e. the `getOn` part of the config). > > Users are reporting similar issues on...

Just had another attempt at reproducing this, this time with a bit of fake test code which responds to a setOn message with a corresponding getOn message, as @itavero suggested...

Actually, looking at the logs originally provided, this might be the same... ``` [24/01/2022, 08:38:02] [Escalier] Publishing MQTT: zigbee2mqtt/boutonentree2/right/set = ON [24/01/2022, 08:38:04] [Escalier] Received MQTT: zigbee2mqtt/boutonentree2 = {"action":null,"last_seen":"2022-01-24T07:38:04.730Z","linkquality":61,"operation_mode_left":null,"operation_mode_right":null,"state_left":"OFF","state_right":"OFF"} [24/01/2022,...

I think returning null or undefined might work.

Thanks. I should fix the crash on null.

`"setActive": ""`

The TV support in mqttthing was added by @tobekas, and I haven't used it personally. Looking at the documentation (https://github.com/arachnetech/homebridge-mqttthing/blob/master/docs/Accessories.md#television), you can switch inputs but not much else. I'm not...

Good spot, thanks.

Sounds odd. Are you able to provider your accessory configuration and an example MQTT message which triggers this error?

Thanks! Silly error: default airPressure value (0) was invalid, and so caused that warning. Should be fixed in 1.1.38.