sparkydave
(š¦šŗ Dave)
May 1, 2024, 11:34pm
27
I just updated from the last 2024.5 beta with no issues.
1 Like
Great update. Loving the data table additions.
I wonder why filters were not added to this āstored settingsā?
I have made some progress by individually reloading each of my Shelly integrations (all 38 of them). After the reload they came right, and stayed online. I have since done a full reboot of the HA machine and everything has come backā¦and stayed back the way I expect it all to be.
tom_l
May 2, 2024, 12:48am
31
Strict Connections?
Yes that was pulled from the release.
1 Like
tom_l
May 2, 2024, 12:52am
32
Great, now look in your /config folder and find the file home-assistant.log.1 to see what went wrong.
bdraco
(J. Nick Koston)
May 2, 2024, 12:55am
33
There is an open issue with a linked PR for matter
opened 09:08PM - 01 May 24 UTC
integration: matter
### The problem
There was an update to the Matter server a short time ago and tā¦ hat went OK, but an update just now to home assistant seems to have borked something. I am only using Matter with an Aqara M2 Hub.
Log shows the following error.
----
Logger: homeassistant.config_entries
Source: config_entries.py:575
First occurred: 21:56:46 (1 occurrences)
Last logged: 21:56:46
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 225, in _setup_endpoint
new_entity = entity_info.entity_class(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/matter/entity.py", line 87, in __init__
self._update_from_device()
File "/usr/src/homeassistant/homeassistant/components/matter/light.py", line 354, in _update_from_device
self._check_transition_blocklist()
File "/usr/src/homeassistant/homeassistant/components/matter/light.py", line 403, in _check_transition_blocklist
device_info.productID,
^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'BridgedDeviceBasicInformation' object has no attribute 'productID'. Did you mean: 'productURL'?
### What version of Home Assistant Core has the issue?
core-2024.5.0
### What was the last working version of Home Assistant Core?
previous
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
Matter
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/matter
### Diagnostics information
[home-assistant_matter_2024-05-01T21-05-53.215Z.log](https://github.com/home-assistant/core/files/15181374/home-assistant_matter_2024-05-01T21-05-53.215Z.log)
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
3 Likes
ATWindsor:
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.
Let us know how that works out and with which roborock. I am 96% sure I will be getting roborocks, just not sure which version.
hkrob
(Rob)
May 2, 2024, 2:10am
35
First HA upgrade failure in quite some timeā¦ tried going from 2024.4.4 to 2024.5.0 today
Python3 out of memory errors on the HA OS screen (screenshot below), tried rebooting, tried increasing available RAM, no luck.
Restore didnāt work either, kept complaining about it being a partial restore (the one which was done automatically when launching the upgrade!)
Ended up working by manually choosing the HA version and rebooting.
ha core update --version 2024.4.4
My advice - take a manual, FULL backup, download it and keep it in case this upgrade goes badly for you
AND, Observer said everything was fine the whole time! (it was not!)
1 Like
A lot of people learning the harsh reality that you should always wait for the X.1 update before upgrading in any major release lol
10 Likes
I personally always wait for .2! Have been bitten before when a release had something I really wanted badly.
2 Likes
tom_l
May 2, 2024, 2:30am
38
Alternatively: a lot of people learning that the beta test group is very small and only covers a subset of available integrations and hardware.
You want the .0 release to work for you?
Then join in the beta testing.
39 Likes
francisp
(Francis)
May 2, 2024, 2:32am
39
Just woke up. Time to upgrade from the bet.
1 Like
lubeda
(LuBeDa)
May 2, 2024, 4:25am
40
Same here, but i did somehow manage to get back to a working 2024.4.4.
yglas
(Yglas)
May 2, 2024, 4:34am
41
Hello, since version 2024.3.2 I canāt update because Huawei Solar integration doesnāt work anymore after the update. I try every new version but have to go back to version 2024.3.1. What can I do to make everything work with the new versions?
Assuming it is this one below (link refers to closed issues)
Do check the issues and raise something new if it does not cover your case.
Issues Ā· wlcrs/huawei_solar (github.com)
yglas
(Yglas)
May 2, 2024, 5:12am
43
Thank you. I managed to fix it, according to the instructions.
xtrmenl
(Xtrmenl)
May 2, 2024, 5:21am
44
Edit important
Just did a full system reboot instead of restart of hass
And
That does the trick!
After initial update (early comment)
As many updated
but canā reach the internal menus of integrations (hacs and official)
Neither can I open backups f.e.
Functionwise it is working
Hacs keeps working but wonāt open(white screen)
z2m works but canāt open (white screen)
glances doesnāt open
backups keep loading
Energy +configuration works completely
ofca
May 2, 2024, 5:37am
45
! WARNING !
2024.5 broke zigbee for some people (myself included). If zigbee is mission critical for you, you may wish to hold your horses before upgrading.
! WARNING !
2 Likes
It was my case, zha failed after upgrade, I have gone back to the previous version