home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.14k stars 29.81k forks source link

Deconz: Unexpected light effect type #114430

Closed pimw1 closed 4 months ago

pimw1 commented 5 months ago

The problem

Since 2024.4.0b0 (and also 2024.4.0b1), deCONZ gives the following error during reboot:

Logger: pydeconz.models.light.light Source: components/deconz/light.py:203 First occurred: 10:38:07 (8 occurrences) Last logged: 10:38:07

Unexpected light effect type 0x5ec4 Unexpected light effect type 0xc2c Unexpected light effect type 0x6041 Unexpected light effect type 0x5a55

I've created an diagnostic file and added it to this issue. I've already done analysis on this file by checking which unique product id and product names are related to which effect type. From this analysis, the following can be concluded:

0x5ec4 -> 'productid': 'Philips-LCA006-1-A60HECLv1', 'productname': 'Hue color lamp' (configured 'name': 'Gang Lamp Plafond') 0x5a55 -> 'productid': 'Philips-LCA006-1-A60HECLv1', 'productname': 'Hue color lamp' (configured 'name': 'Gang Lamp Staand') 0xc2c -> 'productid': 'Philips-LCE002-1-E14ECLv2', 'productname': 'Hue color candle' (configured 'name': 'Keuken Lamp Keukenblok 3') 0x6041 -> 'productid': 'Philips-LCA001-5-A19ECLv6', 'productname': 'Hue color lamp' (configured 'name': 'Slaapkamer Lamp Lantaarn')

I've related these specific lights to the gui of deconz, by making screenshots of the Hue Effects cluster and Hue Entertainment cluster of the respective lights:

0x5ec4 -> 'productid': 'Philips-LCA006-1-A60HECLv1', 'productname': 'Hue color lamp', 'name': 'Gang Lamp Plafond': image image

0x5a55 -> 'productid': 'Philips-LCA006-1-A60HECLv1', 'productname': 'Hue color lamp', 'name': 'Gang Lamp Staand' image image

0xc2c -> 'productid': 'Philips-LCE002-1-E14ECLv2', 'productname': 'Hue color candle', 'name': 'Keuken Lamp Keukenblok 3': image image

0x6041 -> 'productid': 'Philips-LCA001-5-A19ECLv6', 'productname': 'Hue color lamp', 'name': 'Slaapkamer Lamp Lantaarn' image image

Good to know is that the issue appeared yesterday after installing the new Home Assistant beta. During that same day, i also installed the new version of Deconz: v2.26.3. So i cannot be 100% sure if this is due to Home Assistant beta or the new version of Deconz (i upgraded deconz from v2.25.3 -> v2.26.3).

What version of Home Assistant Core has the issue?

2024.4.0b1

What was the last working version of Home Assistant Core?

core-2024.3.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

deCONZ

Link to integration documentation on our website

https://www.home-assistant.io/integrations/deconz/

Diagnostics information

home-assistant_deconz_2024-03-29T09-38-37.138Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: pydeconz.models.light.light
Source: components/deconz/light.py:203
First occurred: 10:38:07 (8 occurrences)
Last logged: 10:38:07

Unexpected light effect type 0x5ec4
Unexpected light effect type 0xc2c
Unexpected light effect type 0x6041
Unexpected light effect type 0x5a55

Additional information

No response

home-assistant[bot] commented 5 months ago

Hey there @kane610, mind taking a look at this issue as it has been labeled with an integration (deconz) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `deconz` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign deconz` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


deconz documentation deconz source (message by IssueLinks)

Kane610 commented 5 months ago

This is a change on deconz side. I've pinged deconz devs to understand the cause

Kane610 commented 5 months ago

Got the response that you should report it on deconz github. We can leave this open until you progress with them

pimw1 commented 5 months ago

Thank you, i've created an issue on the deconz github: https://github.com/dresden-elektronik/deconz-rest-plugin/issues/7686

pimw1 commented 4 months ago

The issue is solved with v2.27.0-beta. Thank you for your help @Kane610

Kane610 commented 4 months ago

Happy to hear it worked out! Good job 🎉

derekcentrico commented 4 months ago

@pimw1 doesn't this still need a PR to pull the new API version into HA? I don't see it but may have missed it.

pimw1 commented 4 months ago

The problem occurs when using the latest stable deconz docker container (v2.26.3). The latest deconz addon for home assistant is v2.25.3, where this bug is not happening. Whenever v2.27.0-beta comes out of beta, this version can be used to create a new version of the addon.

The root cause was a bug in a DDF, which is fixed in v2.27.0-beta. Therefore, there is no need to update/patch the deconz integration in Home Assistant or to apply further fixes in any API in the deconz Docker Container.