Testing: reporting

[Koenkk]

Reporting is a new feature which is currently only available in the dev branch. When reporting is enabled, the device will report their state changes to zigbee2mqtt. This is especially handy when the state of a bulb is changed by e.g. a remote or via groups.

To enable report, add the following to your configuration.yaml:

advanced:
  report: true

As reporting is a feature of the device, not all devices may support this.

Current findings

• IKEA TRADFRI bulbs work as expected
• Hue bulbs only report on/off state (limitation of Hue bulbs) (Testing: reporting #1064 (comment))

[milakov]

Hi!

Gledopto GL-B-007Z:

Changing color temperature triggers this (along with actual ct of the bulb changing):

zigbee2mqtt:error 2019-2-10 22:06:26 No converter available for 'color_temp' (166)

Changing brightness doesn't trigger anything in the logs (but the brightness of the physical bulb actually changes, HA still thinks the brightness is unchanged).

[Koenkk]

@milakov should be fixed in the latest dev branch, if not, please open a separate issue as this is not related to this issue.

[sylarevan]

Just tried with a group of two Hue bulbs. Changing the state (ON or OFF) of the group does not report the individual change of state of each bulb.
Logs in debug mode are here.

[JumpmanJunior]

I tried to activate reporting for a Philips and a Ikea bulb. But when I control the bulbs with a bound Philips dimmer switch the status changes are not reported. Here is the log for the Ikea bulb:

2019-2-10 22:58:08 - debug: Setup reporting for 0x000d6ffffe1df5f5 - genOnOff - onOff
2019-2-10 22:58:09 - debug: Setup reporting for 0x000d6ffffe1df5f5 - genLevelCtrl - currentLevel
2019-2-10 22:58:09 - debug: Successfully setup reporting for 0x000d6ffffe1df5f5 - genOnOff - onOff
2019-2-10 22:58:09 - debug: Successfully setup reporting for 0x000d6ffffe1df5f5 - genLevelCtrl - currentLevel
2019-2-10 22:58:09 - debug: Setup reporting for 0x000d6ffffe1df5f5 - lightingColorCtrl - currentX
2019-2-10 22:58:09 - debug: Successfully setup reporting for 0x000d6ffffe1df5f5 - lightingColorCtrl - currentX
2019-2-10 22:58:09 - debug: Setup reporting for 0x000d6ffffe1df5f5 - lightingColorCtrl - currentY
2019-2-10 22:58:09 - debug: Successfully setup reporting for 0x000d6ffffe1df5f5 - lightingColorCtrl - currentY

[way2many]

I tested reporting of two Tradfri GU10 in my hallway this morning. I switched them off with the wire switch (220V) and put them back on. This is the log:

2/12/2019, 6:19:55 AM - debug: Saving state to file /app/data/state.json
2/12/2019, 6:21:53 AM - debug: Received zigbee message of type 'endDeviceAnnce' with data '"0x90fd9ffffe1a7413"' of device 'TRADFRI bulb GU10 W 400lm' (0x90fd9ffffe1a7413)
2/12/2019, 6:21:53 AM - debug: Setup reporting for 0x90fd9ffffe1a7413 - genOnOff - onOff
2/12/2019, 6:21:53 AM - debug: Received zigbee message of type 'endDeviceAnnce' with data '"0x90fd9ffffe2a3f57"' of device 'TRADFRI bulb GU10 W 400lm' (0x90fd9ffffe2a3f57)
2/12/2019, 6:21:54 AM - debug: Setup reporting for 0x90fd9ffffe1a7413 - genLevelCtrl - currentLevel
2/12/2019, 6:21:54 AM - debug: Successfully setup reporting for 0x90fd9ffffe1a7413 - genOnOff - onOff
2/12/2019, 6:21:54 AM - debug: Successfully setup reporting for 0x90fd9ffffe1a7413 - genLevelCtrl - currentLevel
2/12/2019, 6:21:54 AM - debug: Setup reporting for 0x90fd9ffffe2a3f57 - genOnOff - onOff
2/12/2019, 6:21:54 AM - debug: Successfully setup reporting for 0x90fd9ffffe2a3f57 - genOnOff - onOff
2/12/2019, 6:21:54 AM - debug: Setup reporting for 0x90fd9ffffe2a3f57 - genLevelCtrl - currentLevel
2/12/2019, 6:21:54 AM - debug: Successfully setup reporting for 0x90fd9ffffe2a3f57 - genLevelCtrl - currentLevel
2/12/2019, 6:21:55 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe1a7413"'
2/12/2019, 6:21:56 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe1a7413"'
2/12/2019, 6:21:56 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe1a7413"'
2/12/2019, 6:21:57 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe1a7413"'
2/12/2019, 6:21:57 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe1a7413"'
2/12/2019, 6:21:58 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe1a7413"'
2/12/2019, 6:21:58 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe1a7413"'
2/12/2019, 6:21:58 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe1a7413"'
2/12/2019, 6:21:59 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe1a7413"'
2/12/2019, 6:21:59 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe1a7413"'
2/12/2019, 6:21:59 AM - debug: Received zigbee message of type 'devIncoming' with data '"0x90fd9ffffe1a7413"' of device 'TRADFRI bulb GU10 W 400lm' (0x90fd9ffffe1a7413)
2/12/2019, 6:21:59 AM - info: Device incoming...
2/12/2019, 6:21:59 AM - info: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"device incoming"}'
2/12/2019, 6:21:59 AM - debug: Received zigbee message of type 'devStatus' with data '"online"' of device 'TRADFRI bulb GU10 W 400lm' (0x90fd9ffffe1a7413)
2/12/2019, 6:22:01 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe2a3f57"'
2/12/2019, 6:22:01 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe2a3f57"'
2/12/2019, 6:22:01 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe2a3f57"'
2/12/2019, 6:22:02 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe2a3f57"'
2/12/2019, 6:22:02 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe2a3f57"'
2/12/2019, 6:22:03 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe2a3f57"'
2/12/2019, 6:22:03 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe2a3f57"'
2/12/2019, 6:22:03 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe2a3f57"'
2/12/2019, 6:22:04 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe2a3f57"'
2/12/2019, 6:22:04 AM - debug: Received zigbee message of type 'devInterview' with data '"0x90fd9ffffe2a3f57"'
2/12/2019, 6:22:04 AM - debug: Received zigbee message of type 'devIncoming' with data '"0x90fd9ffffe2a3f57"' of device 'TRADFRI bulb GU10 W 400lm' (0x90fd9ffffe2a3f57)
2/12/2019, 6:22:04 AM - info: Device incoming...
2/12/2019, 6:22:04 AM - info: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"device incoming"}'
2/12/2019, 6:22:04 AM - debug: Received zigbee message of type 'devStatus' with data '"online"' of device 'TRADFRI bulb GU10 W 400lm' (0x90fd9ffffe2a3f57)
2/12/2019, 6:24:55 AM - debug: Saving state to file /app/data/state.json

