could that have to do with the part of the world one is in?
for me the app works splendidly, and I can even see the. driving/walking/cycling (not sire of the exact terminology by heart)
dont forget there was a privacy/security warning on Life360 either. Its when I moved away from it (and never looked back).
Iâve briefly tried and tested that, but it was in now way a replacement for the core device_tracker bluetooth.
there is a new integration in core btw: Bluetooth Monitoring and Discovery - Home Assistant testing that in dev 2022.8 and scheduled for next release.
(must admit I havenât seen a discovered device , so it might not be in the todays nightly just yet. hope it will be in the next so we can test drive it.)
I also needed to change my Redirect URI to https://my.home-assistant.io/redirect/oauth. Seems that the integration is using that URI fixed in a new setup.
2022.7.1 is the first disastrous update Iâve installed. Couldnât get any access to UI. No relevant errors in logs, no amount of restarts, cache clearing, disabling of custom_extensions or 3rd party additions to configuration.yaml made any difference.
Managed to downgrade to 2022.7.0 to recover with full browser clear. Have no idea what the actual issue was, so canât offer any insight.
Not a gripe, just anecdotal info for Devs.
Juist Updating to 2022.7.2
All my Dashboards are broken
Custom element doesnt exist: button-card
All custom cards are down.
Any suggestions?
SOLVED! Had only to restart my browser - i think clearing browser cache is suffisantâŚ
Still persists in 2022.07.02 as well. I also noticed that both the âLuftdatenâ and âDWD_Pollenflugâ (first one gives info on air quality, the second one on pollen in the air) stopped working. As far as I can tell, all three of them (haveibeenpwned, luftdaten and pollenflug) one way or another are depending on http(s) transport to pick up their data. There are quite some exceptions pointing to âhttpcore.read.timeoutâ as well as âhttpx.read.timeoutâ in my logfile.
Iâve opened a bug report.
Solved! i updated the firmware ETHM1 plus from 2.07 to 2.09 now it is working again. The problem with older versions is python 3.10. To update you need an converter usb-rs satel. You can download the firmware from ETHM-1 Plus FLASH Programma voor het updaten van de ETHM-1 Plus.
Update the ETHM1 plus to 2.09, see my reply on this page #9
I have fe 2.09
But updated to HA 2022.7.1 resooved problem.
Try changing the manifest to pycryptodome==3.15.0 .
now see this:
as a detail of:
sudden increase caused by adding
bluetooth:
âŚ
from 3/4% to 12%âŚ
not good.
âa bit highâ is something of an understatement Nick 
https://github.com/home-assistant/core/pull/74653
Iâd love to - but I donât know how to. Can you please help?
edit /config/custom_components/xcomfort_bridge/manifest.json
I opened an issue (first time ever, so not sure itâs a 100% correct) on github:-
SOLVED: The issue was with the integration âRaspberry Pi GPIO PWM custom integrationâ used to control the case fan as a light entity. The integration has now been updated to be compatible with 2022.7.0 - NOTE: the configuration yaml has changed from the previous version (see documentation).
Now a much faster boot and running speed.
So after all, nothing to do with the raspberry_pi integration 
Nope, unfortunately not for me. I havenât used that integration. Iâll see, if this persists in my case and report back.
Not directly - just impacted on the load time.
Wasnât an obvious issue until I realised that this integration was the only new addition since the last HA core update.
Good luck with finding the right solution.
YES!!! That fixed it! 
I cannot thank you enough 
