I have a C7, and just switched internet service, which came with a new router, which I switched over to today. Yes, I've rebooted the hub and uplugged/replugged it.
I have a room lighting rule that turns on my outside lights at sunset. I got home, and some of the lights were not on. I went to the rule, and hit the activate button, and the lights came on.
In Rule machine, I have. a rule that when I come home, it turns on a couple lights inside the house. One of them was not on. In this case, my Apple Homekit hub detects my phone, and uses a virtual switch to tell Hubitat that I'm either home or away. When I leave, it turns the switch on, and when I come home, it. turns the switch off. So the various rules that i have set up look at that switch setting to know if I'm home or not.
On the app on my phone, I can go to the device list, and change the mode of the hub from home to away, but when I touch the dashboard button at the bottom, it can't find the dashboard.
How are the lights connected to Hubitat? Zigbee/z-wave or WiFi/matter?
A router upgrade shouldn’t impact how the hub communicates with Z devices, but WiFi/matter devices could be affected since they’re also on the IP network controlled by the router.
What do the hub logs say around the time these devices apparently missed commands?
Everything I have is either Zigbee or Z-wave, and in the case of the light that didn't come on, it's Z-wave. I didn't think to look at the log, but looking at it now, it's saying something about excessive load on the hub. Looking at it, when it says Button 1 was pushed, that's when I fond they were off, and used the wall switch (which is the actual Z-wav device). Then when it says it was set to 99%, I was usign the Room Lighting app. Dimming to 35% is the normal Room Lighting app doing its thing as it should.
I just did some more digging, and. found others that were having the same excessive load warning on their logs, and rebooting the hub took care of it, so maybe that's why I stopped showing that in mine after unplugging my hub trying to sort some things out.
Is the new subnet the same as the old? Did you have any reservations? If so did you recreate those reservations on the new router? Is the wifi password and SSID the same as the old router?
New SSID and password. As for your other questions, I have no idea what any of that means, but I'm going to say no because my old ISP had to replace my router a couple years ago, and I just plugged the Hubitat into the new router and took of running.
The part of the Hubitat apps not working seems to be resolved. I had rebooted it a couple times and found out about the reset button on the bottom.
However, my phone app still has an issue. If phone is connected to the wifi when I open the Hubitat app, and I go to the dashboard, it won't load. I just get the spinning circle. But if I switch off wifi and just go cell data, it loads up with no problem.
The big issues here...
Make your SSID and PW the same as your old...
Your subnet is lets say 192.168.1.x. Make sure it matches what ever the old one is.
Put a reservation in your router that makes your hubitat the same ip as it was on the old router.
All this has changed so unless you know networking, things are going to have problems finding things on your network in some cases because they're looking for them in a specific place.
If you simply unplugged your hub, and didn't turn it off first and get the red LED and then unplug it, you can sometimes cause corruption in the hub's database.
Just to remove the potential issues it would probably be helpful if you did a reboot of your hub and chose the advanced options on the reboot dialog and chose the database rebuild.
After the reboot to clear and restart your Zigbee and Z-Wave radios, you would want to shut down your hub. After you see the red LED on the hub pull the power, wait about 30 seconds and plug the hub in again.
Those two steps will ensure you're starting with a clean database and restarted radios.
