2024.5: Just a little bit smaller

system · May 1, 2024, 6:50pm

m4v3r1ck · May 1, 2024, 7:07pm

Excited to install and review this release.

Pipo31416 · May 1, 2024, 7:25pm

Collapse

78wesley · May 1, 2024, 7:25pm

The url at Energenie Power-Sockets is invalid in the New integrations it needs to be this Energenie Power-Sockets - Home Assistant

Pipo31416 · May 1, 2024, 7:27pm

Move to room is too late for me …

f1ght3rz · May 1, 2024, 7:43pm

Awesome improvements.
Now what would be a great changer to many people I talked to would be:
Starting to create automations directly from the entity.
Like: tap on a light and find a link to automations where you can select to turn on or off the light and only have to add a trigger.

//Edit:
Jesus… I just saw that this has already been implemented… I’m obviously using Home Assistant for too long and not paying attention.

Krispkiwi · May 1, 2024, 8:12pm

Did the lock per device feature that was in the beta get dropped?

ATWindsor · May 1, 2024, 8:16pm

What seems like the biggest change (for me), is hidden in the “all changes”, the get map feature in roborock, looking forward to test that.

kristofferR · May 1, 2024, 8:27pm

This seems to break HASS.Agent:

github.com/LAB02-Research/HASS.Agent

Notify service missing in HA

opened 06:07PM - 01 May 24 UTC

Wank-ster

