I though buying the best Hub will be a painless experience, but my problem start the first day.
Any help is welcome.
Every other day (sometimes every day) when I tried to access the Main Menu I can't reach the hub it is unresponsive. What I do is I take out the power supply for 10 seconds and plug in back. This resolve the issue every time.
(My idea of automation is not to buy a smart plug to reboot the hub every morning)
My outdoor lights suppose to turn off everyday at 12am, and sometimes is 8am and still turn on, so I know the hub is unresponsive.
This is what I have:
The hub have a static IP address.
The apps that I have:
- Amazon Echo App
- Hubitat Dashboard
- IFTTT Integration
- Lutron Integrator
- Mode Manager
- Notifications
- Rule Machine
Suppor propose a soft reset, what I did, but that didnt solve the problem. At this time Iām thinking maybe is defective.
I'm new in the automatization world, I only have few Lutron Switches and 10 ST leak sensors.
First off, welcome to the Hubitat community. I hope the problems you are currently experiencing will be sorted out.
This is not a good way to reboot the hub. It can lead to database corruption. When you're unable to connect to "http://hub-ip", can you connect to "http://hub-ip:8080"? If you can, then reboot via the web interface.
A couple questions:
Is there any possibility that the static IP address that is assigned isn't sticking?
Is your HE connected to an ASUS or Netgear router? Some users have experienced an issue in this situation, and support (@bobbyD) can sort you out.
Totally agree.
Could you post the rule that runs this automation? What type of lights are they? Zigbee or Z-wave, or controlled via a Lutron switch? Does the Lutron Bridge also have a static IP?
Iām not sure if I can help you solve the underlying issue, but this is almost certainly causing additional problems, as it can cause database corruption.
I am sorry that the Soft Reset didn't solve the problem. As @marktheknife mentioned, pulling the power cord may cause database corruption in certain circumstances. If you could reach back to us at support@hubitat.com we would be more than happy to further investigate. As of right now, your hub doesn't appear to be connected to the cloud.
Sure, please check your private messages here in the community. I sent you a PM last night, but I think you may have missed it. You should have a green notification in the upper right corner. Click on it, then click on my user name to check the message.
I originally had the issue where I could ping the hub setting up a static IP reservation to my hub. Come to find out it was assigning an IP that had already been assigned by DHCP server. If you power off the hub see if you can still ping the IP address. If you can then that IP is already in use by a device on your network.
@joetlawson
I really appreciated your note. I did the test and I was getting ping back with the hub disconnected !
I change the IP to a different one, soft reset the hub, and disabled all apps and divises.
This morning I could reach the hub with no problem, I'll test a couple more days, but has sense to me that the problem was double assignation of IP (if that the right term)
I'll keep you guys posted in few days.
Regards,
Bad news guys.
This morning the hub is unresponsive again. This time I ping the hub, but was unreachable.
I was confident that the problem was the DHCP, but looks like there is other problem.
Yesterday, I did some rules and automations, everything was working fine.
I'll try to factory reset it and start all over again. But is frustrating.
Regards,
Ok, if that happens again, take a look at portal.hubitat.com just to make sure that the IP address really hasn't changed. You can see your hubs there and it will also tell you it's current IP. If that sill doesn't help than I would follow @waynespringer79 recommendation of contacting support
