Open MBRetrofit opened 9 months ago
I also have a similar issue, I thought it was the device loosing connection, but now it seems it was due to an update on ZB2MQTT. :( My device does an update less than once a day. Becomes useless. Tried to force availability on it, but the behavior remains the same:
'0xXXXXXXc946XXXXXX': friendly_name: Power Meter voltage_calibration: '' power_calibration: '' current_calibration: '' energy_calibration: '' availability: true
I have 2 errors every other minute in the logs and it seems it is always after the Power Meter sent its update. Not 100% sure, but it should be related:
debug 2024-01-22 18:30:33Received Zigbee message from 'Power Meter', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[8,226,0,6,157,0,0,202],"type":"Buffer"},"datatype":0,"dp":6}],"seq":53015}' from endpoint 1 with groupID 0
error 2024-01-22 18:30:33Exception while calling fromZigbee converter: tuya.getDataValue is not a function}
debug 2024-01-22 18:30:33TypeError: tuya.getDataValue is not a function at Object.convert (/app/data/extension/externally-loaded.js:18:36) at Receive.onDeviceMessage (/app/lib/extension/receive.ts:147:51) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:167:23) at EventEmitter.emit (node:events:529:35) at EventBus.emitDeviceMessage (/app/lib/eventBus.ts:101:22) at Controller.
(/app/lib/zigbee.ts:115:27) debug 2024-01-22 18:30:33Received Zigbee message from 'Power Meter', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,6,2,124],"type":"Buffer"},"datatype":2,"dp":1}],"seq":53271}' from endpoint 1 with groupID 0
error 2024-01-22 18:30:33Exception while calling fromZigbee converter: tuya.getDataValue is not a function}
debug 2024-01-22 18:30:33TypeError: tuya.getDataValue is not a function at Object.convert (/app/data/extension/externally-loaded.js:18:36) at Receive.onDeviceMessage (/app/lib/extension/receive.ts:147:51) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:167:23) at EventEmitter.emit (node:events:529:35) at EventBus.emitDeviceMessage (/app/lib/eventBus.ts:101:22) at Controller.
(/app/lib/zigbee.ts:115:27)
Not sure what to do with this, simply sharing it here so someone more knowledgeable could find it useful. Any way to import this specific adapter as it was previously without breaking anything else?
Thanks
Any workaround that could be used while this issue isn't fixed?
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days
I've installed ZB2MQTT [1.39.1 commit: [e132316] and it started working again. Still some errors (see below example) but I can get the power consumption and store it in FluxDB.
zhc: Failed to apply calibration to 'current': 'current_calibration' is not a number, got string ()
What happened?
After latest z2m update this device refresh data after 12 or more minutes. On previous version the refresh was a 2,5 minute and I was hoping for a solution to speed up this process.
What did you expect to happen?
As this product is quite nice, a new converter or OTA firmware update it will be much appreciated
How to reproduce it (minimal and precise)
I think that from latest z2m update this delay is based on device parameters change, as if the Power is almost constant the z2m doesn't listen and doesn't update the status.
Zigbee2MQTT version
1.35.0-1
Adapter firmware version
2023.12.4
Adapter
MatSee Plus DAC2161C _TZE204_lsanae15
Debug log
Zigbee2MQTT:debug 2024-01-02 14:34:24: Received Zigbee message from 'Main Fuse', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[8,239,0,11,102,0,2,11],"type":"Buffer"},"datatype":0,"dp":6}],"seq":58372}' from endpoint 1 with groupID 0 Zigbee2MQTT:info 2024-01-02 14:34:24: MQTT publish: topic 'zigbee2mqtt/Main Fuse', payload '{"clear_fault":"OFF","current":2.92,"energy":1284.79,"fault":null,"linkquality":168,"meter_id":"23290885","power":523,"state":"ON","threshold_1":"over_voltage_threshold","threshold_1_protection":"ON","threshold_1_value":270,"threshold_2":null,"threshold_2_protection":null,"threshold_2_value":0,"voltage":228.7}' Zigbee2MQTT:debug 2024-01-02 14:34:24: Received Zigbee message from 'Main Fuse', type 'commandDataReport', cluster 'manuSpecificTuya', data '{"dpValues":[{"data":{"data":[0,1,245,225],"type":"Buffer"},"datatype":2,"dp":1}],"seq":58628}' from endpoint 1 with groupID 0 Zigbee2MQTT:info 2024-01-02 14:34:24: MQTT publish: topic 'zigbee2mqtt/Main Fuse', payload '{"clear_fault":"OFF","current":2.92,"energy":1284.81,"fault":null,"linkquality":172,"meter_id":"23290885","power":523,"state":"ON","threshold_1":"over_voltage_threshold","threshold_1_protection":"ON","threshold_1_value":270,"threshold_2":null,"threshold_2_protection":null,"threshold_2_value":0,"voltage":228.7}'