Cannot Get HSBuddy App To Connect To My Server Thru MYHS

[dparks]

When testing the MyHomeSeer connection in the HSBuddy app I get an error "java.net.socket time out exception". This error is for both HomeSeer and HSBuddy
How can this be fixed?

[ewkearns]

The answer, here, is far above my pay grade, but it sounds like a network "situation." You might want to give a lot more information regarding the operating systems involved and network architecture. A network speed test might be helpful. Also, information about how "local" the connection is or isn't and what is seen with pings and what is not.

[dparks]

This started when I changed my server over to a HomeTrollerPlusG1 with a new License. I deleted the old license in MYHS and set the new as Primary. Now I cannot make the connection.

[avargaskun]

This started when I changed my server over to a HomeTrollerPlusG1 with a new License. I deleted the old license in MYHS and set the new as Primary. Now I cannot make the connection.

What I've seen in the past is that for some people, the MyHS server they get assigned is not accessible from their device for some reason. The following steps will gather more information that may help determine if you're running into the same issue:

• Make sure that the setting under Options > General > Advanced > Use MyHS Direct Route is turned on
• Go to Options > General > Feedback and tap on "Report feedback"
• Go to Options > Connection, check your connection settings and tap on "Test and Save"
• After dismissing the error dialog, tap on the paper-plane icon at the top-left of the screen
• Finish sending the report

Thanks,
Antonio

[dparks]

Followed your instructions and sent feedback. Hope this helps.

[avargaskun]

Thank you for sending those reports. Based on the logs, it looks like MyHS redirects to your server using this address: connected33.homeseer.com

It may be possible that your phone cannot access the server for some reason. Coincidentally, in most similar issues I have investigated recently it is always connected33.homeseer.com - I don't know if this is a new host/fleet behind MyHS (my own systems are behind connectedca.homeseer.com) but it appears to be problematic for some folks.

What I would suggest next is to try an app like PingTools and do a ping and a traceroute against connected33.homeseer.com from the same phone where you are having trouble connecting with HSBuddy, and check the results. It seems to be working for me:



You may want to run the same test on WiFi and on Cellular data to make sure it is not an issue specific to a connection type.

[dparks]

I resolved this issue. When I changed servers and made the new server my primary in MYHS I used the same User Name and Password.
To attempt to solve I created a new user in the server and added this new user to MYHS with same password. That solution allowed me to connect.
It has been working now without issue.

[avargaskun]

I resolved this issue. When I changed servers and made the new server my primary in MYHS I used the same User Name and Password.
To attempt to solve I created a new user in the server and added this new user to MYHS with same password. That solution allowed me to connect.
It has been working now without issue.

Thank you for following up! Not sure why that manifested as a timeout from MyHS - I'd have expected an error to come back instead. Knowing this was the root cause in your case helps, I will suggest others running into similar timeouts to try changing their MyHS username as part of the troubleshooting steps.