Cannot ignore RTSPS Warning in unifiprotect when configured user does not have write access to the camera

[rwjack]

The problem

I have completely disabled the camera entity as I do not need to view the live feed from within HA. All I want from HA is to monitor the stats of my CloudKey, hence the need for this integration, but this warning keeps popping up every restart:

I can't seem to find a way to ignore it.

Even when I go through the flow, and get the "The issue is repaired" popup:

The warning re-appears after a reboot.

On another note, if there is a way to get the same stats as I do with this integration, cpu usage, temperature, disk usage, through SNMP, that would pretty much solve my specific issue.

What version of Home Assistant Core has the issue?

core-2024.6.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

UniFi Protect

Link to integration documentation on our website

https://www.home-assistant.io/integrations/unifiprotect/#camera-streams

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]

unifiprotect documentation
unifiprotect source

[rwjack]

Just an update, I installed a CheckMK agent on my CloudKey which provides me with the desired statistics, so I can just disable the UP integration within HA, although this issue might benefit someone else, so I'll keep it open if that's okay with the code owner.

[bdraco]

Maybe the user that is setup in HA doesn't have permission to enable RTSP so it failing

[rwjack]

Right, that definitely could be it. The user is configured to be "Live Only", but that doesn't explain why I cannot ignore the warning in HA, since I do not want to be livestreaming, hence no need for RTSP.

[issue-triage-workflows]

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.

[rwjack]

bump