So I did install everything according to the instructions and somehow got it wor…king, but I cannot get the "notify" service. It seems that either the service is not created or I do something wrong. I have installed HASS.Agent locally on a Win11 Client ![image](https://github.com/LAB02-Research/HASS.Agent/assets/142676146/3ba50f0a-f212-4f2b-87f6-c1280e4e1a4a) and also in HA: ![image](https://github.com/LAB02-Research/HASS.Agent/assets/142676146/a5528cdf-39a2-49ae-8b8d-074e2362d154) Notification test on the client is successful and also this test ![image](https://github.com/LAB02-Research/HASS.Agent/assets/142676146/448b63de-7ee8-47f2-9315-17645c3995c7) The only thing I see and assume is that I do not have some kind of notify entry in MQTT and don’t know if this is supposed to be there or how in the world this notify service for the client is created within HA ![image](https://github.com/LAB02-Research/HASS.Agent/assets/142676146/32366259-de72-4865-a591-6d36c52f2b09) According to the documentation I assumed that it should be created automatically when I add the device via autodetect. The device pops up and I can add it but no service is created. I found the old hass.agent notification integration but apparently it is deprecated and I should use this one instead. Can anyone help?

hansie_p · May 1, 2024, 8:40pm

My matter integration is not able to start anymore after updating to 2024.5. 2 errors occur:

Error setting up entry Matter for event
Error setting up entry Matter for light
Error setting up entry Matter for lock
Error setting up entry Matter for sensor
Error setting up entry Matter for switch
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/binary_sensor/__init__.py", line 234, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!

Error setting up entry Matter for matter
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/matter/__init__.py", line 129, in async_setup_entry
    await matter.setup_nodes()
  File "/usr/src/homeassistant/homeassistant/components/matter/adapter.py", line 63, in setup_nodes
    self._setup_node(node)
  File "/usr/src/homeassistant/homeassistant/components/matter/adapter.py", line 148, in _setup_node
    self._setup_endpoint(endpoint)
  File "/usr/src/homeassistant/homeassistant/components/matter/adapter.py", line 228, in _setup_endpoint
    self.platform_handlers[entity_info.platform]([new_entity])
    ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
KeyError: <Platform.BINARY_SENSOR: 'binary_sensor'>

Nyak · May 1, 2024, 8:50pm

Same issue and errors. Baremetal installation. Updated to Matter Server 5.6 on 2024.4, no issues. Installing 2024.5 brought on the problems.

Rolled back the Matter server to 5.5 on 2024.5 same issues. Tried reboot/restart (add-on and HAOS), still failing.

Rolled back to Core 2024.4, everything is working again with Matter Sever 5.6.

Sunlust · May 1, 2024, 9:11pm

Same issues with Matter as well, had to roll back to 2024.4.

ChirpyTurnip · May 1, 2024, 9:27pm

Similar problem - all of a sudden many of my Shelly devices drop off…they all come up on restart, everything looks good, a minute or two later and they’re all falling off:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/update/__init__.py", line 118, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!
2024-05-02 09:18:49.472 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Shelly-RearGarageLights for valve
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 575, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/valve/__init__.py", line 111, in async_setup_entry
    return await component.async_setup_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 185, in async_setup_entry
    raise ValueError("Config entry has already been setup!")
ValueError: Config entry has already been setup!

A restart does not resolve. And then of course all your automations, data calculations etc all start failing too and pretty soon the whole thing is looking patchy…

jayjay · May 1, 2024, 9:57pm

Zigbee broke in new core:

2024-05-01 23:56:32.764 DEBUG (MainThread) [zigpy.serial] Opening a serial connection to ‘socket://192.168.0.165:8888’ (115200 baudrate)

2024-05-01 23:56:33.770 DEBUG (MainThread) [bellows.ezsp] Resetting EZSP

2024-05-01 23:56:33.770 DEBUG (MainThread) [bellows.uart] Resetting ASH

2024-05-01 23:56:33.770 DEBUG (MainThread) [bellows.uart] Sending: b’1ac038bc7e’

2024-05-01 23:56:34.850 DEBUG (MainThread) [bellows.uart] RSTACK Version: 2 Reason: RESET_SOFTWARE frame: b’c1020b0a527e’

2024-05-01 23:56:34.851 DEBUG (MainThread) [bellows.ezsp] Switching to EZSP protocol version 4

2024-05-01 23:56:34.851 DEBUG (MainThread) [bellows.ezsp.protocol] Send command version: (4,)

2024-05-01 23:56:34.852 DEBUG (MainThread) [bellows.uart] Sending: b’004221a850ed2c7e’

2024-05-01 23:56:34.902 DEBUG (MainThread) [bellows.uart] Data frame: b’0142a1a8532815d7c1bf7e’

2024-05-01 23:56:34.902 DEBUG (MainThread) [bellows.uart] Sending: b’8160597e’

2024-05-01 23:56:34.904 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received version: [7, 2, 25856]

2024-05-01 23:56:34.904 DEBUG (MainThread) [bellows.uart] Adjusting ACK timeout from 1.60 to 1.43

2024-05-01 23:56:34.905 DEBUG (MainThread) [bellows.ezsp] Switching to EZSP protocol version 7

2024-05-01 23:56:34.905 DEBUG (MainThread) [bellows.ezsp.protocol] Send command version: (7,)

2024-05-01 23:56:34.906 DEBUG (MainThread) [bellows.uart] Sending: b’7d31422157542a1240277e’

2024-05-01 23:56:34.954 DEBUG (MainThread) [bellows.uart] Data frame: b’1242a157542a12b059f17b747e’

2024-05-01 23:56:34.954 DEBUG (MainThread) [bellows.uart] Sending: b’82503a7e’

2024-05-01 23:56:34.955 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received version: [7, 2, 25856]

2024-05-01 23:56:34.956 DEBUG (MainThread) [bellows.uart] Adjusting ACK timeout from 1.43 to 1.27

2024-05-01 23:56:34.956 DEBUG (MainThread) [bellows.ezsp] EZSP Stack Type: 2, Stack Version: 6500, Protocol version: 7

2024-05-01 23:56:34.957 DEBUG (MainThread) [bellows.ezsp.protocol] Send command getValue: (<EzspValueId.VALUE_FORCE_TX_AFTER_FAILED_CCA_ATTEMPTS: 58>,)

2024-05-01 23:56:34.958 DEBUG (MainThread) [bellows.uart] Sending: b’2243215754802f91c37e’

2024-05-01 23:56:35.006 DEBUG (MainThread) [bellows.uart] Data frame: b’2343a157548022b232ae7e’

2024-05-01 23:56:35.006 DEBUG (MainThread) [bellows.uart] Sending: b’83401b7e’

2024-05-01 23:56:35.008 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received getValue: [<EzspStatus.ERROR_INVALID_ID: 55>, b’']

2024-05-01 23:56:35.008 DEBUG (MainThread) [bellows.uart] Adjusting ACK timeout from 1.27 to 1.14

2024-05-01 23:56:35.009 DEBUG (MainThread) [bellows.ezsp] Setting value VALUE_FORCE_TX_AFTER_FAILED_CCA_ATTEMPTS = 1 (old value None)

2024-05-01 23:56:35.009 DEBUG (MainThread) [bellows.ezsp.protocol] Send command setValue: (<EzspValueId.VALUE_FORCE_TX_AFTER_FAILED_CCA_ATTEMPTS: 58>, b’\x01’)

2024-05-01 23:56:35.012 DEBUG (MainThread) [bellows.uart] Sending: b’3340215754812fb358544a7e’

2024-05-01 23:56:35.062 DEBUG (MainThread) [bellows.uart] Data frame: b’3440a15754812209317e’

2024-05-01 23:56:35.062 DEBUG (MainThread) [bellows.uart] Sending: b’8430fc7e’

2024-05-01 23:56:35.063 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received setValue: [<EzspStatus.ERROR_INVALID_ID: 55>]

2024-05-01 23:56:35.064 DEBUG (MainThread) [bellows.uart] Adjusting ACK timeout from 1.14 to 1.02

2024-05-01 23:56:35.065 DEBUG (MainThread) [bellows.ezsp] Could not set value VALUE_FORCE_TX_AFTER_FAILED_CCA_ATTEMPTS = 1: EzspStatus.ERROR_INVALID_ID

2024-05-01 23:56:35.065 DEBUG (MainThread) [bellows.ezsp.protocol] Send command getConfigurationValue: (<EzspConfigId.CONFIG_SOURCE_ROUTE_TABLE_SIZE: 26>,)

2024-05-01 23:56:35.066 DEBUG (MainThread) [bellows.uart] Sending: b’4441215754780fb6b67e’

2024-05-01 23:56:35.114 DEBUG (MainThread) [bellows.uart] Data frame: b’4541a1575478157a599b807e’

2024-05-01 23:56:35.114 DEBUG (MainThread) [bellows.uart] Sending: b’8520dd7e’

2024-05-01 23:56:35.115 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received getConfigurationValue: [<EzspStatus.SUCCESS: 0>, 200]

2024-05-01 23:56:35.115 DEBUG (MainThread) [bellows.uart] Adjusting ACK timeout from 1.02 to 0.92

2024-05-01 23:56:35.116 DEBUG (MainThread) [bellows.ezsp] Current config CONFIG_SOURCE_ROUTE_TABLE_SIZE = 200 exceeds the default of 200, skipping

2024-05-01 23:56:35.116 DEBUG (MainThread) [bellows.ezsp.protocol] Send command getConfigurationValue: (<EzspConfigId.CONFIG_END_DEVICE_POLL_TIMEOUT: 19>,)

2024-05-01 23:56:35.117 DEBUG (MainThread) [bellows.uart] Sending: b’5546215754780660c47e’

2024-05-01 23:56:35.166 DEBUG (MainThread) [bellows.uart] Data frame: b’5646a157547815ba5934767e’

2024-05-01 23:56:35.166 DEBUG (MainThread) [bellows.uart] Sending: b’8610be7e’

2024-05-01 23:56:35.167 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received getConfigurationValue: [<EzspStatus.SUCCESS: 0>, 8]

2024-05-01 23:56:35.168 DEBUG (MainThread) [bellows.uart] Adjusting ACK timeout from 0.92 to 0.83

2024-05-01 23:56:35.169 DEBUG (MainThread) [bellows.ezsp] Setting config CONFIG_END_DEVICE_POLL_TIMEOUT = 8 (old value 8)

2024-05-01 23:56:35.169 DEBUG (MainThread) [bellows.ezsp.protocol] Send command setConfigurationValue: (<EzspConfigId.CONFIG_END_DEVICE_POLL_TIMEOUT: 19>, 8)

2024-05-01 23:56:35.170 DEBUG (MainThread) [bellows.uart] Sending: b’66472157547906ba5940d97e’

2024-05-01 23:56:35.217 DEBUG (MainThread) [bellows.uart] Data frame: b’6747a1575479152fb97e’

2024-05-01 23:56:35.218 DEBUG (MainThread) [bellows.uart] Sending: b’87009f7e’

2024-05-01 23:56:35.218 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received setConfigurationValue: [<EzspStatus.SUCCESS: 0>]

2024-05-01 23:56:35.219 DEBUG (MainThread) [bellows.uart] Adjusting ACK timeout from 0.83 to 0.75

2024-05-01 23:56:35.219 DEBUG (MainThread) [bellows.ezsp.protocol] Send command getConfigurationValue: (<EzspConfigId.CONFIG_TC_REJOINS_USING_WELL_KNOWN_KEY_TIMEOUT_S: 56>,)

2024-05-01 23:56:35.220 DEBUG (MainThread) [bellows.uart] Sending: b’7744215754782d70987e’

2024-05-01 23:56:35.270 DEBUG (MainThread) [bellows.uart] Data frame: b’7044a1575478159e589ca77e’

2024-05-01 23:56:35.270 DEBUG (MainThread) [bellows.uart] Sending: b’8070787e’

2024-05-01 23:56:35.272 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received getConfigurationValue: [<EzspStatus.SUCCESS: 0>, 300]

2024-05-01 23:56:35.272 DEBUG (MainThread) [bellows.uart] Adjusting ACK timeout from 0.75 to 0.68

2024-05-01 23:56:35.273 DEBUG (MainThread) [bellows.ezsp] Setting config CONFIG_TC_REJOINS_USING_WELL_KNOWN_KEY_TIMEOUT_S = 90 (old value 300)

2024-05-01 23:56:35.273 DEBUG (MainThread) [bellows.ezsp.protocol] Send command setConfigurationValue: (<EzspConfigId.CONFIG_TC_REJOINS_USING_WELL_KNOWN_KEY_TIMEOUT_S: 56>, 90)

2024-05-01 23:56:35.274 DEBUG (MainThread) [bellows.uart] Sending: b’0045215754792de85973387e’

2024-05-01 23:56:35.321 DEBUG (MainThread) [bellows.uart] Data frame: b’0145a157547915b6c67e’

2024-05-01 23:56:35.322 DEBUG (MainThread) [bellows.uart] Sending: b’8160597e’

2024-05-01 23:56:35.323 DEBUG (MainThread) [bellows.ezsp.protocol] Application frame received setConfigurationValue: [<EzspStatus.SUCCESS: 0>]

2024-05-01 23:56:35.323 DEBUG (MainThread) [bellows.uart] Adjusting ACK timeout from 0.68 to 0.62

2024-05-01 23:56:35.323 DEBUG (MainThread) [bellows.ezsp.protocol] Send command getConfigurationValue: (<EzspConfigId.CONFIG_INDIRECT_TRANSMISSION_TIMEOUT: 18>,)

2024-05-01 23:56:35.324 DEBUG (MainThread) [bellows.uart] Sending: b’7d314a2157547807672c7e’

Fonzy0083 · May 1, 2024, 9:58pm

completely broke my installation.

Web application is not reacheable. The system freezes and after a while a python3 out of memory error appears.

Cannot rollback core as core update --version=2024.4.4 results in a “Error: another job is running for group home_assistant_core”

Cannot repair supervisor as it remains stuck forever

Cannot restore backup for error: “blocked from execution, system is not running - startup”

CChris · May 1, 2024, 10:03pm

Thank you again for a release which addresses some of the smaller - but annoying topics that bothered me for quite a while now… especially: renaming the entities for the energy dashboard (track single devices)… now, the graph finally looks nice without requireing to change the whole entity name or just reordering / selecting the features (programs) I want to use on my thermostats …

Really great to see the progress of the last couple months now

CChris · May 1, 2024, 10:05pm

have you tried to just power off your hardware?
I had similar issues in the past - but never really related to a specific version I updated.

When such things happened, after rebooting the whole system it came back - and updates could be done without issues.

Fonzy0083 · May 1, 2024, 10:12pm

I restarted many times but the problem persists. I don’t know what to do…

righetti.thomas · May 1, 2024, 10:14pm

Also here everything seems to be “broken”: HA restarts but never fully (“Wrapping up” message appears), and then is not reachable anymore via web interface.
Looking at logs right now…

righetti.thomas · May 1, 2024, 10:14pm

same here…