search

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.31k stars 30.62k forks source link

Unifi integration shows device_tracker status for wi-fi devices incorrectly #104576

Closed Spirituss closed 5 months ago

Spirituss commented 11 months ago

The problem

Wi-fi esp device added as "tracked" in Unifi integration. It is permanently online, Unifi controller web site shows it as online device, but HA integration shows "offline" all the time. The same situation is for many devices.

Снимок экрана 2023-11-27 в 10 03 18

What version of Home Assistant Core has the issue?

core-2023.11.3

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

Unifi

Link to integration documentation on our website

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

Diagnostics information

I find HA devices in Unifi API info ($ip/api/s/default/stat/device/) and see the following client attributes, which have correct (updated) values, while HA shows "not home" all the time:

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

g3r0nim00 commented 10 months ago

same for me... HA: Core 2023.12.4 (updated around 28/12/23 12:00 GMT+1) Supervisor 2023.12.0 Operating System 11.2

UI: UDM SE UniFi OS v3.2.7 (updated at 13/12/23 03:00 GMT+1) Network 8.0.24 (updated at 14/12/23 03:00 GMT+1)

reloading the integration turns (wireless) entities to 'home' for a few minutes and then they appear 'away' (although they are connected for hours to the SSID/AP). This seems to have started somewhere around 30/12/2023, but I can't see any changes in my systems (no HA related updates, no UI related updates around that time). Already removed & re-added the integration, changed the password, restarted HA, ... Currently have the upgrade to Network 8.0.26 pending... (I'm testing an older HA test setup against the current 8.0.24 UI Network release)

for what it's worth, I had the same issues with the following combination (older HA test-vm): HA: Core 2023.12.1 Supervisor 2023.12.0 Operating System 11.2

