Z2m (zigbee2mqtt) - 2.5.1+ No longer sends auto discovery config message

anon31320818 · July 6, 2025, 6:20am

After upgrading yesterday to 2.5.1(-1?), I notice that the add-on no longer publishes device auto discovery messages which leads to all z2m devices as Unavailable and when viewing “More Info”, HASS advises to delete it because the MQTT integration is no longer supplying the device config.

Here is a link to a post I made on an issue in z2m repo. If you are also having this issue, maybe like the issue so it gets traction.

github.com/Koenkk/zigbee2mqtt

CK-BL702-AL-01 GU10 Bulb Offline

opened 08:10PM - 04 Jul 25 UTC

oerix

problem

### What happened? After updating to v2.5.1 ### What did you expect to happen? _No response_ ### How to reproduce _No response_ ### Zigbee2MQTT version 2.5.1 ### Adapter firmware version 0x84b4dbfffebc5f86 Revision: 8.0.2 [GA] ### Adapter SLZB-06M ### Setup Proxmox LXC ### Debug log ``` [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:06] debug: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:07] info: [2025-07-04 20:53:07] info: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:07] debug: [2025-07-04 20:53:08] debug: [2025-07-04 20:53:08] debug: [2025-07-04 20:53:08] debug: [2025-07-04 20:53:08] debug: [2025-07-04 20:53:08] debug: [2025-07-04 20:53:08] debug: [2025-07-04 20:53:10] debug: [2025-07-04 20:53:10] debug: [2025-07-04 20:53:10] debug: [2025-07-04 20:53:10] debug: [2025-07-04 20:53:10] debug: [2025-07-04 20:53:10] debug: ``` one of the Tuya GU10 bulbs stopped …work and shows as `offline`. It worked perfectly find prior to the update. it (minimal and precise) z2m: Received Zigbee message from 'Coordinator', type 'commandMoveToLevelWithOnOff', cluster 'genLevelCtrl', data '{"level":254,"transtime":10}' from endpoint 1 with groupID 2, ignoring s> z2m: Publishing 'set' 'transition' to 'Hallway Lights' z2m: Publishing 'set' 'color_temp' to 'Hallway Lights' zhc:light: Missing colorTempPhysicalMin and/or colorTempPhysicalMax for group 2! zh:controller:group: Command 2 lightingColorCtrl.moveToColorTemp({"colortemp":192,"transtime":10}) zh:ember: ~~~> [ZCL GROUP apsFrame={"profileId":260,"clusterId":768,"sourceEndpoint":1,"destinationEndpoint":255,"options":4416,"groupId":2,"sequence":0} header={"frameControl":{"reserved> zh:ember:ezsp: ===> [FRAME: ID=56:"SEND_MULTICAST" Seq=138 Len=32] zh:ember:uart:ash: ---> [FRAME type=DATA frmTx=2 frmRx=6](ackRx=2) zh:ember:uart:ash: <--- [FRAME type=DATA] zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=3](ackRx=2 frmTx=3) zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=3 frmNum=6](frmRx=6) Added to rxQueue zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=7](ackRx=3) zh:ember:ezsp: <=== [FRAME: ID=56:"SEND_MULTICAST" Seq=138 Len=10] zh:ember:ezsp: ~~~> [SENT type=MULTICAST apsSequence=23 messageTag=11 status=OK] zh:ember:uart:ash: <--- [FRAME type=DATA] zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=3](ackRx=3 frmTx=3) zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=3 frmNum=7](frmRx=7) Added to rxQueue zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=0](ackRx=3) zh:ember:ezsp: <=== [CBFRAME: ID=69:"INCOMING_MESSAGE_HANDLER" Seq=138 Len=43] zh:ember:ezsp: ezspIncomingMessageHandler: type=MULTICAST_LOOPBACK apsFrame={"profileId":260,"clusterId":768,"sourceEndpoint":1,"destinationEndpoint":255,"options":256,"groupId":2,"sequen> zh:controller: Received payload: clusterID=768, address=0, groupID=2, endpoint=1, destinationEndpoint=255, wasBroadcast=false, linkQuality=255, frame={"header":{"frameControl":{"frameType> zhc: Getting definitions for: yale.js,25,tuya.js,183,tuya.js,98,profalux.js,2,profalux.js,0,muller_licht.js,14,lidl.js,0,digi.js,0,bega.js,0 zhc: Candidates for 0x84b4dbfffebc5f86/undefined: ZYA-C4-MOD-S/Yale,SNTZ007/Tuya,IH-K009/Tuya,NSAV061/Profalux,NB102/Profalux,MLI-404011/MLI-404049/Müller Licht,HG06337/Lidl,XBee/Digi,700> z2m: Received Zigbee message from 'Coordinator', type 'commandMoveToColorTemp', cluster 'lightingColorCtrl', data '{"colortemp":192,"transtime":10}' from endpoint 1 with groupID 2, ignori> zhc:light: Missing colorTempPhysicalMin and/or colorTempPhysicalMax for group 2! z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hallway Light 1', payload '{"brightness":254,"color":{"h":48,"hue":48,"s":19,"saturation":19,"x":0.3397,"y":0.3472},"color_mode":"color_temp","c> z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Hallway Lights', payload '{"brightness":254,"color":{"h":48,"hue":48,"s":19,"saturation":19,"x":0.3397,"y":0.3472},"color_mode":"color_temp","co> zh:ember:uart:ash: <--- [FRAME type=DATA] zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=3](ackRx=3 frmTx=3) zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=3 frmNum=0](frmRx=0) Added to rxQueue zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=1](ackRx=3) zh:ember:ezsp: <=== [CBFRAME: ID=63:"MESSAGE_SENT_HANDLER" Seq=138 Len=26] zh:ember:ezsp: ezspMessageSentHandler: status=OK type=MULTICAST indexOrDestination=65533 apsFrame={"profileId":260,"clusterId":8,"sourceEndpoint":1,"destinationEndpoint":255,"options":256> zh:ember:uart:ash: <--- [FRAME type=DATA] zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=3](ackRx=3 frmTx=3) zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=3 frmNum=1](frmRx=1) Added to rxQueue zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=2](ackRx=3) zh:ember:ezsp: <=== [CBFRAME: ID=63:"MESSAGE_SENT_HANDLER" Seq=138 Len=26] zh:ember:ezsp: ezspMessageSentHandler: status=OK type=MULTICAST indexOrDestination=65533 apsFrame={"profileId":260,"clusterId":768,"sourceEndpoint":1,"destinationEndpoint":255,"options":2> zh:ember:uart:ash: <--- [FRAME type=DATA] zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=3](ackRx=3 frmTx=3) zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=3 frmNum=2](frmRx=2) Added to rxQueue zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=3](ackRx=3) zh:ember:ezsp: <=== [CBFRAME: ID=125:"INCOMING_MANY_TO_ONE_ROUTE_REQUEST_HANDLER" Seq=138 Len=16] zh:ember:ezsp: ezspIncomingManyToOneRouteRequestHandler: source=59955 longId=0x4c5bb3fffe2088f5 cost=1 zh:ember:uart:ash: <--- [FRAME type=DATA] zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=3](ackRx=3 frmTx=3) zh:ember:uart:ash: <--- [FRAME type=DATA ackNum=3 frmNum=3](frmRx=3) Added to rxQueue zh:ember:uart:ash: ---> [FRAME type=ACK frmRx=4](ackRx=3) zh:ember:ezsp: <=== [CBFRAME: ID=89:"INCOMING_ROUTE_RECORD_HANDLER" Seq=138 Len=18] zh:ember:ezsp: ezspIncomingRouteRecordHandler: source=50034 sourceEui=0xa4c138809031a5d1 lastHopLqi=180 lastHopRssi=-66 relayCount=0 relayList=

Here is a screenshot showing that z2m is receiving data from those devices and also shows z2m is not sending auto discovery messages to the hass config topic.

francisp · July 6, 2025, 11:18am

Could be related to No discovery messages are published to HomeAssistant after Birth message 'online' recieved to homeassistant/status · Issue #27458 · Koenkk/zigbee2mqtt · GitHub

anon31320818 · July 6, 2025, 6:55pm

Im getting a little farther in debugging the issue. It seems Z2M set HASS MQTT auto discovery off, but when I enable and ‘Save’ it throws an error and doesnt enable auto discovery:

When navigating to the HASS settings page

It’s turned off:

Enabled and Save

anon31320818 · July 6, 2025, 9:45pm

After several attempts at enabling, it finally enabled and is now ending discovery messages. No idea what the underlying issue is.