Koenkk / zigbee2mqtt

Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨
https://www.zigbee2mqtt.io
GNU General Public License v3.0
11.78k stars 1.64k forks source link

Colorock CR-MNZ1 Zigbee version with energy monitor (UNREPORTABLE_ATTRIBUTE, consumption data is null) #22808

Open nifelin123 opened 3 months ago

nifelin123 commented 3 months ago

What happened?

the data of the energy monitor is not pulled up. if you go to the developer console in the haElectricalMeasurement cluster and select the correct attributes there, the data can be read. There is also an error attached below (Status 'UNREPORTABLE_ATTRIBUTE') in the vine. Tried the converter from tuya.ts repository it didn't help. What else do you recommend to do?

10 20 30

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.37.1

Adapter firmware version

20230507

Adapter

CC2652P

Setup

Intel NUC

Debug log

Failed to configure '0x70b3d52b600b9d7a', attempt 1 (Error: ZCL command 0x70b3d52b600b9d7a/1 haElectricalMeasurement.configReport([{"attribute":"rmsVoltage","minimumReportInterval":5,"maximumReportInterval":3600,"reportableChange":5}], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNREPORTABLE_ATTRIBUTE') at Endpoint.checkStatus (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:315:28) at Endpoint.zclCommand (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:770:26) at Endpoint.configureReporting (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:556:9) at Object.rmsVoltage (/app/node_modules/zigbee-herdsman-converters/src/lib/reporting.ts:224:5) at Object.configure (/app/node_modules/zigbee-herdsman-converters/src/devices/tuya.ts:2943:13) at Configure.configure (/app/lib/extension/configure.ts:121:13) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17))

alexps70 commented 2 months ago

I have the same device - no data on voltage/current/power

andregoncalvespires commented 2 months ago

The same here. Any developments?

Koenkk commented 2 months ago

In the reporting tab, do you get an UNREPORTABLE_ATTRIBUTE error for all these attributes?

If it gives an error for all we need to poll the attributes:

Could you check if the issue is fixed with the following external converter:

nifelin123 commented 2 months ago

In the reporting tab, do you get an UNREPORTABLE_ATTRIBUTE error for all these attributes?

  • Cluster: haElectricalMeasurement, attributes rmsVoltage, rmsCurrent, activePower
  • Cluster: seMetering, attributes: currentSummDelivered

If it gives an error for all we need to poll the attributes:

Could you check if the issue is fixed with the following external converter:

  • save this as file next to configuration.yaml as ext_converter.js
  • add it to configuration.yaml:
external_converters:
  - ext_converter.js
  • start z2m, check if issue is fixed

The situation has changed, now only energy data is NULL 3

lpt2007 commented 1 month ago

Hi,

@nifelin123 solution works, but readings not correct?

I connected only input to my Colorock CR-MNZ1 Zigbee version and device shows me those readings? 18 07 2024_11 56 56_REC

Any idea?

andregoncalvespires commented 1 month ago

We are close to a solution. The current reported by the device is in mA. Confirming the consumed energy reported in seMetering.currentSummDelivered

Redram49RUS commented 1 month ago

Could you check if the issue is fixed with the following external converter:

save this as file next to configuration.yaml as ext_converter.js add it to configuration.yaml: external_converters:

Have this error: Integration error: external_converters - Integration 'external_converters' not found.

Koenkk commented 1 month ago

@Redram49RUS you have to add it to your z2m configuration.yaml, not the home assistant one

lpt2007 commented 1 month ago

Hi,

I try external converter. Now I get some values on W / A / V. Current not show correctly, probably number is in mA not A as shown. Energy still Null?

here i screenshot: 20 07 2024_18 10 45_REC

Redram49RUS commented 1 month ago

@Redram49RUS you have to add it to your z2m configuration.yaml, not the home assistant one

Thanks, it worked. The energy remained "Null". The current, as already said, is overestimated - it seems that it is indicated in mA.

Koenkk commented 1 month ago

I've updated the external converter, could you check it again after re-configuring the device by pressing the yellow refresh icon on the device page?

nifelin123 commented 1 month ago

I've updated the external converter, could you check it again after re-configuring the device by pressing the yellow refresh icon on the device page?

ok 10 min.

nifelin123 commented 1 month ago

1 2

I've updated the external converter, could you check it again after re-configuring the device by pressing the yellow refresh icon on the device page?

deleted the old converter, threw the new one and rebooted the system. Now Energy data has Null status. An error occurs when the yellow button is pressed.

The data is updated with a delay of several minutes ERROR

2024-07-21 13:07:08z2m: Failed to configure 'Boiler', attempt 5 (Error: ZCL command 0x70b3d52b600b9d7a/1 haElectricalMeasurement.configReport([{"attribute":"rmsVoltage","minimumReportInterval":5,"maximumReportInterval":3600,"reportableChange":5}], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNREPORTABLE_ATTRIBUTE') at Endpoint.checkStatus (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:316:28) at Endpoint.zclCommand (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:771:26) at Endpoint.configureReporting (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:557:9) at Object.rmsVoltage (/app/node_modules/zigbee-herdsman-converters/src/lib/reporting.ts:221:5) at Object.configure (/app/data/extension/externally-loaded.js:34:9) at Configure.configure (/app/lib/extension/configure.ts:126:13) at Configure.onMQTTMessage (/app/lib/extension/configure.ts:56:21) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17))

Redram49RUS commented 1 month ago

I've updated the external converter, could you check it again after re-configuring the device by pressing the yellow refresh icon on the device page?

2024-07-21 21:21:31Failed to configure 'Варочная панель', attempt 7 (Error: ZCL command 0x70b3d52b600b9be7/1 haElectricalMeasurement.configReport([{"attribute":"rmsVoltage","minimumReportInterval":5,"maximumReportInterval":3600,"reportableChange":5}], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNREPORTABLE_ATTRIBUTE') at Endpoint.checkStatus (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:316:28) at Endpoint.zclCommand (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:771:26) at Endpoint.configureReporting (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:557:9) at Object.rmsVoltage (/app/node_modules/zigbee-herdsman-converters/src/lib/reporting.ts:224:5) at Object.configure (/app/data/extension/externally-loaded.js:34:9) at Configure.configure (/app/lib/extension/configure.ts:121:13) at Configure.onMQTTMessage (/app/lib/extension/configure.ts:55:21) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:174:17))

Koenkk commented 1 month ago

Are you sure you updated the external converter? Line 34 should be commented (which currently causes this rmsVoltage error)

nifelin123 commented 1 month ago

Are you sure you updated the external converter? Line 34 should be commented (which currently causes this rmsVoltage error)

I checked it, attached a photo. everything was updated.

1

andregoncalvespires commented 1 month ago

.js updated, z2m restarted.

image

image

Koenkk commented 1 month ago

Updated https://gist.github.com/Koenkk/436c0291d93741b3ac261455b52722aa, can you check to configure it again?

andregoncalvespires commented 1 month ago

The values ​​have been corrected, the UNREPORTABLE_ATTRIBUTE error no longer appears. I have doubts whether the energy value is being reported correctly by the device. I'm comparing, but I believe that if there is a difference, it is not caused by Z2M.

image

Redram49RUS commented 1 month ago

I also updated ext.js, now current and power readings are not transmitted when a 2 kW load is on, the errors are gone. The energy began to count. UPD: Power and current are transmitted, the delay is 30 to 40 seconds. An electric stove is connected in the kitchen; at low power it turns on for short periods of time to maintain the temperature. When setting power 3 on an electric stove (approximately 650 kW), the relay does not have time to record the current and power data. Is it possible to increase the frequency of current or power sampling?

andregoncalvespires commented 1 month ago

The energy measurement is really unreliable. The Tuya app already showed a large variation. Does anyone know if using calibration could help? Power and Current appear to be normal. Considering the variation between now and 14 hours ago, it shows a consumption of more than 200 kWh and it should be something around 10 kWh

image

Koenkk commented 1 month ago

@andregoncalvespires if the energy measurement via the Tuya gateway is also incorrect, it's not something that can be fixed by z2m

andregoncalvespires commented 1 month ago

It is clear @Koenkk . The question was considering the available calibration options. But I'm already discouraged by this device. Thank you for the fabulous work you and everyone who contributes do.