so how and where do we report that, without anything else than our memory, and no logs to share…
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.
added an issue on the Samba share Samba add-on slower on initial connect · Issue #3043 · home-assistant/addons · GitHub
2 Likes
Had to downgrade as well. Zigbee and Z-Wave automations did not always work.
1 Like
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)
1 Like
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…
After update to.3 this is very active……:
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.
Is this normal now?
Usually that means the Bluetooth adapter has disappeared from the system.
Try unplugging the adapter and plugging it back in again.
If that doesn’t fix it, shutdown, remove power, restore power, and start back up
thx.
how strange, because all of my BT devices seem ok, and even the BT integration is listing the stick and the adapter inside the PC without errors.
Ill take the steps and see what gives.
Same here, Tuya integration is broken, and the scenes from the Tuya app are no longer shown in HA, for now I downgraded to 2023.4.6
1 Like
energi dashboard broken. history is gone and numbers is totaly of. is it my install or is it the update?
andy
restored my backup and energi is back. but i lost some hours…
QVR plugin breaks if there is an asterisk (*) in the password. It didn’t before.
Workaround is to make a new password with no asterisk.
1 Like
After updating I am now getting this error, anybody have any ideas what this is an how to fix it?
Logger: homeassistant.helpers.device_registry
Source: helpers/device_registry.py:269
First occurred: 9:06:29 PM (1 occurrences)
Last logged: 9:06:29 PM
Unexpected exception from <function async_setup_cleanup..cleanup at 0x7f1be03fab90>
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/debounce.py”, line 111, in _handle_timer_finish
await task
File “/usr/src/homeassistant/homeassistant/helpers/device_registry.py”, line 870, in cleanup
async_cleanup(hass, dev_reg, ent_reg)
File “/usr/src/homeassistant/homeassistant/helpers/device_registry.py”, line 859, in async_cleanup
dev_reg.async_purge_expired_orphaned_devices()
File “/usr/src/homeassistant/homeassistant/helpers/device_registry.py”, line 729, in async_purge_expired_orphaned_devices
del self.deleted_devices[deleted_device.id]
File “/usr/src/homeassistant/homeassistant/helpers/device_registry.py”, line 269, in delitem
del self._connections[connection]
I find that the tuya integration is hit and miss. I am having to restart the integration every now and then to get devices working.
1 Like
How did you restore the backup?
If I click on restore of my backup from the frontend, the Raspberry turns off but never turns back on, turning the power off and on, it turns on but without restoring any backups.
The latest update broke my scroll in all dashboards, it became unusable.
EDIT: i found what’s the issue.
div#view{
transform: initial;
padding: 0 !important;
position: fixed !important;
margin: 0 !important;
width: 100%;
}
This minimalist-theme piece of code under card-mod-root-yaml: breaks scrolling in dashboards.
By removing it, the scrolling works again.
This seems to have killed the custom skill. Could be some change with SSL? First everything stopped working, so I disabled skill and renabled.
When authorizing the skill the HA page comes up - but after inputting user/pass I get a message “Unable to link skill”. I’m using cloudfare tunnel (not duckdns), But this worked perfectly before. Unfortunately no Alexa now, very very bummed out.
Anyone having this issue as well? Alexa custom skill with cloudfare ?
Same errors in the log here after the update. Bluetooth seems to be working fine anyway (rpi3)
Logger: root
Source: runner.py:179
First occurred: 16 mei 2023 om 23:29:31 (22442 occurrences)
Last logged: 10:36:35
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’