Trouble with Websocket_api

Third party integrations
21

Hi @koying! Thanks for your swift reply! That’s correct, I have https enabled.
I changed the protocol to wss (instead of ws). I got these errors instead:

2021-05-14T11:07:12.308Z <HassController:NOTICE> HassController#hass attempting reconnection to wss://192.168.50.167:8123/api/websocket/api/websocket
2021-05-14T11:07:12.309Z <HassController:NOTICE> HassController#hass connecting via WS to wss://192.168.50.167:8123/api/websocket/api/websocket
2021-05-14T11:07:12.367Z <HassController:WARN> HassController#hass websocket error during open/negotation: Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: IP: 192.168.50.167 is not in the cert's list:
2021-05-14T11:07:12.368Z <HassController:NOTICE> HassController#hass websocket to wss://192.168.50.167:8123/api/websocket/api/websocket closed during open/negotiation
2021-05-14T11:07:12.373Z <HassController:WARN> HassController#hass failed to connect/initialize communication: Error [ERR_TLS_CERT_ALTNAME_INVALID]: Hostname/IP does not match certificate's altnames: IP: 192.168.50.167 is not in the cert's list:
22

Yep, that’s what I mentioned regarding your certificate being invalid :wink:

Is your certificate a “proper” one, with SAN (alternative names = host names)? If so, you have to use the actual hostname of your certificate in the url. IP will not be accepted.

23

Sorry for being a newbee… But how do I do to solve it?

24

What is the certificate you are using?
For the test, there is a way to disable SSL validation, but probably too much hassle for a test.

Check if "Multisystem reactor” has a way to disable “SSL Verification”

If it doesn’t, and that you don’t know your way around certificates, and that all your connections are local, probably easiest for you is to disable https in HA.

1 Like
25

Thanks!
I disabled https in HA, and that did the trick!