Have not head from MyHS in over 3 minutes error message

[Krumpy]

3 minutes for an automated home is an eternity! I would request that appropriate actions are taken if HS has not heard from MyHS within 30 seconds are at least some user definable time period. I can understand that folks with limited bandwidth or data quota wouldn't want it that frequent. But, seriously, 3 minutes is a very long time.

Was demoing HomeSeer to a perspective customer and they chuckled with a sarcastic "smart house huh!" when HomeSeer didn't appropriately respond from an Alexa command. Checked log:

Apr-22 9:23:47 PM

Warning

Have not heard from MyHS in over 3 minutes, disconnecting for re-connection.

[Uncle Michael]

When I get that error it is usually a network issue and affects more than MyHS. You could ping Google with a recurring event as frequently as you want, but the sticking point is what action to take when there isn't an immediate response. I find that waiting a minute or two is almost always the easiest course of action.

[Krumpy]

No network issue at all on my end. I know this because I monitor the connection... Only HomeSeer unable to reach MyHs. I bet that that one of the MyHs nodes went dead and failed over.

’The bottom line is that we need more intelligence with this technology. We have an automation system that is not very intelligent in terms of MyHS. There needs to be more of a continuous handshake that is configurable with active monitoring and resilience in terms of reestablishing connection. I also would like to see it trigger a HS event such that I can be immediately notified when a issue occurs.

Otherwise, why do we have an automation system? The technology works for us, not us for it!

[Uncle Michael]

I understand - up to a point - but for my system, the automation is entirely local. I do not rely on MyHS expect to connect to my system remotely, That is typically only to "check in". What is your application that requires a robust connection?

[simplextech]

3 minutes for an automated home is an eternity! I would request that appropriate actions are taken if HS has not heard from MyHS within 30 seconds are at least some user definable time period. I can understand that folks with limited bandwidth or data quota wouldn't want it that frequent. But, seriously, 3 minutes is a very long time.

Was demoing HomeSeer to a perspective customer and they chuckled with a sarcastic "smart house huh!" when HomeSeer didn't appropriately respond from an Alexa command. Checked log:

Apr-22 9:23:47 PM

Warning

Have not heard from MyHS in over 3 minutes, disconnecting for re-connection.

It wasn't just you. I confirmed from my two systems last night at this time when I saw your post. I couldn't connect either. For me I do have a GPS system that post data through MyHS so this is important for me. I'm also having MyHS user/permissions issues accessing my development system. But that's another issue/post

[drhtmal]

3 minutes for an automated home is an eternity! I would request that appropriate actions are taken if HS has not heard from MyHS within 30 seconds are at least some user definable time period. I can understand that folks with limited bandwidth or data quota wouldn't want it that frequent. But, seriously, 3 minutes is a very long time.
...

I am curious as to what level of "up time" you expect from your home automation systems?

[Krumpy]

HomeSeer is a great product and is very reliable. HomeSeer Technologies is a great vendor in this space. Like I told Mark at CES a few years ago, "think about how many of these companies where around 20 years ago". MyHS is still a technology that is a little weak in terms of reliability and resiliency --- in my opinion based on my observation and what people post here.

I have been in the industry for a long time and well know what is possible and what is not possible. I do not look at these systems as a hobby, but rather from a professional and business minded perspective. If one can not depend on this stuff, then what good is it? Seems to me that HomeSeer Technologies is in control of this aspect of their software and, therefore, should check to see that it can phone home more than every 3 minutes (or whatever time frame it is). In addition, this is an automation system with a event trigger engine. Would it not be helpful to be alerted when a fault has occurred, and also have this system take necessary action to reestablish connectivity? I am confident that changes can be implemented such that this would occur more frequently than 3+ minutes.

All I am asking for is a little more transparency and necessary capabilities so that one can tailor the necessary functionality to their needs. Auto reconnect after 3 minute connectivity failure is a very long time when a perspective user is attempting to initiate voice control to this system. Feedback - This is what HomeSeer Technologies used to do back in the day 20 years ago. It would take feedback and update as needed. Been using this software a very long time.

In terms of up time requirements I have. Well, I figure that we should ask for improvements when HomeSeer Technologies is empowered to make the necessary changes. I certainly am not asking (or requiring them) to control the Internet such that network outages do not occur. But, creating a better mousetrap in terms of bi-directional handshaking of their technology for MyHS should not be the end of the world. I for one figure that we should request and demand high-availability & application resiliency such that we can depend on these technologies more. Now I fully understand that prices may go up as HST creates a better and more reliable mousetrap in terms of MyHS. This is fine for me from a professional and business minded perspective. My clients demand for this stuff to work. They don't care about the technological challenges involved in making this work.