“No response from hub”

At times when I open the app either from home or work, I get the message “no response from hub” and when I tell Google to turn a light on or off, Google Assistant says “It looks like the Hubitat is unavailable right now”. I have a ST hub right next to the Hubitat hub and have no issues controlling what is connected to that (IKEA shades which their remote is not supported, so to keep the WAF high, these shades have not been moved to Hubitat)

After a few minutes, both the app and voice commands work fine. It just started working a few minutes ago and now it is not responding.

I struggled with this issue for weeks and contacted Hubitat support about it. I was trying to figure out if I could live with it or not, when I finally noticed that I had a vlan subnet overlapping the local subnet my fiber modem was handing out to my local router. So there was literally two paths that incoming packets could take. I overhauled my entire network when I migrated to habitat, and I made an error I just never discovered. So I don't know what your network setup is like, but if it isn't super simple, then I would double check everything.

Also, I had LOTS and LOTS of zigbee/zwave trouble while running smartthings and hubitat at the same time. My hubs were right next to each other also. Once I got everything moved over to hubitat and shutdown the smartthings hub, all of my mesh issues went away. I know many are running this scenarios successfully, but that was my experience.

1 Like

@scottie.holden Thanks for the informative reply. I only have one router and one cable modem, but the ST hub is right next to the ST hub for convenience. No issues noted with ZigBee or Z-Wave devices.
Something else I noticed - the IP of the HE hub toggles between .114 and .115, so when I open the app, I can’t see any dashboards until i run hub discovery. Just tried to turn on a bulb with GH and got the message it couldn’t connect to the Hubitat. Opening the app, all dashboards are there and the devices respond. When another GH command was sent, the light turned on.

@bobbles When I was using Amcrest cameras for my home security I could specify their static IP in their app and never had to set it in the router. I will investigate that. Thanks. If the IP changes, I would assume that is why GH can’t talk to it.
Will report back once I have time to try and not breaking what works. :grimacing:

Most people reserve the address of their hub on their router so that whatever happens, power cut etc., the router will always assign the same address to the HE hub.

couldn't imagine doing it any other way!

been getting this a lot lately, myself. I just keep trying until I get a response, but the amount of effort required each time to succeed seems to be random, as does when it happens.

Hmm. My router is a Tenda AC15 AC1900 model. I drilled into each menu to see if there was a way to reserve an IP. The Tenda website says the DHCP/static IP setting is on the Main Menu but it isn’t there. Sent an email and waiting for a reply.

Looks like it may be under System Settings|DHCP Reservation Dhcp Reservation - Tenda AC18 User Manual [Page 100] | ManualsLib

@thebearmay

Not there. I have the AC15 and you are referencing the AC18. Could it be this router does not support reserved IPs?

Could be... On most routers I've found it under either the DHCP menu or the Devices menu

So I got the No response message last night and this is what I saw on my HUB free memory. Like clockwork for the past couple of weeks. A hub reboot is needed every 3-4 days.

The AC15 does not support DHCP lease reservation. Honestly the 1st router I've ever seen that doesn't.

1 Like

Thank you. Time for a new router. :weary:

1 Like

Bought a Tenda AC25 AC2100 router. Hubitat is on a reserved IP

MANY THANKS to those who helped!

3 Likes

Anything look out of the ordinary when you look at hub stats?

http://hubitat.local/hub/enableStats (Run this to start stat collection and let it collect for about 5 minutes)
http://hubitat.local/hub/stats (Run this after the 5 minutes has elapsed to view the stats)
http://hubitat.local/hub/disableStats (Run this to stop stat collection)

You can use these links to track down the apps and devices by putting the id's from stats
http://hubitat.local/installedapp/configure/APPIDHERE
http://hubitat.local/device/edit/DEVICEIDHERE

I don't think anything glaring obvious.

