I had problems connecting wirelessly a few days ago with my new hub. Today I reset it again and installed the new version of the firmware and it now works fine. I didn’t make any changes to my ASUS router so the problem was definitely the old firmware. Thanks for the speedy firmware revision.
I managed to get the “magic green light” although in the meanwhile I have replaced my MiFi router to an Ac1350 so I could create ethernet connection to the hub.
We’d be interested in hearing about more about the specific setup that didn’t work to see if there is anything we can do on our end to make the hub work well on as many networks as possible. As you can imagine, testing against every possible piece of networking equipment in various configurations is… basically impossible.
I have to admit I did not try to activate my hub through WiFi after you updated the Firmware.
I got tired and bought a new 4G LTE Router which gave me ethernet connection possibility. I only have mobil network and my previous router only provided wireless connection (this why I bought V3 Hub)
Anyhow I CAN move to next step to move on with this journey.
For what it’s worth, I will add my experiences/current state:
Ver 3/2018 hub currently offline for about 5 dys after I performed an IDE reboot. Hub is 2000 miles away in a second home. Hub had been hardwired successfully for a few weeks and then switched without issues to wifi (to strengthen zigbee network ) help ticket is outstanding.
Asus router with merlin software. My suspicion prior to reading this thread was loss of wifi connection to hub. I can still control a wifi camera at the residence so it is not an Internet or router wifi issue.
? Until I can have a friend power cycle the hub ( I will be adding a wifi power plug next trip out) does the hub need to be hardwired to the router for the firmware update ?
Hi @Madisonriver, I can’t say for sure why the hub did not come back online after the IDE reboot but I would guess that you ended up hitting the Wi-Fi issue after the reboot (the problem could be experienced intermittently). The symptoms definitely seem consistent. If that is the case, the latest update (0.24.22) would definitely be beneficial.
The hub should get the firmware update so long as it is able to connect to the network again. This might be as simple as rebooting and letting it connect to Wi-Fi again (if the problem is intermittent) or it may need to be hardwired if the problem is now being hit consistently. Green LED indicates that the hub is connected to the cloud and should be in a state where it can download and apply the update.
In addition to the fixes for the initial Wi-Fi connection this release also includes additional automated recovery steps that should increase overall reliability if something goes sideways; it’s no silver bullet but it is something that should increase reliability overall.
Thanks a ton, appreciate the response. The house is outside of West Yellowstone, and I am in NY haha. So I have a friend who is going to stop by any day now and I instructed him to power cycle the hub – drink a beer – and I would let him know if he had to reconnect via Ethernet. And then drink a few more beers.
I did not add, in the initial setup, which I did hardwired NY – moved the hub (and router) to Montana after we closed on the place, and has been relatively trouble free except my learning experiences with mesh networking… I added a half dozen Iris plugs (both z and zigbee portions of those plugs) etc and was doing well until this reboot issue. And moved the hub > started using wifi , to eleviate possible zigbee interference with the router.
Happy New Year in advance,
Appreciate the follow through!
I will attempt to let you know how it goes if my friend gets to the home – been snowing a bit out west.
Power cycled hub yesterday and wifi connection to hub restablished immediately. Checked hub firmware this morning and it is ver. 24.00022
All devices online and reporting normally