Hello,
Today I updated to core 2023.10. After the update, the ha Web UI will no longer start.
The core log shows some warnings and two Errors (SyncWorker_3) [pyhik.hikvision], but I don’t think that’s something new.
The Supervisor logs show an ERROR (Mainthread) [Supervisor.homeassistant.api] Error on call https://172.30.32.1:8123/api/core/state: - the IP-address is not one I recognize and it’s never been on my network. But I’m unsure if this is related to the problem at hand.
Does anyone have an idea on how to get the system running again, other than a restore?
Thanks -
Banner reports: Home Assistant OS 10.5, Home Assistant Core: 2023.10.0
SU Update works, but reports "No supervisor update available - 2023.10.0
Yes I did update the supervisor - when running the command “su update” HA reports “No supervisor update available - 2023.10.0”. There was however an update to the core, after this topic was started, but after updating core to 2023.10.1 the problem remains.
I have tried to look deeper at the errors. I found this that describes similar symptoms, particularly item C - there is a small time-window at HA startup, where it is possible to connect to the UI. Unfortunately the error is not the same, and the ZHA is not part of my configuration.
I’ve tried downgrading the Core to 2023.9.3 same version as before the upgrade and as last backup, but the issue remains.
I’ve also tried performing a restore, but that does not work (another job running).
Any other thoughts on troubleshooting the installation?
Removing this configuration was necessary to get the system running again. This configuration is part of duckdns add-on configuration. It looks like the SSL certificate expired and this has caused the issue.
Also by painstaking debugging I figured out there was an issue with this integration:
:ihc
When using manual configuration for this integration, this error poped up in the Supervisor log:
ERROR (Mainthread) [Supervisor.homeassistant.api] Error on call https://172.30.32.1:8123/api/core/state:
Not very informative. Restarting the IHC Controller by cycling the power, resolved the issue.