seeing this in the supervisor logs - note I’ve been running Portainer and xteve for nearly 3 years in this configuration with no issues…
22-08-05 14:40:44 INFO (MainThread) [supervisor.resolution.module] Create new suggestion SuggestionType.EXECUTE_REPAIR - ContextType.CORE / None
22-08-05 14:40:44 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.APPLICATION' starting 1 add-ons
22-08-05 14:40:44 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning addon_e4641267_hass-actronque application
22-08-05 14:40:44 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on mikejmcguire/hass-actronque-amd64 with version 2022.5.0
22-08-05 14:40:45 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqtt'
22-08-05 14:40:45 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache
22-08-05 14:40:49 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled
22-08-05 14:40:49 INFO (MainThread) [supervisor.core] Supervisor is up and running
22-08-05 14:40:49 INFO (MainThread) [supervisor.host.info] Updating local host information
22-08-05 14:40:49 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
22-08-05 14:40:49 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
22-08-05 14:40:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
22-08-05 14:40:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
22-08-05 14:40:49 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
22-08-05 14:40:49 INFO (MainThread) [supervisor.host.services] Updating service information
22-08-05 14:40:50 INFO (MainThread) [supervisor.host.network] Updating local network information
22-08-05 14:40:50 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
22-08-05 14:40:50 INFO (MainThread) [supervisor.host.manager] Host information reload completed
22-08-05 14:40:51 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_FAILED/ContextType.DNS_SERVER
22-08-05 14:40:51 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
22-08-05 14:40:51 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_IPV6_ERROR/ContextType.DNS_SERVER
22-08-05 14:40:51 INFO (MainThread) [supervisor.resolution.check] System checks complete
22-08-05 14:40:51 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
22-08-05 14:40:51 WARNING (MainThread) [supervisor.resolution.evaluations.base] Found unsupported images: {'portainer/portainer-ce', 'alturismo/xteve'} (more-info: https://www.home-assistant.io/more-info/unsupported/software)
22-08-05 14:40:53 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-08-05 14:40:53 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
22-08-05 14:40:53 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
22-08-05 14:44:38 INFO (SyncWorker_4) [supervisor.docker.interface] Starting homeassistant
22-08-05 14:44:38 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
22-08-05 14:44:48 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
hmm, rolled forward to 2022.8.1 again, and how this:
22-08-05 14:48:07 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-08-05 14:48:07 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
22-08-05 14:48:07 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
22-08-05 14:48:11 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2022.8.1
22-08-05 14:48:11 INFO (SyncWorker_2) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/qemux86-64-homeassistant:2022.7.7 to ghcr.io/home-assistant/qemux86-64-homeassistant:2022.8.1
22-08-05 14:48:11 INFO (SyncWorker_2) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/qemux86-64-homeassistant with tag 2022.8.1.
22-08-05 14:49:08 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning homeassistant application
22-08-05 14:49:08 INFO (MainThread) [supervisor.homeassistant.core] Successfully started Home Assistant 2022.8.1
22-08-05 14:49:08 INFO (SyncWorker_5) [supervisor.docker.interface] Cleanup images: ['ghcr.io/home-assistant/qemux86-64-homeassistant:2022.7.7']
22-08-05 14:49:13 ERROR (MainThread) [supervisor.homeassistant.api] Error on call https://172.30.32.1:8123/api/config: Cannot connect to host 172.30.32.1:8123 ssl:False [Connect call failed ('172.30.32.1', 8123)
@frenck and @Jc2k just to clarify, if we’ve been using the Bluetooth Low Energy Monitor integration for the Xiaora BLE plant sensors and the new Bluetooth integration has picked them up and automatically added them should we convert over and delete them from the BLEM integration?
Ultimately it’s up to you, you can keep using your custom components as long as they keep working.
I worked with Ernst from that project to get the Xiaomi MiBeacon devices added directly to HA on top of the new Bluetooth framework. I was able to reuse a lot of his parsing code. Right now there isn’t much difference between the 2 other than one is built in, and the older one is more mature/battle tested. So other than simplifying your setup theres no rush to use the new one. But also no reason not to if it works for you.
Longer term, for the plant sensors i’d like to add things BLEM doesn’t - like restoring the battery sensor that the MiFlora integration had.
I don’t know if you can - mine is completely broken, so going back to 2022.7.7 on a VM to at last have some automations that will run overnight for our lighting, etc
8 Dahua cams (inddor and outdoor) here and connected through Onvif. No problems whatsoever after updating HA to 2022.8.0 / 2022.8.1. They all stream just fine.
Hmmm, 8.1 also not resolved my case:
And detailed log:
2022-08-05 08:24:10.743 ERROR (MainThread) [homeassistant.components.onvif] Couldn’t connect to camera ‘xxxxxxxxx’, please verify that the credentials are correct. Error: Invalid data
2022-08-05 08:24:10.793 ERROR (MainThread) [homeassistant.components.onvif] Couldn’t connect to camera ‘xxxxxxxxx’, please verify that the credentials are correct. Error: Invalid data
2022-08-05 08:24:10.901 ERROR (MainThread) [homeassistant.components.onvif] Couldn’t connect to camera ‘xxxxxxxxx’, please verify that the credentials are correct. Error: Invalid data
2022-08-05 08:24:10.906 ERROR (MainThread) [homeassistant.components.onvif] Couldn’t connect to camera ‘xxxxxxxxx’, please verify that the credentials are correct. Error: Invalid data
2022-08-05 08:24:10.910 ERROR (MainThread) [homeassistant.components.onvif] Couldn’t connect to camera ‘xxxxxxxxx’, please verify that the credentials are correct. Error: Invalid data
2022-08-05 08:24:11.469 ERROR (MainThread) [homeassistant.components.onvif] Couldn’t connect to camera ‘xxxxxxxxx’, please verify that the credentials are correct. Error: Invalid data
@Jc2k yes the BLEM that you linked to is what I meant. For some reason, I remember that there was supposedly a “breaking change” on one of the last updates that some users were having a problem with but my Xiaora plant sensors were not affected. I think it was the following change…
Bluetooth (multiple integrations)
Home Assistant is upgrading to Python 3.10 this release and comes with a breaking change affecting multiple integrations.
I didn’t think about the older one being “more mature/battle tested” as you said but that’s true. I was more concerned with the same devices being connected through two integrations and somehow having that cause an issue. Maybe I will leave them both connected or split the devices between the two as a way to monitor the new integration for any possible bugs. At first, I did lose everything and there seemed to be a conflict but now both seem to be working. The signal strength entity has also now shown up for the older BLEM integration and both appear to be displaying the same data.
As for the new integration, yes it definitely integrates a lot easier. I was actually shocked by how quickly it connected. I did not have to deal with all of the connection issues that I had to deal with when I first used the BLEM integration.
And yes, pleeeeease try to restore the battery sensor that the MiFlora integration had.
EIDT: @Jc2k I just noticed that the Xiaora BLE sensors are showing different data than the BLEM. I checked it versus the Andoird App and the app and the BLEM are the same. I’ll continue to monitor it…
Normally when you report a bug you get a response within a few hours but this time it has been quiet for over 2 weeks and I am forced to stay stuck in release 2022.06.7. I have reported this bug under number #75437 (and AppDeamon issue on HA supervised #1551). The problems do not occur with HA OS on a Raspberry. It does occur on an Intel NUC running HA Supervised. It seems to have something to do with Appdeamon. Appdeamon does not start up properly and displays an error message. In addition, the log is filled up at a rapid rate. I do have 20 Gb available on the hard drive but still after a while I get a message that I am starting to run out of free space. I turned off Appdeamon and that did stop the log filling. So it indeed seems to be due to Appdeamon but again only on a HA supervised. And is it true that you cannot update to Supervisor 2022.07.1, Supervisor 2022.08.0 or Supervisor 2022.08.1?
