Couple of errors not sure what to do

[Operations8 (Nick)]

i am seeing a few errors/warnings in the log, not sure how to fix this. Nr4. maybe something to do with that Samba backup doesnt work anymore? (error: Cannot create backup). Maybe not error/warning is a immediate problem, but i assumed HASS should run with as little errors as possible.

Nr 1: EDIT: Solved by @Mats789
s>```
Logger: homeassistant.components.automation.download_ring_video_front_porch
Source: helpers/script.py:420
Integration: Automatisering (documentation, issues)
First occurred: 12:20:41 (2 occurrences)
Last logged: 12:21:37

Download Ring Video (Front Porch): Error executing script. Invalid data for call_service at pos 2: invalid url for dictionary value @ data[‘url’]

```
Is part of thiis automation:

```
alias: Download Ring Video (Front Porch)
description: “”
trigger:
- platform: state
entity_id:
- binary_sensor.voordeur_motion
to: “on”
action:
- wait_for_trigger:
- platform: state
entity_id: select.voordeur_event_select
attribute: eventId
timeout: “00:05”
- service: downloader.download_file
data_template:
url: “{{ states.select.voordeur_event_select.attributes.recordingUrl }}”
subdir: Voordeur
filename: “{{ now().strftime( ‘%Y%m%dT%H%M%S_motion.mp4’ ) }}”
overwrite: false

```
Downloader developermodus looks like this:

</s> <s>service: downloader.download_file</s> <s>data:</s> <s> overwrite: false</s> <s>

Nr2: EDIT: Solved by @Tom_I

```
Logger: homeassistant.components.mqtt.mixins
Source: components/mqtt/mixins.py:294
Integration: MQTT (documentation, issues)
First occurred: 00:16:43 (58 occurrences)
Last logged: 12:21:04

MQTT entity name starts with the device name in your config {‘name’: ‘Beneden Snooze Minutes’, ‘unique_id’: ‘9c7613534481_snooze_minutes’, ‘state_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/snooze_minutes/state’, ‘command_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/snooze_minutes/command’, ‘min’: 1.0, ‘max’: 1440.0, ‘icon’: ‘hass:timer-sand’, ‘availability_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/status’, ‘payload_available’: ‘online’, ‘payload_not_available’: ‘offline’, ‘device’: {‘identifiers’: [‘9c7613534481’], ‘name’: ‘Beneden’, ‘manufacturer’: ‘Ring’, ‘model’: ‘Chime Pro v2’, ‘connections’: []}, ‘encoding’: ‘utf-8’, ‘mode’: <NumberMode.AUTO: ‘auto’>, ‘step’: 1.0, ‘availability_mode’: ‘latest’, ‘qos’: 0, ‘payload_reset’: ‘None’, ‘optimistic’: False, ‘retain’: False, ‘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 ‘Snooze Minutes’
MQTT entity name starts with the device name in your config {‘name’: ‘Beneden Play Ding Sound’, ‘unique_id’: ‘9c7613534481_play_ding_sound’, ‘state_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/play_ding_sound/state’, ‘command_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/play_ding_sound/command’, ‘icon’: ‘hass:bell-ring’, ‘availability_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/status’, ‘payload_available’: ‘online’, ‘payload_not_available’: ‘offline’, ‘device’: {‘identifiers’: [‘9c7613534481’], ‘name’: ‘Beneden’, ‘manufacturer’: ‘Ring’, ‘model’: ‘Chime Pro v2’, ‘connections’: []}, ‘encoding’: ‘utf-8’, ‘payload_off’: ‘OFF’, ‘availability_mode’: ‘latest’, ‘qos’: 0, ‘optimistic’: False, ‘payload_on’: ‘ON’, ‘retain’: False, ‘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 ‘Play Ding Sound’
MQTT entity name starts with the device name in your config {‘name’: ‘Beneden Play Motion Sound’, ‘unique_id’: ‘9c7613534481_play_motion_sound’, ‘state_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/play_motion_sound/state’, ‘command_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/play_motion_sound/command’, ‘icon’: ‘hass:bell-ring’, ‘availability_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/status’, ‘payload_available’: ‘online’, ‘payload_not_available’: ‘offline’, ‘device’: {‘identifiers’: [‘9c7613534481’], ‘name’: ‘Beneden’, ‘manufacturer’: ‘Ring’, ‘model’: ‘Chime Pro v2’, ‘connections’: []}, ‘encoding’: ‘utf-8’, ‘payload_off’: ‘OFF’, ‘availability_mode’: ‘latest’, ‘qos’: 0, ‘optimistic’: False, ‘payload_on’: ‘ON’, ‘retain’: False, ‘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 ‘Play Motion Sound’
MQTT entity name starts with the device name in your config {‘name’: ‘Beneden Nightlight Enabled’, ‘unique_id’: ‘9c7613534481_nightlight_enabled’, ‘state_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/nightlight_enabled/state’, ‘command_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/nightlight_enabled/command’, ‘json_attributes_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/nightlight_enabled/attributes’, ‘icon’: ‘mdi:lightbulb-night’, ‘availability_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/status’, ‘payload_available’: ‘online’, ‘payload_not_available’: ‘offline’, ‘device’: {‘identifiers’: [‘9c7613534481’], ‘name’: ‘Beneden’, ‘manufacturer’: ‘Ring’, ‘model’: ‘Chime Pro v2’, ‘connections’: []}, ‘encoding’: ‘utf-8’, ‘payload_off’: ‘OFF’, ‘availability_mode’: ‘latest’, ‘qos’: 0, ‘optimistic’: False, ‘payload_on’: ‘ON’, ‘retain’: False, ‘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 ‘Nightlight Enabled’
MQTT entity name starts with the device name in your config {‘name’: ‘Beneden Info’, ‘unique_id’: ‘9c7613534481_info’, ‘state_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/info/state’, ‘device_class’: <SensorDeviceClass.TIMESTAMP: ‘timestamp’>, ‘value_template’: Template<template=({{ value_json[“lastUpdate”] | default("") }}) renders=0>, ‘json_attributes_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/info/state’, ‘icon’: ‘mdi:information-outline’, ‘availability_topic’: ‘ring/bb3f1170-2265-4c20-a100-88aece947022/chime/9c7613534481/status’, ‘payload_available’: ‘online’, ‘payload_not_available’: ‘offline’, ‘device’: {‘identifiers’: [‘9c7613534481’], ‘name’: ‘Beneden’, ‘manufacturer’: ‘Ring’, ‘model’: ‘Chime Pro v2’, ‘connections’: []}, ‘encoding’: ‘utf-8’, ‘availability_mode’: ‘latest’, ‘qos’: 0, ‘force_update’: False, ‘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 ‘Info’
```

