sabeechen
commented
1 year ago The logs don't say what going wrong, but something is messed up. Could you restart the addon, then provide a bug report from right after the error first comes up?
Open jimd58 opened 1 year ago
sabeechen
commented
1 year ago The logs don't say what going wrong, but something is messed up. Could you restart the addon, then provide a bug report from right after the error first comes up?
videobuff
commented
1 year ago I have suddenly the same problem. I created a backup with my own naming, and then it got stuck. Now already for 30 minutes. Restarting the Raspberry PI4 did not help. It continued where it had stopped when restarting the pi.
I have the same problem, backup is pending and whatever I do (reboot, restart etc) it continues with pending. There is plenty of space on the USB stich attaxhed to the RPI where i run the OS. And google drive has hundreds of gigs free still.
This the log from backups.
08-07 00:05:43 INFO [backup.ui.uiserver] Starting server on port 8099
08-07 00:05:43 INFO [backup.ui.uiserver] Server started
08-07 00:05:43 DEBUG [backup.model.syncer] Sync requested by Coordinator
08-07 00:05:43 INFO [backup.model.coordinator] Syncing Backups
08-07 00:05:44 DEBUG [backup.drive.driverequests] Requesting refreshed Google Drive credentials
08-07 00:06:57 INFO [backup.ha.hasource] Requesting a new backup
08-07 00:06:57 WARNING [backup.ha.hasource] A backup was already in progress
08-07 00:06:57 ERROR [backup.ui.uiserver] Error serving POST http://192.168.2.32:8123/backup?custom_name=Full-6-Augustus-23-evening&retain_drive=true&retain_ha=true¬e=
08-07 00:06:57 ERROR [backup.ui.uiserver]
addon/backup/ui/uiserver.py:791 (error_middleware)
addon/backup/ui/uiserver.py:294 (backup)
addon/backup/model/coordinator.py:253 (startBackup)
addon/backup/model/coordinator.py:353 (_withSoftLock)
addon/backup/model/coordinator.py:261 (_startBackup)
addon/backup/ha/hasource.py:212 (create)
addon/backup/ha/hasource.py:100 (raiseIfNeeded)
backup.exceptions.exceptions.BackupInProgress
08-07 00:06:57 DEBUG [backup.model.syncer] Sync requested by HomeAssistant
08-07 00:06:57 INFO [backup.model.coordinator] Syncing Backups
08-07 00:08:38 INFO [backup.drive.drivesource] Deleting 'Full Backup 2023-07-28 01:00:00' From Google Drive
08-07 00:08:44 INFO [backup.drive.drivesource] Deleting 'Full Backup 2023-07-29 01:00:00' From Google Drive
08-07 00:08:48 INFO [backup.drive.drivesource] Deleting 'Full Backup 2023-07-30 01:00:00' From Google Drive
08-07 00:08:54 INFO [backup.drive.drivesource] Deleting 'Full Backup 2023-07-31 01:00:00' From Google Drive
08-07 00:08:59 INFO [backup.drive.drivesource] Deleting 'Full Backup 2023-08-01 01:00:00' From Google Drive
08-07 00:09:38 INFO [backup.model.coordinator] Syncing Backups
08-07 00:10:50 INFO [backup.ha.hasource] A backup was already in progress
08-07 00:10:50 ERROR [backup.ui.uiserver] Error serving POST http://192.168.2.32:8123/backup?custom_name=&retain_drive=false&retain_ha=false¬e=
08-07 00:10:50 ERROR [backup.ui.uiserver]
addon/backup/ui/uiserver.py:791 (error_middleware)
addon/backup/ui/uiserver.py:294 (backup)
addon/backup/model/coordinator.py:253 (startBackup)
addon/backup/model/coordinator.py:353 (_withSoftLock)
addon/backup/model/coordinator.py:261 (_startBackup)
addon/backup/ha/hasource.py:200 (create)
backup.exceptions.exceptions.BackupInProgress
08-07 00:16:26 INFO [backup.model.coordinator] Syncing Backups
If you have anything else that could help explain what happened, click "Markdown" above and write it here.Addon version: 0.111.1
Home Assistant Version: 2023.8.1
Supervisor Version: 2023.07.1
Supervisor Channel: stable
Hassos Version: 10.4
Docker Version: 23.0.6
Architecture: aarch64
Machine: raspberrypi4-64
Date: 2023-08-06T22:27:45.533491+00:00
Timezone: Europe/Amsterdam
Failure Time: Never
Last Good Sync: 2023-08-06T22:16:26.716600+00:00
Next Sync: 2023-08-06T23:00:00+00:00
Next Backup: 2023-08-06T23:00:00+00:00
Next Cache Warm: 2023-08-06T22:56:04.119885+00:00
Time Offset: 0.0
No error could be identified automatically.Backups:
{
"HomeAssistant": {
"backups": 5,
"retained": 0,
"deletable": 5,
"name": "HomeAssistant",
"title": "Home Assistant",
"latest": "2023-08-06T22:06:57Z",
"max": 4,
"enabled": true,
"icon": "home-assistant",
"ignored": 32,
"detail": "",
"size": "1.6 GB",
"ignored_size": "2.0 GB",
"free_space": "87.3 GB"
},
"GoogleDrive": {
"backups": 5,
"retained": 0,
"deletable": 5,
"name": "GoogleDrive",
"title": "Google Drive",
"latest": "2023-08-05T23:00:00Z",
"max": 10,
"enabled": true,
"icon": "google-drive",
"ignored": 0,
"detail": "fhaschott@gmail.com",
"size": "2.0 GB",
"ignored_size": "0.0 B",
"free_space": "11.3 GB"
}
} {
"Setting.MAX_BACKUPS_IN_GOOGLE_DRIVE": 10,
"Setting.DAYS_BETWEEN_BACKUPS": 1.0,
"Setting.IGNORE_OTHER_BACKUPS": true,
"Setting.DELETE_BEFORE_NEW_BACKUP": true,
"Setting.BACKUP_TIME_OF_DAY": "01:00",
"Setting.SEND_ERROR_REPORTS": true
} 08-07 00:05:43 INFO [backup.ui.uiserver] Starting server on port 8099
08-07 00:05:43 INFO [backup.ui.uiserver] Server started
08-07 00:05:43 DEBUG [backup.model.syncer] Sync requested by Coordinator
08-07 00:05:43 INFO [backup.model.coordinator] Syncing Backups
08-07 00:05:44 DEBUG [backup.drive.driverequests] Requesting refreshed Google Drive credentials
08-07 00:06:57 INFO [backup.ha.hasource] Requesting a new backup
08-07 00:06:57 WARNING [backup.ha.hasource] A backup was already in progress
08-07 00:06:57 ERROR [backup.ui.uiserver] Error serving POST http://192.168.2.32:8123/backup?custom_name=Full-6-Augustus-23-evening&retain_drive=true&retain_ha=true¬e=
08-07 00:06:57 ERROR [backup.ui.uiserver]
addon/backup/ui/uiserver.py:791 (error_middleware)
addon/backup/ui/uiserver.py:294 (backup)
addon/backup/model/coordinator.py:253 (startBackup)
addon/backup/model/coordinator.py:353 (_withSoftLock)
addon/backup/model/coordinator.py:261 (_startBackup)
addon/backup/ha/hasource.py:212 (create)
addon/backup/ha/hasource.py:100 (raiseIfNeeded)
backup.exceptions.exceptions.BackupInProgress
08-07 00:06:57 DEBUG [backup.model.syncer] Sync requested by HomeAssistant
08-07 00:06:57 INFO [backup.model.coordinator] Syncing Backups
08-07 00:08:38 INFO [backup.drive.drivesource] Deleting 'Full Backup 2023-07-28 01:00:00' From Google Drive
08-07 00:08:44 INFO [backup.drive.drivesource] Deleting 'Full Backup 2023-07-29 01:00:00' From Google Drive
08-07 00:08:48 INFO [backup.drive.drivesource] Deleting 'Full Backup 2023-07-30 01:00:00' From Google Drive
08-07 00:08:54 INFO [backup.drive.drivesource] Deleting 'Full Backup 2023-07-31 01:00:00' From Google Drive
08-07 00:08:59 INFO [backup.drive.drivesource] Deleting 'Full Backup 2023-08-01 01:00:00' From Google Drive
08-07 00:09:38 INFO [backup.model.coordinator] Syncing Backups
08-07 00:10:50 INFO [backup.ha.hasource] A backup was already in progress
08-07 00:10:50 ERROR [backup.ui.uiserver] Error serving POST http://192.168.2.32:8123/backup?custom_name=&retain_drive=false&retain_ha=false¬e=
08-07 00:10:50 ERROR [backup.ui.uiserver]
addon/backup/ui/uiserver.py:791 (error_middleware)
addon/backup/ui/uiserver.py:294 (backup)
addon/backup/model/coordinator.py:253 (startBackup)
addon/backup/model/coordinator.py:353 (_withSoftLock)
addon/backup/model/coordinator.py:261 (_startBackup)
addon/backup/ha/hasource.py:200 (create)
backup.exceptions.exceptions.BackupInProgress
08-07 00:16:26 INFO [backup.model.coordinator] Syncing Backups [33m23-08-07 00:17:14 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon TasmoAdmin is unhealthy, restarting...[0m
[32m23-08-07 00:17:14 INFO (SyncWorker_2) [supervisor.docker.interface] Stopping addon_a0d7b954_sonweb application[0m
[32m23-08-07 00:17:19 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning addon_a0d7b954_sonweb application[0m
[32m23-08-07 00:17:21 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/tasmoadmin/aarch64 with version 0.25.0[0m
[33m23-08-07 00:18:52 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon TasmoAdmin is unhealthy, restarting...[0m
[32m23-08-07 00:18:52 INFO (SyncWorker_7) [supervisor.docker.interface] Stopping addon_a0d7b954_sonweb application[0m
[32m23-08-07 00:18:57 INFO (SyncWorker_7) [supervisor.docker.interface] Cleaning addon_a0d7b954_sonweb application[0m
[32m23-08-07 00:18:59 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/tasmoadmin/aarch64 with version 0.25.0[0m
[31m23-08-07 00:20:30 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-8008' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:1042> exception=AddonsJobError('Rate limit exceeded, more then 10 calls in 0:30:00')>[0m
Traceback (most recent call last):
File "/usr/src/supervisor/supervisor/addons/addon.py", line 1056, in watchdog_container
await self._restart_after_problem(self, event.state)
File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 144, in wrapper
raise on_condition(
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more then 10 calls in 0:30:00
[32m23-08-07 00:24:47 INFO (MainThread) [supervisor.api.middleware.security] /core/info access from cebe7a76_hassio_google_drive_backup[0m
[32m23-08-07 00:24:47 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup[0m
[32m23-08-07 00:24:47 INFO (MainThread) [supervisor.api.middleware.security] /mounts access from cebe7a76_hassio_google_drive_backup[0m
[32m23-08-07 00:24:47 INFO (MainThread) [supervisor.api.middleware.security] /addons access from cebe7a76_hassio_google_drive_backup[0m
[32m23-08-07 00:25:31 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from a0d7b954_ssh[0m
[32m23-08-07 00:25:31 INFO (MainThread) [supervisor.api.middleware.security] /network/info access from a0d7b954_ssh[0m
[32m23-08-07 00:25:31 INFO (MainThread) [supervisor.api.middleware.security] /host/info access from a0d7b954_ssh[0m
[32m23-08-07 00:25:31 INFO (MainThread) [supervisor.api.middleware.security] /core/info access from a0d7b954_ssh[0m
[32m23-08-07 00:27:34 INFO (MainThread) [supervisor.api.middleware.security] /core/info access from cebe7a76_hassio_google_drive_backup[0m
[32m23-08-07 00:27:34 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/info access from cebe7a76_hassio_google_drive_backup[0m
[32m23-08-07 00:27:34 INFO (MainThread) [supervisor.api.middleware.security] /mounts access from cebe7a76_hassio_google_drive_backup[0m
[32m23-08-07 00:27:34 INFO (MainThread) [supervisor.api.middleware.security] /addons access from cebe7a76_hassio_google_drive_backup[0m
[32m23-08-07 00:27:45 INFO (MainThread) [supervisor.api.middleware.security] /supervisor/logs access from cebe7a76_hassio_google_drive_backup[0m
[33m2023-08-07 00:13:01.766 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Beweging Keuken/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/Beweging Keuken/set/sensitivity', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138a62dc0d23f'], 'manufacturer': 'TuYa', 'model': 'Motion sensor (IH012-RT01)', 'name': 'Beweging Keuken', 'connections': []}, 'entity_category': <EntityCategory.CONFIG: 'config'>, 'icon': 'mdi:tune', 'json_attributes_topic': 'zigbee2mqtt/Beweging Keuken', 'name': 'Beweging Keuken sensitivity', 'options': ['low', 'medium', 'high'], 'state_topic': 'zigbee2mqtt/Beweging Keuken', 'unique_id': '0xa4c138a62dc0d23f_sensitivity_zigbee2mqtt', 'value_template': Template<template=({{ value_json.sensitivity }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'payload_available': 'online', 'payload_not_available': 'offline', 'enabled_by_default': True, 'optimistic': False}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Sensitivity'[0m
[33m2023-08-07 00:13:01.771 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Beweging Keuken/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/Beweging Keuken/set/keep_time', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138a62dc0d23f'], 'manufacturer': 'TuYa', 'model': 'Motion sensor (IH012-RT01)', 'name': 'Beweging Keuken', 'connections': []}, 'entity_category': <EntityCategory.CONFIG: 'config'>, 'icon': 'mdi:av-timer', 'json_attributes_topic': 'zigbee2mqtt/Beweging Keuken', 'name': 'Beweging Keuken keep time', 'options': ['30', '60', '120'], 'state_topic': 'zigbee2mqtt/Beweging Keuken', 'unique_id': '0xa4c138a62dc0d23f_keep_time_zigbee2mqtt', 'value_template': Template<template=({{ value_json.keep_time }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'payload_available': 'online', 'payload_not_available': 'offline', 'enabled_by_default': True, 'optimistic': False}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Keep time'[0m
[33m2023-08-07 00:13:01.785 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Extender-Ikea/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0x2c1165fffec5a512'], 'manufacturer': 'IKEA', 'model': 'TRADFRI signal repeater (E1746)', 'name': 'Extender-Ikea', 'sw_version': '2.3.086', 'connections': []}, 'device_class': <BinarySensorDeviceClass.UPDATE: 'update'>, 'enabled_by_default': False, 'entity_category': <EntityCategory.DIAGNOSTIC: 'diagnostic'>, 'json_attributes_topic': 'zigbee2mqtt/Extender-Ikea', 'name': 'Extender-Ikea update available', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Extender-Ikea', 'unique_id': '0x2c1165fffec5a512_update_available_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['state'] == "available" }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Update available'[0m
[33m2023-08-07 00:13:01.792 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-1/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0xa4c13815d0b24fcc'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-1', 'connections': []}, 'device_class': <BinarySensorDeviceClass.UPDATE: 'update'>, 'enabled_by_default': False, 'entity_category': <EntityCategory.DIAGNOSTIC: 'diagnostic'>, 'json_attributes_topic': 'zigbee2mqtt/Kamer-1', 'name': 'Kamer-1 update available', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Kamer-1', 'unique_id': '0xa4c13815d0b24fcc_update_available_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['state'] == "available" }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Update available'[0m
[33m2023-08-07 00:13:01.797 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-2/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0xa4c1383af63d4473'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-2', 'connections': []}, 'device_class': <BinarySensorDeviceClass.UPDATE: 'update'>, 'enabled_by_default': False, 'entity_category': <EntityCategory.DIAGNOSTIC: 'diagnostic'>, 'json_attributes_topic': 'zigbee2mqtt/Kamer-2', 'name': 'Kamer-2 update available', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Kamer-2', 'unique_id': '0xa4c1383af63d4473_update_available_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['state'] == "available" }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Update available'[0m
[33m2023-08-07 00:13:01.801 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-3/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138b17fd10030'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-3', 'connections': []}, 'device_class': <BinarySensorDeviceClass.UPDATE: 'update'>, 'enabled_by_default': False, 'entity_category': <EntityCategory.DIAGNOSTIC: 'diagnostic'>, 'json_attributes_topic': 'zigbee2mqtt/Kamer-3', 'name': 'Kamer-3 update available', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Kamer-3', 'unique_id': '0xa4c138b17fd10030_update_available_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['state'] == "available" }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Update available'[0m
[33m2023-08-07 00:13:01.807 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-5/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138e1d1f24e1f'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-5', 'connections': []}, 'device_class': <BinarySensorDeviceClass.UPDATE: 'update'>, 'enabled_by_default': False, 'entity_category': <EntityCategory.DIAGNOSTIC: 'diagnostic'>, 'json_attributes_topic': 'zigbee2mqtt/Kamer-5', 'name': 'Kamer-5 update available', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Kamer-5', 'unique_id': '0xa4c138e1d1f24e1f_update_available_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['state'] == "available" }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Update available'[0m
[33m2023-08-07 00:13:01.810 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-6/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138fe2a3a2d5a'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-6', 'connections': []}, 'device_class': <BinarySensorDeviceClass.UPDATE: 'update'>, 'enabled_by_default': False, 'entity_category': <EntityCategory.DIAGNOSTIC: 'diagnostic'>, 'json_attributes_topic': 'zigbee2mqtt/Kamer-6', 'name': 'Kamer-6 update available', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Kamer-6', 'unique_id': '0xa4c138fe2a3a2d5a_update_available_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['state'] == "available" }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Update available'[0m
[33m2023-08-07 00:13:01.814 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-7/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138fe8df5bc9e'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-7', 'connections': []}, 'device_class': <BinarySensorDeviceClass.UPDATE: 'update'>, 'enabled_by_default': False, 'entity_category': <EntityCategory.DIAGNOSTIC: 'diagnostic'>, 'json_attributes_topic': 'zigbee2mqtt/Kamer-7', 'name': 'Kamer-7 update available', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Kamer-7', 'unique_id': '0xa4c138fe8df5bc9e_update_available_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['state'] == "available" }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Update available'[0m
[33m2023-08-07 00:13:01.819 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Beweging Sauna/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0xa4c1380bc3e44a6c'], 'manufacturer': 'TuYa', 'model': 'Motion sensor (IH012-RT01)', 'name': 'Beweging Sauna', 'connections': []}, 'device_class': <BinarySensorDeviceClass.MOTION: 'motion'>, 'json_attributes_topic': 'zigbee2mqtt/Beweging Sauna', 'name': 'Beweging Sauna occupancy', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Beweging Sauna', 'unique_id': '0xa4c1380bc3e44a6c_occupancy_zigbee2mqtt', 'value_template': Template<template=({{ value_json.occupancy }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline', '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 'Occupancy'[0m
[33m2023-08-07 00:13:01.829 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Beweging Sauna/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0xa4c1380bc3e44a6c'], 'manufacturer': 'TuYa', 'model': 'Motion sensor (IH012-RT01)', 'name': 'Beweging Sauna', 'connections': []}, 'device_class': <BinarySensorDeviceClass.BATTERY: 'battery'>, 'entity_category': <EntityCategory.DIAGNOSTIC: 'diagnostic'>, 'json_attributes_topic': 'zigbee2mqtt/Beweging Sauna', 'name': 'Beweging Sauna battery low', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Beweging Sauna', 'unique_id': '0xa4c1380bc3e44a6c_battery_low_zigbee2mqtt', 'value_template': Template<template=({{ value_json.battery_low }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline', '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 'Battery low'[0m
[33m2023-08-07 00:13:01.838 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Beweging Sauna/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0xa4c1380bc3e44a6c'], 'manufacturer': 'TuYa', 'model': 'Motion sensor (IH012-RT01)', 'name': 'Beweging Sauna', 'connections': []}, 'device_class': <BinarySensorDeviceClass.TAMPER: 'tamper'>, 'json_attributes_topic': 'zigbee2mqtt/Beweging Sauna', 'name': 'Beweging Sauna tamper', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Beweging Sauna', 'unique_id': '0xa4c1380bc3e44a6c_tamper_zigbee2mqtt', 'value_template': Template<template=({{ value_json.tamper }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline', '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 'Tamper'[0m
[33m2023-08-07 00:13:01.843 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Beweging Keuken/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138a62dc0d23f'], 'manufacturer': 'TuYa', 'model': 'Motion sensor (IH012-RT01)', 'name': 'Beweging Keuken', 'connections': []}, 'device_class': <BinarySensorDeviceClass.MOTION: 'motion'>, 'json_attributes_topic': 'zigbee2mqtt/Beweging Keuken', 'name': 'Beweging Keuken occupancy', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Beweging Keuken', 'unique_id': '0xa4c138a62dc0d23f_occupancy_zigbee2mqtt', 'value_template': Template<template=({{ value_json.occupancy }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline', '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 'Occupancy'[0m
[33m2023-08-07 00:13:01.847 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Beweging Keuken/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138a62dc0d23f'], 'manufacturer': 'TuYa', 'model': 'Motion sensor (IH012-RT01)', 'name': 'Beweging Keuken', 'connections': []}, 'device_class': <BinarySensorDeviceClass.BATTERY: 'battery'>, 'entity_category': <EntityCategory.DIAGNOSTIC: 'diagnostic'>, 'json_attributes_topic': 'zigbee2mqtt/Beweging Keuken', 'name': 'Beweging Keuken battery low', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Beweging Keuken', 'unique_id': '0xa4c138a62dc0d23f_battery_low_zigbee2mqtt', 'value_template': Template<template=({{ value_json.battery_low }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline', '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 'Battery low'[0m
[33m2023-08-07 00:13:01.850 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Beweging Keuken/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138a62dc0d23f'], 'manufacturer': 'TuYa', 'model': 'Motion sensor (IH012-RT01)', 'name': 'Beweging Keuken', 'connections': []}, 'device_class': <BinarySensorDeviceClass.TAMPER: 'tamper'>, 'json_attributes_topic': 'zigbee2mqtt/Beweging Keuken', 'name': 'Beweging Keuken tamper', 'payload_off': 'False', 'payload_on': 'True', 'state_topic': 'zigbee2mqtt/Beweging Keuken', 'unique_id': '0xa4c138a62dc0d23f_tamper_zigbee2mqtt', 'value_template': Template<template=({{ value_json.tamper }}) renders=0>, 'qos': 0, 'encoding': 'utf-8', 'payload_available': 'online', 'force_update': False, 'payload_not_available': 'offline', '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 'Tamper'[0m
[33m2023-08-07 00:13:01.884 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT device name is equal to entity name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Extender-Ikea/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/bridge/request/device/ota_update/update', 'device': {'identifiers': ['zigbee2mqtt_0x2c1165fffec5a512'], 'manufacturer': 'IKEA', 'model': 'TRADFRI signal repeater (E1746)', 'name': 'Extender-Ikea', 'sw_version': '2.3.086', 'connections': []}, 'device_class': <UpdateDeviceClass.FIRMWARE: 'firmware'>, 'entity_picture': 'https://github.com/Koenkk/zigbee2mqtt/raw/master/images/logo.png', 'json_attributes_topic': 'zigbee2mqtt/Extender-Ikea', 'latest_version_template': Template<template=({{ value_json['update']['latest_version'] }}) renders=0>, 'latest_version_topic': 'zigbee2mqtt/Extender-Ikea', 'name': 'Extender-Ikea', 'payload_install': '{"id": "0x2c1165fffec5a512"}', 'state_topic': 'zigbee2mqtt/Extender-Ikea', 'unique_id': '0x2c1165fffec5a512_update_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['installed_version'] }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'payload_available': 'online', 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The entity name will be set to `null`[0m
[33m2023-08-07 00:13:01.900 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT device name is equal to entity name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-1/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/bridge/request/device/ota_update/update', 'device': {'identifiers': ['zigbee2mqtt_0xa4c13815d0b24fcc'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-1', 'connections': []}, 'device_class': <UpdateDeviceClass.FIRMWARE: 'firmware'>, 'entity_picture': 'https://github.com/Koenkk/zigbee2mqtt/raw/master/images/logo.png', 'json_attributes_topic': 'zigbee2mqtt/Kamer-1', 'latest_version_template': Template<template=({{ value_json['update']['latest_version'] }}) renders=0>, 'latest_version_topic': 'zigbee2mqtt/Kamer-1', 'name': 'Kamer-1', 'payload_install': '{"id": "0xa4c13815d0b24fcc"}', 'state_topic': 'zigbee2mqtt/Kamer-1', 'unique_id': '0xa4c13815d0b24fcc_update_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['installed_version'] }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'payload_available': 'online', 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The entity name will be set to `null`[0m
[33m2023-08-07 00:13:01.906 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT device name is equal to entity name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-2/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/bridge/request/device/ota_update/update', 'device': {'identifiers': ['zigbee2mqtt_0xa4c1383af63d4473'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-2', 'connections': []}, 'device_class': <UpdateDeviceClass.FIRMWARE: 'firmware'>, 'entity_picture': 'https://github.com/Koenkk/zigbee2mqtt/raw/master/images/logo.png', 'json_attributes_topic': 'zigbee2mqtt/Kamer-2', 'latest_version_template': Template<template=({{ value_json['update']['latest_version'] }}) renders=0>, 'latest_version_topic': 'zigbee2mqtt/Kamer-2', 'name': 'Kamer-2', 'payload_install': '{"id": "0xa4c1383af63d4473"}', 'state_topic': 'zigbee2mqtt/Kamer-2', 'unique_id': '0xa4c1383af63d4473_update_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['installed_version'] }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'payload_available': 'online', 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The entity name will be set to `null`[0m
[33m2023-08-07 00:13:01.913 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT device name is equal to entity name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-3/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/bridge/request/device/ota_update/update', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138b17fd10030'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-3', 'connections': []}, 'device_class': <UpdateDeviceClass.FIRMWARE: 'firmware'>, 'entity_picture': 'https://github.com/Koenkk/zigbee2mqtt/raw/master/images/logo.png', 'json_attributes_topic': 'zigbee2mqtt/Kamer-3', 'latest_version_template': Template<template=({{ value_json['update']['latest_version'] }}) renders=0>, 'latest_version_topic': 'zigbee2mqtt/Kamer-3', 'name': 'Kamer-3', 'payload_install': '{"id": "0xa4c138b17fd10030"}', 'state_topic': 'zigbee2mqtt/Kamer-3', 'unique_id': '0xa4c138b17fd10030_update_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['installed_version'] }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'payload_available': 'online', 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The entity name will be set to `null`[0m
[33m2023-08-07 00:13:01.920 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT device name is equal to entity name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-5/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/bridge/request/device/ota_update/update', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138e1d1f24e1f'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-5', 'connections': []}, 'device_class': <UpdateDeviceClass.FIRMWARE: 'firmware'>, 'entity_picture': 'https://github.com/Koenkk/zigbee2mqtt/raw/master/images/logo.png', 'json_attributes_topic': 'zigbee2mqtt/Kamer-5', 'latest_version_template': Template<template=({{ value_json['update']['latest_version'] }}) renders=0>, 'latest_version_topic': 'zigbee2mqtt/Kamer-5', 'name': 'Kamer-5', 'payload_install': '{"id": "0xa4c138e1d1f24e1f"}', 'state_topic': 'zigbee2mqtt/Kamer-5', 'unique_id': '0xa4c138e1d1f24e1f_update_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['installed_version'] }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'payload_available': 'online', 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The entity name will be set to `null`[0m
[33m2023-08-07 00:13:01.926 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT device name is equal to entity name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-6/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/bridge/request/device/ota_update/update', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138fe2a3a2d5a'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-6', 'connections': []}, 'device_class': <UpdateDeviceClass.FIRMWARE: 'firmware'>, 'entity_picture': 'https://github.com/Koenkk/zigbee2mqtt/raw/master/images/logo.png', 'json_attributes_topic': 'zigbee2mqtt/Kamer-6', 'latest_version_template': Template<template=({{ value_json['update']['latest_version'] }}) renders=0>, 'latest_version_topic': 'zigbee2mqtt/Kamer-6', 'name': 'Kamer-6', 'payload_install': '{"id": "0xa4c138fe2a3a2d5a"}', 'state_topic': 'zigbee2mqtt/Kamer-6', 'unique_id': '0xa4c138fe2a3a2d5a_update_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['installed_version'] }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'payload_available': 'online', 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The entity name will be set to `null`[0m
[33m2023-08-07 00:13:01.932 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT device name is equal to entity name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-7/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/bridge/request/device/ota_update/update', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138fe8df5bc9e'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-7', 'connections': []}, 'device_class': <UpdateDeviceClass.FIRMWARE: 'firmware'>, 'entity_picture': 'https://github.com/Koenkk/zigbee2mqtt/raw/master/images/logo.png', 'json_attributes_topic': 'zigbee2mqtt/Kamer-7', 'latest_version_template': Template<template=({{ value_json['update']['latest_version'] }}) renders=0>, 'latest_version_topic': 'zigbee2mqtt/Kamer-7', 'name': 'Kamer-7', 'payload_install': '{"id": "0xa4c138fe8df5bc9e"}', 'state_topic': 'zigbee2mqtt/Kamer-7', 'unique_id': '0xa4c138fe8df5bc9e_update_zigbee2mqtt', 'value_template': Template<template=({{ value_json['update']['installed_version'] }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'payload_available': 'online', 'payload_not_available': 'offline', 'enabled_by_default': True}, this is not expected. Please correct your configuration. The entity name will be set to `null`[0m
[33m2023-08-07 00:13:01.942 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-1/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/Kamer-1/set/child_lock', 'device': {'identifiers': ['zigbee2mqtt_0xa4c13815d0b24fcc'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-1', 'connections': []}, 'json_attributes_topic': 'zigbee2mqtt/Kamer-1', 'name': 'Kamer-1 child lock', 'payload_lock': 'LOCK', 'payload_unlock': 'UNLOCK', 'state_locked': 'LOCK', 'state_topic': 'zigbee2mqtt/Kamer-1', 'state_unlocked': 'UNLOCK', 'unique_id': '0xa4c13815d0b24fcc_child_lock_zigbee2mqtt', 'value_template': Template<template=({{ value_json.child_lock }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'state_unlocking': 'UNLOCKING', 'payload_available': 'online', 'state_jammed': 'JAMMED', 'payload_not_available': 'offline', 'state_locking': 'LOCKING', 'enabled_by_default': True, 'optimistic': False}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Child lock'[0m
[33m2023-08-07 00:13:01.951 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-2/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/Kamer-2/set/child_lock', 'device': {'identifiers': ['zigbee2mqtt_0xa4c1383af63d4473'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-2', 'connections': []}, 'json_attributes_topic': 'zigbee2mqtt/Kamer-2', 'name': 'Kamer-2 child lock', 'payload_lock': 'LOCK', 'payload_unlock': 'UNLOCK', 'state_locked': 'LOCK', 'state_topic': 'zigbee2mqtt/Kamer-2', 'state_unlocked': 'UNLOCK', 'unique_id': '0xa4c1383af63d4473_child_lock_zigbee2mqtt', 'value_template': Template<template=({{ value_json.child_lock }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'state_unlocking': 'UNLOCKING', 'payload_available': 'online', 'state_jammed': 'JAMMED', 'payload_not_available': 'offline', 'state_locking': 'LOCKING', 'enabled_by_default': True, 'optimistic': False}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Child lock'[0m
[33m2023-08-07 00:13:01.956 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-3/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/Kamer-3/set/child_lock', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138b17fd10030'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-3', 'connections': []}, 'json_attributes_topic': 'zigbee2mqtt/Kamer-3', 'name': 'Kamer-3 child lock', 'payload_lock': 'LOCK', 'payload_unlock': 'UNLOCK', 'state_locked': 'LOCK', 'state_topic': 'zigbee2mqtt/Kamer-3', 'state_unlocked': 'UNLOCK', 'unique_id': '0xa4c138b17fd10030_child_lock_zigbee2mqtt', 'value_template': Template<template=({{ value_json.child_lock }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'state_unlocking': 'UNLOCKING', 'payload_available': 'online', 'state_jammed': 'JAMMED', 'payload_not_available': 'offline', 'state_locking': 'LOCKING', 'enabled_by_default': True, 'optimistic': False}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Child lock'[0m
[33m2023-08-07 00:13:01.961 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-5/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/Kamer-5/set/child_lock', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138e1d1f24e1f'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-5', 'connections': []}, 'json_attributes_topic': 'zigbee2mqtt/Kamer-5', 'name': 'Kamer-5 child lock', 'payload_lock': 'LOCK', 'payload_unlock': 'UNLOCK', 'state_locked': 'LOCK', 'state_topic': 'zigbee2mqtt/Kamer-5', 'state_unlocked': 'UNLOCK', 'unique_id': '0xa4c138e1d1f24e1f_child_lock_zigbee2mqtt', 'value_template': Template<template=({{ value_json.child_lock }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'state_unlocking': 'UNLOCKING', 'payload_available': 'online', 'state_jammed': 'JAMMED', 'payload_not_available': 'offline', 'state_locking': 'LOCKING', 'enabled_by_default': True, 'optimistic': False}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Child lock'[0m
[33m2023-08-07 00:13:02.211 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-6/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/Kamer-6/set/child_lock', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138fe2a3a2d5a'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-6', 'connections': []}, 'json_attributes_topic': 'zigbee2mqtt/Kamer-6', 'name': 'Kamer-6 child lock', 'payload_lock': 'LOCK', 'payload_unlock': 'UNLOCK', 'state_locked': 'LOCK', 'state_topic': 'zigbee2mqtt/Kamer-6', 'state_unlocked': 'UNLOCK', 'unique_id': '0xa4c138fe2a3a2d5a_child_lock_zigbee2mqtt', 'value_template': Template<template=({{ value_json.child_lock }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'state_unlocking': 'UNLOCKING', 'payload_available': 'online', 'state_jammed': 'JAMMED', 'payload_not_available': 'offline', 'state_locking': 'LOCKING', 'enabled_by_default': True, 'optimistic': False}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Child lock'[0m
[33m2023-08-07 00:13:02.227 WARNING (MainThread) [homeassistant.components.mqtt.mixins] MQTT entity name starts with the device name in your config {'availability': [{'topic': 'zigbee2mqtt/bridge/state', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}, {'topic': 'zigbee2mqtt/Kamer-7/availability', 'value_template': Template<template=({{ value_json.state }}) renders=0>, 'payload_available': 'online', 'payload_not_available': 'offline'}], 'availability_mode': 'all', 'command_topic': 'zigbee2mqtt/Kamer-7/set/child_lock', 'device': {'identifiers': ['zigbee2mqtt_0xa4c138fe8df5bc9e'], 'manufacturer': 'TuYa', 'model': 'Smart plug (with power monitoring) (TS011F_plug_1)', 'name': 'Kamer-7', 'connections': []}, 'json_attributes_topic': 'zigbee2mqtt/Kamer-7', 'name': 'Kamer-7 child lock', 'payload_lock': 'LOCK', 'payload_unlock': 'UNLOCK', 'state_locked': 'LOCK', 'state_topic': 'zigbee2mqtt/Kamer-7', 'state_unlocked': 'UNLOCK', 'unique_id': '0xa4c138fe8df5bc9e_child_lock_zigbee2mqtt', 'value_template': Template<template=({{ value_json.child_lock }}) renders=0>, 'qos': 0, 'retain': False, 'encoding': 'utf-8', 'state_unlocking': 'UNLOCKING', 'payload_available': 'online', 'state_jammed': 'JAMMED', 'payload_not_available': 'offline', 'state_locking': 'LOCKING', 'enabled_by_default': True, 'optimistic': False}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'Child lock'[0m
[33m2023-08-07 00:13:06.010 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for ttgo-display @ 192.168.2.199: Error connecting to ('192.168.2.199', 6053): [Errno 113] Connect call failed ('192.168.2.199', 6053) (SocketAPIError)[0m
`Well, at night it has solved itsself. This morning the pending backup had disappeared and a normal full backup was created. I'll be feeding the ducks soon.
Here is the backups log from last night.
` 08-07 00:16:26 INFO [backup.model.coordinator] Syncing Backups 08-07 00:39:14 INFO [backup.drive.drivesource] Saving new Google Drive credentials 08-07 00:39:15 DEBUG [backup.model.syncer] Sync requested by GoogleDrive 08-07 00:39:15 INFO [backup.model.coordinator] Syncing Backups 08-07 00:40:13 INFO [backup.model.coordinator] Syncing Backups 08-07 00:40:14 INFO [backup.ha.hasource] Deleting 'Full Backup 2023-08-03 01:00:00' from Home Assistant 08-07 00:40:14 INFO [backup.watcher] A backup directory file was modified, we'll check for new backups soon. 08-07 00:40:24 DEBUG [backup.watcher] Checking backup source for changes... 08-07 00:40:24 DEBUG [backup.model.syncer] Sync requested by Backup Directory Watcher 08-07 00:40:24 INFO [backup.model.coordinator] Syncing Backups 08-07 00:51:44 DEBUG [backup.model.destinationprecache] Preemptively retrieving and caching info from the backup destination to avoid peak demand 08-07 01:00:00 DEBUG [backup.model.syncer] Sync requested by Coordinator 08-07 01:00:00 INFO [backup.model.coordinator] Syncing Backups 08-07 01:00:00 INFO [backup.ha.hasource] Deleting 'Full Backup 2023-08-04 01:00:00' from Home Assistant 08-07 01:00:00 INFO [backup.watcher] A backup directory file was modified, we'll check for new backups soon. 08-07 01:00:00 INFO [backup.ha.hasource] A backup was already in progress 08-07 01:00:00 ERROR [backup.model.coordinator] A backup is already in progress 08-07 01:00:00 INFO [backup.model.coordinator] I'll try again in 0 seconds 08-07 01:00:01 DEBUG [backup.model.syncer] Sync requested by Coordinator 08-07 01:00:01 INFO [backup.model.coordinator] Syncing Backups 08-07 01:00:02 INFO [backup.ha.hasource] A backup was already in progress 08-07 01:00:02 ERROR [backup.model.coordinator] A backup is already in progress 08-07 01:00:02 INFO [backup.model.coordinator] I'll try again in 10 seconds 08-07 01:00:04 INFO [backup.debugworker] Sending error report (see settings to disable) 08-07 01:00:10 DEBUG [backup.watcher] Checking backup source for changes... 08-07 01:00:12 DEBUG [backup.model.syncer] Sync requested by Coordinator 08-07 01:00:12 INFO [backup.model.coordinator] Syncing Backups 08-07 01:00:12 INFO [backup.ha.hasource] A backup was already in progress 08-07 01:00:12 ERROR [backup.model.coordinator] A backup is already in progress 08-07 01:00:12 INFO [backup.model.coordinator] I'll try again in 20 seconds 08-07 01:00:32 DEBUG [backup.model.syncer] Sync requested by Coordinator 08-07 01:00:32 INFO [backup.model.coordinator] Syncing Backups 08-07 01:00:33 INFO [backup.ha.hasource] A backup was already in progress 08-07 01:00:33 ERROR [backup.model.coordinator] A backup is already in progress 08-07 01:00:33 INFO [backup.model.coordinator] I'll try again in 40 seconds 08-07 01:00:44 DEBUG [backup.model.destinationprecache] Preemptively retrieving and caching info from the backup destination to avoid peak demand 08-07 01:01:13 DEBUG [backup.model.syncer] Sync requested by Coordinator 08-07 01:01:13 INFO [backup.model.coordinator] Syncing Backups 08-07 01:01:14 INFO [backup.ha.hasource] A backup was already in progress 08-07 01:01:14 ERROR [backup.model.coordinator] A backup is already in progress 08-07 01:01:14 INFO [backup.model.coordinator] I'll try again in 1 minutes, 20 seconds 08-07 01:01:45 DEBUG [backup.model.destinationprecache] Preemptively retrieving and caching info from the backup destination to avoid peak demand 08-07 01:02:34 DEBUG [backup.model.syncer] Sync requested by Coordinator 08-07 01:02:34 INFO [backup.model.coordinator] Syncing Backups 08-07 01:02:34 INFO [backup.ha.hasource] A backup was already in progress 08-07 01:02:34 ERROR [backup.model.coordinator] A backup is already in progress 08-07 01:02:34 INFO [backup.model.coordinator] I'll try again in 2 minutes, 40 seconds 08-07 01:02:46 DEBUG [backup.model.destinationprecache] Preemptively retrieving and caching info from the backup destination to avoid peak demand 08-07 01:04:45 INFO [backup.model.coordinator] Syncing Backups 08-07 01:04:46 INFO [backup.ha.hasource] A backup was already in progress 08-07 01:04:46 ERROR [backup.model.coordinator] A backup is already in progress 08-07 01:04:46 INFO [backup.model.coordinator] I'll try again in 5 minutes, 20 seconds 08-07 01:04:46 DEBUG [backup.model.destinationprecache] Preemptively retrieving and caching info from the backup destination to avoid peak demand 08-07 01:10:06 DEBUG [backup.model.syncer] Sync requested by Coordinator 08-07 01:10:06 INFO [backup.model.coordinator] Syncing Backups 08-07 01:10:06 INFO [backup.ha.hasource] A backup was already in progress 08-07 01:10:06 ERROR [backup.model.coordinator] A backup is already in progress 08-07 01:10:06 INFO [backup.model.coordinator] I'll try again in 10 minutes, 40 seconds 08-07 01:10:47 DEBUG [backup.model.destinationprecache] Preemptively retrieving and caching info from the backup destination to avoid peak demand 08-07 01:20:46 DEBUG [backup.model.syncer] Sync requested by Coordinator 08-07 01:20:46 INFO [backup.model.coordinator] Syncing Backups 08-07 01:20:46 INFO [backup.ha.hasource] A backup was already in progress 08-07 01:20:46 ERROR [backup.model.coordinator] A backup is already in progress 08-07 01:20:46 INFO [backup.model.coordinator] I'll try again in 21 minutes, 20 seconds 08-07 01:29:48 DEBUG [backup.model.destinationprecache] Preemptively retrieving and caching info from the backup destination to avoid peak demand 08-07 01:42:06 DEBUG [backup.model.syncer] Sync requested by Coordinator 08-07 01:42:06 INFO [backup.model.coordinator] Syncing Backups 08-07 01:42:07 INFO [backup.ha.hasource] A backup was already in progress 08-07 01:42:07 ERROR [backup.model.coordinator] A backup is already in progress 08-07 01:42:07 INFO [backup.model.coordinator] I'll try again in 42 minutes, 40 seconds 08-07 02:14:48 DEBUG [backup.model.destinationprecache] Preemptively retrieving and caching info from the backup destination to avoid peak demand 08-07 02:14:49 DEBUG [backup.drive.driverequests] Requesting refreshed Google Drive credentials 08-07 02:24:47 DEBUG [backup.model.syncer] Sync requested by Coordinator 08-07 02:24:47 INFO [backup.model.coordinator] Syncing Backups 08-07 02:24:47 INFO [backup.ha.hasource] A backup was already in progress 08-07 02:24:47 ERROR [backup.model.coordinator] A backup is already in progress 08-07 02:24:47 INFO [backup.model.coordinator] I'll try again in 1 hours, 25 minutes, 20 seconds 08-07 03:06:57 DEBUG [backup.model.syncer] Sync requested by HomeAssistant 08-07 03:06:57 INFO [backup.model.coordinator] Syncing Backups 08-07 03:06:59 INFO [backup.ha.hasource] Requesting a new backup 08-07 03:07:06 INFO [backup.debugworker] Sending error report (see settings to disable) 08-07 03:18:16 INFO [backup.watcher] A backup directory file was modified, we'll check for new backups soon. 08-07 03:18:26 DEBUG [backup.watcher] Checking backup source for changes... 08-07 03:19:02 INFO [backup.watcher] A backup directory file was modified, we'll check for new backups soon. 08-07 03:19:02 INFO [backup.ha.hasource] Backup finished 08-07 03:19:03 DEBUG [backup.model.syncer] Sync requested by HomeAssistant 08-07 03:19:03 INFO [backup.model.coordinator] Syncing Backups 08-07 03:19:03 DEBUG [backup.drive.driverequests] Requesting refreshed Google Drive credentials 08-07 03:19:04 INFO [backup.drive.drivesource] Uploading 'Full Backup 2023-08-07 03:06:57' to Google Drive
`
sabeechen
commented
1 year ago There is a problem in how the addon communicates with Home Assistant. Home Assistant returns the same message for "a backup is in progress" and "the backup could be made", eg if the connection to a NAS is broken. Currently the only way around this this is to restart the addon so it attempts to create the backup again (or wait for it to time out) until the backup API Home Assistant exposes is changed to indicate what the reason for the error is.
videobuff
commented
1 year ago Thanks very nmuch for the replay. It solved itsself, which is really nice. I think my problem was that my old system used an RPI4 with USB dongle, but it got overloaded with vodeo fragments and was vreating bigger and bigger backups. I moved to a NUC with 1Tb storage and i limited the video creation and now all is really well.
I changed backup location from Google Drive to OMV NAS (local) and it loops. Any help is appreciated. Otherwise, how can I stop this?
Description:
Addon version:
0.111.1Home Assistant Version:2023.6.3Supervisor Version:2023.06.2Supervisor Channel:stableHassos Version:10.3Docker Version:23.0.6Architecture:aarch64Machine:raspberrypi4-64Date:2023-06-27T23:47:09.567307+00:00Timezone:America/Los_AngelesFailure Time:NeverLast Good Sync:2023-06-27T23:16:36.764242+00:00Next Sync:2023-06-28T00:46:41.479615+00:00Next Backup:2023-06-28T06:57:00+00:00Next Cache Warm:2023-06-28T00:43:46.789248+00:00Time Offset:0.0Exception:
Backups:
Config:
Addon Logs:
Supervisor Logs:
Home Assistant Core Logs: