#Your HA instance needs to be able to
1 messages ยท Page 1 of 1 (latest)
Go to repairs and use the icon in the upper right to check system info
What do you see in the Home Assistant Cloud section?
Home Assistant Cloud
Ingelogd true
Afloop abonnement 28 mei 2024 om 02:00
Relayer verbonden true
Relayer Region eu-central-1
Op afstand ingeschakeld true
Op afstand verbonden false
Alexa ingeschakeld false
Google ingeschakeld false
Externe server eu-central-1-9.ui.nabu.casa
Certificaatstatus generating
Certificaatserver bereikbaar ok
Authenticatieserver bereikbaar ok
Home Assistant Cloud bereikbaar ok
this is what you wanted to see is it not?
@keen edge i do not see any issues or do i overlook something
nope that's it. What do you see on the Settings > Cloud page?
I do not see anything that should explain my issue:
Nabu Casa-account
nie***@l****t.nl
Active user. You will be charged on May 28, 2024.
Cloudverbindingsstatus: Verbonden
Hmmm:
Afstandsbediening
Externe toegang wordt voorbereid. We zullen je op de hoogte brengen wanneer het klaar is.
i also get this message in the notification screen:
Home Assistant Cloud
Unable to create a certificate. We will automatically retry it and notify you when it's available.
@keen edge is there something else to check?
sorry, got pulled away
"Unable to create a certificate" needs to change before you'll see a connection. In your logs you might see a reason.
this is the only error that i can't figure for what it is:
Logger: homeassistant
Source: requirements.py:271
First occurred: 17:36:42 (27 occurrences)
Last logged: 19:02:42
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 880, in async_init
flow, result = await task
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 898, in _async_init
flow = await self.async_create_flow(handler, context=context, data=data)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 1000, in async_create_flow
handler = await _async_get_flow_handler(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2096, in _async_get_flow_handler
await _load_integration(hass, domain, hass_config)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2072, in _load_integration
await async_process_deps_reqs(hass, hass_config, integration)
File "/usr/src/homeassistant/homeassistant/setup.py", line 420, in async_process_deps_reqs
await requirements.async_get_integration_with_requirements(
File "/usr/src/homeassistant/homeassistant/requirements.py", line 52, in async_get_integration_with_requirements
return await manager.async_get_integration_with_requirements(domain)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/requirements.py", line 168, in async_get_integration_with_requirements
await self._async_process_integration(integration, done)
File "/usr/src/homeassistant/homeassistant/requirements.py", line 183, in _async_process_integration
await self.async_process_requirements(
File "/usr/src/homeassistant/homeassistant/requirements.py", line 242, in async_process_requirements
self._raise_for_failed_requirements(name, missing)
File "/usr/src/homeassistant/homeassistant/requirements.py", line 271, in _raise_for_failed_requirements
raise RequirementsNotFound(integration, [req])
homeassistant.requirements.RequirementsNotFound: Requirements for google_home not found: ['glocaltokens==0.6.9'].
finally ๐
I hope it makes more sense to you @keen edge then for me ๐
That's google home related. How is HA running here? What installation, what's it running on?
do you have access to the ssh add-on terminal
yes
can you run ha core rebuild in there
btw it is the "Advanced SSH & Web Terminal"
that's fine
i use atm OS 11.2 rc2
ok
done
Logger: homeassistant.components.esphome.dashboard
Source: helpers/update_coordinator.py:303
Integration: ESPHome (documentation, issues)
First occurred: 19:28:47 (1 occurrences)
Last logged: 19:28:47
Error requesting ESPHome Dashboard data: Cannot connect to host 127.0.0.1:65277 ssl:default [Connect call failed ('127.0.0.1', 65277)]
Logger: homeassistant.components.esphome.dashboard
Source: components/esphome/dashboard.py:126
Integration: ESPHome (documentation, issues)
First occurred: 19:28:47 (1 occurrences)
Last logged: 19:28:47
Dashboard unavailable; skipping reauth: Cannot connect to host 127.0.0.1:65277 ssl:default [Connect call failed ('127.0.0.1', 65277)]
Logger: homeassistant.util.package
Source: util/package.py:102
First occurred: 19:29:20 (3 occurrences)
Last logged: 19:29:35
Unable to install package glocaltokens==0.6.9: ERROR: Cannot install glocaltokens==0.6.9 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
are you using custom integrations?
Yes i do
try restarting HA in safe mode which will disable those
expand the advanced options after choosing the restart option
is switching now
btw thanks for your time ๐
Notification:
Invalid config
The following integrations and platforms could not be set up:
daily_schedule (Show logs)
hacs (Show logs)
Please check your config and logs.
That should mean that i now in safemode?
no different log are shown atm.
and the notification about the license did popup again
@keen edge sorry to say i do not see anything changing.
what license notification is this?
Home Assistant Cloud
Unable to create a certificate. We will automatically retry it and notify you when it's available.
@keen edge can i monitor somewhere the progress of creating the certificate?
only in the logs. Have you restored from a backup recently, or when this began ?
And have you configured an alias using your own domain?
No, it started after on of the latest HA upgrades.
yes i have also setup my own domain as well.
using the new alias option at nabucasa.com?
yep
have you made changes there?
no none at all
As in, did you setup the acme challenge dns entries and then remove them?
You might go to your provider's management panel and double check that nothing has been changed.
right, the nabucasa url and the custom alias are both needing certificates
Alternatively, you might remove the alias in your settings at nabucasa.com, then restart HA.
After that, see if HA can sucessfully validate the certificate for the Nabu Casa URL, as the alias will no longer be involved.
Then test the Nabu Casa URL
system will be restarted now after removing the alias from nc.com
that did the trick. i have access via the Nabu Casa URL
Do you want to report this issue to the right people.?
ok good to hear. It's already known that an alias that is no longer in place will prevent the nabucasa url from working, and it will get stuck in this state of "preparing" or "can't update certificate"
But you said it was in place. The only way to know that would be to check the configuration at your dns provider.
You can try adding the alias back now, making sure it is valid
i just did earlier. let me see what the state is/