No frontends for add-ons after migration to SSD on Raspi 5

I have HA running on a Raspi 5. I am using the SSH/Terminal, VSC and Z-Wave JS add-ons. Everything is/was running fine.

I migrated from the SD card to a NVMe SSD and set the Raspi up to boot from the SSD and to run without SD card. I did this by

  • Running a full backup
  • Powering the Raspi down
  • Install HA on the new SSD
  • Attach SSD to Raspi
  • Boot Raspi with a minimal Raspbian to modify the bootloader
  • Power down Raspi, remove SD card, boot from SSD

That went fine, Raspi bootet up from SSD and I was presented with the onboarding screen. I choose to restore from the backup I perviously made and that went fine, too. All devices, services etc. came up as expected, as far as I have checked so far, everything is working.

Then I found out, that my three add-ons seem not to work: Selecting them from the sidebar always tell me, that these are not running.
image

This is consostent with the status in the add-on manager.

I tried starting multiple times, de- and re-installing, rebooting - no change. Then I started to look in the add-ons’ logfiles and found them to my big surprise to be running, e.g.:

[15:53:31] INFO: Starting the ttyd daemon...
[15:53:31] INFO: Starting the SSH daemon...

[...]

Starting session: shell on pts/0 for dirk from 192.168.178.25 port 32163 id 0
Received disconnect from 192.168.178.25 port 32163:11: disconnected by user
Disconnected from user dirk 192.168.178.25 port 32163

As you can see, the service is running and I am able to connect to it and use it from an external machine, too. What is not working is the “frontend” in HA, which I could previously start from the sidebar.

The same is true for the other add-ons: Z-Wave JS gives the same error messages in the frontend, but my devices work fine, and the log does not indicate any problems, too:

[...]

2024-03-23 17:16:49.919 INFO APP: GET /health/zwave 301 0.589 ms - 191
2024-03-23 17:17:19.974 INFO APP: GET /health/zwave 301 0.507 ms - 191
2024-03-23 17:17:50.030 INFO APP: GET /health/zwave 301 0.472 ms - 191
2024-03-23 17:18:20.082 INFO APP: GET /health/zwave 301 0.514 ms - 191
2024-03-23 17:18:50.138 INFO APP: GET /health/zwave 301 0.525 ms - 191
2024-03-23 17:19:20.199 INFO APP: GET /health/zwave 301 0.577 ms - 191
2024-03-23 17:19:50.265 INFO APP: GET /health/zwave 301 0.544 ms - 191
2024-03-23 17:20:20.327 INFO APP: GET /health/zwave 301 0.531 ms - 191
2024-03-23 17:20:50.382 INFO APP: GET /health/zwave 301 0.464 ms - 191
2024-03-23 17:21:20.434 INFO APP: GET /health/zwave 301 0.563 ms - 191
2024-03-23 17:21:50.482 INFO APP: GET /health/zwave 301 0.503 ms - 191
2024-03-23 17:22:20.529 INFO APP: GET /health/zwave 301 0.461 ms - 191
2024-03-23 17:22:50.580 INFO APP: GET /health/zwave 301 0.504 ms - 191
2024-03-23 17:23:20.634 INFO APP: GET /health/zwave 301 0.507 ms - 191

[...]

Same seems to be the case for the VSC integration, but there I haven’t any idea on how to check without frontend :wink:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

-----------------------------------------------------------
 Add-on: Studio Code Server
 Fully featured Visual Studio Code (VSCode) experience integrated in the Home Assistant frontend.
-----------------------------------------------------------
 Add-on version: 5.15.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 12.1  (aarch64 / raspberrypi5-64)
 Home Assistant Core: 2024.3.3
 Home Assistant Supervisor: 2024.03.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[16:06:15] INFO: Configuring timezone (Europe/Berlin)...
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-user: starting
s6-rc: info: service init-mysql: starting
s6-rc: info: service init-mosquitto: starting
s6-rc: info: service init-code-server: starting
s6-rc: info: service init-code-server successfully started
s6-rc: info: service init-mysql successfully started
s6-rc: info: service init-mosquitto successfully started
s6-rc: info: service init-user successfully started
s6-rc: info: service code-server: starting
s6-rc: info: service code-server successfully started
s6-rc: info: service legacy-services: starting
[16:06:15] INFO: Starting code-server...
s6-rc: info: service legacy-services successfully started
[2024-03-23T15:06:16.095Z] info  Wrote default config file to /root/.config/code-server/config.yaml
[2024-03-23T15:06:16.511Z] info  code-server 4.20.0 d0215eca8804d0be5d3551c39404e336032c3141
[2024-03-23T15:06:16.513Z] info  Using user-data-dir /data/vscode
[2024-03-23T15:06:16.525Z] info  Using config file /root/.config/code-server/config.yaml
[2024-03-23T15:06:16.526Z] info  HTTP server listening on http://0.0.0.0:1337/
[2024-03-23T15:06:16.527Z] info    - Authentication is disabled
[2024-03-23T15:06:16.527Z] info    - Not serving HTTPS
[2024-03-23T15:06:16.527Z] info  Session server listening on /data/vscode/code-server-ipc.sock

