-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assist Microphone Addon Error with connecting addon to HA #3271
Comments
Hi ! what is your local url HA parameter ? |
Hi |
Oups. Delete your last comment for security ! And if you use local ip with http ( no cert) ? |
I'm having the same issue. I'm using https://......duckdns.org:8123 for both the internal and the external URL value. Does the log entry mean the validation is failing because the cert's host is being compared to homeassistant:8123? Why would this occur? |
Since the 2.2.2 update, I'm not seeing the certificate error. Now I'm seeing an empty URL: aiohttp.client_exceptions.InvalidURL: wss://:8123/api/websocket Traceback (most recent call last): |
i tried ngix the ssl error is gone, but still made problems with detecting Anker powerconf. So i removed ngix and went back to old state I removed the addon and install now 2.2.2 and tried it again. I get these messages: /run: line 21: bashio::core.ip_address: command not found |
Hi, Error in Ver 2.2.2 |
2.2.3 is available 👍 |
ok got it |
I have same issue with duckdns and Assist Microphone. I think the "host" in configuration is not valid. How should I config the Assist Microphone add-on host value?! And the solution: if you use DuckDNS, you need to install and setup NGINX to add "host" configuration as local IP adress. |
Same issue. I do not want to setup yet another addon to SSL proxy like nginx. It's better to just have the option to disable SSL for an addon. The problem is that this addon does not seem to copy over /etc/ssl/certs/ca-certificates.crt into the addon docker container. It does create an environment variable for it. But it's not copied, its a different file. Workaround 1 (until restart):
Workaround 2 (until update):
Permanent solutionFor perhaps the next version @synesthesiam
|
For future travelers, the official Assist Microphone add-on (https://github.com/home-assistant/addons/tree/master/assist_microphone) does not use a websocket connection anymore, and so there are no issues with certificates. |
Describe the issue you are experiencing
Setup Assist Microphone is possible. After the first start this error occurs in the Logs of Addon.
Anker power conf is on latest Firmware
Addon is on 2.2.1
HA OS 11
Core 10.3
Error is
File "/usr/local/lib/python3.11/dist-packages/aiohttp/connector.py", line 988, in _wrap_create_connection raise client_error(req.connection_key, exc) from exc aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host homeassistant:8123 ssl:default [Connect call failed ('172.30.32.1', 8123)]
SSL is activ but my ha is running on domain:443 but I don't know if it is relevant.
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
Whisper
What is the version of the add-on?
2.2.1.
Steps to reproduce the issue
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
Additional information
Assist Microphone is until now not listed in official addons.
The text was updated successfully, but these errors were encountered: