You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently noticed that the device settings are broken:
default_on_off_state
alarm_consumed_energy
alarm_power_max
alarm_voltage_max
alarm_voltage_min
consumed_energy_limit
voltage_max
voltage_min
power_max
Changing values causes an error: Cluster with name '64635' does not exist'
And an additional question, why is rms_current always equal to 28?
What did you expect to happen?
I think this error appeared after update 1.36.1 but I'm not sure. I thought that OpenHab had problems, but today I found out that the problem is in z2m.
How to reproduce it (minimal and precise)
Just run latest release with Perenio PEHPL0X devices.
Zigbee2MQTT version
1.40.1
Adapter firmware version
20240710
Adapter
SONOFF Zigbee 3.0 USB Dongle Plus (ZBDongle-P)
Setup
z2m standalone, node-v20.16.0-win-x64
Debug log
one of my device: perenio/pehpl0x/dev05
on boot: z2m: Failed to configure 'perenio/pehpl0x/dev05', attempt 1 (Error: Cluster with name '64635' does not exist at getClusterDefinition (r:\servers\nodejs\zigbee2mqtt\node_modules\zigbee-herdsman\src\zspec\zcl\utils.ts:166:15) at Object.getCluster (r:\servers\nodejs\zigbee2mqtt\node_modules\zigbee-herdsman\src\zspec\zcl\utils.ts:285:29) at Function.create (r:\servers\nodejs\zigbee2mqtt\node_modules\zigbee-herdsman\src\zspec\zcl\zclFrame.ts:52:31) at Endpoint.zclCommand (r:\servers\nodejs\zigbee2mqtt\node_modules\zigbee-herdsman\src\controller\model\endpoint.ts:892:33) at Endpoint.configureReporting (r:\servers\nodejs\zigbee2mqtt\node_modules\zigbee-herdsman\src\controller\model\endpoint.ts:648:20) at Object.configure (r:\servers\nodejs\zigbee2mqtt\node_modules\zigbee-herdsman-converters\src\devices\perenio.ts:363:28) at Configure.configure (r:\servers\nodejs\zigbee2mqtt\lib\extension\configure.ts:125:13) at EventEmitter.wrappedCallback (r:\servers\nodejs\zigbee2mqtt\lib\eventBus.ts:174:17))
on use: z2m: Publish 'set' 'default_on_off_state' to 'perenio/pehpl0x/dev06' failed: 'Error: Cluster with name '64635' does not exist'
The text was updated successfully, but these errors were encountered:
What happened?
I recently noticed that the device settings are broken:
Changing values causes an error: Cluster with name '64635' does not exist'
And an additional question, why is rms_current always equal to 28?
What did you expect to happen?
I think this error appeared after update 1.36.1 but I'm not sure. I thought that OpenHab had problems, but today I found out that the problem is in z2m.
How to reproduce it (minimal and precise)
Just run latest release with Perenio PEHPL0X devices.
Zigbee2MQTT version
1.40.1
Adapter firmware version
20240710
Adapter
SONOFF Zigbee 3.0 USB Dongle Plus (ZBDongle-P)
Setup
z2m standalone, node-v20.16.0-win-x64
Debug log
one of my device: perenio/pehpl0x/dev05
on boot:
z2m: Failed to configure 'perenio/pehpl0x/dev05', attempt 1 (Error: Cluster with name '64635' does not exist at getClusterDefinition (r:\servers\nodejs\zigbee2mqtt\node_modules\zigbee-herdsman\src\zspec\zcl\utils.ts:166:15) at Object.getCluster (r:\servers\nodejs\zigbee2mqtt\node_modules\zigbee-herdsman\src\zspec\zcl\utils.ts:285:29) at Function.create (r:\servers\nodejs\zigbee2mqtt\node_modules\zigbee-herdsman\src\zspec\zcl\zclFrame.ts:52:31) at Endpoint.zclCommand (r:\servers\nodejs\zigbee2mqtt\node_modules\zigbee-herdsman\src\controller\model\endpoint.ts:892:33) at Endpoint.configureReporting (r:\servers\nodejs\zigbee2mqtt\node_modules\zigbee-herdsman\src\controller\model\endpoint.ts:648:20) at Object.configure (r:\servers\nodejs\zigbee2mqtt\node_modules\zigbee-herdsman-converters\src\devices\perenio.ts:363:28) at Configure.configure (r:\servers\nodejs\zigbee2mqtt\lib\extension\configure.ts:125:13) at EventEmitter.wrappedCallback (r:\servers\nodejs\zigbee2mqtt\lib\eventBus.ts:174:17))
on use:
z2m: Publish 'set' 'default_on_off_state' to 'perenio/pehpl0x/dev06' failed: 'Error: Cluster with name '64635' does not exist'
The text was updated successfully, but these errors were encountered: