Today at about 2am (CET) Withings sent me an email with a notification it cannot connect my instance of HA (through NabuCasa). The same message I got at about 10am.
It leads me to check if HA really doesn’t work through NC. Indeed, it wasn’t working.
Quick grep from HA log:
config $ cat ./home-assistant.log | grep nabu
2022-06-17 00:15:14 INFO (SyncWorker_3) [hass_nabucasa.acme] Load exists ACME registration
2022-06-17 00:15:14 INFO (SyncWorker_6) [hass_nabucasa.acme] Initialize challenge for a new ACME certificate
2022-06-17 00:15:16 INFO (MainThread) [hass_nabucasa.acme] Wait 60sec for publishing DNS to ACME provider
2022-06-17 00:16:16 INFO (SyncWorker_2) [hass_nabucasa.acme] Finishing challenge for the new ACME certificate
2022-06-17 00:16:20 INFO (SyncWorker_2) [hass_nabucasa.acme] Renew old certificate: /config/.cloud/remote_fullchain.pem
2022-06-17 00:16:22 INFO (MainThread) [snitun.utils.aiohttp_client] AioHTTP snitun client disconnected from: eu-central-1-0.ui.nabu.casa:443
2022-06-17 00:16:29 INFO (MainThread) [snitun.utils.aiohttp_client] AioHTTP snitun client connected to: eu-central-1-0.ui.nabu.casa:443
Nothing which would directly point to the problem. However it was obvious that it doesn’t work.
Restart of HA did recover this functionality, despite some error of snitun.
config $ cat ./home-assistant.log | grep nabu
2022-06-17 10:41:16 INFO (MainThread) [hass_nabucasa.iot] Connected
2022-06-17 10:41:22 ERROR (MainThread) [hass_nabucasa.remote] Connection problem to snitun server
2022-06-17 10:41:34 INFO (MainThread) [homeassistant.components.netatmo] Register Netatmo webhook: https://hooks.nabu.casa/.....
2022-06-17 10:41:35 INFO (MainThread) [snitun.utils.aiohttp_client] AioHTTP snitun client connected to: eu-central-1-0.ui.nabu.casa:443
Any idea why NC lost connection all of sudden?
I experience a similar issue about once a year.