Unifi Protect - Camera Detections to Record Being Disabled

[bwscheller]

The problem

After installing the Unifi Protect Integration, I noticed that I was no longer receiving notifications from my Unifi Protect Cameras. I was able to look at the settings for each camera and determine that the Detections to Record had all been disabled. Every day I would need to access each camera and re-enable the Detections to Record. After disabling the Unifi Protect Integration last night, I did not have to re-enable the Detections to Record this morning.

What version of Home Assistant Core has the issue?

2022.7.3

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/

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

[probot-home-assistant[bot]]

Hey there @briis, @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! _{^{(message by CodeOwnersMention)}}

---

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

[AngellusMortis]

Can you please provide your logbook entries from the time it was changed? You can use the Logbook page on the left side sidebar, filter for the entity and then screenshot that.

[bwscheller]

Here are the logbook entries for the person detection entity:

[image: image.png]

On Tue, Jul 12, 2022 at 9:07 AM Christopher Bailey @.***> wrote:

Can you please provide your logbook entries from the time it was changed? You can use the Logbook page on the left side sidebar, filter for the entity and then screenshot that.

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

[AngellusMortis]

I am guessing you cannot attach images using email.

[bwscheller]

[bwscheller]

I just recently installed the Protect integration. My plan to was to create an automation that would trigger on person or vehicle detections on the Front Door camera and then send the feed to a Google Nest Hub in the kitchen. There are no automations that are setup to manipulate the settings of the cameras and I have always done that through the Protect app not Home Assistant.

[AngellusMortis]

Since there no name of who change the switch, that means the integration is receiving data from Protect saying it was off.

It also looks like you have an unstable connection to Protect. Does the timeline in UniFi Protect show the camera disconnecting or losing power often?

If it does, then I am guessing that may be the cause. Assuming the camera is a G4 Doorbell or G4 Doorbell Pro, you probably are using a transformer and a WiFi connection. The most likely case with a doorbell is that one of those two connections are unstable causing the doorbell to disconnect over and over again. I am guessing it is the transformer because that would cause the doorbell to lose power and reboot, which could cause UniFi Protect to broadcast an invalid Websocket message saying the detections are off when it comes back online.

If it does not, then your connection between Home Assistant and Protect is unstable causing the Websocket connection to disconnect often. The CPU being overloaded on the UniFi OS console running Network, or the UniFi OS console running Protect or the HA instance/machine is the most likely cause of that.

I cannot really help you troubleshoot the upstream issues any better than that because there is no good way in Home Assistant to have to capture the raw Websocket messages so you can send us for me to analyze. As a last resort, if you cannot figure out upstream what is causing the issue, you can always disable the configuration switch for enabling/disabling specific detections and then HA cannot turn them off.

[bwscheller]

Thank you, your last message allowed me to figure out the cause of both my Unifi integration issues. You are correct that on the current firmware my doorbell does often disconnect, so I looked at a G4 Dome camera that is hard wired. When I looked at the logbook entries for it, I realized the detection settings are implemented as switches and there is an automation to turn off all switched at night.