Jorge Schrauwen

No, mine is set to do full deploys. it’s still not resolved, the problem is not the node deployment but that when a setup payload is received later for a...

> This still an issue, yes. I've also been hitting this, e.g. https://musicbrainz.org/artist/aabb1d9f-be12-45b3-a84d-a1fc3e8181fd Although I've been able to work around it with `MusicBrain Picard` which I was using anyway to...

I can't reproduce this either, I have a lot of tvshow.nfo hint files for my anime e.g. mine for Acchi Kocchi is ```xml Acchi Kocchi あっちこっち 8890 12291 63712 2012-04-06...

I think the PR/issue file on zh having to do with the data type for type pm25 might be related to this. I’ll see if I can find my vindstyrke,...

I can confirm I see the error during pairing on mine too: ``` Zigbee2MQTT:error 2024-01-22 21:20:26: Failed to configure '0x90ab96fffefa5d91', attempt 1 (Error: ConfigureReporting 0x90ab96fffefa5d91/1 pm25Measurement([{"attribute":"measuredValueIkea","minimumReportInterval":60,"maximumReportInterval":120,"reportableChange":2}], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":4476,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Status 'UNSUPPORTED_ATTRIBUTE')...

> So if I understand correctly it works after changing to: > > ```js > measuredValueIkea: {ID: 0x0000, type: DataType.singlePrec}, > ``` Yes, but then it overlaps with the regular...

I don’t think that will work, yesterday i tried with just measuredValue commented and it didn’t pick the ikea one. I’m guessing because there is no manufacturerCode send by the...

I think the best way to fix is probably removing the ikea one from cluster.ts and specifying the data type during the configure reporting. For decoding the dt doesn’t seem...

This should hopefully be fixed in the february release (https://github.com/Koenkk/zigbee-herdsman-converters/pull/6972)

In the dev release / next release in may, it should now be possible to configure reporting via the frontend again.