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
73.45k stars 30.69k forks source link

ZHA: identify device - only when it's on? #104763

Closed ChristophCaina closed 8 months ago

ChristophCaina commented 11 months ago

The problem

OK, I'm Not Sure If this is really an issue or maybe a Feature / Change request... Or If it is even possible at all...

We have some Christmas Decoration, which is Equipt with a zigbee light bulb.

The zha Integration provides a Button "identify" - euch will Trigger a flashing / blinking of the lightbulb.

But: This is only working, when the light bulb is switched on. I think, it would make Sense, If the Button would Trigger the effect Always, Independent of the state...

What version of Home Assistant Core has the issue?

2023.12.b0

What was the last working version of Home Assistant Core?

Unknown

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Zha

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 11 months ago

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

Code owner commands Code owners of `zha` 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 zha` 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)


zha documentation zha source (message by IssueLinks)

TheJulianJES commented 11 months ago

This is only working, when the light bulb is switched on.

The implementation of the identify command is likely incorrect on your bulb then. I doubt this can be fixed properly. Please upload the device diagnostics file though. It can be found on the device page, three dots, download diagnostics.

ChristophCaina commented 11 months ago

Thanks. You are right, it is only thus specific bulb... Others are working as expected.

Here are the device information & diagnostics... zha-c4b8635ee52ce7e7eebcdac6d44af482-LEDVANCE P40S TW-25be6d7667fbe50e9673d5a10df74b7e.json

TheJulianJES commented 11 months ago

Hmm, LEDVANCE/Osram is definitely not known for a great implementation of everything Zigbee. The best we could do is add a quirk to intercept the identify command, then send an on() command, send the identify command, and finally send off() with a delay.

Otherwise, you could have a look if LEDVANCE provides a firmware update for your bulb here. OTA updates for LEDVANCE can be enabled in your configuration.yaml. More info is available in the HA docs and in the community wiki.

ChristophCaina commented 11 months ago

So... I guess, there's no new firmware available?

Not 100% sure, if MAYBE an earlier update attempt was successfull...

2023-12-04 00:18:10.438 DEBUG (MainThread) [zigpy.ota.provider] Ledvance: Finished downloading firmware update list

2023-12-04 00:18:10.600 DEBUG (MainThread) [zigpy.zcl] [0x9805:1:0x0019] OTA query_next_image handler for 'LEDVANCE P40S TW': field_control=1, manufacturer_id=4489, image_type=164, current_file_version=34825552, hardware_version=2, model='P40S TW'
2023-12-04 00:18:10.601 DEBUG (MainThread) [zigpy.ota.provider] Downloading https://api.update.ledvance.com/v1/zigbee/firmwares/download?Company=4489&Product=164&Version=2.19.101.80 for ImageKey(manufacturer_id=4489, image_type=164)
2023-12-04 00:18:10.902 DEBUG (MainThread) [zigpy.ota.provider] ImageKey(manufacturer_id=4489, image_type=164): version: 34825552, hw_ver: (None, None), OTA string: P40S_TW

2023-12-04 00:18:10.902 DEBUG (MainThread) [zigpy.ota.provider] Finished downloading 198246 bytes from https://api.update.ledvance.com/v1/zigbee/firmwares/download?Company=4489&Product=164&Version=2.19.101.80 for ImageKey(manufacturer_id=4489, image_type=164) ver 34825552
2023-12-04 00:18:10.903 DEBUG (MainThread) [zigpy.zcl] [0x9805:1:0x0019] OTA image version: 34825552, size: 198246. Update needed: False

But even if: there's no change on the device... maybe, a quirk would be an idea?

issue-triage-workflows[bot] commented 8 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.