So I’ve been running Home Assistant OS on a Raspberry Pi 3+ for a month with no issues and I decided to move it to my Turing Pi CM3 (Compute module 3) system to save some space. Did a full backup, shut down the Rpi3, loaded the OS on the CM3 module and…
Nothing.
Reason is the files in the boot partition do not include the bcm2710-rpi-cm3.dtb file as it’s not really built to support CM3 modules. Added it, started to come up but I can see the custom kernel is not genned to support the ethernet and it crashes after 4 seconds of booting probably because the mmc access is not genned into the kernel.
sigh I’ll figure that out later. So in the meantime I loaded up the latest RPI OS on the CM3+, booted up and installed core. Install went relatively well, system is up, no backup/restore function but I went into the .homeassistant directory, extracted the data tar file contents (including the . directories), fired up and all came up properly.
EXCEPT: The system throws occasional errors because the Home Assistant Supervisor (hassio) integration fails to start and the “Raspberry Pi” integrations depends on hassio to work.
Now this makes sense, core doesn’t have the concept of the Supervisor integration and doesn’t need to report on all the state bits of the Pi since I have ssh access into the OS. However it’s popping the error and I’d like to remove the integration.
Which would be easy if it showed up in the Integrations tab, but it doesn’t (probably because Core never has this) so I can’t just use the trash can method.
Which files do I need to edit in the .storage directory to get rid of hassio? I looked at the files with grep, and all references seem to be under the category of “Disabled” which would be fine except something is causing Core to try to start it anyway.
Any thoughts? Thanks!