In the version 2022.4.6 you should have a warning like this:
Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for….
since this 2023.5 update my HAOS system is way slower in responding to the initial smb connection (on my Mac) than before. It was mostly instantaneous, but currently takes about 6-8 seconds. Still no 1st world problem, but very noticeable regression.
No log, just slower.
Using the stock Samba share add-on.
Not via Ethernet(for me), Accessing Samba Share from another Ethernet connected Device, thou startup/reboot of HA system takes much longer time now, before it’s “available” from any devices
PS: i have a shortcut on another Windows-laptop(Ethernet Connected), notice NO port-number !
Did you have to re-add/reconfigure all your devices?
edit: to answer my own question, nope. I made a backup of config/custom_components/localtuya, deleted the folder, restarted HA, installed it through HACS and rebooted. All my localtuya devices worked right away after that.
To clarify, delete (or move) the nest custom component located at config/custom_components/nest and restart HA to start using the built in core nest support. You will need to go to integrations and set up again using the Cloud Console etc.
Then update to 2023.5.x and Nest is working (Doorbell and thermostat for me)
any ideas how to troubleshoot my install? I have tried updating twice now, reverting back each time, With the latest update my ha just keeps restarting with nothing in logs… I have read breaking changes and all possible docs with regards to this upgrade, even moved away from Maria addon to native sql light… nada think the only thing I can do is wait until another update? This has not been a good update at all… there are some fundamental and significant changes that have not been considered or documented properly…
Logger: root
Source: runner.py:179
First occurred: 20:42:42 (3098 occurrences)
Last logged: 21:19:29
A message handler raised an exception: 'org.bluez.Device1'. Traceback (most recent call last): File "src/dbus_fast/message_bus.py", line 811, in dbus_fast.message_bus.BaseMessageBus._process_message File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/manager.py", line 854, in _parse_msg condition_callback() File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/manager.py", line 709, in callback self._properties[device_path][defs.DEVICE_INTERFACE][property_name] KeyError: 'org.bluez.Device1'
Since the update, I’ve had issues with my Reimann Sum helpers becoming unavailable. I’ve re-done them to get the data working, but they continually go “unavailable”. This seems to be connected with no data situations. For example a smart plug on a dryer - the helper becomes unavailable when the plug is still powered by the dryer is not running.