The end of the year is approaching and I don’t see a shift anywhere in what the “Year of the Voice” focused on this year.
2 Likes
Do you read me?
hi, is anyone else experiencing this? Roborock integration.
2023-10-04 22:21:19.638 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration roborock which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-10-04 22:21:32.641 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration roborock: Unable to import component: cannot import name 'async_process_integration_platform_for_component' from 'homeassistant.helpers.integration_platform' (/usr/src/homeassistant/homeassistant/helpers/integration_platform.py)
File "/config/custom_components/roborock/__init__.py", line 20, in <module>
Nice work! As always.
However, I am not happy with the new logo. It’s like going back in time. I can imagine this new logo for the very first HA version. The previous logo symbolized the precision and versatility of HA. The new logo suggests the complexity of a basic calculator.
14 Likes
can you give an example, thanks
I saw on Discord that there will be a new version of the HACS roborock integration in the next day or two. 2023.10. The latest GitHub master works fine already.
1 Like
forget this, em went down at same time as update
reinstalling fixed it. Thank you.
Seems OK here.
login where?
I had the same issue, after Backup restore, it works.
Hi! Great update, thanks for that!
With this new “Private BLE Device”-Tracker, it is the first time I use tracker in Home Assistant. I setup this integration for my iPhone and Apple Watch. Now I am “at Home” instead of “unknown”. Nice!
But if I disable Bluetooth on both devices, I thought that my person should change to “Not at Home” or back to “Unknown”.
I read a bit documentation regarding this topic and now I am wonder about the default value for “consider_home” (and how I can change them)?
Does any of the experienced people have a tip?
1 Like
my bad, seems the em has stopped at the same time as I did the update. not the first time to just decide to go offline.
Disabling Bluetooth on an iOS device doesn’t actually “fully” disable Bluetooth as they are usually trackable even with the power off because of Find My. You likely have to remove the device from the range of the Bluetooth adapter or completely drain the battery.
2 Likes
Is there a way to know if issue 99947 (MyQ integration forbidden) made it into the release? This issue says it will (well, it says 2023.10.x but underneath it says core released 10/4/2023), but for me at least it still fails. Or is there a more appropriate place to ask? (The issue is locked.)
Any tips for retrieving the IRK for AirTags?
1 Like
Z2M is working fine. MQTT is working fine. HA frontend is broken. Every time I reboot Home Assistant, all zigbee devices show “Unavailable”. They never come back if I let it sit. Z2M shows all devices online. MQTT browser shows all states are proper and persistent. Rebooting Z2M sometimes fixes it, most devices will start to come back online as “Unknown” and the eventually update properly. Some devices still remain as “Unavailable”. For the ones that are “Unavailable”, I change the name in Z2M + HA to something else, then back to what it was, and that specific device starts working again.
As soon as I reboot HA again. the problem comes back, all devices are “Unavailable”.
This is an HA issue, not a Z2M issue, and not an MQTT issue.
This has been happening since the last 4-7 releases of core. (Can’t remember when it broke exactly)
Even a new HA install, re-pared all devices, same issue. Please fix this!
Issues don’t make it into code. PRs do.
And if you want to refer to an issue, have the decency to link to it.
If you had, you will see the appropriate PR is Update MyQ to use python-myq 3.1.9 by Lash-L · Pull Request #100949 · home-assistant/core · GitHub and the changelog for 2023.10 shows that it is included Full changelog for Home Assistant Core 2023.10 - Home Assistant - this page is linked in the release announcement.
1 Like
My apologies @nickrout, I do not participate in the development so I did not know how to track it (MyQ/Python) to the PR’s inclusion in the release, though I see now the PR number is in the notes (I did not know that). But my point at the time is that it was still broken. However…
A couple hours after I did all the installs this just magically started working. Before that it was giving the same error even after updating HA and supervisor. No idea why, but working now.
Thank you for the patient answer.
6 Likes