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.05k stars 29.72k forks source link

UP Floodlight light switch no longer maintains on / off state in 2024.2.1 #110570

Closed TazUk closed 6 months ago

TazUk commented 6 months ago

The problem

WIth Unifi Protect v2.11.21 on Cloud Key+ running UnifiOS 3.2.10 and UP Floodlight Firmware v1.12.0 HomeAssistant Container 2024.2.1

Since updating from 2024.1.6 I can no longer properly control the UP Floodlight from HomeAssistant.

Starting with the light off and turning it on using the light entity does turn the floodlight on (and brightness percentage is passed successfully if performed with a service call) however the light entity almost immediately shows as off again, while in the UnifiProtect application the floodlight remains on. The light can then only be turned off from within Unifi Protect.

When changing the light state in the UnifiProtect application, HA does not reflect any changes.

Light worked correctly before I updated HomeAssistant from 2024.1.6 to 2024.2.1

Please note that I have tested and seen the same behaviour after restarts of:

What version of Home Assistant Core has the issue?

core-2024.2.1

What was the last working version of Home Assistant Core?

core-2024.1.6

What type of installation are you running?

Home Assistant Container

Integration causing the issue

unifiprotect

Link to integration documentation on our website

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

Diagnostics information

config_entry-unifiprotect-7dcfd9a976d7b1b57cf55a867ab4816a.json

Example YAML snippet

service: light.turn_on
target:
  entity_id: light.garden_floodlight
data:
  brightness_pct: 60

Anything in the logs that might be useful for us?

No log entries recorded.

Additional information

No response

home-assistant[bot] commented 6 months ago

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

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


unifiprotect documentation unifiprotect source (message by IssueLinks)

AngellusMortis commented 6 months ago

@home-assistant add-label needs-more-information

AngellusMortis commented 6 months ago

Missing debug logs.

TazUk commented 6 months ago

Debug logs:

Tests:

home-assistant_unifiprotect_2024-02-14T18-30-14.018Z.log

markunik commented 6 months ago

I've been having the same problem recently with all my Unifi FloodLights. I think the issue began after 2024.2.1 HA core update. My setup info: UNVR with Unifi OS 3.2.9 running Unifi Protect 2.11.21 with devices UP-FloodLight firmware 1.12.0. Will be waiting for an update on this matter... Thanks.