When starting up, I have one error in the log. I have no idea, if it is related, because I don’t understand it:

Logger: homeassistant
Quelle: components/sonos/__init__.py:206
Erstmals aufgetreten: 17:10:43 (4 Vorkommnisse)
Zuletzt protokolliert: 17:11:13

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/urllib3/util/connection.py", line 95, in create_connection
    raise err
  File "/usr/local/lib/python3.12/site-packages/urllib3/util/connection.py", line 85, in create_connection
    sock.connect(sa)
TimeoutError: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/urllib3/connectionpool.py", line 715, in urlopen
    httplib_response = self._make_request(
                       ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/urllib3/connectionpool.py", line 416, in _make_request
    conn.request(method, url, **httplib_request_kw)
  File "/usr/local/lib/python3.12/site-packages/urllib3/connection.py", line 244, in request
    super(HTTPConnection, self).request(method, url, body=body, headers=headers)
  File "/usr/local/lib/python3.12/http/client.py", line 1331, in request
    self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/local/lib/python3.12/http/client.py", line 1377, in _send_request
    self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.12/http/client.py", line 1326, in endheaders
    self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/local/lib/python3.12/http/client.py", line 1085, in _send_output
    self.send(msg)
  File "/usr/local/lib/python3.12/http/client.py", line 1029, in send
    self.connect()
  File "/usr/local/lib/python3.12/site-packages/urllib3/connection.py", line 205, in connect
    conn = self._new_conn()
           ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/urllib3/connection.py", line 179, in _new_conn
    raise ConnectTimeoutError(
urllib3.exceptions.ConnectTimeoutError: (<urllib3.connection.HTTPConnection object at 0x7f84e64aa0>, 'Connection to 192.168.50.85 timed out. (connect timeout=10)')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/requests/adapters.py", line 486, in send
    resp = conn.urlopen(
           ^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/urllib3/connectionpool.py", line 799, in urlopen
    retries = retries.increment(
              ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/urllib3/util/retry.py", line 592, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='192.168.50.85', port=1400): Max retries exceeded with url: /xml/DeviceProperties1.xml (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f84e64aa0>, 'Connection to 192.168.50.85 timed out. (connect timeout=10)'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/sonos/__init__.py", line 482, in _async_handle_discovery_message
    await self.async_subscribe_to_zone_updates(discovered_ip)
  File "/usr/src/homeassistant/homeassistant/components/sonos/__init__.py", line 206, in async_subscribe_to_zone_updates
    await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/soco/core.py", line 445, in household_id
    self._household_id = self.deviceProperties.GetHouseholdID()[
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/soco/services.py", line 207, in _dispatcher
    return self.send_command(action, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/soco/services.py", line 474, in send_command
    args = self.compose_args(action, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/soco/services.py", line 334, in compose_args
    for action in self.actions:
                  ^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/soco/services.py", line 682, in actions
    self._actions = list(self.iter_actions())
                    ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/soco/services.py", line 708, in iter_actions
    scpd_body = requests.get(self.base_url + self.scpd_url, timeout=10).content
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/requests/api.py", line 73, in get
    return request("get", url, params=params, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/requests/adapters.py", line 507, in send
    raise ConnectTimeout(e, request=request)
requests.exceptions.ConnectTimeout: HTTPConnectionPool(host='192.168.50.85', port=1400): Max retries exceeded with url: /xml/DeviceProperties1.xml (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f84e64aa0>, 'Connection to 192.168.50.85 timed out. (connect timeout=10)'))

Any ideas welcome!

Is this IP it is trying to connect the right one? First step for met would be to check the network settings of HA.

Power down your Pi (no reboot, power off) and start it again.

1 Like

The IP belongs to a Sonos Playbase, which currently isn’t reachable from HA’s subnet. HA’s IP is 192.168.10.201 (and has been the same before the switch to the SSD), so I doubt a bit that the frontends not showing is related to this. The Sonos service doesn’t detect any devices, which I guess is the result of this error…

That did it! Thanks! Any idea/hint, why a power down was needed and a restart (or many restarts :wink:) wasn’t sufficient?