Error in the log each time I start HA
See original GitHub issueI get the error in the log each time I start HA,
Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:567
Integration: Sensor (documentation, issues)
First occurred: 10:45:50 AM (1 occurrences)
Last logged: 10:45:50 AM
Platform google_home does not generate unique IDs. ID Google Home/device already exists - ignoring sensor.google_home_device
And the sensors is unavailable
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
HA won't start or produce an error log - I'm a bit panicky
Everything was working fine, I did some editing in my sensors.yaml and now HA won't start up and doesn't produce a error log...
Read more >How To Troubleshoot Common HAProxy Errors - DigitalOcean
There are three main commands, and a common log location that you can use to get started troubleshooting HAProxy errors.
Read more >HA Logging - Thales Docs
Logging of HA-related events takes place on the Luna HSM Client workstation. The log file haErrorLog.txt shows HA errors, as well as add-member ......
Read more >Troubleshooting VMware High Availability (HA) issues in ...
Enabling VMware HA fails. You see the error: Operation Timed out. Purpose. This article discusses troubleshooting a component of HA (FDM) in ...
Read more >Reviewing cluster message log files - IBM
Reviewing cluster message log files ; system error log, Contains time-stamped, formatted messages from all AIX® subsystems, including scripts and daemons. For ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For tracking purposes here is the ticket for unique id generation
I think what’s going on here is we use device name for unique id and you have devices with the same names: “Google Home”. We need to use something more unique for unique id, e.g. internal device id, serial number or mac address.