Nope. 10 charrrr
I understand. Maybe after the next big update when you get bored lol.
Has anybody succeeded in making a binary_sensor template for person detection?
My attempt doesnāt seem to be working:
binary_sensor:
- platform: template
sensors:
front_door_person:
friendly_name: Front Door Person Detected
device_class: "motion"
value_template: "{{ is_state_attr('binary_sensor.motion_front_door' ,'event_object' ,'Person') }}"
Homekitās little picture in picture feature is nice, but I need a binary sensor to feed it.
This is mine:
{{ (is_state('binary_sensor.motion_front_doorbell', 'on') and is_state('sensor.front_doorbell_detected_object', 'person')) }}
1 Like
Thanks, Iāll try it.
Nope. 10 charrrr
1 Like
OK thanks Iāll remove the motion part. Iām on the latest beta, do you mean detected object sensor is deprecated ?
Ah ok I see thanks
Ok what @Holdestmade did actually work, but I prefer simplicity, so Iāll try your suggestion.
After all of this youāre going to bake a binary sensor into the integration and Iāllā¦ at least have learned something lol.
Edit: Works as well. Thanks to both.
I rmaād my G4 Doorbell and would like to delete the old instance thatās there but I donāt have the option to remove it. I also replaced my UDM Pro with an SE model and would like to delete the old UDMPro device from the integration. Also no option to delete.
Anyone know the correct process to remove stale devices?
Remove the whole integration and re-add it
I was really hoping that wouldnāt be the answer. Thanks for the response.
Iāll wait and see if anyone has a workaround that is less ānuclearā but my gut tells me youāre 100% right. Total remove and re-add or edit the config registries. Neither would be preferred.
I have removed and re-added many times through all the beta testing. Everything comes back as the way it was when you removed it. If your customizing entity names in HA then youāre doing it wrong. Customize the names in protect and through the unifi dashboard. So that way when you re-add it, all of the names for all of your devices get re-added. Itās the complete opposite of nuclear itās actually a really smooth and easy processā¦
1 Like
Sigh. Thank you both for the responses. Iāve been using this integration since it was first released and unfortunately I have customized all my entity names. I have them in many automations and referenced in many frontend cards. They are also built out in my inlfuxdb and referenced in multiple grafana dashboards. I have done the nuclear option before but I didnāt have many devices at the time, so simply renamed the entities to what they were before ā¦ I guess I should bite the bullet now and just edit my automations, frontend cards and grafana dashboards now to use the default names.
This will be a PITA. Cāest la vie. Thanks again for confirming.
1 Like
That is unfortunate, but then again, without your work nothing of this would be possible. So small āpriceā to pay for people using this. Thanks for all the documentation regarding upgrading/migrating.
Is there no longer a way to disable the infrareds? When I enable privacy mode the IR is still on so visitors starting over at my house get an impression that the cameras are on and recording.
So do I 
I was looking for a toggle and completely missed this. Sorry, and thanks 
When enabling realtime metrics and it says will increase cpu, is that CPU on the device running Protect or is that the CPU running Home Assistant?
Thanks so much! I have plenty of cpu to spare on my HA install. Hoping this helps with automations I running off person detections from my G4 cameras. They are good but seem to have a couple of seconds of lag.