Hi there—thanks for maintaining the Technicolor integration!
I'm running into three distinct issues that are preventing the integration from working on recent versions of Home Assistant:
1. SSL certificate verification fails
Logs show:
Authentication failed. Exception: HTTPSConnectionPool(host='192.168.0.1', port=443):
Max retries exceeded with url: / (Caused by SSLError(
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed:
self-signed certificate (_ssl.c:1032)
))
yaml
Copiar código
This happens because the router uses a self-signed certificate, and the integration doesn’t offer a way to disable SSL verification (e.g., a verify_ssl: false option). It would be great if the integration supported disabling cert validation for local network connections.
2. HTTP URL is malformed after HTTPS fails
After the SSL failure, it attempts fallback to HTTP, but logs indicate it's building the URL incorrectly:
Authentication failed. Exception:
HTTPConnectionPool(host='http', port=80):
Max retries exceeded with url: /192.168.0.1:80
(Caused by NameResolutionError("<urllib3.connection.HTTPConnection object
at 0x…>: Failed to resolve 'http'"))
yaml
Copiar código
And similarly:
Failed to connect to Technicolor ((ConnectionError(
MaxRetryError('HTTPConnectionPool(host='http', port=80):
Max retries exceeded with url: /192.168.0.1:80 (Caused by
NameResolutionError("<urllib3.connection.HTTPConnection object at …>: Failed to resolve 'http'"))
')),))
yaml
Copiar código
This suggests the integration constructs something like http://http/192.168.0.1:80 — clearly malformed. The fallback logic for HTTP needs to be fixed to correctly target http://<router_ip>/.
3. Obsolete Home Assistant API (async_forward_entry_setup)
The logs also show:
AttributeError: 'ConfigEntries' object has no attribute 'async_forward_entry_setup'.
Did you mean: 'async_forward_entry_setups'?
vbnet
Copiar código
That's because async_forward_entry_setup was deprecated and removed in recent HA versions. The correct pattern now is:
await hass.config_entries.async_forward_entry_setups(entry, ["device_tracker"])
instead of:
python
Copiar código
hass.async_create_task(
hass.config_entries.async_forward_entry_setup(entry, "device_tracker")
)
You can reference the HA dev blog post here:
developers.home-assistant.io
Hi there—thanks for maintaining the Technicolor integration!
I'm running into three distinct issues that are preventing the integration from working on recent versions of Home Assistant:
1. SSL certificate verification fails
Logs show:
Authentication failed. Exception: HTTPSConnectionPool(host='192.168.0.1', port=443):
Max retries exceeded with url: / (Caused by SSLError(
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed:
self-signed certificate (_ssl.c:1032)
))
yaml
Copiar código
This happens because the router uses a self-signed certificate, and the integration doesn’t offer a way to disable SSL verification (e.g., a
verify_ssl: falseoption). It would be great if the integration supported disabling cert validation for local network connections.2. HTTP URL is malformed after HTTPS fails
After the SSL failure, it attempts fallback to HTTP, but logs indicate it's building the URL incorrectly:
Authentication failed. Exception:
HTTPConnectionPool(host='http', port=80):
Max retries exceeded with url: /192.168.0.1:80
(Caused by NameResolutionError("<urllib3.connection.HTTPConnection object
at 0x…>: Failed to resolve 'http'"))
yaml
Copiar código
And similarly:
Failed to connect to Technicolor ((ConnectionError(
MaxRetryError('HTTPConnectionPool(host='http', port=80):
Max retries exceeded with url: /192.168.0.1:80 (Caused by
NameResolutionError("<urllib3.connection.HTTPConnection object at …>: Failed to resolve 'http'"))
')),))
yaml
Copiar código
This suggests the integration constructs something like
http://http/192.168.0.1:80— clearly malformed. The fallback logic for HTTP needs to be fixed to correctly targethttp://<router_ip>/.3. Obsolete Home Assistant API (
async_forward_entry_setup)The logs also show:
AttributeError: 'ConfigEntries' object has no attribute 'async_forward_entry_setup'.
Did you mean: 'async_forward_entry_setups'?
vbnet
Copiar código
That's because
async_forward_entry_setupwas deprecated and removed in recent HA versions. The correct pattern now is: