Failed to setup reporting for Innr RB 285 C

While repairing all my bulbs I noticed that my 3 Innr RB 285 C never completed there reporting setup:

Zigbee2MQTT:error 2020-12-28 11:52:57: Failed to setup reporting for '0x00158d000502f5ce' - Error: ConfigureReporting 0x00158d000502f5ce/1 lightingColorCtrl([], {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null}) failed (Timeout - 65149 - 1 - 48 - 768 - 7 after 10000ms)
    at Timeout._onTimeout (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:46:35)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)

This is also repeated everytime I restart zigbee2mqtt.

My other Innr RB 250 C/RS 230 C do not have the issue.

I did notice everything was on firmware 2.1 except the 1/3 RB 285 C’s which is at 2.0. But that doesn’t seem to have any effect as the all 3 have the issue.

If I manually add meta.reporting == 1 to the database the error goes away during restart.

All inner bulbs are reporting lightingColorCtrl though… maybe they report by default and that is why it fails?

devce	setup of lightingColorCtrl reporting	reporting
RB 250 C	OK	OK
RB 285 C	timeout	OK
RS 240 C	OK	OK

[sjorge]

Excellent, I’m going to close this.

I see you’re working on a smart way to setup reporting, I think once that is implemented and as mentioned in https://github.com/Koenkk/zigbee-herdsman-converters/issues/2037, we shy away from setting up enhancedHue reporting (which we currently don’t do anyway, normal hue/sat is fine if colorCaps says it is), the original issues should also been fixed. If not, I’ll probably deal with it once I get a better grip on colorCaps en enhancedHue madness.

[Koenkk]

Those docs can be found here: https://www.zigbee2mqtt.io/information/mqtt_topics_and_message_structure.html#zigbee2mqttbridgerequestdeviceconfigure_reporting

@sjorge merged the fix