Nr3:

Logger: homeassistant.components.zha.core.cluster_handlers
Source: components/zha/core/cluster_handlers/__init__.py:508
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 00:15:49 (5 occurrences)
Last logged: 00:15:53

[0xAF7A:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
[0xAF7A:1:0x0702]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
[0xAF7A:1:0x0b04]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>')]
[0xE0B6:1:0x0b04]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), TimeoutError()]
[0xE0B6:1:0x0006]: async_initialize: all attempts have failed: [DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), DeliveryError('Failed to deliver message: <EmberStatus.DELIVERY_FAILED: 102>'), TimeoutError()]

Nr4:

Logger: homeassistant.components.hassio.handler
Source: components/hassio/handler.py:548
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 00:15:13 (13 occurrences)
Last logged: 00:15:14

/store return code 500

Nr5:

Logger: homeassistant.components.websocket_api.http.connection
Source: custom_components/browser_mod/browser.py:65
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 00:15:27 (5 occurrences)
Last logged: 00:15:30

[140633787055168] Error handling message: Unknown error (unknown_error) Nick Janssen from 172.71.182.203 (Mozilla/5.0 (Linux; Android 13; SM-S908B Build/TP1A.220624.014; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/115.0.5790.166 Mobile Safari/537.36 Home Assistant/2023.7.5-10506 (Android 13; SM-S908B))
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 26, in _handle_async_response
    await func(hass, connection, msg)
  File "/config/custom_components/browser_mod/connection.py", line 143, in handle_update
    dev = getBrowser(hass, browserID)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/browser_mod/browser.py", line 198, in getBrowser
    browsers[browserID] = BrowserModBrowser(hass, browserID)
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/browser_mod/browser.py", line 42, in __init__
    self.update_entities(hass)
  File "/config/custom_components/browser_mod/browser.py", line 71, in update_entities
    _assert_browser_sensor("sensor", "path", "Browser path", icon="mdi:web")
  File "/config/custom_components/browser_mod/browser.py", line 65, in _assert_browser_sensor
    adder = hass.data[DOMAIN][DATA_ADDERS][type]
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
KeyError: 'sensor'

Nr6:

Logger: zigpy.application
Source: components/zha/core/gateway.py:205
First occurred: 12:56:34 (1 occurrences)
Last logged: 12:56:34

Device is partially initialized: <Device model=None manuf=None nwk=0x1E92 ieee=00:17:88:01:0c:d6:0f:d7 is_initialized=False>

Nr7:

Logger: homeassistant.config_entries
Source: config_entries.py:430
First occurred: 12:56:10 (1 occurrences)
Last logged: 12:56:10

Config entry '40:A3:CC:B1:11:4B' for bluetooth integration not ready yet: Bluetooth adapter None with address 40:A3:CC:B1:11:4B not found; Retrying in background

[Mats789]

@Operations8

N1. The error states:
invalid url for dictionary value @ data['url']

Which must be:
url: "{{ states.select.voordeur_event_select.attributes.recordingUrl }}"

Have you tested this in development tools?

What about?

{{ state_attr('select.voordeur_event_select','recordingUrl') }}

[Operations8 (Nick)]

I have clicked automations in developer tools, this give me a green result.
You piece of code did fix the problem. Strange the code i used came straight from a how to.

Thanks, one error down

[Mats789]

@Operations8

automations in developer tools, this give me a green result

Not sure what you mean by automations in developer tools, I use templates under development tools to check that it gives me the correct results. (I’m not using MQTT)

[Operations8 (Nick)]

I found what you meant. The tab with the demo template in there right?

[tom_l]

@Operations8

Nr2

See:

PSA: MQTT Name changes in 2023.8

Everyone, there will be MQTT name changes in the next release of the software. There is nothing to worry about, your names are safe. However the change caused addons like Z2M (and other MQTT integrations) to update their discovery information. As it stands, Z2M will not be able to release a version with this fix until September 2023. During that time a warning will be in your logs indicating that there is an issue. You can safely ignore this warning. As of this writing, there may also be a…

[Mats789]

@Operations8

The tab with the demo template in there right?

Right