I have now multiple questions:

• What is "endDeviceAnnce" and why did the bulb publish this?
• Am I correct to interpreting this as when physically switched off, the bulb lose it's reporting function (if it has one)?
• Am I also correct that when physically switched off, the bulb re-pair itself ?

As I'm unable to bind my Hue Dimmer Switch to my Hue suspension Fair I cannot test the reporting function on those one.

[nanosonde]

I am also trying to achieve the same.
I have a TRADFRI remote and TRADFRI driver paired to zigbee2mqtt. I have found out the group ID of the remote by sniffing. Then I have created a group with this ID and added the TRADFRI driver to this group. I can successfully control the driver with the remote and z2m.

The reporting configuration seems to have worked:

  zigbee2mqtt:debug 2/13/2019, 1:45:38 PM Setup reporting for 0x000d6ffffe2cxxxx - genOnOff - onOff
  zigbee2mqtt:debug 2/13/2019, 1:45:38 PM Successfully setup reporting for 0x000d6ffffe2cxxxx - genOnOff - onOff
  zigbee2mqtt:debug 2/13/2019, 1:45:38 PM Setup reporting for 0x000d6ffffe2cxxxx - genLevelCtrl - currentLevel
  zigbee2mqtt:debug 2/13/2019, 1:45:38 PM Successfully setup reporting for 0x000d6ffffe2cxxxx - genLevelCtrl - currentLevel

However, I do not get any reports in z2m if it is controlled by the remote.

[nanosonde]

I am not seeing any attribute reports with the sniffer either.
So is it the report configuration which did not work properly although it claims success?

[nanosonde]

From the ZCL Configure Reporting Message I see that there is a min interval of 1 and a max interval of 3600. 3600s would be 1h.
So how does the device choose which to use? Is it possible to lower the value to 10s and see what happens?

