krahabb / meross_lan

Home Assistant integration for Meross devices
MIT License
423 stars 47 forks source link

Connection Issue - Cannot connect to host/connect call failed #424

Open jordan803 opened 5 months ago

jordan803 commented 5 months ago

When trying to add Garage Door accessory, I get the error: Cannot connect to host 10.50.50.66:80 ssl:default [Connect call failed ('10.50.50.66', 80)]

Screenshot 2024-04-25 at 11 11 20 AM

Version of the custom_component

Latest Version v5.0.4

Configuration


Add your logs here.

Describe the bug

This error comes up when trying to add a new device to HA through the Local LAN option.

I've tried removing and re-adding the add on and also rebooting HA and the accessory. I don't think it's a network issue because the devices are on the same subnet and the error comes up if I enter any other IP as well. It seems like an issue with communication between the application layer and network layer.

Debug log

\ 2024-04-25 11:07:42.245 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration meross_cloud which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-04-25 11:07:42.247 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration meross_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-04-25 11:07:42.247 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-04-25 11:07:45.904 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues 2024-04-25 11:08:35.326 WARNING (SyncWorker_7) [homeassistant.loader] We found a custom integration meross_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-04-25 11:08:35.327 WARNING (SyncWorker_7) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

Add your logs here.

kudos commented 2 months ago

Highlighting in case it isn't noticed, it's trying to do SSL on port 80.

krahabb commented 2 months ago

That's only a synthetic log message stating that the connection function has been called with 'default' value (which is nevertheless 'ssl==enabled' in aiohttp) but that only means that ssl would be set in place in case the protocol requires it and, based off conventions used in aiohttp, since the url is something in the line 'http://{host}:80/config', the connection would not use ssl anyway, independently of the ssl configuration parameter.