• 22 Posts
  • 50 Comments
Joined 2 years ago
cake
Cake day: June 1st, 2023

help-circle
  • It looks like the Shelly device initiates contact with home assistant you may be able to just tell it to talk to the same api endpoint (following is for 2nd gen devices):

    In this case, navigate to the local IP address of your Shelly device, Settings >> Connectivity >> Outbound WebSocket and check the box Enable Outbound WebSocket, under server enter the following address:

    ws:// + Home_Assistant_local_ip_address:Port + /api/shelly/ws (for example: ws://192.168.1.100:8123/api/shelly/ws), click Apply to save the settings. In case your installation is set up to use SSL encryption (HTTPS with certificate), an additional s needs to be added to the WebSocket protocol, too, so that it reads wss:// (for example: wss://192.168.1.100:8123/api/shelly/ws).

    Assuming you are buying a new unit I’d try following that guide after backing up and seeing if it updates normally. The first gen devices used a different protocol, full instructions for both can be found here.

















  • We can get the port list another way. From the terminal on the raspberry pi run the command “nmap localhost”. Let us know what that shows, but I would expect to see either 80, 443, or both.

    As a side note, if you did not give the nextcloud container a certificate when you made it, you cannot use https:// on the browser, as it has no way to talk using that security mechanism. It is only capable in that case of using http:// and port 80. You will need to disable forced https to access the site (this is fine on the local network if every device is trusted, and only encrypted vpn service in like zerotier is used imo). This might be your problem here, especially if you are seeing both ports listed as open on the pi.


  • You would be given a safety risk warning page by your browser if you did the self signed certificate that you’d need to tell it to connect anyway, so that likely isn’t the issue. Looking at ports, how are you trying to connect to the server? If you did not assign a certificate at all, you would want to use port 80, port 443 if you did install a certificate.

    For instance, my Nextcloud is on ip 192.168.50.30 With that in mind I would be using:

    No certificate: http://192.168.50.30:80 Certificate: https://192.168.50.30:443

    Does this look like what you are typing in?

    As two additional questions, what is the output of “docker container ls” typed into the terminal? And what operating system did you install on the pi, was it raspbian?


  • At a glance your first issue is finding the correct ip address, you should only have one local ip address to access it with (inside your home network).

    To find your local ip, type “ip a” into the terminal, and look for the address under “eth0“ for a wired connection, or “wlan0” for wireless. This will allow you to connect using the ip and port while on your home network to test the connection and make sure it works right.

    After that, I highly recommend the vpn option, it will simplify connecting to it while not at home without creating security issues like setting it up with a domain. I personally use zerotier, that guide will help you get it set up on the raspberry pi. Not the last bit about a “managed ip.” That will be the address to tell your phone to connect too once you have the vpn set up on the phone as well.