2023.7: Responding services

[Kertz1954]

Heads up for Dutch users who are using the buienradar integration.
If you are seeing “unknown” in your weather related dashboards this morning, don’t worry, it’s not an HA problem. Since late yesterday evening, there has been no weather stations listed in the Buienradar JSON file. The 5 day forecast is still present and available.
You can follow this link to see the current JSON contents.
https://data.buienradar.nl/2.0/feed/json

[jirka.jirutka]

After update to last version 2023.7.1, my recorder still freezing. System must be restarted, again, again.
Installed MariaDB

recorder:
  purge_keep_days: 90
  db_url: mysql://****:****@core-mariadb/homeassistant?charset=utf8mb4

Not acces to system page

[plasmac0r]

Many thanks for the great work!

[michaelkrtikos (Michail Kritikos)]

In the previous versions, the switch would control the “LED output” switch located in the hyperion interface under “remote control”.

Since the output to the LEDs is off also the light would turn off.

I can raise an issue on github…

[Mariusthvdb (Marius)]

so is it a bug, when using a unique_id:, but not a name: the new template image entity is NOT getting the object_id and name based on the unique_id?

  - image:
      - unique_id: test_name_template_image
#         name: Test name template image
        url: 'http://<server>.local:<port>/local/images/bonen.jpg'

while ‘regular’ templates get it applied correctly, with the prefixed template_:

  - sensor:

      - unique_id: test_name_template_sensor
        state: >
          {{states('input_boolean.test')}}

template image does no use unique_id for name/entity_id

[nickrout]

Are you guys perhaps running into this change?

Decouple Hyperion entitites and clear source when light is off

[Mariusthvdb (Marius)]

this seems to work alright:

template:

  - trigger:

      - platform: state
        entity_id:
          - binary_sensor.oprit_vehicle_detected
          - binary_sensor.oprit_person_detected
        to: 'on'

# below triggers are required to prevent broken image placeholders
# do cause the state to show the last triggered time, end not perse the time the image was shot
      - platform: event
        event_type: delayed_homeassistant_start
      - platform: event
        event_type: event_template_reloaded

    image:

      - unique_id: last_snapshot_oprit_camera
        name: Last snapshot oprit camera
        url: 

though one has got to bear in mind the date in the picture-entity shows the dat of the last triggered, and not necessarily the date of the moment the image was taken.

taking the trigger on the template reload and homeassistant start events out of the trigger template would solve that, but then would result in a broken image placeholder upon restart, or template reload…

trigger template image does not restore state?

trigger template image does not restore state

[Purpleturtle]

I follow a morning routine where, after my alarm goes off and I am detected by a specific motion sensor, I want my calendar to be read out to me. The blueprint created by @allenporter works as a notification on my smartphone, but it doesn’t function as a voice output. How can I resolve this issue?

[Mariusthvdb (Marius)]

will report in the Plugwise topic too, but since this is a first discovery in 2023.7.1, I figured maybe other people experienced it too:

No idea what vn/a might be, and my Plugwise integration is working fine. tbh, I am a bit wary clicking Configureer there, as I dont want to mess up the other integration sections…

[Blacky]

Thanks for getting back to us Nick. What would be the best way to inform Shelly of the new grouping advertisement data as I am sure they would like to keep up with HA?

[m4v3r1ck]

That’s a strange change in 2023.7.1, as this is my plugwise integration page in 2023.7.

Yours discovered a new device? Confusing to say the least and obvious a new layout?

Following.

[Eoin]

Sometimes it’s the small things that make a difference, love having the Utility Meter helper on the device page. Thanks team for another great release!

[malorezzanzo64]

I don’t know if the cause is the update but as soon as I updated to 2023.7 from 2023.6.0 a lot of jinja templates start to raise “RecursionError: maximum recursion depth exceeded”

[petro]

post the templates please

[malorezzanzo64]

Sorry, it was my fault. I accidentally edited the jinja file and so it threw that error

[templeton_nash]

I’ve just installed 2023.7(.1) and no issues. Great work everyone!

[Delvino (Djamon Staal)]

