The JSON result for a device from the deCONZ REST API is devided into several section (e.g. config or state). For a long time I was convinced the deCONZ websocket only emits events for state changes and the binding only listens to those state changes. As some devices places their temperature values and especially their battery values in the config part the binding never - only during initialization - updated them. Today I looked into the documentation again and found that config events are triggered too. I immediately implemented a handling for it:
