Unexpected error fetching home data:

DoerakkerHA commented 9 months ago

The problem

upon boot the following errors are reported: 2024-01-22 07:24:30.052 ERROR (MainThread) [homeassistant.components.proximity.coordinator] Unexpected error fetching home data: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 300, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/proximity/coordinator.py", line 227, in _async_update_data assert new_distance is not None and old_distance is not None

applied last update this morning

What version of Home Assistant Core has the issue?

core-2024.1.5

What was the last working version of Home Assistant Core?

core-2024.1.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

proximity

Link to integration documentation on our website

https://www.home-assistant.io/integrations/proximity

Diagnostics information

2024-01-22 07:24:30.052 ERROR (MainThread) [homeassistant.components.proximity.coordinator] Unexpected error fetching home data: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 300, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/proximity/coordinator.py", line 227, in _async_update_data assert new_distance is not None and old_distance is not None ^^^^^^^^^^^^^^^^^^^^^^^^ AssertionError

Example YAML snippet

zone_config: 
- name: clement_werk
  latitude: !secret clement_werk_latitude
  longitude: !secret clement_werk_longitude
  radius: 1000
  passive: false
  icon: mdi:factory

- name: buurt
  latitude: !secret home_latitude
  longitude: !secret home_longitude
  radius: 750
  passive: false
  icon: mdi:map-marker-circle

- name: plus_elspeet
  latitude: 52.28678
  longitude: 5.78903
  radius: 50
  passive: false
  icon: mdi:shopping-outline

home:
  zone: home
  ignored_zones:
    #- zone.clement_werk
  devices:
    - person.ronald
    - person.clement
  tolerance: 50
  unit_of_measurement: m
clement_werk:
  zone: clement_werk
  devices:
    - person.clement
  tolerance: 3
  unit_of_measurement: km
buurt:
  zone: buurt
  devices:
    - person.ronald
    - person.clement
  tolerance: 50
  unit_of_measurement: m

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 9 months ago