Device Stats enabled: false
Device stats start time: 1604418474662
Device stats total run time: 320854
device id 2297 runcount 5 total runtime 71 average run time 14.2
device id 377 runcount 11 total runtime 75 average run time 6.8181818182
device id 723 runcount 7 total runtime 53 average run time 7.5714285714
device id 1780 runcount 3 total runtime 14 average run time 4.6666666667
device id 1909 runcount 4 total runtime 20 average run time 5
device id 371 runcount 8 total runtime 40 average run time 5
device id 336 runcount 10 total runtime 114 average run time 11.4
device id 1814 runcount 10 total runtime 54 average run time 5.4
device id 1811 runcount 11 total runtime 57 average run time 5.1818181818
device id 1778 runcount 2 total runtime 9 average run time 4.5
device id 732 runcount 7 total runtime 33 average run time 4.7142857143
device id 1572 runcount 16 total runtime 641 average run time 40.0625
device id 337 runcount 7 total runtime 45 average run time 6.4285714286
device id 372 runcount 5 total runtime 28 average run time 5.6
device id 344 runcount 5 total runtime 28 average run time 5.6
device id 1942 runcount 2 total runtime 12 average run time 6
device id 1816 runcount 11 total runtime 52 average run time 4.7272727273
device id 352 runcount 3 total runtime 12 average run time 4
device id 1813 runcount 5 total runtime 26 average run time 5.2
device id 2552 runcount 1 total runtime 56 average run time 56
device id 4981 runcount 2 total runtime 26 average run time 13
device id 1571 runcount 16 total runtime 637 average run time 39.8125
device id 2679 runcount 3 total runtime 32 average run time 10.6666666667
device id 3093 runcount 2 total runtime 542 average run time 271
device id 3285 runcount 2 total runtime 10 average run time 5
device id 731 runcount 1 total runtime 6 average run time 6
device id 2981 runcount 5 total runtime 22 average run time 4.4
device id 2231 runcount 1 total runtime 4 average run time 4
device id 3062 runcount 9 total runtime 152 average run time 16.8888888889
device id 1299 runcount 11 total runtime 183 average run time 16.6363636364
device id 1815 runcount 3 total runtime 15 average run time 5
device id 12 runcount 1 total runtime 4 average run time 4
device id 724 runcount 1 total runtime 8 average run time 8
device id 394 runcount 1 total runtime 11 average run time 11
device id 2038 runcount 1 total runtime 79 average run time 79
device id 725 runcount 1 total runtime 7 average run time 7
device id 376 runcount 3 total runtime 34 average run time 11.3333333333
device id 730 runcount 1 total runtime 12 average run time 12
device id 1457 runcount 1 total runtime 820 average run time 820
device id 728 runcount 1 total runtime 29 average run time 29
device id 1819 runcount 2 total runtime 101 average run time 50.5
device id 719 runcount 3 total runtime 15 average run time 5
device id 4469 runcount 1 total runtime 8 average run time 8
device id 1779 runcount 1 total runtime 5 average run time 5
device id 1809 runcount 1 total runtime 3 average run time 3
device id 726 runcount 1 total runtime 11 average run time 11
device id 4150 runcount 1 total runtime 10 average run time 10
device id 942 runcount 1 total runtime 7 average run time 7
device id 268 runcount 1 total runtime 6 average run time 6
device id 3893 runcount 3 total runtime 139 average run time 46.3333333333
device id 729 runcount 1 total runtime 11 average run time 11
device id 588 runcount 2 total runtime 29 average run time 14.5
device id 3413 runcount 2 total runtime 592 average run time 296
device id 733 runcount 1 total runtime 7 average run time 7
device id 4501 runcount 1 total runtime 4 average run time 4
device id 335 runcount 3 total runtime 16 average run time 5.3333333333
device id 4853 runcount 2 total runtime 25 average run time 12.5
device id 1818 runcount 1 total runtime 30 average run time 30
device id 373 runcount 2 total runtime 13 average run time 6.5
device id 2 runcount 1 total runtime 5 average run time 5
device id 398 runcount 1 total runtime 3 average run time 3
device id 696 runcount 1 total runtime 8 average run time 8
device id 2203 runcount 1 total runtime 3 average run time 3
device id 1821 runcount 2 total runtime 58 average run time 29
App Stats enabled: false
App stats start time: 1604418474665
App stats total run time: 320855
app id 816 runcount 68 total runtime 10626 average run time 156.2647058824
app id 910 runcount 33 total runtime 1802 average run time 54.6060606061
app id 5684 runcount 101 total runtime 1773 average run time 17.5544554455
app id 4755 runcount 1 total runtime 24 average run time 24
app id 3 runcount 8 total runtime 167 average run time 20.875
app id 2330 runcount 1 total runtime 199 average run time 199
app id 912 runcount 1 total runtime 25 average run time 25
app id 3247 runcount 1 total runtime 16 average run time 16
app id 1911 runcount 1 total runtime 43 average run time 43
app id 3599 runcount 3 total runtime 718 average run time 239.3333333333
app id 1261 runcount 2 total runtime 2233 average run time 1116.5
app id 4694 runcount 1 total runtime 65 average run time 65
app id 4367 runcount 2 total runtime 231 average run time 115.5
app id 3791 runcount 7 total runtime 562 average run time 80.2857142857
app id 3347 runcount 4 total runtime 332 average run time 83
app id 1168 runcount 4 total runtime 764 average run time 191

Not the cause of your issues but the run time on this app is terrible.

Try taking a longer sample and see if something starts to stand out.

That's the Echobee Integration app. Cloud dependant so should be ok I guess.

1 Like

Predictable at least.

Yea, you running 223 or 224? Using the new nest integration with image capture?

Download the Hubitat app