Connected2.homeseer.com not working

[Guest]

So this surely explain what happened with alexa https://forums.homeseer.com/forum/ho...-does-not-work

[zwolfpack]

reference closed thread https://forums.homeseer.com/forum/ho...y-home-network

Several folks were reporting issues over past day. This wasn't universal. According to my monitoring script, running on two systems, I've been connected (thru connected33) since 3/30 @8:28 AM PDT. (I see that both did a quick reconnect this morning @ 8:04 AM PDT, but that was so quick that the 30 second event poll missed it). I used Alexa during that time as well.

Not sure what the reasoning is to close that new thread so quickly ... maybe the forum moderators are trying to "flatten the curve?" ...

[Guest]

... maybe the forum moderators are trying to "flatten the curve?" ...

ROFL ...

Whatever the case, after being up for a grand total of 14 hours, MyHS is down for me again! Went down 2 hours ago.

[Guest]

MyHS (backend) back up 20 minutes ago.

[Guest]

What's up with the MyHS backend? Seems unstable to me. Been down and up 4 times in the last 3 hours. Playing havoc with my Google Home. One minute it works. The next there's no homeseer.

[integlikewhoa]

rjh Rich this problem is back.

[rjh]

Which problem, can you be more specific?

rjh Rich this problem is back.

[integlikewhoa]

rjh connected2 doesn't work for phlocation and imperihome apps on any of my devices for multiple HS3 installs. If I use connected22 it works.

[zwolfpack]

rjh connected2 doesn't work for phlocation and imperihome apps on any of my devices for multiple HS3 installs. If I use connected22 it works.

Something odd with you DNS. connected2 is currently aliased to connected22 (meaning they both resolve to the same IP).

$ nslookup connected2.homeseer.com
Server:         192.168.1.1
Address:        192.168.1.1#53

Non-authoritative answer:
connected2.homeseer.com canonical name = connected3.trafficmanager.net.
connected3.trafficmanager.net   canonical name = connected22.homeseer.com.
[COLOR=#FF0000]Name:   connected22.homeseer.com
Address: 45.76.21.192[/COLOR]

What result do you get for this command (works on Windows or Linux) ?

[integlikewhoa]

So I have to houses in different states. One is currently using connected33 and one is using connected22.

If I use those two for each of the houses they work. But normally I use connected2 and it works. Right now neither house works with connected2.

[integlikewhoa]

What result do you get for this command (works on Windows or Linux) ?

C:\Windows\system32>nslookup connected2.homeseer.com
Server: ubnt
Address: 192.168.1.1

Non-authoritative answer:
Name: connected33.homeseer.com
Address: 45.77.216.233
Aliases: connected2.homeseer.com
connected3.trafficmanager.net

and the other house I

get C:\WINDOWS\system32>nslookup connected2.homeseer.com
Server: Router
Address: 192.168.1.1

Non-authoritative answer:
Name: connected22.homeseer.com
Address: 45.76.21.192
Aliases: connected2.homeseer.com
connected3.trafficmanager.net

[Guest]

do not enter $

[integlikewhoa]

I run unifi controllers at both houses. I went and rebooted both HS3 servers without a fix.
I rebooted both routers and seems I have fixed the issue. Problem is I don't know why I have this problem.

Can someone explain in easy to understand lingo of my issue and how i prevent it from happening again.

Thanks,
Jim

[zwolfpack]

I monitor my MyHS connection with the script posted earlier in this thread and save the results with the Device History plugin. connected2 hasn't pointed to connected33 since 4/17 @12:11PM PST.

Your first house appears to have a weird DNS caching issue.

[rjh]

Right now we have moved to load sharing for our servers. The load sharing is using the Azure traffic manager to direct traffic to the server that is the closest to your location. Your HS system will connect to one of our servers and stay connected unless the server goes down or it detects that there is a better server. When you try to connect to your home system using a JSON request you need to use the URL https://connected2.homeseer.com. Sounds like you are using that. If you happen to connect to a server that your HS system is NOT connected to, it detects this and issues a redirect to the correct server.

So a couple of things:

The system issuing the request needs to handle DNS OK in that the TTL (timeout) is very short, so the resolved IP address could change at any time. I do know that some of the connected systems are not honoring the DNS changes. I can tell this as some systems were not switching to the correct system when we changed the DNS.

Second, your system that is issuing the request needs to handle a redirect. I don't see why it wouldn't but it's something to check.

You can figure out which system your HS system is connected to by pinging connected2.homeseer.com, then one of the actual servers (connected22.homeseer.com and connected33.homeseer.com). See which IP matches one of the servers.

If you think your system is honoring the DNS and the redirect, let me know the URL you are using and I can check the logs and see if the request is getting dropped, and for what reason. (the parameters are important)