After upgrading to 7.1 my Enphase Envoy is unable to connect.

RuntimeError: Could not connect or determine Envoy model. Check that the device is up at 'http://192.168.xxx.xxx'.
2023-07-07 14:06:40.956 ERROR (MainThread) [frontend.js.latest.202307051] :0:0 Script error.
2023-07-07 14:07:23.161 ERROR (MainThread) [homeassistant.components.enphase_envoy] Unexpected error fetching envoy Envoy xxxxxxxxxxxx data: Could not connect or determine Envoy model. Check that the device is up at 'http://192.168.xxx.xxx'.
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 283, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 242, in _async_update_data
    return await self.update_method()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/enphase_envoy/__init__.py", line 44, in async_update_data
    await envoy_reader.getData()
  File "/usr/local/lib/python3.11/site-packages/envoy_reader/envoy_reader.py", line 136, in getData
    await self.detect_model()
  File "/usr/local/lib/python3.11/site-packages/envoy_reader/envoy_reader.py", line 209, in detect_model
    raise RuntimeError(
RuntimeError: Could not connect or determine Envoy model. Check that the device is up at 'http://192.168.xxx.xxx'.
2023-07-07 14:07:28.269 ERROR (MainThread) [frontend.js.latest.202307051] :0:0 Script error.
2023-07-07 14:08:14.481 DEBUG (MainThread) [envoy_reader.envoy_reader] Fetched from http://192.168.xxx.xxx/production.json: <Response [301 Moved Permanently]>: <html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>openresty/1.17.8.1</center>
</body>
</html>

2023-07-07 14:08:14.485 DEBUG (MainThread) [envoy_reader.envoy_reader] Fetched from http://192.168.xxx.xxx/api/v1/production: <Response [301 Moved Permanently]>: <html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>openresty/1.17.8.1</center>
</body>
</html>

2023-07-07 14:08:14.489 DEBUG (MainThread) [envoy_reader.envoy_reader] Fetched from http://192.168.xxx.xxx/production: <Response [301 Moved Permanently]>: <html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>openresty/1.17.8.1</center>
</body>
</html>

2023-07-07 14:08:14.489 ERROR (MainThread) [homeassistant.components.enphase_envoy] Unexpected error fetching envoy Envoy xxxxxxxxxxxx data: Could not connect or determine Envoy model. Check that the device is up at 'http://192.168.xxx.xxx'.
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 283, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 242, in _async_update_data
    return await self.update_method()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/enphase_envoy/__init__.py", line 44, in async_update_data
    await envoy_reader.getData()
  File "/usr/local/lib/python3.11/site-packages/envoy_reader/envoy_reader.py", line 136, in getData
    await self.detect_model()
  File "/usr/local/lib/python3.11/site-packages/envoy_reader/envoy_reader.py", line 209, in detect_model
    raise RuntimeError(
RuntimeError: Could not connect or determine Envoy model. Check that the device is up at 'http://192.168.xxx.xxx'.
2023-07-07 14:08:14.491 DEBUG (MainThread) [homeassistant.components.enphase_envoy] Finished fetching envoy Envoy xxxxxxxxxxxx data in 0.146 seconds (success: False)
2023-07-07 14:08:14.492 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Envoy xxxxxxxxxxxx' for enphase_envoy integration not ready yet: Could not connect or determine Envoy model. Check that the device is up at 'http://192.168.xxx.xxx'.; Retrying in background

[Groove (Andy)]

Got all excited when I saw something about the Energy dashboard until I realised it was just a new gauge.

When will the dashboard actually get some more customisation options ? There is a large thead on Github here asking for colour changing abilities for accessibility / readability reasons etc for example

Energy Usage graph colour select or customisation option for stack · home-assistant/frontend · Discussion #12397 · GitHub

[denwald]

Hi, which cache did you clear? The browser cache, or a cache specific to HA?

[paddy0174 (Patrick)]

The browser cache. The problem is, the Javascript files are big and get cached by the browser. Sometimes even a few cache hardresets are needed, to really get rid of the “old” scripts.