home-assistant[bot]
commented
2 months ago Hey there @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!
Code owner commands
Code owners of `unifiprotect` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign unifiprotect` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.(message by CodeOwnersMention)
unifiprotect documentation unifiprotect source (message by IssueLinks)
robbiedehand
The problem
error flooding my logbook
homeassistant.components.binary_sensor] Platform unifiprotect does not generate unique IDs
What version of Home Assistant Core has the issue?
System Information version | core-2024.4.4 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.2 os_name | Linux os_version | 6.6.25-haos arch | x86_64 timezone | Europe/Amsterdam config_dir | /config
Home Assistant Community Store
GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4976 Installed Version | 1.34.0 Stage | running Available Repositories | 1468 Downloaded Repositories | 3Home Assistant Cloud
logged_in | true -- | -- subscription_expiration | 6 april 2025 om 02:00 relayer_connected | true relayer_region | eu-central-1 remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | false remote_server | eu-central-1-11.ui.nabu.casa certificate_status | ready instance_id | f27fa3eb042343809da79269e9d6d322 can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | okHome Assistant Supervisor
host_os | Home Assistant OS 12.2 -- | -- update_channel | stable supervisor_version | supervisor-2024.04.0 agent_version | 1.6.0 docker_version | 25.0.5 disk_total | 234.0 GB disk_used | 32.0 GB healthy | true supported | true board | generic-x86-64 supervisor_api | ok version_api | ok installed_addons | Tailscale (0.18.0), ESPHome (2024.4.1), AdGuard Home (5.0.7), chrony (3.0.1), Whisper (2.0.0), OneDrive Backup (2.3.1), AirCast (4.2.1), Studio Code Server (5.15.0), Mosquitto broker (6.4.0), Uptime Kuma (0.12.0), AirSonos (4.2.1), Advanced SSH & Web Terminal (17.2.0), openWakeWord (1.10.0), File editor (5.8.0), Plex Media Server (3.5.0), Z-Wave JS (0.5.0)Dashboards
dashboards | 3 -- | -- resources | 0 views | 6 mode | storageRecorder
oldest_recorder_run | 23 april 2024 om 23:36 -- | -- current_recorder_run | 24 april 2024 om 01:36 estimated_db_size | 2723.96 MiB database_engine | sqlite database_version | 3.44.2Spotify
api_endpoint_reachable | ok -- | --What was the last working version of Home Assistant Core?
core-2024.4.4
What type of installation are you running?
Home Assistant OS
Integration causing the issue
unifiprotect
Link to integration documentation on our website
https://www.home-assistant.io/integrations/unifiprotect
Diagnostics information
config_entry-unifiprotect-a419284e3d55a7aedee2b852438c0e3e.json config_entry-unifiprotect-d97450c2475b2d3bccab7533a72aea75.json home-assistant_2024-04-26T13-59-53.129Z.log
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response