Reporting tab interface completely broken after 1.33.1 update

[DmitriK]

What happened?

After upgrading to 1.33.1, my VINDSTYRKA devices were no longer updating at the rate that I had previously configured them. Upon going to the reporting tab, I noticed that all the clusters were listed twice, once with my original settings, and once with what appears to be the default. It also appears to be impossible to fix. I can disable all the extra entries except for pm25measurement, where I first have to change the attribute to measuredValueIkea, otherwise I get a Request 'zigbee2mqtt/bridge/request/device/configure_reporting' failed with error: 'ConfigureReporting 0x385cfbfffea36292/1 pm25Measurement([{"attribute":"measuredValue","minimumReportInterval":60,"maximumReportInterval":65535,"reportableChange":2}], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'INVALID_DATA_TYPE')'
However, attempting to change any of the settings results in more duplicates returning, though they seem to match my settings.
Screenshot of what this looks like after any attempt at editing:

What did you expect to happen?

A) zigbee2mqtt does not erase my previous reporting settings
B) I can actually use the reporting tab to adjust the settings.

How to reproduce it (minimal and precise)

Unsure what the minimum requirement is. As mentioned above, I'm using VINDSTYRKA devices (don't know if it's specific to them), and simply trying to set reporting settings.

Zigbee2MQTT version

1.33.1

Adapter firmware version

0x26580700

Adapter

ConBee2/RaspBee2

Debug log

log.txt

[sanyafifa]

I connected my new sensor E2112 yesterday - and there is no data from it except LQI.

Zigbee2MQTT version
1.33.1 dev

[alexh3o]

Hi,
After noticing my ZLinky did'nt update properly for some values, I noticed the same problem in reporting page.
Some duplicates can be deleted, others not, and when I try to change a value (min rep interval or min rep change), a duplicate reporting is added again instead of changing the adequate line.
This is on a raspberry pi 4 and HA supervised:
Core 2023.11.1
Supervisor 2023.11.0
Frontend 20231030.
Zigbee2mqtt 1.33.2

[Koenkk]

@alexh3o could you provide your data/database.db?

[alexh3o]

Here is the part for ZLinky

{"id":58,"type":"Router","ieeeAddr":"0x00158d000966cc3e","nwkAddr":43723,"manufId":4151,"manufName":"LiXee","powerSource":"Mains (single phase)","modelId":"ZLinky_TIC\u0000","epList":[1,242],"endpoints":{"1":{"profId":260,"epId":1,"devId":83,"inClusterList":[0,3,1794,2820,2817,65382,1],"outClusterList":[25],"clusters":{"genBasic":{"attributes":{"modelId":"ZLinky_TIC\u0000","manufacturerName":"LiXee","powerSource":1,"zclVersion":3,"appVersion":12,"stackVersion":2,"hwVersion":1,"dateCode":"20230214","swBuildId":"4000-0013"}},"liXeePrivate":{"attributes":{"linkyMode":0,"currentTarif":"BASE\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000","warnDPS":0}},"haElectricalMeasurement":{"attributes":{"rmsCurrentMax":90,"apparentPower":1950,"rmsCurrent":7}},"seMetering":{"attributes":{"meterSerialNumber":{"type":"Buffer","data":[48,51,49,55,54,50,48,52,53,49,49,53]},"activeRegisterTierDelivered":"TH..","currentSummDelivered":[0,39755333]}},"haMeterIdentification":{"attributes":{"availablePower":60}}},"binds":[{"cluster":1794,"type":"endpoint","deviceIeeeAddress":"0x00124b0024c82c76","endpointID":1},{"cluster":2817,"type":"endpoint","deviceIeeeAddress":"0x00124b0024c82c76","endpointID":1},{"cluster":2820,"type":"endpoint","deviceIeeeAddress":"0x00124b0024c82c76","endpointID":1},{"cluster":65382,"type":"endpoint","deviceIeeeAddress":"0x00124b0024c82c76","endpointID":1}],"configuredReportings":[{"cluster":1794,"attrId":0,"minRepIntval":60,"maxRepIntval":900,"repChange":100},{"cluster":2820,"attrId":1288,"minRepIntval":60,"maxRepIntval":900,"repChange":1},{"cluster":2820,"attrId":1295,"minRepIntval":60,"maxRepIntval":900,"repChange":1},{"cluster":65382,"attrId":5,"minRepIntval":60,"maxRepIntval":900,"repChange":1},{"cluster":65382,"attrId":5,"minRepIntval":60,"maxRepIntval":900,"repChange":1,"manufacturerCode":null},{"cluster":1794,"attrId":0,"minRepIntval":60,"maxRepIntval":900,"repChange":10,"manufacturerCode":null},{"cluster":2820,"attrId":1295,"minRepIntval":15,"maxRepIntval":900,"repChange":1,"manufacturerCode":null}],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[33],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":12,"stackVersion":2,"hwVersion":1,"dateCode":"20230214","swBuildId":"4000-0013","zclVersion":3,"interviewCompleted":true,"meta":{"configured":1745911956},"lastSeen":1699468392019,"defaultSendRequestWhen":"immediate"}

I can send the whole database.db if it's useful, should I do it here or through a more private channel ?

[seblu]

I'm also affected by this. In my case, duplication occurs when I'm updating values in the Reporting tab.

[seblu]

Same issue with freshly released 1.34.0. Despite no error reported, it looks like it happens when the original value cannot be changed.

After updating activePower min rep change value from 10 to 1:

• A new line is added at the bottom with the requested value.
• The old line remain with its value field updated to the requested value.
  

After a page reload, value is back and new row is still here:

• The original line value has changed to the original value. As if it has not changed.
• The new line remain with the requested value.
  

I can remove the new line. On another device, the same behavior was fixed by repairing (removing/pairing).

[alexh3o]

Hi, if you remove and repair your device, you can configure reporting without having duplicates after ?

[emandtf]

Just updated to 1.34.0 and now (without doing anything) many "entities" in database.db are duplicated and reported with default/wrong Reporting times/repo_changes together with the new "manufacturerCode: null" JSON attribute.....

Those duplicated entities are the same that was previously affected by this duplication bug when we was trying to update their values.

A questions: should we keep the ones with "manufacturerCode: null" (because it's the new/right standard ATM) or the old ones without this new attribute?

[Koenkk]

Pushed a fix! After upgrading, click Apply on the configured reportings to get rid of the duplicates.

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

[emandtf]

Pushed a fix! After upgrading, click Apply on the configured reportings to get rid of the duplicates.

Changes will be available in the dev branch in a few hours from now. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

Unfortunately switching to Dev branch doesn't solve anything. Now Z2M neither starts.....

zigbee2mqtt@1.34.0-dev start
node index.js
Building Zigbee2MQTT... (initial build), failed
Error: Command failed: npm run build
at ChildProcess.exithandler (node:child_process:419:12)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1091:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)