In an attempt to solve some Z-Wave range problems I moved my C7 and in the process had to cycle power on my router. Of course it handled out a different IP so I reduced the router DHCP range and assigned a static to the C7 outside of that range. I can access the C7 and use the Dashboard on my PC, but the iPhone dashboard no longer works. When I open Dashboard on the iPhone app I get "no response from hub". If I go to settings and Select Hub, it briefly flashes something about multiple hubs found and then starts "loading mobile devices" which times out in error.
Can you setup a DHCP reservation on your router instead?
Alternatively, set this list of name servers on the hub: “9.9.9.9, 8.8.8.8, 1.1.1.1”.
2 Likes
Ok, my original DHCP IP was 192.168.1.12. After I cycled power on the router it changed to 192.168.1.3. I then changed the router DHCP range to 2-128 and set the C7 to 192.168.1.130 static. I can reach the router by typing 192.168.1.130 into my browser. My iPhone app has stopped working. When I "find hubs" it show my hub at 192.168.1.3 and none of the advanced discovery tools do anything. If I click on "connect to hub" (192.168.1.3) I get "this site can't be reached".
Why does this have to be so confusing?
I really don't understand the previous suggestions.
What should my DNS be set to and where do I set it?
In your router's DHCP settings set a reservation for the hub. This will use the hub's MAC address (on the bottom of the hub) and you simply assign an ip then set the hub to DHCP. If you want to set it to 192.168.1.130, you have to set DNS within the static settings. Set the primary to 1.1.1.1 and the second to 8.8.8.8. This will get you through to hubitat's servers so the "connect to hub" will work...
1 Like
Well I don't fully understand it, but it's working now. I left the router DHCP range at 2-128 and reserved 3 for the C7 using the MAC address. I switched the C7 back to DHCP and set the DNS as suggested. I just went back to look at it again and its now has 192.168.1.1 listed in addition to the 1.1.1.1,8.8.8.8. Is that a problem?
Now to get back to my Z-Wave range problems.
Nope. It's fine.
Well once you set the hub to DHCP your dns is automatically taken care of, you don't need to set it. Only when you set a static ip on the hub do you need to do the DNS. But this won't hurt. The reason things work now is that the DNS can point the hub where it needs to go.
2 Likes
As long as router/gateway provides DNS services, no. Also, it's third in the list, so the other two servers will probably take care of name resolution before it gets a chance.
1 Like
Well, since yesterday's changes my router (WNDR4500v2) has locked up twice. That has never happened prior to connecting the HE. I've cleared the DNS fields, but if they're not even in play while DHCP I wouldn't think that will make any difference. Those 192.168.1.1 settings seem to fill in automatically.
That's weird. What happens if you fill in 8.8.8.8, 8.8.4.4, 1.1.1.1, 1.0.0.1, 9.9.9.9 instead of 192.168.1.1 and save? Does 192.168.1.1 come back? The example DNS servers string is good to use all around, BTW.
I just realized that when I relocated the HE yesterday and "cleaned up" the wiring associated with my PC, printer, router, HE, etc. I inadvertently used the switched half of the outlet to power the HE and the router. So when I would leave the den and turn off the lights those devices would power down and my wife would start bitching about the TV not working. Then I would go in the den to start troubleshooting not knowing that the router was now booting back up. Hopefully I'm past that now and everything will remain stable.
1 Like
Everything seems to be working now DHCP with the reserved address in the router so I'm not going to tempt fate and mess around with it any further if I don't need to.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
