[Bug] TypeError: Cannot read properties of undefined (reading 'getCharacteristic') about homebridge-z2m HOT 8 CLOSED

Previously the Coordinator was never created as it was marked as supported: false by the information provided by Zigbee2MQTT.

Since Zigbee2MQTT v1.35 it actually changed to supported: true, which caused data to be referenced for the Coordinator that is actually not supplied by Zigbee2MQTT.
That last part is fixed, but I did not do anything specific to get rid of any "Coordinator accessories" that might have been incorrectly created.

I would suggest to clean them by hand indeed, as indicated in a previous comment.

from homebridge-z2m.

Previously the Coordinator was never created as it was marked as supported: false by the information provided by Zigbee2MQTT.

Since Zigbee2MQTT v1.35 it actually changed to supported: true, which caused data to be referenced for the Coordinator that is actually not supplied by Zigbee2MQTT.

That last part is fixed, but I did not do anything specific to get rid of any "Coordinator accessories" that might have been incorrectly created.

I would suggest to clean them by hand indeed, as indicated in a previous comment.

Understood and thank you, this could be closed it seems

from homebridge-z2m.

Turns out that "removing the cached Coordinators" made it run again. Was that the fix for 1.9.3? Just curious to see if it's something I need to look out for until further notice, and I guess that would make it related to #794 after all.

from homebridge-z2m.

Turns out that "removing the cached Coordinators" made it run again. Was that the fix for 1.9.3? Just curious to see if it's something I need to look out for until further notice, and I guess that would make it related to #794 after all.

@yandy-r how do you removed cached coordinators ?

from homebridge-z2m.

Turns out that "removing the cached Coordinators" made it run again. Was that the fix for 1.9.3? Just curious to see if it's something I need to look out for until further notice, and I guess that would make it related to #794 after all.

@yandy-r how do you removed cached coordinators ?

Homebridge Settings -> Remove Single Cached Accessory (near the bottom) -> Then look fo the one you want to remove

from homebridge-z2m.

Turns out that "removing the cached Coordinators" made it run again. Was that the fix for 1.9.3? Just curious to see if it's something I need to look out for until further notice, and I guess that would make it related to #794 after all.

@yandy-r how do you removed cached coordinators ?

Homebridge Settings -> Remove Single Cached Accessory (near the bottom) -> Then look fo the one you want to remove

@yandy-r That's my error - how to know which accessory to remove ? - I don't see ID !

[1/4/2024, 3:23:34 PM] Loaded 21 cached accessories from cachedAccessories.0E4F3B3A4F53.

/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Accessory.js:1800
.getCharacteristic(Characteristic_1.Characteristic.Identify)
^
TypeError: Cannot read properties of undefined (reading 'getCharacteristic')
at Accessory._sideloadServices (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/dist/lib/Accessory.js:1800:13)
at Function.Accessory.deserialize (/var/lib/homebridge/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:2188:15)
at Function.deserialize (/var/lib/homebridge/node_modules/homebridge/src/platformAccessory.ts:172:33)
at /var/lib/homebridge/node_modules/homebridge/src/bridgeService.ts:240:34
at Array.map ()
at BridgeService.loadCachedPlatformAccessoriesFromDisk (/var/lib/homebridge/node_modules/homebridge/src/bridgeService.ts:239:58)
at ChildBridgeFork.startBridge (/var/lib/homebridge/node_modules/homebridge/src/childBridgeFork.ts:142:5)
[1/4/2024, 3:23:35 PM] [homebridge-z2m] Child bridge process ended

from homebridge-z2m.

@yandy-r ohh i figure it out - i removed Coordinator - i had 5 coordinators no idea why and i removed all of them.

from homebridge-z2m.

Yeah i updated Z2M to 1.35 before updating Homebridge add-on Z2M and it start crashes and creating this Coordinator Device , after updating to latest version of the add-on - Coordinator was still there and need to delete it manually to be able to start the add-on.

from homebridge-z2m.