Unifi Protect G4 Doorbell Occupancy not detected

[PsychoV3]

The problem

Unifi Protect G4 Doorbell Occupancy not detected - I.e. Doorbell pressed and sensor isnt updated.

Very likely an Early Access issue: Protect 5.0.20

What version of Home Assistant Core has the issue?

core-2024.9.1

What was the last working version of Home Assistant Core?

2024.9.1

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

home-assistant_unifiprotect_2024-09-12T09-50-07.727Z.log

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

[JohnnyPrimus]

im no expert on this integration, so dont consider any of this commentary on HA or unifiprotect integration - but that said, I took a look at your logs and I guess am wondering how your network is configured?

You seem to be losing connection between your home assistant server and your router (UDM something I'm assuming? since apparently protect is running directly on your router rather than being an nvr) frequently. In fact the logs shows a lot of stuff that HA is trying to talk to it can't find because it can't connect.

Then at the very end of the log, suddenly unifi is starting to do discovery on devices it can apparently suddenly talk to and then the log ends. Could very well be early access related.... but I did want to ask how the network is setup so author or anyone else can better understand what could be going on here.

Lastly - I saw "couldnt auto detect the source ip for 255.255.255.255 on your operating system"....this could be a total red herring, but what are your network settings on the router and your clients? e.g...your not using 255.255.255.255 as a subnet mask right? if not this is probably a non-issue to do with broadcast

[PsychoV3]

Defo not using that as a subnet....There are issues with z-wave I have yet to resolve, just stopped working and will not restart with current configuration. xxx.xxx.xxx.15/18/36 address "issues" are not issues.

HA runs on two subnets/vlans with two interfaces.

And yes UDMP.

Probably left the log on for too long, as was distracted mid capture.

[PsychoV3]

Right been looking at this affer updating to Early Access 5.0.26 and the binnary sensor appears to work now (it wasnt for me).... Also I was using the state of the device, which wasn't working and still isn't but this may have been something in a change I missed.