Closed Coolie1101 closed 2 years ago
I'm guessing this could be because you have a camera name 'frontdoor' and a zone called 'FrontDoor'. One sensor is referring to objects for the camera, the other is referring to objects for the zone. Try renaming one of them.
camera name 'frontdoor' and a zone called 'FrontDoor'
Indeed I do, had no idea sensors were created for the camera itself, thanks.
Hey @dermotduffy, any idea how to remove/delete old zones?
Review my comments on this issue which give a number of options: https://github.com/blakeblackshear/frigate-hass-integration/issues/140
Already deleted the entities, but the zones still show up under devices.
Devices with no entities are (IIRC) automatically garbage collected after some time. If you don't want to wait you could manually remove them from .storage/core.device_registry
after you take a backup.
I went with the latter, works so far.
Just out of curiosity, how long does it normally take to be automatically removed?, FYI, been like that since the first day I installed a few weeks ago, and was testing out different options to get an understanding of how things work.
Apologies, not sure. In reality, the real issue is with this integration. It should automatically remove cameras/zone that are associated with the integration but no longer 'live' -- that's just not implemented yet.
... so lets keep this bug to reflect that feature gap.
No worries, thanks for your help.
Amazing, would this also take care of the existing unused entities after updating?
@Coolie1101 only unused entities that are associated with a Frigate device. Frigate devices were introduced from v1.1.0 onwards (~July). Crufty entities created prior to that would not be cleaned by this functionality.
So orpaned entities from within the past couple days would get purged after the new release?
I'm only asking because I disabled (removed from config) a couple zones which still show up as unavailable.
That's a good test. Yes, as long as were running with an integration >= v1.1.0 when you first added those zones, then the next release should clean that up for you without you needing to do anything.
Awesome, definitely newer than v1.1.0, as I only started using Frigate a couple weeks ago.
Also the link to the doc link in the integration links "https://github.com/blakeblackshear/frigate" as appose to "https://github.com/blakeblackshear/frigate-hass-integration"
then the next release should clean that up for you without you needing to do anything.
I mite be wrong, but this doesn't seem to be the case, I am now on version 2.2.2/0.11.0-cbf26e0
and still have duplicated entities.
Version of the custom_component
v2.1.0
Configuration
Describe the bug
I have duplicated sensors for each specified object, eg:- "sensor.frontdoor_person" and "sensor.frontdoor_person_2"
Debug log