2022.8: You can fix it!

just upgraded from a functional 2022.8.0 Supervised installation to 2022.8.1, and it now won’t start the homeassistant container.

Not getting anything logged, and nothing changed in my config at all …

It’s got me concerned that it’s not even coming up in safe mode for me to be able to work out what’s going on - can someone point me in the direction of where to start looking ?

I can roll back to 2022.8.0, but the container still won’t start, is returning an error 143, which is suitably vague when I google it

Can you confirm if the first code you posted is working and not the second code? If the first one is working for you, than my theory is correct but if both are not working, than is something else.

After the update, all my entities were visible and the RM devices are still registered in the integration. Just will not respond to any commands.

Hello. great release!! thanks. I’m just wondering when will tuya doorbell press events be added in either tuya/localtuya/HA? Again many thanks even for just an estimate :slight_smile:

The first codeblock is a sample from one of my .storage files, which I don’t think is actually used directly for anything (I believe they’re basically temporary output files created during the learning process?). That is indeed what both of my files there look like though. The second codeblock is from my current configuration.yaml (and as far as I understand, that’s the bit that HA is actually reading/working with.

With both of those in place, none of the switches are loading in HA for me (although the devices/entities themselves do).

I just rolled back to 2022.7.7 and both of my switches are showing up now.

From the looks of it, it seems the recent update will only work with the first bit of code you posted. You will need to create a switch from those command if that is real or not.

What I did was create a script for each of those commands and than use those script to create a template switch. I don’t know if there is another easier way. So in your example code.

      - service: remote.send_command
          entity_id: remote.rm4_remote # need to see what your actual entity id is
          device: kitchen_ac
          - turn_on

      - service: remote.send_command
          entity_id: remote.rm4_remote # need to see what your actual entity id is
          device: kitchen_ac
          - turn_off
  - platform: template
       friendly_name: 'Kitchen Switch Light'
         - service: script.turn_on_kitchen
         - service: script.turn_off_kitchen

I just rolled back to 2022.7.7 and both of my switches are showing up now.

oh. Seems like both were not working for you on 8.1 update.

I’d try re-running the install again and make sure the host is up-to-date as well.

Thanks David - Debian was up to date prior to updating to 2022.8.1.

When you say try the install again, you mean running the Supervised installation?

Yep. It’s always fixed these types of things for me and won’t delete anything either. Also maybe check the agent is up-to-date as well

yeah, done that - still got the same behaviour… looks like I’m staring down the barrel of a rebuild, although I’m now getting an exit code 256 on the homeassistant container, which means it still won’t start in safe mode even :face_with_raised_eyebrow:

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 Cannot connect to host ssl:False [Connect call failed ('', 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?

@almighty59 I’m assuming you mean you currently use https://github.com/custom-components/ble_monitor?

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.


Yes all of my Broadlink entities are gone since upgrading to 2022.8 and 2022.8.1.

Thank you for your follow-up post. Reloading the Broadlink integration fixed the issue for me as well.

1 Like

Dahua cameras connection not possible also…

Not sure what’s going on. Update to 2022.8.1 is taking ages. 5 minutes now? Should I abort somehow or is it going to stuff up my installation?

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

Yeah … there is. It’s just a messy way of doing it. It’s called powering off and powering on again.

Edit: How do I update from the CLI to find out what’s happening?