2023.7: Responding services

tom_l · July 6, 2023, 6:41am

Anyone else with the slim proto media player (Squeezebox Player) seeing this?

Logger: homeassistant.setup
Source: setup.py:379
First occurred: 16:32:28 (1 occurrences)
Last logged: 16:32:28

Unable to prepare setup for platform slimproto.media_player: Platform not found (Exception importing homeassistant.components.slimproto.media_player).

EDIT: opened an issue:

github.com/home-assistant/core

2032.7.0 squeezebox player platform not found

opened 06:51AM - 06 Jul 23 UTC

tomlut

integration: squeezebox

### The problem After updating to 2023.7.0 I can no longer connect to my Raspia…udio Muse Luxe speaker via the SqueezePlayer integration. The following error is logged: ``` Logger: homeassistant.setup Source: setup.py:379 First occurred: 16:32:28 (1 occurrences) Last logged: 16:32:28 Unable to prepare setup for platform slimproto.media_player: Platform not found (Exception importing homeassistant.components.slimproto.media_player). ``` The device web page is still reachable via a web browser. ### What version of Home Assistant Core has the issue? core-2023.7.0 ### What was the last working version of Home Assistant Core? core-2023.6.3 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Squeezebox (Logitech Media Server) ### Link to integration documentation on our website https://www.home-assistant.io/integrations/squeezebox/ ### Diagnostics information _No response_ ### Example YAML snippet ```yaml Set up via UI. ``` ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

tom_l · July 6, 2023, 7:04am

Seems odd that you have to supply a URL and a picture option.

adorobis · July 6, 2023, 7:04am

Wow, since upgrade last night my log file is 700MB. Let’s see what’s inside…

pepeEL · July 6, 2023, 7:11am

Hi. I updated to 2023.7 and i dont have copy and past cards and also dont have number cards. Why?

pepe59 · July 6, 2023, 7:18am

I have 4 players here and Squeezebox integration (Logitech Media Server) and everything works as expected in HA version 2023.7

Mariusthvdb · July 6, 2023, 7:19am

the picture is for the entity_picture, the url is for the actual image
would have been neat if that would have auto set to the actual image. I havent tried that yet, so will do so now and report

update

changing that config to

template:

  - image:

      - unique_id: my_first_tmeplate_image
        name: My first template image
        url: 'http://<my_server>.local:<port>/local/images/bonen.jpg'
#         picture: /local/images/bonen.jpg

does indeed auto set the entity_picture to the image in the url:

we can override that though, so that is nice:

      - unique_id: my_first_tmeplate_image
        name: My first template image
        url: 'http:/<my_server>.local:<port>/local/images/bonen.jpg'
        picture: /local/images/espresso_art.jpg

the access token changes on each of those, so I must give the another check as I dont understand yet what that is/does.

for the frontend:

  cards:

    - type: entity
      entity: image.my_first_template_image

    - type: picture-entity
      entity: image.my_first_template_image

    - type: picture
      image: 'http://<my_server>.local:<port>/local/images/bonen.jpg'

considering the last type: picture I wonder what the added value of the new image template will be over that, being the identical url.

tom_l · July 6, 2023, 7:19am

Thanks for the info. I’ll give it another go.

EDIT: it really is an issue. See update in link above.

Michael_Baadsgaard · July 6, 2023, 7:31am

I have added the new Google Translate text-to-speech integration and tried it out with this code, but i dont work.my speaker makes a beep sound as if something is going to be said, but it doesn’t say anything.
have also tried without
options:
tld: dk
language: da

service: tts.speak
data:
  cache: true
  media_player_entity_id: media_player.stue
  message: >-
    hej med dig hej med dig hej med dig hej med dig hej med dig hej med dig hej
    med dig hej mhej med dig hej med dig ed dig hej med dig hej med dig hej med
    dig hej med dig hej med dig 
  options:
    tld: dk
  language: da
target:
  entity_id: tts.google_da_dk

sesame26 · July 6, 2023, 7:37am

Same issue here.

Issue reported here:

github.com/home-assistant/core

Time delay showing up as "Delay Translation Error" in Automations and Scripts

opened 09:30AM - 06 Jul 23 UTC

smarthomefamilyverrips

