-
Notifications
You must be signed in to change notification settings - Fork 14
Homesee failed to setup #73
Comments
Do you have the ASCII interface enabled on the HS4 Setup->Network tab? Make sure that "Enable Control using ASCII Commands" is checked under "Remote Control Settings" and make sure the port is set to 11000. |
Hmm. Can you ping your HS4 machine from HA? Try 'telnet 192.168.1.5 11000' and hit ENTER a couple of times. You should get 'error, bad format', since you aren't sending a proper ASCII command to the interface. |
Can you provide more details about your HA and HS4 installations? Are you running in VMs or on bare hardware? Is HS4 on Windows or Linux? Since you can reach your HS4 system with "ping" I'm suspecting a firewall on the hS4 side of the connection is blocking the telnet from the integration. |
It's on a Win 10 PC bare. I just realized i have Symantec Endpoint on this PC I'm uninstalling it now and try again. Will report back shortly. |
symantec gone, firewall off, delete and setup again and same result |
Sorry, I'm fresh out of ideas. It's usually either a connectivity issue or a firewall. Ping confirmed connectivity and you turned off the firewall. Possibly a netmask issue since ping uses ICMP and telnet uses TCP. |
just wanted to update... somehow everything seems to synced up overnight. Issue is no longer present and i can now control HS with HA |
Trying to setup HS4 for the first time but it always get an error connecting to ASCII
Failed to connect to HomeSeer ASCII connection at 192.168.1.5:11000, aborting entry setup.
9:23:41 AM – (ERROR) HomeSeer (custom integration) - message first occurred at 7:35:53 AM and shows up 3 times
Error opening connection to HomeSeer ASCII at 192.168.1.5:11000: [Errno 110] Connect call failed ('192.168.1.5', 11000)
9:23:16 AM – (ERROR) /usr/local/lib/python3.9/site-packages/libhomeseer/listener.py - message first occurred at 7:35:28 AM and shows up 5 times
The text was updated successfully, but these errors were encountered: