I have an Aeotec V3_HUB firmware 000.056.00009
Connected via Wifi.
For the past 3 days it has been constantly going offline (solid blue led) and then back online resulting in a ton of notifications and annoyances. At least 20 times in the last 24hrs if not more.
I figured it would work itself out after a bit and came on here searching, expecting there to be some sort of major server issue happening. I do not see any recent posts about this so I guess its just me? Prior to this it has worked fine for at least a month since I got it.
Nothing has changed, it is in the same location, same Wifi. I rebooted the router in case that was part of the issue but it has not stopped. It is not disconnecting from the Wifi, it is just losing the cloud connection.
It only has 4 z-wave devices connected to it at the moment so nothing major going on that should be stressing it out.
With WiFi there always something that you can’t control: Noise from other wifi networks, and apliances.
Are you able to test if the connection to the cloud is stable through ETH physical port?
Can you be sure the SmartThings hub is correctly connected to your WiFi network?
If you are comfortable configuring your WiFi network you could try ‘fixing’ the IP address of your SmartThings via your router administration screen. That worked for me a few years ago (albeit with a wired V2 SmartThings hub. My symptom was that, while my SmartThings hub was showing a blue LED, I looked at DHCP leases on my router’s administration page and noticed that the SmartThings hub had a spurious IP address that was outside my WiFi network address range.
After leaving the hub on ethernet for 2 weeks it stayed connected the whole time.
Having it further away from my test area was a hassle, pairing was not working well. So I moved it back today on Wifi again, and now its working fine again (same as it was for a month before I made this post).
Back to the cloud connection disconnecting and reconnecting periodically.
I have a two laptops, mobile phone, and two Hubitat hubs in this same room. None of those get disconnected from anything. I am often connected to one of the laptops via RDP for long periods of time and it stays connected. All devices show full signal strength.
These 3 devices are all in the same room on the same 2.4ghz Wifi. Only difference is STv3 hub is connected via a different SSID. You can see the ST hub has a better signal strength than the Hubitat hub.
Those hubs are in the same room as each other, in my office. There is no ethernet in here.
When I relocated the hub to be next to the router the connection was stable but pairing devices was not working as well. It is about 30ft from my office with 3 stud/sheetrock walls in between. Since I am using this hub for testing I am removing and re-adding devices from my office as needed to test things.
I could understand there being an issue if my Wifi was weak in this room, but it clearly is not. Everything else works fine.
I can do this, but why should it matter? The hub has a DHCP IP address and it is on a 24hr lease, so nothing is changing once it has the IP. The IP will stay the same as long as the hub stays connected. Also the cloud connection is going to the internet, not my local LAN so the internal LAN IP should not matter.
All I can say is fixing the IP address of my SmartThings hub solved a cyclic disconnection problem I had a few years ago. My router DHCP function has a pin/fix IP facility.
My V2 hub was connected to ethernet but I found (via my router) that it had a spurious IP address (way outside my IP address range) during the brief disconnection events.
Shit happens sometimes. Write down the IP address of your hub and compare it to the one it has after a week.
Do you want it to work or do you want to put as many obstacles in the way as possible?
Use Ethernet even if it means that you have to run a cable, because your WiFi connection is obviously not stable enough. Use fixed/reserved IP addresses for stuff that is… fixed, stationary. It’s just common sense and best practice.
Set a fixed IP in DHCP on the router, rebooted router and then the hub so it would get a new IP lease, now I just get a flashing blue light constantly. I will have to mess with it later and figure out how to get it reconnected again.
Good thing I only use for device/driver testing and not to run my house.
Finally got it reconnected last night. Originally when I set it up there was a warning somewhere to not connect it to a shared SSID Wifi, so I connected it to my IoT SSID which is 2.4Ghz only. It did work fine on there for a month with no issues, so possibly an update to the hub platform messed something up. Anyway, this time I ignored that warning and connected it to my main SSID. I did not realize this thing has 5Ghz support which is how it connected. Also using the fixed IP I set on the router now as well.
So far its staying connected again. Seems like it is happier on the 5Ghz for some reason even though the 2.4Ghz gets a stronger signal. Maybe it was just not playing nice with my routers 2.4ghz radio.
I do know what I am doing and talking about. Not to be “that guy” but I have a technical degree in computer networking from years ago. May not remember how to configure a cisco enterprise switch from command line anymore but I would still say I am advanced.
This is from the router, might be able to get something more definitive from command line. I have never had this be wrong. The Wireless “log” breaks it down between which SSID and radio the devices are on and this hub is clearly on the 5GHZ
