Sensors for certain Zigbee devices are not created after the 2023.11.1 update

[Murianwind]

The problem

After the 2023.11.1 update, sensors for certain Zigbee devices are not created. In Z2M, the sensor operates normally, but in HA, the sensor is not created and does not operate.

What version of Home Assistant Core has the issue?

core-2023.11.1

What was the last working version of Home Assistant Core?

core-2023.11.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

MQTT

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.mqtt.mixins
Source: components/mqtt/mixins.py:279
Integration: MQTT (documentation, issues)
First occurred: 05:51:40 (1 occurrences)
Last logged: 05:51:40

Error 'Entity category `config` is invalid' when processing MQTT discovery message topic: 'homeassistant/binary_sensor/0x8cf681fffe3e2688/card/config', message: '{'availability': [{'topic': 'zigbee2mqtt/bridge/state'}, {'topic': 'zigbee2mqtt/작업 기록/availability'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0x8cf681fffe3e2688'], 'manufacturer': 'Dawon DNS', 'model': 'IOT Card holder (KB-HD100-ZB)', 'name': '작업 기록'}, 'entity_category': 'config', 'icon': 'mdi:clipboard-check', 'json_attributes_topic': 'zigbee2mqtt/작업 기록', 'name': 'Card', 'object_id': '작업_기록_card', 'origin': {'name': 'Zigbee2MQTT', 'sw_version': '1.33.2', 'support_url': 'https://www.zigbee2mqtt.io'}, 'payload_off': False, 'payload_on': True, 'state_topic': 'zigbee2mqtt/작업 기록', 'unique_id': '0x8cf681fffe3e2688_card_zigbee2mqtt', 'value_template': '{{ value_json.card }}', 'platform': 'mqtt'}'

Additional information

No response

[elupus]

Needs to be fixed in z2m. Sensor entities are no longer allowed to be set as config category. #101471

[elupus]

Please upgrade z2m. Should be fixed there already. Reopen if still an issue.

[Murianwind]

The version of z2m is currently up to date.

[home-assistant]

Hey there @emontnemery, @jbouwh, mind taking a look at this issue as it has been labeled with an integration (mqtt) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of mqtt can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign mqtt Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

mqtt documentation
mqtt source
_{^{(message by IssueLinks)}}

[jbouwh]

Similar to #103192. This issue should be fixed in Z2M as has been made clear.

[elupus]

This specific issue is solved by 1.33.3 of z2m.

[jbouwh]

MQTT related from 2023.12.0 there will be a 3 months cooling down period. Unfortunate the patch did not make it into the patch release,

[jbouwh]

Closing this issue as the fixes have been merged and the milestone set.