search

zachcheatham / ha-omada

Home Assistant TP-Link Omada Integration
189 stars 26 forks source link

Cannot connect to service #35

Closed kwil2011 closed 3 months ago

kwil2011 commented 2 years ago

I have the hardware controller I am trying to setup the integration but having no luck i have tried the following URLS https://192.168.*.*:8043 with SSL checked 2022-07-06 12:39:04 WARNING (MainThread) [custom_components.omada.controller] Unable to connect to Omada at https://192.168.*.*:8043: Error connecting to https://192.168.*.*:8043/api/info: Cannot connect to host 192.168..:8043 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1129)')] 2022-07-06 12:39:21 WARNING (MainThread) [custom_components.omada.controller] Unable to connect to Omada at https://192.168.*.*:8043: Error connecting to https://192.168.0.5:8043/api/info: Cannot connect to host 192.168..:8043 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1129)')]

without SSL checked 2022-07-06 12:41:51 WARNING (MainThread) [custom_components.omada.controller] Unable to connect to Omada at https://192.168.*.*:8043: Unknown site 'Default'

then using http:// SSL checked 2022-07-06 12:44:10 WARNING (MainThread) [custom_components.omada.api.controller] Error connecting to http://192.168.*.*:8043/api/info: API returned HTTP 400. 2022-07-06 12:44:10 WARNING (MainThread) [custom_components.omada.controller] Unable to connect to Omada at http://192.168.*.*:8043: Call to http://192.168.0.5:8043/api/info received status code 400:

Then using http:// SSL unchecked 2022-07-06 12:45:30 WARNING (MainThread) [custom_components.omada.api.controller] Error connecting to http://192.168.*.*:8043/api/info: API returned HTTP 400. 2022-07-06 12:45:30 WARNING (MainThread) [custom_components.omada.controller] Unable to connect to Omada at http://192.168.*.*:8043: Call to http://192.168.*.*:8043/api/info received status code 400:

Any assistance would be appreciated

zachcheatham commented 1 year ago

If you normally use https to connect to the controller via your browser, you should enter the same address during setup. If there is no valid SSL certificate setup for your controller, please also disable SSL verification.

Which version of the controller are you using? Also, please be sure the Site "Default" exists within your controller.

wuppiwuppi commented 1 year ago

I found out, that it is not possible to use the non-ssl connection like http://192.168.0.1:8088 using https with or without a valid ssl is a must have: https://192.168.0.1:8043

is this intended?