2024.1: Happy automating!

tom_l · January 3, 2024, 9:51pm

It’s an issue with zigbee2mqtt:

1.35.0 - Bridge Connection state entity parsing undefined state key

opened 10:40PM - 01 Jan 24 UTC

problem

### What happened? The Zigbee2Mqtt bridge entity `Connection state` is attempti…ng to parse the `state` key, which is not present in the state_topic defined for this entity. As a result, Home Assistant raises two exceptions: ``` Logger: homeassistant.helpers.template Source: helpers/template.py:2318 First occurred: 5:21:04 PM (1 occurrences) Last logged: 5:21:04 PM Template variable error: 'value_json' is undefined when rendering '{{ value_json.state }}' ``` ``` Logger: homeassistant.helpers.template Source: helpers/template.py:749 First occurred: 5:21:04 PM (1 occurrences) Last logged: 5:21:04 PM Error parsing value: 'value_json' is undefined (value: online, template: {{ value_json.state }}) ``` As seen below, the entity is looking for the `state` key in the topic `zigbee/bridge/state`: ```json4 device: hw_version: zStack3x0 20200925 identifiers: - zigbee2mqtt_bridge_0x00124b0021600270 manufacturer: Zigbee2MQTT model: Bridge name: Zigbee2MQTT Bridge sw_version: 1.35.0 device_class: connectivity entity_category: diagnostic name: Connection state object_id: zigbee2mqtt_bridge_connection_state origin: name: Zigbee2MQTT sw_version: 1.35.0 support_url: https://www.zigbee2mqtt.io payload_off: offline payload_on: online state_topic: zigbee/bridge/state unique_id: bridge_0x00124b0021600270_connection_state_zigbee value_template: '{{ value_json.state }}' platform: mqtt ``` However, Zigbee2MQTT publishes `online` / `offline` directly to the `zigbee/bridge/state` topic instead of within a `state` key at the `zigbee/bridge/state` topic. ``` Received 5:21:04 PM QoS: 0, Retained Payload: online ``` ### What did you expect to happen? _No response_ ### How to reproduce it (minimal and precise) _No response_ ### Zigbee2MQTT version 1.35.0 ### Adapter firmware version 20200925 ### Adapter Electrolama ### Debug log _No response_

If you don’t actually use it you can disable the setting legacy_availability_payload. Or put up with it until there’s a zigbee2mqtt update.

It doesn’t actually break anything.