UI: (didn't change) UDM SE UniFi OS v3.2.7 (updated at 13/12/23 03:00 GMT+1) Network 8.0.24 (updated at 14/12/23 03:00 GMT+1)

mattiss commented 10 months ago

Hi, I also had the issue, and can confirm it all started right after the upgrade to UniFi OS 3.2.7 I followed some of the advice found in this thread and went on with the restarting of my UDM Pro and all the switches and access points. It seems to have done the trick and I have not experienced the issue for the past 3 days.🤞 Hope this helps (and stays stable...)

g3r0nim00 commented 10 months ago

Hi, I also had the issue, and can confirm it all started right after the upgrade to UniFi OS 3.2.7 I followed some of the advice found in this thread and went on with the restarting of my UDM Pro and all the switches and access points. It seems to have done the trick and I have not experienced the issue for the past 3 days.🤞 Hope this helps (and stays stable...)

for me it didn't start right after the UniFi OS upgrade... it ran without issues for +/- 16 days after 3.2.7 was installed

Kane610 commented 10 months ago

Always start by restarting the full unifi system when observing issues

danmalone326 commented 10 months ago

I wanted to update @pascal-de-ladurantaye 's automation to restart the Unifi integration only when necessary and while writing this up, found some additional information that maybe can help with troubleshooting this issue.

To detect if the Unifi integration needs to be restarted, I wanted a wired device that should always be Home. Even better was the device tracker for the UDMPRO itself. Using that, I added a condition to the automation to only continue if the UDMPRO is not Home. With that additional condition, I can trigger it every minute without any unnecessary disruption. I was also able to find the needed entry_id in the UI (mostly) by going to the integration page, click on the 3-dots menu, right click on Download diagnostics and copy link address. Paste that link into your text editor and the entry_id is everything after the last /. http://homeassistant.local:8123/api/diagnostics/config_entry/1f69d1ebf31473379add24209f92ec9b

Here's my full automation:

alias: Reload Unifi integration when needed
description: ""
trigger:
  - platform: time_pattern
    hours: "*"
    minutes: "*"
    seconds: "45"
condition:
  - condition: not
    conditions:
      - condition: state
        entity_id: device_tracker.udmpro
        state: home
action:
  - service: homeassistant.reload_config_entry
    data:
      entry_id: 1f69d1ebf31473379add24209f92ec9b
mode: single

Since enabling this automation, my family has been happily (?) getting their "it's garbage day" notifications when they get home. I've also been looking closer at the device tracker states to see if detect this sooner without causing a restart loop. What I found was that when this issue occurs, the Person entity and the device_tracker entity associated with the person both change from Home to unavailable, while the UDMPRO changes from Home, to Away for 15 seconds, then unavailable. Other Unifi devices, switch and APs, had the same Home->Away->unavailable changes, while all other wired and wireless devices were Home->unavailable. Maybe this can help chip away at the problem. Let me know if there is anything else I can provide.

Current HA: Core 2023.12.4 Supervisor 2023.12.0 Operating System 11.2 Frontend 20231208.2

UDMPRO versions and install dates Unifi OS 3.2.7 - December 14, 3:22:31 AM Network 8.0.24 - December 14, 3:32:10 AM Protect 2.10.0 - December 19, 3:21:35 AM Access 1.21.9+4628 - December 22, 3:20:46 AM

First occurrence of problem - December 24, 3:42:45am Since then, I've had recurrences anywhere between 5 minutes and 5 days and can't find any pattern.

g3r0nim00 commented 10 months ago

Always start by restarting the full unifi system when observing issues

I will... but before restarting the UI setup I wanted to see if I encounter the same issues in a lower version of HA-core.

I'm not sure if the following observation makes any sense (or was shared before, sorry in that case)? When I lastly reloaded the integration an hour ago, my iPhone was detected 'home'. As expected, it switched to 'away' after some time. But when switched to 'away', the attribute section of the entity changes: all wireless related info seems to be gone... Image 03-01-2024 at 14 24 Image 03-01-2024 at 14 47

rtsundland commented 10 months ago

Having this issue as well. Reload integration, works for about an hour, then devices go away but they are definitely on the network. I reload (again) and they immediately come back.

UniFi OS v3.2.7 HA 2023.12.4

Kane610 commented 10 months ago

As expected, it switched to 'away' after some time. But when switched to 'away', the attribute section of the entity changes: all wireless related info seems to be gone...

That's by design

ellmout commented 10 months ago

Hi everyone, I had the same bug, i fully restart my UDM PRO, and the bug was gone. It's been working for 5 days now.

mikehawke1337 commented 10 months ago

I can confirm that restarting all Unifi gear did not solve the problem for me. Devices are home for about two hours and then go away until I restart the Unifi HASS integration. Automating the integration restart is a workaround, but far from a solution.

Can also confirm that this behavior started with the 3.2.7 upgrade of Unifi OS, bundled with Network application 7.5.187 (I am not on 8.x yet)

Edit: Tested multiple things. I had a Unifi SSO account for the HASS integration before and changed to a local account, completely deleted and re-added the integration and restarted integration, HASS, and Unifi in multiple different orders. Result: Now the clients go away after one hour instead of two. No log entries that suggest any issue, it appears that there is just some form of timeout and the integration isn't trying to re-login?

freddeh commented 10 months ago

I can confirm I have the same issues. Reloading helps for the moment.

ellmout commented 10 months ago

Hi everyone, I had the same bug, i fully restart my UDM PRO, and the bug was gone. It's been working for 5 days now.

Oh my bad, its stop working again this morning at 3am ! Had to reboot again.

mikehawke1337 commented 10 months ago

@Kane610 I just updated to Unifi Network 8.0.26 on a UDM with 3.2.7 just for this bug, stable for 4 hours so far (before it always failed 1-2 hours in). Will keep you posted.

Can confirm that another non-UDM Unifi controller on 8.0.24 has never had this issue, leading me to believe it's either a specific UDM issue or an issue with Unifi Network <8.0.x

Edit: 7+ hours in, it looks like 8.0.26 fixes the problem. It's the Release Candidate version, which I usually do not like to install, but it did not cause any noticeable issues for me at least. May be a solution for others here, too.

g3r0nim00 commented 10 months ago

for me it's also stable since I've upgraded to Network 8.0.26 on the 3rd of january... (no reboot, just upgrade of network app). Leaving/returning to my home correctly translates into the HA home/away state...

rtsundland commented 10 months ago

Not sure when it happened, but my UDM and HA NUC was restarted on 1/3, I'm now on 8.0.26 and 3.2.7 and can also confirm the device tracker is working again.

5bomen commented 10 months ago

I am using the UDM Pro, latest Network version, rebooted all Unifi devices, but still experiencing presense detection issues. Somehow HA looses visibility on all persons after a short time.

HA: Core 2024.1.2 Supervisor 2023.12.0 Operating System 11.3 Frontend 20240104.0

UDM: Network 8.0.26 UniFi OS 3.2.7

rtsundland commented 9 months ago

Broken again as of this morning.

UniFi OS v3.2.7 HA 2023.12.4

Kane610 commented 9 months ago

I've put up a PR to add some more logging towards web sockets https://github.com/home-assistant/core/pull/108265 I have no idea if this will give anything

Kane610 commented 9 months ago

I've provided an additional log with the upcoming 2024.2.0 release (https://github.com/home-assistant/core/pull/109167)

By configuring debug logging only for the integration and not library it will not be overly many prints

logger:
  default: info
  logs:
    homeassistant.components.unifi: debug

This log should be seen every minute and then we can conclude if web socket stops altogether 2024-01-30 21:50:24.861 DEBUG (MainThread) [homeassistant.components.unifi] Last received websocket timestamp: 2024-01-30 20:50:24.438440+00:00

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.

Spirituss commented 8 months ago

Bump

fxfitz commented 8 months ago

Bump. After this email today, I noticed I indeed was still having the issue.

Kane610 commented 8 months ago

@Spirituss and @fxfitz follow these instructions and share your observations https://github.com/home-assistant/core/issues/104576#issuecomment-1919832446

fxfitz commented 8 months ago

Alright, so before running this test I rebooted both Home Assistant and my Unifi Dream Wall. Currently running HA Core 2024.2.1 and UnifiOS 3.2.9.

Around 6:36am local time, I turned off WiFi on my cell phone. This should be the snippet covering that time range:

2024-02-16 06:34:08.992 DEBUG (MainThread) [homeassistant.components.unifi] Last received websocket timestamp: 2024-02-16 12:34:08.989719+00:00
2024-02-16 06:35:08.993 DEBUG (MainThread) [homeassistant.components.unifi] Last received websocket timestamp: 2024-02-16 12:35:07.688735+00:00
2024-02-16 06:36:08.993 DEBUG (MainThread) [homeassistant.components.unifi] Last received websocket timestamp: 2024-02-16 12:36:08.833788+00:00
2024-02-16 06:37:08.994 DEBUG (MainThread) [homeassistant.components.unifi] Last received websocket timestamp: 2024-02-16 12:37:08.198545+00:00
2024-02-16 06:38:08.995 DEBUG (MainThread) [homeassistant.components.unifi] Last received websocket timestamp: 2024-02-16 12:38:08.989717+00:00
2024-02-16 06:39:08.995 DEBUG (MainThread) [homeassistant.components.unifi] Last received websocket timestamp: 2024-02-16 12:39:08.703131+00:00
2024-02-16 06:40:08.999 DEBUG (MainThread) [homeassistant.components.unifi] Last received websocket timestamp: 2024-02-16 12:40:08.996401+00:00
2024-02-16 06:41:09.000 DEBUG (MainThread) [homeassistant.components.unifi] Last received websocket timestamp: 2024-02-16 12:41:08.312586+00:00
2024-02-16 06:42:09.001 DEBUG (MainThread) [homeassistant.components.unifi] Last received websocket timestamp: 2024-02-16 12:42:08.663108+00:00
2024-02-16 06:43:09.001 DEBUG (MainThread) [homeassistant.components.unifi] Last received websocket timestamp: 2024-02-16 12:43:08.749165+00:00
2024-02-16 06:44:09.002 DEBUG (MainThread) [homeassistant.components.unifi] Last received websocket timestamp: 2024-02-16 12:44:08.755097+00:00

So, we're seeing a connection from Unifi.

At the time of writing this (about 6:49am local), the device_tracker is still showing "home" in home assistant:

CleanShot 2024-02-16 at 06 48 57@2x

Also, within UniFi, that same device is showing up as "offline":

CleanShot 2024-02-16 at 06 49 52@2x

fxfitz commented 8 months ago

Blah. And then right after I posted the above, I flipped to "not home" :shakes-fist: I thought I waited enough time. :-(

CleanShot 2024-02-16 at 06 52 17@2x

I can run a longer test later, but was seeing what I could get done before work.

Either way, it seemed like it took way too long to flip to "not home", but the integration is probably getting the data directly from Unifi? Next time I'll keep a closer eye to see when the Unifi console flips the device from "online" to "offline". In the screenshot above, you can see that the "Uptime" column has 6:41am, which is about five minutes after I turned the WiFi off on the cell phone. :-/

Kane610 commented 8 months ago

The integration bases the home/away status on when it last received updated data about the client and does some internal checks if it should be valid after that it will set a timer to count down based on what your connection time is set to in the integration (default is 300 seconds). So that would mean that UniFi still send data about your device even though you marked it as offline.

5bomen commented 8 months ago

Since the upgrade of HA to 2024.2.2 yesterday the status of the Unifi devices themselves is no longer reported away. But the status of the phones is still not reported correctly. Which is actually not helping as I used the away status of my UDM to trigger a reload of the integration.

My log is now full with Unifi errors: 2024-02-18 11:43:17.117 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 11:43:17.118 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 11:49:29.633 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 11:49:29.634 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 11:52:42.036 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 11:52:42.037 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 11:55:46.427 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 11:55:46.428 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 12:09:02.065 ERROR (MainThread) [aiounifi.interfaces.messages] Bad JSON data '' 2024-02-18 12:24:35.961 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 12:24:35.962 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 12:29:41.270 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 12:29:41.271 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 12:33:31.049 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 12:33:31.050 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 12:48:52.392 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 12:48:52.393 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 13:30:49.157 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 13:30:49.158 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 13:34:15.137 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 13:34:15.138 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 13:38:43.898 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 13:38:43.898 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 13:55:30.457 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 13:55:30.458 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 13:59:53.646 ERROR (MainThread) [aiounifi.interfaces.messages] Bad JSON data '' 2024-02-18 14:00:21.552 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 14:00:21.553 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 14:03:31.950 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 14:03:31.951 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 14:12:09.198 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 14:12:09.198 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected

Op vr 16 feb 2024 om 16:52 schreef Robert Svensson @.***

:

The integration bases the home/away status on when it last received updated data about the client and does some internal checks if it should be valid after that it will set a timer to what your connection time is set to in the integration (default is 300 seconds). So that would mean that UniFi still send data about your device even though you marked it as offline.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/104576#issuecomment-1948702365, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASNL62ALFM2YMPVMVOSXOTTYT56DJAVCNFSM6AAAAAA73RS5LGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBYG4YDEMZWGU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

5bomen commented 8 months ago

Unifi versions: Network 8.0.28, UniFi OS 3.2.9

Op zo 18 feb 2024 om 14:30 schreef Ronald Bosch @.***>:

Since the upgrade of HA to 2024.2.2 yesterday the status of the Unifi devices themselves is no longer reported away. But the status of the phones is still not reported correctly. Which is actually not helping as I used the away status of my UDM to trigger a reload of the integration.

My log is now full with Unifi errors: 2024-02-18 11:43:17.117 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 11:43:17.118 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 11:49:29.633 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 11:49:29.634 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 11:52:42.036 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 11:52:42.037 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 11:55:46.427 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 11:55:46.428 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 12:09:02.065 ERROR (MainThread) [aiounifi.interfaces.messages] Bad JSON data '' 2024-02-18 12:24:35.961 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 12:24:35.962 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 12:29:41.270 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 12:29:41.271 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 12:33:31.049 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 12:33:31.050 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 12:48:52.392 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 12:48:52.393 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 13:30:49.157 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 13:30:49.158 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 13:34:15.137 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 13:34:15.138 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 13:38:43.898 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 13:38:43.898 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 13:55:30.457 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 13:55:30.458 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 13:59:53.646 ERROR (MainThread) [aiounifi.interfaces.messages] Bad JSON data '' 2024-02-18 14:00:21.552 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 14:00:21.553 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 14:03:31.950 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 14:03:31.951 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected 2024-02-18 14:12:09.198 ERROR (MainThread) [aiounifi.interfaces.connectivity] UniFi websocket error: 'Received frame with non-zero reserved bits' 2024-02-18 14:12:09.198 ERROR (MainThread) [homeassistant.components.unifi] Websocket disconnected

Op vr 16 feb 2024 om 16:52 schreef Robert Svensson < @.***>:

The integration bases the home/away status on when it last received updated data about the client and does some internal checks if it should be valid after that it will set a timer to what your connection time is set to in the integration (default is 300 seconds). So that would mean that UniFi still send data about your device even though you marked it as offline.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/104576#issuecomment-1948702365, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASNL62ALFM2YMPVMVOSXOTTYT56DJAVCNFSM6AAAAAA73RS5LGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBYG4YDEMZWGU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

Kane610 commented 8 months ago

@5bomen if you downgrade to last where it last worked, does it start working again? Are you sure you didn't upgrade UniFi or change any configuration?

issue-triage-workflows[bot] commented 7 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.

Spirituss commented 7 months ago

Bump

issue-triage-workflows[bot] commented 7 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.

Wojcioo commented 7 months ago

Bump

issue-triage-workflows[bot] commented 6 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.

Spirituss commented 6 months ago

bump

issue-triage-workflows[bot] commented 6 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.

Spirituss commented 6 months ago

bump Still is the case

issue-triage-workflows[bot] commented 5 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.