Closed Dulcow closed 4 years ago
This most likely happens because the config looks somewhat like
netatmo:
api_key: !secret netatmo_api_key
secret_key: !secret netatmo_secret_key
username: !secret netatmo_username
password: !secret netatmo_password
climate:
- platform: netatmo
Actually only the following part is needed if auto discovery is used (default), otherwise discovery has to be deactivated.
netatmo:
api_key: !secret netatmo_api_key
secret_key: !secret netatmo_secret_key
username: !secret netatmo_username
password: !secret netatmo_password
I will close the bug. It was due to some faulty configuration on my side.
Home Assistant release with the issue:
0.102.0
Last working Home Assistant release (if known): N/A
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io on RaspBerry PI 3b+
Integration:
https://www.home-assistant.io/integrations/netatmo/
Description of problem: Temperatures seem to be in synced between the two copies of thermostats. There is sometimes a bit of lag between the two instances but it looks the same to me after a few minutes.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):Traceback (if applicable):
Additional information: I can still see the following message popping up in the logs:
homeassistant.exceptions.HomeAssistantError: Entity id already exists: sensor.netatmo_bathroom_battery. Platform netatmo does not generate unique IDs