### The problem After update to 2023.7, all Time Delay actions within automatio…ns/scripts says "Delay Translation Error: The intl string context variable "string" was not provided to the string "for {string}" while the action itself still seems to work and execute as expected. ### What version of Home Assistant Core has the issue? 2023.7 ### What was the last working version of Home Assistant Core? 2023.6.2 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Home Assistant Automation ### Link to integration documentation on our website https://www.home-assistant.io/docs/automation/ ### Diagnostics information None ### Example YAML snippet ```yaml - delay: hours: 0 minutes: 0 seconds: 0 milliseconds: 30 ``` ### Anything in the logs that might be useful for us? ```txt None ``` ### Additional information None

Holdestmade · July 6, 2023, 7:38am

I found the same, I tried just copying the URL I use for a local file camera
/local/images/image.jpg
But that didn’t work and I needed to do the same as you.
Odd that it works in local file camera but not inage

aBoss222 · July 6, 2023, 7:45am

Hi all, I am trying to do the basics, but when I create the Script with the “Calendar: List event” the field variables doent show for me.

I have upgraded the version, but still not showing.

Someone know what can be the issue ?

adorobis · July 6, 2023, 7:46am

Looks like the problem is the esphome integration or the esphome firmware. I’ve set up a ble_rssi sensor for one of my devices which recently stopped working properly (the Xiaomi Miscale) and when the scale is not sending data esphome is sending a valua ‘nan’ which is causing a lot of error messages in the log:

2023-07-06 09:10:50.385 ERROR (MainThread) [homeassistant.components.mqtt.models] Exception raised when updating state of sensor.xiaomi_scale_rssi, topic: 'bttracker2/sensor/xiaomi_scale_rssi/state' with payload: b'nan'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 590, in state
    numerical_value = int(value)
                      ^^^^^^^^^^