Of course I would expect that it immediately sends a changed state, but I do not how this reporting is meant to work in detail.

[Koenkk]

@nanosonde just change https://github.com/Koenkk/zigbee2mqtt/blob/dev/lib/extension/reporting.js#L12 to 10 .

[nanosonde]

@Koenkk I have changed it to 10s and verified with the sniffer that this is sent over the wire.
Unfortunately, it does not work too.

[nanosonde]

@Koenkk Somewhere in the deconz-plugin issues I have read that reporting for a TRADFRI device(?) only worked when it is read back. I am not absolutely sure anymore.

[nanosonde]

Got it working. I have disabled the generic reporting setup using "report: true".
Instead I have changed device.js for the 10W dimmer similiar to the TRADFRI power outlet.

    {
        zigbeeModel: ['TRADFRI transformer 10W', 'TRADFRI Driver 10W'],
        model: 'ICPSHC24-10EU-IL-1',
        vendor: 'IKEA',
        description: 'TRADFRI driver for wireless control (10 watt)',
        //extend: generic.light_onoff_brightness,
        fromZigbee: [fz.ignore_onoff_change, fz.state],
        toZigbee: [tz.on_off],
        configure: (ieeeAddr, shepherd, coordinator, callback) => {
            const device = shepherd.find(ieeeAddr, 1);
            const cfg = {direction: 0, attrId: 0, dataType: 16, minRepIntval: 0, maxRepIntval: 1000, repChange: 0};
            const actions = [
                (cb) => device.bind('genOnOff', coordinator, cb),
                (cb) => device.foundation('genOnOff', 'configReport', [cfg], foundationCfg, cb),
            ];

            execute(device, actions, callback);
        },
    },

This way the driver immediately reports state changes.

[nanosonde]

@Koenkk
Maybe I am missing something, but is the binding to the coordinator missing if reports are enabled using the generic mechansim? Or is this only required for TRADFRI devices?

zigbee2mqtt/lib/extension/reporting.js

Line 43 in c9c599b

