Not attribute reporting devices (Lights)

According to Zigbee specifications, devices like switches and lights should report attribute changes to the coordinator. Some vendors, however, do not implement attribute reports correctly. Vendors that use an old SDK from ATMEL for Zigbee version 1.x are especially known for this issue.

Signify's Philips Hue has been moving away from ATMEL chips. Newer devices with Silicon Labs chips (lights also feature Bluetooth support) should report attribute changes correctly (at least after re-pairing with latest firmware).

Some older GLEDOPTO and "MUELLER LICHT INT" devices are also known for their wrong implementation of this feature.

For all lights, ZHA is polling the status from the devices in a random interval. All Philips Hue lights – even those that also send attribute reports – are polled in a way smaller interval (every couple of minutes). Of course, polling is way slower than the Zigbee devices "pushing" attribute changes. This is especially noticeable when a controller/remote directly bound to a Zigbee devices changes the device's status, as ZHA doesn't see the change until it polls the light (if the device isn't sending any attribute reports).

Controllers/remotes are only sending commands to its bound group, so the coordinator can then catch the commands from the controllers and the status changes from the lights in the group => full control of what is happening in the system.