ValueError: invalid literal for int() with base 10: 'nan'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/mqtt/models.py", line 270, in process_write_state_requests
    entity.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 742, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 809, in _async_write_ha_state
    state = self._stringify_state(available)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 748, in _stringify_state
    if (state := self.state) is None:
                 ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 594, in state
    raise ValueError(
ValueError: Sensor sensor.xiaomi_scale_rssi has device class 'signal_strength', state class 'measurement' unit 'dBm' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'nan' (<class 'str'>)

Not sure if that was behaving the same way before the HA upgrade to 2023.7.0 or not as accidentally I’ve set it up shortly before the upgrade last night.

amaisano · July 6, 2023, 8:01am

Two other things/maybe-coincidences I’ve noticed since updating:

recorder config entity_globs are behaving differently. sensor.*power* used to match both ...outlet_power and ...outlet_power_watts. Now, it only matches the latter. My history for items that don’t have additional text after the “power” match are now no longer tracking state history.
My ssh commands for my LAN hostname isn’t working any more. ssh [email protected] used to work, now they “Cannot be resolved”.

Anyone else?

tom_l · July 6, 2023, 8:32am

You need to open an issue for that component with ESPhome. It should send the state unavailable / none, not ‘nan’.

Boromin · July 6, 2023, 8:43am

same issue for me

adorobis · July 6, 2023, 8:54am

Yeah, just did that. Let’s see how it goes there.

github.com/esphome/issues

ble_rrsi sensor causing errors in HA

opened 07:58AM - 06 Jul 23 UTC

adorobis

### The problem I've set up `ble_rssi` platform sensor to monitor my Xiaomi M…iscale which recently stopped working properly (mostly esphome is not able to read the measurements anymore). Now I'm receiving lots of errors in HA log. ### Which version of ESPHome has the issue? 2023.6.4 ### What type of installation are you using? Docker ### Which version of Home Assistant has the issue? 2023.7.0 ### What platform are you using? ESP32 ### Board ESP32 DEVKITV1 ### Component causing the issue ble_rssi ### Example YAML snippet ```yaml sensor: - platform: ble_rssi mac_address: 0C:95:41:7E:E8:17 name: "Xiaomi Scale RSSI" esp32_ble_tracker: scan_parameters: interval: 60s window: 20s ``` ### Anything in the logs that might be useful for us? ```txt 2023-07-06 09:10:50.385 ERROR (MainThread) [homeassistant.components.mqtt.models] Exception raised when updating state of sensor.xiaomi_scale_rssi, topic: 'bttracker2/sensor/xiaomi_scale_rssi/state' with payload: b'nan' Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 590, in state numerical_value = int(value) ^^^^^^^^^^ ValueError: invalid literal for int() with base 10: 'nan' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/mqtt/models.py", line 270, in process_write_state_requests entity.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 742, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 809, in _async_write_ha_state state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 748, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 594, in state raise ValueError( ValueError: Sensor sensor.xiaomi_scale_rssi has device class 'signal_strength', state class 'measurement' unit 'dBm' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'nan' (<class 'str'>) ``` ### Additional information I've changed the `scan_interval` parameters to 60s and 20s accordingly as with default parameters the esphome has not been receiving any data from the scale. I'm using mqtt so that the last reading is visible in HA. With esphome native integration the last reading would not be visible in HA after e.g. restart of HA.

NCO3 · July 6, 2023, 8:58am

Hi @Michael_Baadsgaard

I have the same issue.
Would it make sense to create a new thread, because this is about “responding services” in 2023.7?
This would increase the visibility.

Mariusthvdb · July 6, 2023, 9:16am

the oddest thing:
Ive been running the beta, and one of my main enjoyments was the fact 2023.7 took down system memory significantly.
Having updated to release yesterday, I am sorry to say that somehow, mysteriously, higher memory usage has returned. quite abruptly:

I did turn on Matter add-on, which would cause higher usage, so Ive turned that off again (dont have any devices anyway yet, only a bridge), but mem has remained like this nonetheless…

Only other changes made were the Esphome updating to the .4 release.

tom_l · July 6, 2023, 9:17am

All of my Shelly devices seem to have gained a duplicate Reboot button:

Screenshot 2023-07-06 at 19-14-52 Settings – Home Assistant

2023-07-06 17:27:35.823 ERROR (MainThread) [homeassistant.components.button] Error while setting up shelly platform for button
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 353, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/src/homeassistant/homeassistant/components/shelly/button.py", line 136, in async_setup_entry
    await er.async_migrate_entries(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1328, in async_migrate_entries
    ent_reg.async_update_entity(entry.entity_id, **updates)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 936, in async_update_entity
    return self._async_update_entity(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 882, in _async_update_entity
    raise ValueError(
ValueError: Unique id '40F520045522_reboot' is already in use by 'button.lounge_front_shelly_sw_reboot'
2023-07-06 17:27:35.845 ERROR (MainThread) [homeassistant.components.button] Error while setting up shelly platform for button
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 353, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/src/homeassistant/homeassistant/components/shelly/button.py", line 136, in async_setup_entry
    await er.async_migrate_entries(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1328, in async_migrate_entries
    ent_reg.async_update_entity(entry.entity_id, **updates)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 936, in async_update_entity
    return self._async_update_entity(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 882, in _async_update_entity
    raise ValueError(
ValueError: Unique id '40F52004CE9C_reboot' is already in use by 'button.kitchen_shelly_sw_reboot'
2023-07-06 17:27:35.854 ERROR (MainThread) [homeassistant.components.button] Error while setting up shelly platform for button
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 353, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/src/homeassistant/homeassistant/components/shelly/button.py", line 136, in async_setup_entry
    await er.async_migrate_entries(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1328, in async_migrate_entries
    ent_reg.async_update_entity(entry.entity_id, **updates)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 936, in async_update_entity
    return self._async_update_entity(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 882, in _async_update_entity
    raise ValueError(
ValueError: Unique id '40F5200469DC_reboot' is already in use by 'button.lounge_rear_shelly_sw_reboot'
2023-07-06 17:27:35.869 ERROR (MainThread) [homeassistant.components.button] Error while setting up shelly platform for button
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 353, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/src/homeassistant/homeassistant/components/shelly/button.py", line 136, in async_setup_entry
    await er.async_migrate_entries(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1328, in async_migrate_entries
    ent_reg.async_update_entity(entry.entity_id, **updates)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 936, in async_update_entity
    return self._async_update_entity(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 882, in _async_update_entity
    raise ValueError(
ValueError: Unique id 'E8DB84D3232F_reboot' is already in use by 'button.hot_water_reboot'
2023-07-06 17:27:35.923 ERROR (MainThread) [homeassistant.components.button] Error while setting up shelly platform for button
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 353, in _async_setup_platform
    await asyncio.shield(task)
  File "/usr/src/homeassistant/homeassistant/components/shelly/button.py", line 136, in async_setup_entry
    await er.async_migrate_entries(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 1328, in async_migrate_entries
    ent_reg.async_update_entity(entry.entity_id, **updates)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 936, in async_update_entity
    return self._async_update_entity(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_registry.py", line 882, in _async_update_entity
    raise ValueError(
ValueError: Unique id 'A4CF12B9E940_reboot' is already in use by 'button.shellyem_b9e940_reboot'

Mariusthvdb · July 6, 2023, 9:18am

yes, Ive reported that exact same message during the beta

had to manually edit the registry to get rid of these…

Shelly is also much chattier than before with the frequent DeviceConnectionError()

part of my Beta experience summary