unifi PoE not working

[grillsoftware]

The problem

Pulled the latest home assistant version and make the integration to a Unifi Controller CLoud Key. The user is local-access and role administrator with all permissions.

I can see PoE switches once the integration is done.

When turning PoE clients on/off I get this response.

2022-04-28 17:48:42 DEBUG (MainThread) [aiounifi.devices] Override port 5 with mode off
2022-04-28 17:48:42 DEBUG (MainThread) [aiounifi.controller] https://10.7.254.30:443/proxy/network/api/s/default/rest/device/619d429784b28907dd89df7e
2022-04-28 17:48:42 DEBUG (MainThread) [aiounifi.controller] 403 application/json <ClientResponse(https://10.7.254.30:443/proxy/network/api/s/default/rest/device/619d429784b28907dd89df7e) [403 Forbidden]>

What version of Home Assistant Core has the issue?

core-2022.4.7

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

unifi controller

Link to integration documentation on our website

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

Diagnostics information

config_entry-unifi-2cfea9d7d7a07a560690b6f774e3a19c.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2022-04-28 17:48:42 DEBUG (MainThread) [aiounifi.devices] Override port 5 with mode off
2022-04-28 17:48:42 DEBUG (MainThread) [aiounifi.controller] https://10.7.254.30:443/proxy/network/api/s/default/rest/device/619d429784b28907dd89df7e
2022-04-28 17:48:42 DEBUG (MainThread) [aiounifi.controller] 403 application/json <ClientResponse(https://10.7.254.30:443/proxy/network/api/s/default/rest/device/619d429784b28907dd89df7e) [403 Forbidden]>

Additional information

No response

[probot-home-assistant]

Hey there @Kane610, mind taking a look at this issue as it has been labeled with an integration (unifi) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

---

unifi documentation
unifi source
_{^{(message by IssueLinks)}}

[Kane610]

What version of UniFi controller are you running?
Is it the same message for any port or only for specific ports? What devices are you trying to control?
Has it worked on previous releases?

[daylehouse]

Same for me too. Any ports with a PoE client fail to enable or disable PoE.

Unifi Version - UniFi OS UCK G2 Plus 2.4.8
Unifi Network - V 7.1.61
Switch Firmware - 6.2.14

Local user account with Administrator permissions used for integration from HA. Controlling a couple of IP phones and Dante devices. Not trying to control Unifi devices (APs etc) as not supported.

[grillsoftware]

Current versions:
Unifi Network Controller: 7.1.61
Unifi OS: 2.4.8
Switch PoE firmware: 6.2.14

Connecting to a Cloud Key with Local user and role Administrator.

Trying to turn on/off a port where an Axis Camera is connected. There are other clients that I can't tell what they are (I'm not onsite) that I try to turn on/off but it's also not working.

It used to work in the previous version of the Network Controller

[daylehouse]

If I configure the port directly on the network switch, the switch entity in HA does reflect if the port has PoE enabled or disabled (on or off state). Looks like the call from HA to Unifi to enable or disable PoE is failing?

[grillsoftware]

If I configure the port directly on the network switch, the switch entity in HA does reflect if the port has PoE enabled or disabled (on or off state). Looks like the call from HA to Unifi to enable or disable PoE is failing?

Yes, I activated the logs and I can see the request going out and the response coming in. The response to change the port status has the code 403 (Forbidden).

2022-04-28 17:48:42 DEBUG (MainThread) [aiounifi.devices] Override port 5 with mode off
2022-04-28 17:48:42 DEBUG (MainThread) [aiounifi.controller] https://10.7.254.30:443/proxy/network/api/s/default/rest/device/619d429784b28907dd89df7e
2022-04-28 17:48:42 DEBUG (MainThread) [aiounifi.controller] 403 application/json <ClientResponse(https://10.7.254.30:443/proxy/network/api/s/default/rest/device/619d429784b28907dd89df7e) [403 Forbidden]>

[Kane610]

I don't have any time for the next few days. But will look at this after. Same issue seems to be with block commands. Maybe unifi have changed something

[Kane610]

Tested and works fine with UniFiOS UDM Pro 1.11.4, UniFi Network 7.1.61

Check that your user has credentials enough to control POE.

[Maxybo]

To add also, same issue for me PoE control has stopped working.

UDM PRO 2.4.9
Switch fw 6.2.14
Network Controller 7.1.61#

Using account with full access rights.

[Kane610]

Using account with full access rights.

Super admin? Can you share a screenshot of the user config page of the user?

[Maxybo]

It's a local admin account created in the Unifi OS (UDMPRO)
This is the account that I have used for a while now without issue, everything else seems to work in terms of tracking, only noticed when the PoE management stopped working.

)

[daylehouse]

Same here, I am using a local Administrator account. I don’t have a signed trusted certificate loaded on the Unifi if that could be related? The only other admin role is owner. Regards, Dayle

…

________________________________ From: Maxybo ***@***.***> Sent: Wednesday, May 11, 2022 11:58:00 AM To: home-assistant/core ***@***.***> Cc: daylehouse ***@***.***>; Comment ***@***.***> Subject: Re: [home-assistant/core] unifi PoE not working (Issue #71017) It's a local admin account created in the Unifi OS (UDMPRO) This is the account that I have used for a while now without issue, everything else seems to work in terms of tracking, only noticed when the PoE management stopped working. [Screenshot 2022-05-11 115323]<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F29385580%2F167833586-29ef24e6-4d53-4d9a-adcb-10ca830ba68e.png&data=05%7C01%7C%7Ce9c4b8633376476f1e9d08da333d1d81%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637878634819258352%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0tlLO8L3Fs%2F0tU%2BkHX6xortOsmByxrjGqXnDIf9vP5U%3D&reserved=0> [Screenshot 2022-05-11 115342]<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F29385580%2F167833611-474ecf90-d00f-4614-bd32-25afb5720721.png&data=05%7C01%7C%7Ce9c4b8633376476f1e9d08da333d1d81%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637878634819258352%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7mmC9QShrG8QQWv6Qfphtnk%2FTbrr8Gt%2B%2FZNOlFDHhJ0%3D&reserved=0> ) — Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhome-assistant%2Fcore%2Fissues%2F71017%23issuecomment-1123576863&data=05%7C01%7C%7Ce9c4b8633376476f1e9d08da333d1d81%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637878634819258352%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jV1BRF9ptxefFDpGtLVDaXd8Wgah%2FyzfzKi2ezlTx4A%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOEYM3VHSIRPNJUS2XH5D33VJOHDRANCNFSM5UTJZW2Q&data=05%7C01%7C%7Ce9c4b8633376476f1e9d08da333d1d81%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637878634819258352%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=p4FYPmnUU3wQYhGWOtjpkU9obuWTc5fQsGGJvmxV%2F7w%3D&reserved=0>. You are receiving this because you commented.Message ID: ***@***.***>

[Kane610]

What happens if you start downgrading your system, do you find a point where it starts working again?

[MidnightLink]

+1. Same problem here. See #70356

[iMiMx]

I think maybe my problem started with the upgrade of the switch to 6.2.14 - pretty sure I was on 6.2.11 previously.

Model
USW-Pro-24-PoE
Firmware Version
6.2.14

I've got a lot of 'stuff' hanging off this switch, so will try and downgrade perhaps early Sunday morning....when the lazy people are all still asleep.

[Kane610]

will try and downgrade perhaps early Sunday morning

Thanks

[iMiMx]

6.2.11 did not resolve the problem - but caused a whole heap of other issues during the downgrade. Thanks unifi.

Might be a while before I can test some more downgrades, need to let the general moaning from the family subside a bit!

[Kane610]

I've started doing some general refactoring of the unifi library. When I'm further along I will also upgrade my switch to the latest firmware and see if that has any effect.

[stephack]

Chiming in to report similar issues.
I have a UDM-SE with 24POE-Enterprise switch. I'm not sure when it stopped working because the unifi integration was on a VM on a server that I had shutdown for a month. Once I spun it back up, my poe control and Mac based blocking stopped working. Both switch and UDM are on the latest production firmware.
Hopefully we get this sorted soon as I use this to limit access to devices for my kids based on a schedule.

[github-actions]

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.

[stephack]

Unfortunately I'm still seeing this with the latest update 2022.6.6
To reiterate my issue... I'm no longer able to control devices via POE or via simple mac blocking.
The entity in HA simply toggles itself back on and nothing changes. The devices remain on and able to communicate on the network.

Other seem to be posting similar issues in the forums but are not posting their issue via github.

[Maxybo]

Can confirm the issue is still present with the latest stable release also.

[MidnightLink]

+1. Problem persisting

[tsspmq]

I think the guy working on issue 73071 has figured out why this is happening but not how to fix just yet.

[MidnightLink]

Opening this back up. The fix DOES fix it temporarily but it seems after some time (an hour I believe? Not 100% sure) it loses authorization. The only fix is to delete and set back up the integration but it happens again.

New message that I'm receiving.