itavero/homebridge-z2m

[Bug] Failed to process MQTT message on 'zigbee2mqtt/bridge/devices'. (Maybe check the MQTT version?)

mrmaximas opened this issue · 10 comments

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

Today, most likely after another z2m update, I can't say for sure, the plugin restarts cyclically and multiplied an unsupported accessory named coordinator. i added coordinator's ieee address 0x00124b002a1aa3c4 to exceptions, it's help. i had to delete it from the accessory cache and had a hard time starting the plugin. of course I didn't change the mqtt version.

Related devices

No response

Related Devices

No response

Steps To Reproduce

No response

Expected behavior

No response

Device entry

No response

Status update

No response

Messages from this plugin

[12/27/2023, 4:49:47 AM] [homebridge-z2m] Restoring accessory: Living Room Main Light 6 (0xa4c1388a09cdf1f4)
[12/27/2023, 4:49:47 AM] [homebridge-z2m] Restoring accessory: 0x00158d00079c32a2 (0x00158d00079c32a2)
[12/27/2023, 4:49:47 AM] [homebridge-z2m] Restoring accessory: 0xa4c138e891447cb0 (0xa4c138e891447cb0)
[12/27/2023, 4:49:47 AM] [homebridge-z2m] Restoring accessory: Living Room Main Lights (1001)
[12/27/2023, 4:49:47 AM] [homebridge-z2m] Restoring accessory: Living Room Wall Lights (1002)
[12/27/2023, 4:49:47 AM] [homebridge-z2m] Restoring accessory: Living Room Bookshelf Lights (1003)
[12/27/2023, 4:49:47 AM] Registering accessory 'homebridge-airrohr.airrohr'
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Connected to MQTT server
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Zigbee2MQTT is ONLINE
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Using Zigbee2MQTT v1.34.0-dev (identified via zigbee2mqtt/bridge/info)
[12/27/2023, 4:49:48 AM] [homebridge-z2m] New accessory: Coordinator
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Failed to process MQTT message on 'zigbee2mqtt/bridge/devices'. (Maybe check the MQTT version?)
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Cannot read properties of null (reading 'vendor')
[12/27/2023, 4:49:48 AM] [homebridge-z2m] New accessory: Coordinator
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Failed to process MQTT message on 'zigbee2mqtt/bridge/devices'. (Maybe check the MQTT version?)
[12/27/2023, 4:49:48 AM] [homebridge-z2m] Cannot read properties of null (reading 'vendor')
[12/27/2023, 4:58:25 AM] [homebridge-z2m] New accessory: Coordinator

[12/27/2023, 4:58:25 AM] [homebridge-z2m] Failed to process MQTT message on 'zigbee2mqtt/bridge/devices'. (Maybe check the MQTT version?)

[12/27/2023, 4:58:25 AM] [homebridge-z2m] Cannot read properties of null (reading 'vendor')

[12/27/2023, 4:58:25 AM] [homebridge-z2m] New accessory: Coordinator

[12/27/2023, 4:58:25 AM] [homebridge-z2m] Failed to process MQTT message on 'zigbee2mqtt/bridge/devices'. (Maybe check the MQTT version?)

[12/27/2023, 4:58:25 AM] [homebridge-z2m] Cannot read properties of null (reading 'vendor')

[12/27/2023, 4:58:26 AM] [homebridge-z2m] New accessory: Coordinator

[12/27/2023, 4:58:26 AM] [homebridge-z2m] Failed to process MQTT message on 'zigbee2mqtt/bridge/devices'. (Maybe check the MQTT version?)

[12/27/2023, 4:58:26 AM] [homebridge-z2m] Cannot read properties of null (reading 'vendor')

This plugin

latest beta but on release same result

Homebridge

1.7.0

Zigbee2MQTT

1.34.0-dev commit: 265d280e

Homebridge Config UI X (if applicable)

latest

[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: Living Room Main Light 6 (0xa4c1388a09cdf1f4)
[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: 0x00158d00079c32a2 (0x00158d00079c32a2)
[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: 0xa4c138e891447cb0 (0xa4c138e891447cb0)
[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: Living Room Main Lights (1001)
[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: Living Room Wall Lights (1002)
[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: Living Room Bookshelf Lights (1003)
[12/27/2023, 5:06:19 AM] [homebridge-z2m] Restoring accessory: Coordinator (0x00124b002a1aa3c4)
TypeError: Cannot read properties of null (reading 'vendor')
at isDeviceDefinition (/usr/local/lib/node_modules/homebridge-z2m/src/z2mModels.ts:302:72)
at Zigbee2mqttAccessory.updateDeviceInformation (/usr/local/lib/node_modules/homebridge-z2m/src/platformAccessory.ts:418:30)
at new Zigbee2mqttAccessory (/usr/local/lib/node_modules/homebridge-z2m/src/platformAccessory.ts:98:10)
at Zigbee2mqttPlatform.addAccessory (/usr/local/lib/node_modules/homebridge-z2m/src/platform.ts:575:19)
at Zigbee2mqttPlatform.configureAccessory (/usr/local/lib/node_modules/homebridge-z2m/src/platform.ts:474:10)
at /usr/local/lib/node_modules/homebridge/src/bridgeService.ts:328:25
at Array.filter ()
at BridgeService.restoreCachedPlatformAccessories (/usr/local/lib/node_modules/homebridge/src/bridgeService.ts:288:69)
at ChildBridgeFork.startBridge (/usr/local/lib/node_modules/homebridge/src/childBridgeFork.ts:186:24)

I'm not running dev myself, just the 1.34.0 release of Zigbee2MQTT and I'm not experiencing this.
Can you check that using the actual released version solves this?

Also, can you share the contents of the MQTT message published to zigbee2mqtt/bridge/devices ?

I'm not running dev myself, just the 1.34.0 release of Zigbee2MQTT and I'm not experiencing this. Can you check that using the actual released version solves this?

Also, can you share the contents of the MQTT message published to zigbee2mqtt/bridge/devices ?

copypaste.txt

I'm running into the same (had been working fine for some time) on both -dev and non-dev latest branch. I am running on docker as well, this just started today.

I'm running into the same (had been working fine for some time) on both -dev and non-dev latest branch. I am running on docker as well, this just started today.

removing the cached accessory helped and the plugin started, though the original error is weird

copypaste.txt

Unfortunately the contents of that file seems to be incomplete. It's supposed to be a JSON, but when I try to format it, it's missing a part at the end.

Seems that I have implemented this check incorrectly.
It also seems that there are now (e.g. starting the latest Zigbee2MQTT release) devices that do not contain a vendor.

If someone can share the entries from zigbee2mqtt/bridge/devices that do not contain a vendor, that would be great. Not sure when I'll have time to patch this though, but I do want to make sure that there's no other keys missing/optional now.

Seems that I have implemented this check incorrectly. It also seems that there are now (e.g. starting the latest Zigbee2MQTT release) devices that do not contain a vendor.

If someone can share the entries from zigbee2mqtt/bridge/devices that do not contain a vendor, that would be great. Not sure when I'll have time to patch this though, but I do want to make sure that there's no other keys missing/optional now.

https://drive.google.com/file/d/1W02wXoL2mWNjZCNlTeapq-Jpllg0hJiu/view?usp=sharing

Closing this issue. Let's continue in #794