#Failure to connect Shelly Pro3EM and Shelly Pro2 to HA

1 messages · Page 1 of 1 (latest)

chrome dagger
#

using the instructions in https://www.home-assistant.io/integrations/shelly/

Failure to connect Shelly Pro3EM and Shelly Pro2 to HA
As far as I'm aware, they're gen2 devices, both with firmware 1.7.4

HA IP is 172.16.50.6:8123
I've also attempted to configure outbound websocket on Shelly with Default TLS
ws://172.16.50.6:8123/api/shelly/ws
Calling that address results in 404. Calling http://172.16.50.6:8123/api/websocket returns

 No WebSocket UPGRADE hdr: None
 Can "Upgrade" only to "WebSocket".

Currently no SSL cert configured - but I may want to do that over my reverse proxy in the future.

Both shellys show up in HA Shelly integration but are unable to be added.
Shellys are connected via WIFI
I've also attempted adding manually using shelly IPs but that was unsuccessful, too. IPs are all static. No devices have the same IPs

image.png
chrome dagger
#

I've now also made sure that the firewall was not the issue by explicitly allowing traffic between HA and the Shelly subnet

#

I've also confirmed that some sort of connection is possible by providing the shelly the default websocket endpoint but it results in warnings/errors because it receives unexpected format

📎 message.txt
# 
Logger: aiohttp.websocket
Source: components/websocket_api/http.py:317
First occurred: 16:49:22 (146 occurrences)
Last logged: 17:26:52

    10.99.20.6: Client protocols ['json-rpc'] don’t overlap server-known ones ()
    10.99.20.7: Client protocols ['json-rpc'] don’t overlap server-known ones ()