New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unifi Switch Port Error #25893
Comments
I have the same problem I think
|
I have the same:
Plus another error in this component: |
This seems to happen when something gets disconnected from the network, I'm investigating what can be the cause of this. |
Hey guys! Anyone interested in verifying this fix in the betas starting later today? |
Absolutely. I'll give it a go and report back. |
So what you need to do is also to go into the entity registry and remove those POE control switches that are reporting that issue. The reason for this is that I think that a UniFi bug which causes wireless devices to show as wired devices triggers these faulty poe control switch entities |
Apologies for the lack of updates—believe it or not my USG failed on me and I'm waiting for a replacement... 🙄 |
@aaronwolen too bad :/. Fortunately you don't need the USG to test this, only a controller and a POE switch |
I'd be happy to help test...I too am seeing this error. You mention deleting the POE control switches in the entity registry. Can you help me understand which entities to delete? How do I identify them? |
Any difference after 0.100? |
Unfortunately, I've found the errors to be too inconsistent. Sometimes after a restart I don't get them. I didn't receive them on 0.100.2, but the device_tracker component is blowing up for Unifi, so I'm back to running 0.99.3 (my home automation relies heavily on presence). |
Describe blowing up please :) |
Thanks Kane610! Now that I have device_tracker working again, I'm not seeing these errors on 0.100.2. Re: device_tracker: I still had it configured in YAML. Apparently I missed the breaking notes to remove it. |
I still have this problem in 0.101.2
|
any updates on this? Still seeing it in the latest (0.102.3) release. |
I have this on 0.102.3 on my unifi with 1 UniFi AP-nanoHD + UniFi AP-AC-LR + 1 UniFi Switch 8 POE-60W:
|
This issue seems to be back in 0.104:
|
+1 Seeing this behaviour on 104 also |
+1 Seeing this behaviour on 104.3 also |
+1 Seeing this behavior on 104.3 as well. |
+1 seeing this. Can't start homeassistant, can't remove integration(through homeassistant UI) |
+1 seeing the same - my indicates 34k times! |
I'm seeing this in 105.2. Can't figure out how to turn it off in the logs either. |
+1 here... I also am experincing this. Can we re-open this or should I log a new one? |
Started seeing it today as well. Over 2K times in the last few hours. |
+1 on this issue for me |
been happening for months now for me |
@wbradmoore Your posted reminded me to share what has worked for me: Simply removing and re-adding the integration. For whatever reason, it solved it for me. |
Home Assistant release with the issue:
0.97.2
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io VM
Component/platform:
https://www.home-assistant.io/components/unifi/#switch
Description of problem:
After installation of current 0.97.2 upgrade to resolve unifi "upgradeable" issue, the new switch issue appeared.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):N/A - Unifi configured through Integration
Traceback (if applicable):
Additional information:
Cloud-hosted Unifi Controller.
Controller: 5.11.36
Switch FW: 4.0.49.10569
The text was updated successfully, but these errors were encountered: