Not able to make home-assistant-remote work about remote_homeassistant HOT 23 CLOSED

Hello,

this looks actually correct.
The remote instances don't need to have remote_homeassistant installed (clarified that in the instructions now), but it shouldn't hurt either.
Do you see any error messages in "Developer Tools - Logs" in the web UI of the primary instance?

from remote_homeassistant.

Hi, Lukas! Sorry it took so much to answer. I had to restart the remote host.

This is what is says in the log:

Log Details (ERROR)
Logger: custom_components.remote_homeassistant
Source: custom_components/remote_homeassistant/init.py:176
First occurred: 6:03:34 PM (144 occurrences)
Last logged: 6:28:10 PM

Could not connect to ws://[REMOTE_HOST_IP_via_ZEROTIER]:8123/api/websocket, retry in 10 seconds...

Any ideas what it means? BTW, I still can connect to it via my extra pc (which is the 3rd device in the ZeroTier virtual network, but also in the same physical network with the main HA instance. First is the main HA instance on a Proxmox, Second is the remote HA instance on a Raspberry 3B+)

from remote_homeassistant.

Hi Lukas! Did you have a chance to look into this? Do you know what I should do?

Thank you so much!

from remote_homeassistant.

I just tested the setup on the same network. I modified the IP address in the configuration.yaml to reflect the changes. Now I have:

remote_homeassistant:
  instances:
  - host: 192.168.1.101
    port: 8123
    access_token: !secret ggs_same_network_access_token
    entity_prefix: "ggs_"

I still get the error:

Logger: custom_components.remote_homeassistant
Source: custom_components/remote_homeassistant/init.py:176
First occurred: 3:50:10 PM (32 occurrences)
Last logged: 3:55:20 PM

Could not connect to ws://192.168.1.101:8123/api/websocket, retry in 10 seconds...

I also tried using - host: https://192.168.1.101. Still nothing

Please help! :(

PS: I am running master HA on Proxmox on a pc and the slave HA on a Raspberry Pi 3b

from remote_homeassistant.

I followed the user Krash' advice on the Home Assistant in this forum post and disabled DuckDNS settings of the slave instance by commenting out the code in configuration.yaml necessary for DuckDNS to function. And thus Remote Home Assistant worked and I had access from the master instance.

If I add the code again, WebSocket stops working and it seems I get 2 errors asociated with this addon:

1st Error
Logger: custom_components.remote_homeassistant
Source: custom_components/remote_homeassistant/init.py:229
First occurred: 12:25:23 PM (1 occurrences)
Last logged: 12:25:23 PM

2nd Error
Logger: custom_components.remote_homeassistant
Source: custom_components/remote_homeassistant/init.py:176
First occurred: 12:25:23 PM (33 occurrences)
Last logged: 12:32:07 PM

Could not connect to ws://10.242.0.97:8123/api/websocket, retry in 10 seconds..
websocket connection is closing

Do you know if there is a solution to using a secured connection via DuckDNS and using home-assistant-remote as well?
Thank you so much!

from remote_homeassistant.

I am using doing this via duckdns from a different location.

Here's the snippet from configuration.yaml

remote_homeassistant:
instances:

• host: remotehostname.duckdns.org
  port: 8123
  secure: true
  access_token: !secret master_access

from remote_homeassistant.

Sorry, but there is nothing much I can do about the

Could not connect to ws://10.242.0.97:8123/api/websocket, retry in 10 seconds

errors. Master HA on Proxmox on a pc and the slave HA on a Raspberry Pi 3b is by the way exactly the same setup as mine.

Unfortunately I'm not familiar with DuckDNS, but as there seems to be no network connectivity possible between your two instances so I don't suspect DNS is the problem here.

Are you able to connect to the web interface of HA ( http://10.242.0.97:8123 ) from another PC in the same network? Are master and slave in the same network (seems to be the case from your description in the first post)? Can you e.g. ping the Raspberry from your Proxmox VM?
If not, is there any local firewall on the Raspberry blocking access?

from remote_homeassistant.

Thank you both for all your input. I have a problem with my port forwarding on the remote router and I cannot test with DuckDNS or any other Dynamic DNS provider like no-ip.com yet. Like I said before I only tested with ZeroTier One. And as ZeroTier One is used to simulate a local network even though your devices are on different physical networks, I have local network issues. Like previously mentioned, on a local network, the remote host cannot be secured. It needs to be unsecured in order for home-assistant-remote to work. This is the problem.

So to recapitulate, if you would like to simulate my situation you can try puting the master and the slave on the same network and once you secure the slave, you cannot access it anymore. Is this normal for everyone or just a bug for some of us? And if first case, can you update it to make it work? :)

Otherwise on the forums, a user there said that if you connect to the remote / slave host via internet, it will work even if it is secured.

Thank you much!

from remote_homeassistant.

Hi Lukas,

I would just like to confirm I am having the same issues as mentioned above by @ygreq. Sounds like I also have the same setup as both of you. NUC at home running Proxmox and remote RPi's, all connected with ZeroTier. I am able to ping in both directions (ie from home to remote and vice versa). I have five remote devices, only one remote device is sending data. I have tried all manor of disabling remote devices and re-enabling them with no success. This system was working for me previously with a number of websocket errors on the master instance. Interestingly, a sensor is created "sensor.remote_connection<ZT_address>_8123". This sensor says it is connected but sending no data. I intermittently have the error
"Could not connect to ws://<ZT_address>:8123/api/websocket, retry in 10 seconds..." More usually now though, there are no errors in the log at all.

Any ideas? Has anyone else managed to overcome this problem?

from remote_homeassistant.

I should add also, I am able to connect to the web interface of all remote devices.

from remote_homeassistant.

Try to use DuckDNS instead of ZeroTier and see if that works. DIsable ZeroTier on all devices while doing that just to be sure.

Unfortunately I could not use DuckDNS as I have some problems with the remote router so I cannot set it up last time I tried.

Let me know if that works.

from remote_homeassistant.

I'm in the same position as you @ygreq. My remote modem / router is behind a CGNAT'ed mobile network. ZeroTier finds the instance no problem but DuckDNS does not. I've had it working fine with ZT. For some reason it has just stopped.

from remote_homeassistant.

You said remoteaccess worked for you with ZeroTier but only recently stopped working? If this is the case, when did it stop working?

from remote_homeassistant.

One of the instances still is working. The other four instances died maybe three days ago. It definitely works with ZT.

from remote_homeassistant.

@ygreq one of my other instances has popped back up tonight. I now have 2 of 5 connected. Don't know what happened to make it connect.

from remote_homeassistant.

Anyone else suffering from this non-parsing of data - try rebooting the "Host System" from "Supervisor" -> "System"
Worked for me. Thanks to @lukas-hetzenecker. Your addon makes a world of IoT possible.

from remote_homeassistant.

@Automan69 So you say it works for you using ZeroTier? And now it works without any problems thanks to the rebooting thing? That is great news! Did you do anything special to make it work with ZeroTier?

from remote_homeassistant.

Hi @Automan69 ! I just tried again to reconnect via ZeroTier. Still the same problem. May I ask that you share the steps you did? Maybe also paste the code you used in HA configuration.yaml? For example did you use https:// before the ip address of your remote instance? Did you use different ports like 8123, 81234 for each instance?

Thank you so much!

from remote_homeassistant.

ZT.txt

I've used the same port each time.

I've not locked down the remote instance as that instance has no ports open and is on a double nat'ed mobile network in Australia.

from remote_homeassistant.

@ygreq , it is also possible you have not setup your zt access properly. You need to tick the box of each zt instance in the zt interface. I'm just assuming you have done that. All instances also need to be on the same zt network.

from remote_homeassistant.

Is this issue still relevant? Seems to be more of a network connection issue rather than problem with the component?

from remote_homeassistant.

I did not see the replies. I will check asap. Probably after the holidays!!

Thank you, Automan69!!

from remote_homeassistant.

Closing this now as I don't think this is a problem with this component. Feel free to open it again if you disagree.

from remote_homeassistant.