this.zigbee.report(

There is no binding to the coordinator happening as it is done as show in my previous comment.

[nanosonde]

BTW: It looks like this with the above code change:

  zigbee2mqtt:debug 2/13/2019, 7:10:02 PM Received zigbee message of type 'cmdToggle' with data '{"cid":"genOnOff","data":{}}' of device 'TRADFRI remote control' (0xd0cf5efffe0bxxxx)
  zigbee2mqtt:info 2/13/2019, 7:10:02 PM MQTT publish: topic 'zigbee2mqtt/ikea_remotecontrol', payload '{"action":"toggle","linkquality":10,"last_seen":"2019-02-13T19:10:02.922Z","elapsed":5628497}'
  zigbee2mqtt:debug 2/13/2019, 7:10:02 PM Received zigbee message of type 'attReport' with data '{"cid":"genOnOff","data":{"onOff":1}}' of device 'TRADFRI transformer 10W' (0x000d6ffffe2cyyyy)
  zigbee2mqtt:info 2/13/2019, 7:10:02 PM MQTT publish: topic 'zigbee2mqtt/ikea_driver', payload '{"state":"ON","last_seen":"2019-02-13T19:10:02.955Z","linkquality":7,"elapsed":628194}'

[Koenkk]

@nanosonde I've also added the binding, meaning it should be the same as your custom configure now. Can you factory reset/re-pair the device and verify that it works with report: true?

[nanosonde]

@Koenkk I have tested latest dev and seems to be working now as with the custom configure.
As I did a complete ./update.sh I experience an error now concerning the remote control:

  zigbee2mqtt:debug 2/13/2019, 8:42:05 PM Coordinator is already in group '611'
  zigbee2mqtt:error 2/13/2019, 8:42:05 PM Failed to apply coordinator group for IKEA TRADFRI remote control (0xd0cf5efffe0bxxxx)
  zigbee2mqtt:debug 2/13/2019, 8:42:05 PM Coordinator is already in group '99'

Did you change anything here?
This was working before. Group ID 611 is correct. Why is the coordinator already in group 611?
Is it from my testgroup under "groups" in the configuration with the same ID to which I have added my tradfri driver?

If I remove "coordinator_group" from the device config then this error is gone and I also receive the reports from button pushes.

BTW:
Neither the driver nor the remote control need to be put close to the coordinator to pair them.
The remote control just needs the 4-button-press sequence for factory reset which also restarts pairing (without touchlink). The driver just needs a short press with a paperclip to factory reset and restart pairing.

[nanosonde]

@Koenkk I have tested latest dev and seems to be working now as with the custom configure.
As I did a complete ./update.sh I experience an error now concerning the remote control:

  zigbee2mqtt:debug 2/13/2019, 8:42:05 PM Coordinator is already in group '611'
  zigbee2mqtt:error 2/13/2019, 8:42:05 PM Failed to apply coordinator group for IKEA TRADFRI remote control (0xd0cf5efffe0bxxxx)
  zigbee2mqtt:debug 2/13/2019, 8:42:05 PM Coordinator is already in group '99'

Ok, I will answer that by myself after studying the code.
So actually this is NOT a failure, but it is just as the previous message tells it: the ZDO of the coordinator already has the group added. So this is a bit misleading and not a real failure.

[Koenkk]

@nanosonde you are right, fixed.

[Koenkk]

Groups will now also report their state (on zigbee2mqtt/[GROUP_FRIENDLY_NAME). (dev branch)

[dreimer1986]

  zigbee2mqtt:error 2019-2-15 10:15:42 Failed to setup reporting for 0x84182600000b8298 - lightingColorCtrl - currentX - (Error: AF data request fails, status code: 233. MAC no ack.)
  zigbee2mqtt:error 2019-2-15 10:15:44 Failed to setup reporting for 0x84182600000b79b7 - genLevelCtrl - currentLevel - (Error: AF data request fails, status code: 233. MAC no ack.)
  zigbee2mqtt:warn 2019-2-15 10:15:45 Failed to configure Motion (0x000d6f000e059aae) ('Error: AF data request fails, status code: 240. MAC transaction expired.') (attempt #1)
  zigbee2mqtt:warn 2019-2-15 10:15:45 This can be ignored if the device is working properly
  zigbee2mqtt:error 2019-2-15 10:15:45 Failed to setup reporting for 0x7cb03eaa00a1184a - lightingColorCtrl - currentX - (Error: AF data request fails, status code: 233. MAC no ack.)
  zigbee2mqtt:error 2019-2-15 10:15:46 Failed to setup reporting for 0x84182600000b743a - genOnOff - onOff - (Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.)
  zigbee2mqtt:error 2019-2-15 10:15:47 Failed to setup reporting for 0x84182600000b743a - lightingColorCtrl - colorTemperature - (Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.)
  zigbee2mqtt:error 2019-2-15 10:15:47 Failed to setup reporting for 0x84182600000b743a - genLevelCtrl - currentLevel - (Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.)
  zigbee2mqtt:error 2019-2-15 10:15:47 Failed to setup reporting for 0x84182600000b83ef - genOnOff - onOff - (Error: AF data request fails, status code: 233. MAC no ack.)
  zigbee2mqtt:error 2019-2-15 10:15:47 Failed to setup reporting for 0x84182600000b83ef - genLevelCtrl - currentLevel - (Error: AF data request fails, status code: 233. MAC no ack.)
  zigbee2mqtt:error 2019-2-15 10:15:47 Failed to setup reporting for 0x84182600000b743a - lightingColorCtrl - currentY - (Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.)
  zigbee2mqtt:error 2019-2-15 10:15:47 Failed to setup reporting for 0x84182600000b743a - lightingColorCtrl - currentX - (Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.)
  zigbee2mqtt:error 2019-2-15 10:15:48 Failed to setup reporting for 0x8418260000ca9270 - lightingColorCtrl - currentY - (Error: AF data request fails, status code: 233. MAC no ack.)
  zigbee2mqtt:error 2019-2-15 10:15:50 Failed to setup reporting for 0x7cb03eaa00a1184a - genLevelCtrl - currentLevel - (Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.)

I added reporting to all my bulbs, in a group or not. Reporting does not work, but on startup you see this after it reconnected to all Zigbee devices. Do I have to repair all my bulbs to make it work?

EDIT: Debug loglevel: https://h.kremowka.xyz/etayakilox.coffeescript

[Koenkk]

@dreimer1986 can you control the bulb individually (turn on/off)?

[alinelena]

@Koenkk i get he same error as @dreimer1986

  2/16/2019, 8:21:25 AM - debug: Setup binding for 0x000b57fffeb0c77e - genOnOff
  2/16/2019, 8:21:25 AM - debug: Setup reporting for 0x000b57fffeb0c77e - genOnOff - onOff
  2/16/2019, 8:21:25 AM - debug: Setup binding for 0x000b57fffeb0c77e - genLevelCtrl
  2/16/2019, 8:21:25 AM - debug: Setup reporting for 0x000b57fffeb0c77e - genLevelCtrl - currentLevel
)>2/16/2019, 8:21:25 AM - error: Failed to setup reporting for 0x000b57fffeb0c77e - genOnOff - onOff - (Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network.)
  2/16/2019, 8:21:25 AM - debug: Setup binding for 0x000b57fffeb24cb3 - genOnOff
  2/16/2019, 8:21:26 AM - debug: Setup reporting for 0x000b57fffeb24cb3 - genOnOff - onOff
  2/16/2019, 8:21:26 AM - debug: Setup binding for 0x000b57fffeb24cb3 - genLevelCtrl
  2/16/2019, 8:21:26 AM - error: Failed to setup reporting for 0x000b57fffeb0c77e - genLevelCtrl - currentLevel - (Error: AF data request fails, status code: 205. No network route. Please confirm that the device has (re)joined the network

much later I get a binding success message for both bulbs here.
nothing more about reporting except the error. However reporting works and I can control them individually too or via the group.

I am on this

  2/16/2019, 8:21:21 AM - info: Starting zigbee2mqtt version 1.1.1 (commit #577bb0d)

I think that somehow one sets reporting too early

[dreimer1986]

@Koenkk yes, controlling any of the bulbs works fine. Only reporting is not and the log fills a bit more when activated.

[alinelena]

@dreimer1986 this is what is in my log

2/16/2019, 4:01:38 PM - info: MQTT publish: topic 'zigbee2mqtt/bedroom_lights', payload '{"state":"OFF","brightness":255}'
2/16/2019, 4:01:38 PM - debug: Received zigbee message of type 'attReport' with data '{"cid":"genOnOff","data":{"onOff":0}}' of device 'TRADFRI bulb E26 W opal 1000lm' (0x000b57fffeb0c77e)
2/16/2019, 4:01:38 PM - info: MQTT publish: topic 'zigbee2mqtt/ikea_bedroom_1', payload '{"state":"OFF","linkquality":49,"brightness":254}'
2/16/2019, 4:01:38 PM - debug: Received zigbee message of type 'devChange' with data '{"cid":"genOnOff","data":{"onOff":0}}' of device 'TRADFRI bulb E26 W opal 1000lm' (0x000b57fffeb0c77e)
2/16/2019, 4:01:38 PM - info: MQTT publish: topic 'zigbee2mqtt/ikea_bedroom_1', payload '{"state":"OFF","linkquality":49,"brightness":254}'
2/16/2019, 4:01:38 PM - debug: Received zigbee message of type 'attReport' with data '{"cid":"genOnOff","data":{"onOff":0}}' of device 'TRADFRI bulb E26 W opal 1000lm' (0x000b57fffeb24cb3)
2/16/2019, 4:01:38 PM - info: MQTT publish: topic 'zigbee2mqtt/ikea_bedroom_2', payload '{"state":"OFF","linkquality":15,"brightness":254}'
2/16/2019, 4:01:38 PM - debug: Received zigbee message of type 'devChange' with data '{"cid":"genOnOff","data":{"onOff":0}}' of device 'TRADFRI bulb E26 W opal 1000lm' (0x000b57fffeb24cb3)
2/16/2019, 4:01:38 PM - info: MQTT publish: topic 'zigbee2mqtt/ikea_bedroom_2', payload '{"state":"OFF","linkquality":15,"brightness":254}'  

annoying bit is the messages are reported twice

[dreimer1986]

Nope, no report over here. Will repair the devices later these days. Maybe this finally fixes that and maybe my Smart+ Motion sensor to not only send me temperature information, but MOTION too ^^

[Kryzek]

While re-pairing my devices got this error with my Hue white and color ambiance E26/E27/E14 (9290012573A) -bulb:

error 2019-11-14T17:05:05: Failed to setup reporting for '0x001788010278b40a' - Error: Timeout - 4247 - 11 - 2 - 6 - 7 after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

Edit: wrong entry

[Kryzek]

When I restarted my Zigbee2MQTT I noticed that some Hue bulbs spit out an error.

Hue White Single bulb B22 (8718696449691)
zigbee2mqtt:error 2019-11-21 13:43:05: Failed to setup reporting for '0x0017880102b3b0ab' - Error: Timeout - 33592 - 11 - 2 - 6 - 7 after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
	
Hue white and color ambiance E26/E27/E14 (9290012573A)
zigbee2mqtt:error 2019-11-21 13:43:05: Failed to setup reporting for '0x001788010278b40a' - Error: Timeout - 26093 - 11 - 3 - 6 - 7 after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

[bodiroga]

+1 @Kryzek!

In my case I have 3x Philips Hue bulbs (quite old): 2x Philips Hue Lux A19 bulb E27 and 1x Philips Hue white A60 bulb E27.

And here you can find the log messages:

zigbee2mqtt:error 2019-12-13T22:45:31: Failed to setup reporting for '0x001788011040a46b' - Error: Timeout - 17728 - 11 - 2 - 6 - 7 after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
zigbee2mqtt:error 2019-12-13T22:45:31: Failed to setup reporting for '0x0017880100db65c0' - Error: Timeout - 49932 - 11 - 3 - 6 - 7 after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
zigbee2mqtt:error 2019-12-13T22:45:41: Failed to setup reporting for '0x0017880100db6159' - Error: Timeout - 46369 - 11 - 4 - 6 - 7 after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

My coordinator is a CC2652R and I'm using the latest stable version of program: "zigbee2mqtt version 1.7.1" (commit #b459c35).

What type of log reports would you need, @Koenkk?

Thank you very much and best regards,

Aitor

[czikus]

I can confirm the problem with all my hue bulbs on the latest dev (1.7.1+dev (commit #1972eb4)):

error 2019-12-14 11:00:27: Failed to setup reporting for '0x0017880110450438' - Error: Timeout - 32594 - 11 - 2 - 6 - 7 after 10000ms
    at Timeout._onTimeout (/opt/zigbee2mqtt/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at listOnTimeout (internal/timers.js:536:17)
    at processTimers (internal/timers.js:480:7)

[Koenkk]

@bodiroga Sniffing the traffic is needed to pinpoint the problem (https://www.zigbee2mqtt.io/how_tos/how_to_sniff_zigbee_traffic.html).

[bodiroga]

Hi @Koenkk!

I have followed the steps described in your link (as always, amazing documentation, well done sir) and attached to this message you can find the packages captured with wireshark. This is the order I have followed:

• Start wireshark with sudo whsniff -c 11 | wireshark -k -i -
• Restart the docker container with docker restart zigbee2mqtt
• Wait until the timeout messages appear in the log file (docker logs -f zigbee2mqtt)

As in the previous message, the error messages have been:

zigbee2mqtt:error 2019-12-15T20:44:29: Failed to setup reporting for '0x001788011040a46b' - Error: Timeout - 17728 - 11 - 2 - 6 - 7 after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
zigbee2mqtt:error 2019-12-15T20:44:29: Failed to setup reporting for '0x0017880100db65c0' - Error: Timeout - 49932 - 11 - 3 - 6 - 7 after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
zigbee2mqtt:error 2019-12-15T20:44:39: Failed to setup reporting for '0x0017880100db6159' - Error: Timeout - 46369 - 11 - 4 - 6 - 7 after 10000ms
    at Timeout.object.timer.setTimeout [as _onTimeout] (/app/node_modules/zigbee-herdsman/dist/utils/waitress.js:44:24)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)

zigbee2mqtt.zip

I don't understand what the packages captured by wireshark mean, but I hope that they can be useful. If you need anything else, don't hesitate to ask, please 😉

Best regards,

Aitor

[Koenkk]

@bodiroga it seems that your bulbs don't support reporting (probably because of the old firmware???). This can be seen in the log:

[bodiroga]

@bodiroga it seems that your bulbs don't support reporting (probably because of the old firmware???).

Oh, that's a shame 😢 It's true that the bulbs are quite old, but I though that they could be able to report their status, as they have received the newest firmware not so long ago (20181121):

{"ieeeAddr":"0x0017880100db65c0","type":"Router","networkAddress":xxxxx,"model":"433714","friendly_name":"philips-white-1","manufacturerID":4107,"manufacturerName":"Philips","powerSource":"Mains (single phase)","modelID":"LWB004","hardwareVersion":1,"softwareBuildID":"5.127.1.26420","dateCode":"20181121","lastSeen":1576599446324}

Before pairing the bulbs with the CC2652R, I checked if a new firmware was available for them, but the one from 11/2018 was the latest one. I did it using the first generation Philips Hue Bridge, but I don't know if that matters, as far as I know, it shouldn't.

Anyway, many thanks @Koenkk for having a look at my log file 😉

EDIT: BTW, if the bulb reports that it's not able to support that feature, shouldn't herdsman catch that message, cancel the reporting timer and print something like "warn - Device '0x001788011040a46b' doesn't allow reporting functionality."? Should I open a feature (or bug) request in zigbee-hedsman repository?

[Koenkk]

Yes please open a bug at herdsman, can you also provide the herdsman debug logging in this report when setting up the reporting fails?

To enable herdsman debug logging, see https://www.zigbee2mqtt.io/information/debug.html#zigbee-herdsman-debug-logging

[Odianosen25]

Hello @Koenkk,

Thanks again for this great software. I am using this feature and I have the following setup

• Have 2 Philips Hue Bulbs in a Group
• Have the Philips Hue Dimmer which I binded to the Philips Hue Bulbs Group
• When I turn on/off the Group using the dimmer, no report is send back from the group, neither the bulbs
• If I increase the brightness with it, the bulbs report their brightness level individually, but nothing on the group
• Also though the brightness is reported by the bulbs individually (not the group), the state reports as OFF, even though the bulbs are ON; of course there is no brightness without being ON anyway

I am on 1.10 .0 and using the CC2531.

Regards

[chaliluc]

After installing the latest dev branch, I activated reporting in my configuration.yaml for 3 Fyrtur roller blinds but it only works for two of them.

Below is an extract of my configuration.yaml file:
advanced: report: true devices: '0xd0cf5efffeea6130': friendly_name: salon_store_1 retrieve_state: true '0xd0cf5efffeef59d3': friendly_name: salon_store_2 retrieve_state: true '0xd0cf5efffed98efe': friendly_name: salon_store_3 retrieve_state: true

The database.db file for those 3 devices looks like this:
{ "id":6, "type":"EndDevice", "ieeeAddr":"0xd0cf5efffeea6130", "nwkAddr":37388, "manufId":4476, "manufName":"IKEA of Sweden", "powerSource":"Battery", "modelId":"FYRTUR block-out roller blind", "epList":[ 1 ], "endpoints":{ "1":{ "profId":260, "epId":1, "devId":514, "inClusterList":[ 0, 1, 3, 4, 5, 32, 258, 4096, 64636 ], "outClusterList":[ 25, 4096 ], "clusters":{ "genBasic":{ "attributes":{ "modelId":"FYRTUR block-out roller blind", "manufacturerName":"IKEA of Sweden", "powerSource":3, "zclVersion":3, "appVersion":34, "stackVersion":99, "hwVersion":1, "dateCode":"20190311", "swBuildId":"2.2.007" } }, "closuresWindowCovering":{ "attributes":{ "currentPositionLiftPercentage":0 } }, "genPowerCfg":{ "attributes":{ "batteryPercentageRemaining":85 } } }, "binds":[ { "cluster":1, "type":"endpoint", "deviceIeeeAddress":"0x00124b00194306a5", "endpointID":1 }, { "cluster":258, "type":"endpoint", "deviceIeeeAddress":"0x00124b00194306a5", "endpointID":1 } ] } }, "appVersion":34, "stackVersion":99, "hwVersion":1, "dateCode":"20190311", "swBuildId":"2.2.007", "zclVersion":3, "interviewCompleted":true, "meta":{ "configured":2, "reporting":1 }, "lastSeen":1583860545569 } { "id":7, "type":"EndDevice", "ieeeAddr":"0xd0cf5efffeef59d3", "nwkAddr":32168, "manufId":4476, "manufName":"IKEA of Sweden", "powerSource":"Battery", "modelId":"FYRTUR block-out roller blind", "epList":[ 1 ], "endpoints":{ "1":{ "profId":260, "epId":1, "devId":514, "inClusterList":[ 0, 1, 3, 4, 5, 32, 258, 4096, 64636 ], "outClusterList":[ 25, 4096 ], "clusters":{ "genBasic":{ "attributes":{ "modelId":"FYRTUR block-out roller blind", "manufacturerName":"IKEA of Sweden", "powerSource":3, "zclVersion":3, "appVersion":34, "stackVersion":99, "hwVersion":1, "dateCode":"20190311", "swBuildId":"2.2.007" } }, "closuresWindowCovering":{ "attributes":{ "currentPositionLiftPercentage":19 } }, "genPowerCfg":{ "attributes":{ "batteryPercentageRemaining":100 } } }, "binds":[ { "cluster":1, "type":"endpoint", "deviceIeeeAddress":"0x00124b00194306a5", "endpointID":1 }, { "cluster":258, "type":"endpoint", "deviceIeeeAddress":"0x00124b00194306a5", "endpointID":1 } ] } }, "appVersion":34, "stackVersion":99, "hwVersion":1, "dateCode":"20190311", "swBuildId":"2.2.007", "zclVersion":3, "interviewCompleted":true, "meta":{ "configured":2, "reporting":1 }, "lastSeen":1583860591537 } { "id":8, "type":"EndDevice", "ieeeAddr":"0xd0cf5efffed98efe", "nwkAddr":51147, "manufId":4476, "manufName":"IKEA of Sweden", "powerSource":"Battery", "modelId":"FYRTUR block-out roller blind", "epList":[ 1 ], "endpoints":{ "1":{ "profId":260, "epId":1, "devId":514, "inClusterList":[ 0, 1, 3, 4, 5, 32, 258, 4096, 64636 ], "outClusterList":[ 25, 4096 ], "clusters":{ "genBasic":{ "attributes":{ "modelId":"FYRTUR block-out roller blind", "manufacturerName":"IKEA of Sweden", "powerSource":3, "zclVersion":3, "appVersion":34, "stackVersion":99, "hwVersion":1, "dateCode":"20190311", "swBuildId":"2.2.009" } }, "closuresWindowCovering":{ "attributes":{ "currentPositionLiftPercentage":17 } } }, "binds":[ { "cluster":1, "type":"endpoint", "deviceIeeeAddress":"0x00124b00194306a5", "endpointID":1 }, { "cluster":258, "type":"endpoint", "deviceIeeeAddress":"0x00124b00194306a5", "endpointID":1 } ] } }, "appVersion":34, "stackVersion":99, "hwVersion":1, "dateCode":"20190311", "swBuildId":"2.2.009", "zclVersion":3, "interviewCompleted":true, "meta":{ "configured":2, "reporting":1 }, "lastSeen":1583860579950 }

The first one (id = 6) is the one that doesn't work, while the two others (id = 7 and id=8) are reporting their positions just fine.

Another very strange thing is that those 3 blinds are the exact same, purchased at the same time, and run the latest firmware. However, the third one doesn't report on its battery, and has the complete attribute "genPowerCfg" missing in the database.db.

Is there something to do to fix this?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[shirou93]

Report feature work with xiaomi bulbs? This vendor not in table.

[magnushacker]

On https://www.zigbee2mqtt.io/information/report.html#support, there is a footnote that says "The color/brightness of a Trådfri bulb can be changed while the state=off, it also reports back the change.". This doesn't work for me.

I'd like to use this to set the brightness of my bedside lamp to 10 during the night, so that it's not super bright the first time I turn it on in the morning. The remote is bound to a group with the bulb in it, so I can control the bulb directly without z2m. Using the remote to turn on however always sets the same brightness as when I turned it off with the remote.

[MyKEms]

I experience same issue. I use Ikea toggle switch with bulb paired into the same group. If I control light via HA the status of light is updated.

However toggle switch button will report an action to the z2m but the bulb will not report status on/off back to z2m.

UPDATE I had reporting enabled but it was not reporting status back to the Z2M. I disabled this feature and re-enabled and now I can see status even it’s not controlled directly via Z2M.

[jd1900]

It seems that new Gledopto LED controllers (Zigbee LED controller RGB + CCT pro model (GL-C-008P)) support reporting. At least for state and brightness.

[elgerg]

@jd1900 How did you set up and configure this for the GL-C-008P?

I have one and when the device is altered using a remote there is no report of the change.

This is the remote for the led controller:
https://www.aliexpress.com/item/1005002797042241.html?spm=a2g0s.9042311.0.0.12d84c4dSCBzTS

[elgerg]

Ok, i have managed to figure out what needs setting to get the on/off state:

Does anyone know how to get it to report the change in brightness/colour?

Thanks
Alex