Hey there @mib1185, mind taking a look at this issue as it has been labeled with an integration (proximity) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `proximity` 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 proximity` 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)}}

proximity documentation proximity source _{^{(message by IssueLinks)}}

mib1185 commented 9 months ago

Hi @DoerakkerHA

please enable debug logging, restart HA and provide the home-assistant.log after the error message occur again To do so add the following to your configuration.yaml:

logger:
  default: info
  logs:
    homeassistant.components.proximity: debug

Note: it is better to drag the log into the comment (which will add it as an attachment) and not copy paste as it is hard to read logs in GitHub.

mib1185 commented 9 months ago

further questions

did this config ever worked before?
are all entities available which are related to person.ronald and person.clement?

DoerakkerHA commented 9 months ago

Home Assistant Core

2024-01-22 20:18:10.253 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret my_project_id retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.256 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret home_latitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.256 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret home_longitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.256 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret my_external_url retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.256 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret my_internal_url retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.257 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret my_ssl_cert retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.258 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret my_ssl_key retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.287 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Loading /config/zones/zones/secrets.yaml

2024-01-22 20:18:10.288 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Loading /config/zones/secrets.yaml

2024-01-22 20:18:10.288 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret clement_werk_latitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.288 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret clement_werk_longitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.289 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret home_latitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.289 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret home_longitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.289 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret shopping_nunspeet_latitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.290 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret shopping_nunspeet_longitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:10.677 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hass_agent_notifier which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.678 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration huesyncbox which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.679 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration simple_thermostat which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.680 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration edge_tts which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.681 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hass_agent which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.682 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hass_agent_mediaplayer which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.684 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration google_home which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.685 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration scheduler which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.686 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration variable which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.687 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.688 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration sems which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.689 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration met_next_6_hours_forecast which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.691 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration momentary which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:10.692 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration toon_climate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

2024-01-22 20:18:19.118 ERROR (MainThread) [homeassistant.config] Platform error: binary_sensor - No module named 'homeassistant.components.time_date.binary_sensor'

Traceback (most recent call last):

File "/usr/src/homeassistant/homeassistant/config.py", line 1483, in async_process_component_config

platform = p_integration.get_platform(domain)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/src/homeassistant/homeassistant/loader.py", line 842, in get_platform

cache[full_name] = self._import_platform(platform_name)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/src/homeassistant/homeassistant/loader.py", line 859, in _import_platform

return importlib.import_module(f"{self.pkg_path}.{platform_name}")

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/local/lib/python3.11/importlib/init.py", line 126, in import_module

return _bootstrap._gcd_import(name[level:], package, level)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "", line 1204, in _gcd_import

File "", line 1176, in _find_and_load

File "", line 1140, in _find_and_load_unlocked

ModuleNotFoundError: No module named 'homeassistant.components.time_date.binary_sensor'

2024-01-22 20:18:20.566 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'None' has no attribute 'attributes' when rendering '{% if states.sun.sun.attributes %}

{% if (as_timestamp(states.sun.sun.attributes.next_dusk)) | int(0)

(as_timestamp(states.sun.sun.attributes.next_setting)) | int(0) < 0 %}

mdi:weather-sunset-down

{% elif (as_timestamp(states.sun.sun.attributes.next_rising)) | int(0)

(as_timestamp(states.sun.sun.attributes.next_dawn)) | int(0) < 0 %}

mdi:weather-sunset-up

{% elif (states.sun.sun.attributes.elevation) | int(0) < -6 %}

mdi:weather-night

{% else %}

mdi:weather-sunny

{% endif %}

{% else %}

mdi:weather-partly-lightning

{% endif %}'

2024-01-22 20:18:20.596 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'None' has no attribute 'attributes' when rendering '{% if states.sun.sun.attributes %}

{% if (as_timestamp(states.sun.sun.attributes.next_dusk)) | int(0)

(as_timestamp(states.sun.sun.attributes.next_setting)) | int(0) < 0 %}

mdi:weather-sunset-down

{% elif (as_timestamp(states.sun.sun.attributes.next_rising)) | int(0)

(as_timestamp(states.sun.sun.attributes.next_dawn)) | int(0) < 0 %}

mdi:weather-sunset-up

{% elif (states.sun.sun.attributes.elevation) | int(0) < -6 %}

mdi:weather-night

{% else %}

mdi:weather-sunny

{% endif %}

{% else %}

mdi:weather-partly-lightning

{% endif %}'

2024-01-22 20:18:21.480 WARNING (MainThread) [homeassistant.components.sensor] STATE_CLASS_TOTAL_INCREASING was used from sems, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.TOTAL_INCREASING instead, please create a bug report at https://github.com/TimSoethout/goodwe-sems-home-assistant/issues

2024-01-22 20:18:21.486 WARNING (MainThread) [homeassistant.components.sensor] STATE_CLASS_TOTAL_INCREASING was used from sems, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorStateClass.TOTAL_INCREASING instead, please create a bug report at https://github.com/TimSoethout/goodwe-sems-home-assistant/issues

2024-01-22 20:18:21.492 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_POWER was used from sems, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.POWER instead, please create a bug report at https://github.com/TimSoethout/goodwe-sems-home-assistant/issues

2024-01-22 20:18:21.498 WARNING (MainThread) [homeassistant.const] POWER_WATT was used from sems, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.WATT instead, please create a bug report at https://github.com/TimSoethout/goodwe-sems-home-assistant/issues

2024-01-22 20:18:21.504 WARNING (MainThread) [homeassistant.const] DEVICE_CLASS_ENERGY was used from sems, this is a deprecated constant which will be removed in HA Core 2025.1. Use SensorDeviceClass.ENERGY instead, please create a bug report at https://github.com/TimSoethout/goodwe-sems-home-assistant/issues

2024-01-22 20:18:21.509 WARNING (MainThread) [homeassistant.const] ENERGY_KILO_WATT_HOUR was used from sems, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.KILO_WATT_HOUR instead, please create a bug report at https://github.com/TimSoethout/goodwe-sems-home-assistant/issues

2024-01-22 20:18:21.702 ERROR (MainThread) [homeassistant.components.automation] Automation with alias '[People] - Notify when phone is fully charged' failed to setup triggers and has been disabled: Unknown device 'c1c24c382c7507d5805df36dfc3488bb'

2024-01-22 20:18:21.845 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_COOL was used from simple_thermostat, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.COOLING instead, please create a bug report at https://github.com/dadge/simple_thermostat/issues

2024-01-22 20:18:21.850 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_HEAT was used from simple_thermostat, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.HEATING instead, please create a bug report at https://github.com/dadge/simple_thermostat/issues

2024-01-22 20:18:21.855 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_IDLE was used from simple_thermostat, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.IDLE instead, please create a bug report at https://github.com/dadge/simple_thermostat/issues

2024-01-22 20:18:21.861 WARNING (MainThread) [homeassistant.components.climate.const] CURRENT_HVAC_OFF was used from simple_thermostat, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACAction.OFF instead, please create a bug report at https://github.com/dadge/simple_thermostat/issues

2024-01-22 20:18:21.866 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_COOL was used from simple_thermostat, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.COOL instead, please create a bug report at https://github.com/dadge/simple_thermostat/issues

2024-01-22 20:18:21.871 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_HEAT was used from simple_thermostat, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.HEAT instead, please create a bug report at https://github.com/dadge/simple_thermostat/issues

2024-01-22 20:18:21.876 WARNING (MainThread) [homeassistant.components.climate.const] HVAC_MODE_OFF was used from simple_thermostat, this is a deprecated constant which will be removed in HA Core 2025.1. Use HVACMode.OFF instead, please create a bug report at https://github.com/dadge/simple_thermostat/issues

2024-01-22 20:18:21.881 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_PRESET_MODE was used from simple_thermostat, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.PRESET_MODE instead, please create a bug report at https://github.com/dadge/simple_thermostat/issues

2024-01-22 20:18:21.887 WARNING (MainThread) [homeassistant.components.climate.const] SUPPORT_TARGET_TEMPERATURE was used from simple_thermostat, this is a deprecated constant which will be removed in HA Core 2025.1. Use ClimateEntityFeature.TARGET_TEMPERATURE instead, please create a bug report at https://github.com/dadge/simple_thermostat/issues

2024-01-22 20:18:25.994 DEBUG (MainThread) [homeassistant.components.proximity] setup clement_werk with config:{'zone': 'clement_werk', 'devices': ['person.clement'], 'tolerance': 3, 'unit_of_measurement': 'km', 'ignored_zones': []}

2024-01-22 20:18:25.994 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching clement_werk data in 0.000 seconds (success: True)

2024-01-22 20:18:25.994 DEBUG (MainThread) [homeassistant.components.proximity] setup buurt with config:{'zone': 'buurt', 'devices': ['person.ronald', 'person.clement'], 'tolerance': 50, 'unit_of_measurement': 'm', 'ignored_zones': []}

2024-01-22 20:18:25.995 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching buurt data in 0.000 seconds (success: True)

2024-01-22 20:18:25.995 DEBUG (MainThread) [homeassistant.components.proximity] setup plus_elspeet with config:{'zone': 'zone.plus_elspeet', 'devices': ['person.ronald', 'person.clement'], 'tolerance': 25, 'unit_of_measurement': 'm', 'ignored_zones': []}

2024-01-22 20:18:25.995 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching plus_elspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:25.996 DEBUG (MainThread) [homeassistant.components.proximity] setup interakt_countour_nunspeet with config:{'zone': 'interakt_countour_nunspeet', 'devices': ['person.ronald'], 'tolerance': 25, 'unit_of_measurement': 'm', 'ignored_zones': []}

2024-01-22 20:18:25.996 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching interakt_countour_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:25.996 DEBUG (MainThread) [homeassistant.components.proximity] setup shopping_nunspeet with config:{'zone': 'shopping_nunspeet', 'devices': ['person.ronald', 'person.clement'], 'tolerance': 100, 'unit_of_measurement': 'm', 'ignored_zones': []}

2024-01-22 20:18:25.996 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching shopping_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:25.996 DEBUG (MainThread) [homeassistant.components.proximity] setup appie_nunspeet with config:{'zone': 'appie_nunspeet', 'devices': ['person.ronald', 'person.clement'], 'tolerance': 50, 'unit_of_measurement': 'm', 'ignored_zones': []}

2024-01-22 20:18:25.997 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching appie_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:25.997 DEBUG (MainThread) [homeassistant.components.proximity] setup lidl_nunspeet with config:{'zone': 'lidl_nunspeet', 'devices': ['person.ronald', 'person.clement'], 'tolerance': 100, 'unit_of_measurement': 'm', 'ignored_zones': []}

2024-01-22 20:18:25.997 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching lidl_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:25.997 DEBUG (MainThread) [homeassistant.components.proximity] setup welkoop_nunspeet with config:{'zone': 'welkoop_nunspeet', 'devices': ['person.ronald', 'person.clement'], 'tolerance': 50, 'unit_of_measurement': 'm', 'ignored_zones': []}

2024-01-22 20:18:25.997 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching welkoop_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:26.386 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Loading /config/secrets.yaml

2024-01-22 20:18:26.391 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret my_project_id retrieved from secrets.yaml in folder /config

2024-01-22 20:18:26.394 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret home_latitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:26.394 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret home_longitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:26.394 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret my_external_url retrieved from secrets.yaml in folder /config

2024-01-22 20:18:26.394 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret my_internal_url retrieved from secrets.yaml in folder /config

2024-01-22 20:18:26.395 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret my_ssl_cert retrieved from secrets.yaml in folder /config

2024-01-22 20:18:26.396 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret my_ssl_key retrieved from secrets.yaml in folder /config

2024-01-22 20:18:26.431 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Loading /config/zones/zones/secrets.yaml

2024-01-22 20:18:26.431 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Loading /config/zones/secrets.yaml

2024-01-22 20:18:26.432 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret clement_werk_latitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:26.432 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret clement_werk_longitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:26.432 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret home_latitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:26.432 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret home_longitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:26.433 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret shopping_nunspeet_latitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:26.433 DEBUG (SyncWorker_0) [homeassistant.util.yaml.loader] Secret shopping_nunspeet_longitude retrieved from secrets.yaml in folder /config

2024-01-22 20:18:31.959 WARNING (MainThread) [homeassistant.helpers.entity] Entity None (<class 'custom_components.simple_thermostat.climate.SimpleThermostat'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <ClimateEntityFeature.TARGET_TEMPERATURE|PRESET_MODE: 17>, please create a bug report at https://github.com/dadge/simple_thermostat/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation

2024-01-22 20:18:34.523 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/DOERAKKER-PC/availability', 'icon': 'mdi:window-maximize', 'unique_id': '55ce3d09-141f-429e-a4e0-6de2e6f5f039', 'device': {'identifiers': ['hass.agent-DOERAKKER-PC'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'DOERAKKER-PC', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'DOERAKKER-PC_activewindow', 'state_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_activewindow/state', 'encoding': 'utf-8', 'force_update': False, 'payload_not_available': 'offline', 'payload_available': 'online', 'availability_mode': 'latest', 'qos': 0, 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_activewindow'

2024-01-22 20:18:34.524 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/DOERAKKER-PC/availability', 'icon': 'mdi:chart-areaspline', 'unique_id': 'b6c7f91e-b38f-49a2-b1d4-c4693e1fdb08', 'unit_of_measurement': '%', 'device': {'identifiers': ['hass.agent-DOERAKKER-PC'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'DOERAKKER-PC', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'DOERAKKER-PC_cpuload', 'state_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_cpuload/state', 'encoding': 'utf-8', 'force_update': False, 'payload_not_available': 'offline', 'payload_available': 'online', 'availability_mode': 'latest', 'qos': 0, 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_cpuload'

2024-01-22 20:18:34.525 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/DOERAKKER-PC/availability', 'icon': 'mdi:speaker', 'unique_id': 'DOERAKKER-PC_audio_default_device', 'device': {'identifiers': ['hass.agent-DOERAKKER-PC'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'DOERAKKER-PC', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'DOERAKKER-PC_audio Default Device', 'state_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_audio/DOERAKKER-PC_audio_default_device/state', 'encoding': 'utf-8', 'force_update': False, 'payload_not_available': 'offline', 'payload_available': 'online', 'availability_mode': 'latest', 'qos': 0, 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_audio Default Device'

2024-01-22 20:18:34.526 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/DOERAKKER-PC/availability', 'icon': 'mdi:speaker', 'unique_id': 'DOERAKKER-PC_audio_default_device_state', 'device': {'identifiers': ['hass.agent-DOERAKKER-PC'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'DOERAKKER-PC', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'DOERAKKER-PC_audio Default Device State', 'state_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_audio/DOERAKKER-PC_audio_default_device_state/state', 'encoding': 'utf-8', 'force_update': False, 'payload_not_available': 'offline', 'payload_available': 'online', 'availability_mode': 'latest', 'qos': 0, 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_audio Default Device State'

2024-01-22 20:18:34.531 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/DOERAKKER-PC/availability', 'icon': 'mdi:speaker', 'unique_id': 'DOERAKKER-PC_audio_default_device_volume', 'device': {'identifiers': ['hass.agent-DOERAKKER-PC'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'DOERAKKER-PC', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'DOERAKKER-PC_audio Default Device Volume', 'state_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_audio/DOERAKKER-PC_audio_default_device_volume/state', 'encoding': 'utf-8', 'force_update': False, 'payload_not_available': 'offline', 'payload_available': 'online', 'availability_mode': 'latest', 'qos': 0, 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_audio Default Device Volume'

2024-01-22 20:18:34.532 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/DOERAKKER-PC/availability', 'icon': 'mdi:speaker', 'unique_id': 'DOERAKKER-PC_audio_default_device_muted', 'device': {'identifiers': ['hass.agent-DOERAKKER-PC'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'DOERAKKER-PC', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'DOERAKKER-PC_audio Default Device Muted', 'state_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_audio/DOERAKKER-PC_audio_default_device_muted/state', 'encoding': 'utf-8', 'force_update': False, 'payload_not_available': 'offline', 'payload_available': 'online', 'availability_mode': 'latest', 'qos': 0, 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_audio Default Device Muted'

2024-01-22 20:18:34.533 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/DOERAKKER-PC/availability', 'icon': 'mdi:volume-high', 'unique_id': 'DOERAKKER-PC_audio_peak_volume', 'device': {'identifiers': ['hass.agent-DOERAKKER-PC'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'DOERAKKER-PC', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'DOERAKKER-PC_audio Peak Volume', 'state_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_audio/DOERAKKER-PC_audio_peak_volume/state', 'encoding': 'utf-8', 'force_update': False, 'payload_not_available': 'offline', 'payload_available': 'online', 'availability_mode': 'latest', 'qos': 0, 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_audio Peak Volume'

2024-01-22 20:18:34.534 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/DOERAKKER-PC/availability', 'icon': 'mdi:music-box-multiple-outline', 'json_attributes_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_audio/DOERAKKER-PC_audio_audio_sessions/attributes', 'unique_id': 'DOERAKKER-PC_audio_audio_sessions', 'device': {'identifiers': ['hass.agent-DOERAKKER-PC'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'DOERAKKER-PC', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'DOERAKKER-PC_audio Audio Sessions', 'state_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_audio/DOERAKKER-PC_audio_audio_sessions/state', 'encoding': 'utf-8', 'force_update': False, 'payload_not_available': 'offline', 'payload_available': 'online', 'availability_mode': 'latest', 'qos': 0, 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_audio Audio Sessions'

2024-01-22 20:18:34.548 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/DOERAKKER-PC/availability', 'icon': 'mdi:microphone', 'unique_id': 'DOERAKKER-PC_audio_default_input_device', 'device': {'identifiers': ['hass.agent-DOERAKKER-PC'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'DOERAKKER-PC', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'DOERAKKER-PC_audio Default Input Device', 'state_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_audio/DOERAKKER-PC_audio_default_input_device/state', 'encoding': 'utf-8', 'force_update': False, 'payload_not_available': 'offline', 'payload_available': 'online', 'availability_mode': 'latest', 'qos': 0, 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_audio Default Input Device'

2024-01-22 20:18:34.549 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/DOERAKKER-PC/availability', 'icon': 'mdi:microphone', 'unique_id': 'DOERAKKER-PC_audio_default_input_device_state', 'device': {'identifiers': ['hass.agent-DOERAKKER-PC'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'DOERAKKER-PC', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'DOERAKKER-PC_audio Default Input Device State', 'state_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_audio/DOERAKKER-PC_audio_default_input_device_state/state', 'encoding': 'utf-8', 'force_update': False, 'payload_not_available': 'offline', 'payload_available': 'online', 'availability_mode': 'latest', 'qos': 0, 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_audio Default Input Device State'

2024-01-22 20:18:34.550 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/DOERAKKER-PC/availability', 'icon': 'mdi:microphone', 'unique_id': 'DOERAKKER-PC_audio_default_input_device_muted', 'device': {'identifiers': ['hass.agent-DOERAKKER-PC'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'DOERAKKER-PC', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'DOERAKKER-PC_audio Default Input Device Muted', 'state_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_audio/DOERAKKER-PC_audio_default_input_device_muted/state', 'encoding': 'utf-8', 'force_update': False, 'payload_not_available': 'offline', 'payload_available': 'online', 'availability_mode': 'latest', 'qos': 0, 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_audio Default Input Device Muted'

2024-01-22 20:18:34.556 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability_topic': 'homeassistant/sensor/DOERAKKER-PC/availability', 'icon': 'mdi:microphone', 'unique_id': 'DOERAKKER-PC_audio_default_input_device_volume', 'device': {'identifiers': ['hass.agent-DOERAKKER-PC'], 'manufacturer': 'LAB02 Research', 'model': 'Microsoft Windows NT 10.0.19045.0', 'name': 'DOERAKKER-PC', 'sw_version': '2022.14.0', 'connections': []}, 'name': 'DOERAKKER-PC_audio Default Input Device Volume', 'state_topic': 'homeassistant/sensor/DOERAKKER-PC/DOERAKKER-PC_audio/DOERAKKER-PC_audio_default_input_device_volume/state', 'encoding': 'utf-8', 'force_update': False, 'payload_not_available': 'offline', 'payload_available': 'online', 'availability_mode': 'latest', 'qos': 0, 'enabled_by_default': True}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes '_audio Default Input Device Volume'

2024-01-22 20:18:35.122 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for slimmelezer-bron @ 192.168.178.13: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.178.13', port=6053))]: [Errno 113] Connect call failed ('192.168.178.13', 6053) (SocketAPIError)

2024-01-22 20:18:37.608 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] buurt updated: distance=13: direction=stationary: device=ronald

2024-01-22 20:18:37.609 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching buurt data in 0.000 seconds (success: True)

2024-01-22 20:18:37.609 ERROR (MainThread) [homeassistant.components.proximity.coordinator] Unexpected error fetching plus_elspeet data:

Traceback (most recent call last):

File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 300, in _async_refresh

self.data = await self._async_update_data()

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/src/homeassistant/homeassistant/components/proximity/coordinator.py", line 227, in _async_update_data

assert new_distance is not None and old_distance is not None

^^^^^^^^^^^^^^^^^^^^^^^^

AssertionError

2024-01-22 20:18:37.615 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching plus_elspeet data in 0.006 seconds (success: False)

2024-01-22 20:18:37.616 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] interakt_countour_nunspeet updated: distance=10101: direction=stationary: device=ronald

2024-01-22 20:18:37.616 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching interakt_countour_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:37.617 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] shopping_nunspeet updated: distance=9329: direction=stationary: device=ronald

2024-01-22 20:18:37.617 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching shopping_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:37.617 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] appie_nunspeet updated: distance=9264: direction=stationary: device=ronald

2024-01-22 20:18:37.617 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching appie_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:37.618 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] lidl_nunspeet updated: distance=9193: direction=stationary: device=ronald

2024-01-22 20:18:37.618 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching lidl_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:37.618 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] welkoop_nunspeet updated: distance=8630: direction=stationary: device=ronald

2024-01-22 20:18:37.618 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching welkoop_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:37.619 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] clement_werk updated: distance=33: direction=stationary: device=clement

2024-01-22 20:18:37.619 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching clement_werk data in 0.000 seconds (success: True)

2024-01-22 20:18:37.619 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] closest device is one of the other devices -> unknown

2024-01-22 20:18:37.620 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching buurt data in 0.000 seconds (success: True)

2024-01-22 20:18:37.620 ERROR (MainThread) [homeassistant.components.proximity.coordinator] Unexpected error fetching plus_elspeet data:

Traceback (most recent call last):

File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 300, in _async_refresh

self.data = await self._async_update_data()

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/src/homeassistant/homeassistant/components/proximity/coordinator.py", line 227, in _async_update_data

assert new_distance is not None and old_distance is not None

^^^^^^^^^^^^^^^^^^^^^^^^

AssertionError

2024-01-22 20:18:37.625 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching plus_elspeet data in 0.005 seconds (success: False)

2024-01-22 20:18:37.625 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] closest device is one of the other devices -> unknown

2024-01-22 20:18:37.625 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching shopping_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:37.626 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] closest device is one of the other devices -> unknown

2024-01-22 20:18:37.626 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching appie_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:37.627 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] closest device is one of the other devices -> unknown

2024-01-22 20:18:37.627 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching lidl_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:37.628 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] closest device is one of the other devices -> unknown

2024-01-22 20:18:37.628 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching welkoop_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:37.729 WARNING (MainThread) [homeassistant.components.homeassistant.triggers.numeric_state] Error initializing 'monitor 00 solar power produced' trigger: In 'numeric_state' condition: unknown entity proximity.home

2024-01-22 20:18:54.724 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] buurt updated: distance=5: direction=stationary: device=ronald

2024-01-22 20:18:54.724 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching buurt data in 0.000 seconds (success: True)

2024-01-22 20:18:54.725 ERROR (MainThread) [homeassistant.components.proximity.coordinator] Unexpected error fetching plus_elspeet data:

Traceback (most recent call last):

File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 300, in _async_refresh

self.data = await self._async_update_data()

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File "/usr/src/homeassistant/homeassistant/components/proximity/coordinator.py", line 227, in _async_update_data

assert new_distance is not None and old_distance is not None

^^^^^^^^^^^^^^^^^^^^^^^^

AssertionError

2024-01-22 20:18:54.730 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching plus_elspeet data in 0.005 seconds (success: False)

2024-01-22 20:18:54.730 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] interakt_countour_nunspeet updated: distance=10098: direction=stationary: device=ronald

2024-01-22 20:18:54.730 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching interakt_countour_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:54.731 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] shopping_nunspeet updated: distance=9326: direction=stationary: device=ronald

2024-01-22 20:18:54.731 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching shopping_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:54.732 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] appie_nunspeet updated: distance=9261: direction=stationary: device=ronald

2024-01-22 20:18:54.732 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching appie_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:54.732 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] lidl_nunspeet updated: distance=9190: direction=stationary: device=ronald

2024-01-22 20:18:54.732 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching lidl_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:18:54.733 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] welkoop_nunspeet updated: distance=8626: direction=stationary: device=ronald

2024-01-22 20:18:54.733 DEBUG (MainThread) [homeassistant.components.proximity.coordinator] Finished fetching welkoop_nunspeet data in 0.000 seconds (success: True)

2024-01-22 20:20:10.443 WARNING (Recorder) [homeassistant.components.sensor.recorder] The unit of sensor.waterverbruik_per_kwartier (m³) cannot be converted to the unit of previously compiled statistics (None). Generation of long term statistics will be suppressed unless the unit changes back to None or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this

2024-01-22 20:20:10.444 WARNING (Recorder) [homeassistant.components.sensor.recorder] The unit of sensor.waterverbruik_per_uur (m³) cannot be converted to the unit of previously compiled statistics (None). Generation of long term statistics will be suppressed unless the unit changes back to None or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this

2024-01-22 20:20:10.444 WARNING (Recorder) [homeassistant.components.sensor.recorder] The unit of sensor.waterverbruik_per_dag (m³) cannot be converted to the unit of previously compiled statistics (None). Generation of long term statistics will be suppressed unless the unit changes back to None or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this

2024-01-22 20:20:10.444 WARNING (Recorder) [homeassistant.components.sensor.recorder] The unit of sensor.waterverbruik_per_week (m³) cannot be converted to the unit of previously compiled statistics (None). Generation of long term statistics will be suppressed unless the unit changes back to None or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this

2024-01-22 20:20:10.444 WARNING (Recorder) [homeassistant.components.sensor.recorder] The unit of sensor.openweathermap_rain (mm/h) cannot be converted to the unit of previously compiled statistics (mm). Generation of long term statistics will be suppressed unless the unit changes back to mm or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this

2024-01-22 20:20:10.445 WARNING (Recorder) [homeassistant.components.sensor.recorder] The unit of sensor.openweathermap_snow (mm/h) cannot be converted to the unit of previously compiled statistics (mm). Generation of long term statistics will be suppressed unless the unit changes back to mm or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this

mib1185 commented 9 months ago

please don't paste the content of the log, but attach the file

DoerakkerHA commented 9 months ago

This will have to wait till tomorrow … my IPhone does not cooperate Kind RegardsROnald GroeneveldSent from my iPhone +31 650 989 689On 22 Jan 2024, at 20:31, Michael @.***> wrote: please don't paste the content of the log, but attach the file

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

DoerakkerHA commented 9 months ago

home-assistant.log

DoerakkerHA commented 9 months ago

error found: in the definition of the plus_elspeet: zone: zone.plus_elspeet

during entry visual code showed zone. instead of just the name of the zone plus_elspeet. Upon setting it back to just the zone name the error did no longer occur

home-assistant / core