Looking for some help. I can no longer access my HE hub from my phone over wifi but I still can access the cloud version. I can also access it from the Lan on my laptop. I was able to access it all the time. Then got a new router/wifi. I was able to access it after hooking that all up. Then it just stopped. I tried the IP search, the Mac search and neither can find it. Its definitely on the same wifi. I also have my Lutron and cameras on the wired connection. And have access to them with no problem, through wifi and Lan. Does anyone have any suggestions? I'm using an android phone and have a Net Gear Night Hawk R7000 router. Thank you for any help.
Hmm can you access your hub via WiFi using your laptop ?
Maybe take a look here re setting IP reservation etc.
Did you replace the old router, or add the Night Hawk behind the existing ISP router?
I just tried accessing on my laptop and it worked fine. Unplugged the ethernet and everything. So it's obviously narrowed down to my phone.
1 Like
I replaced it. I have the internet converter box then the Net Gear router. Previously I had Belkin.
Are you trying to access it via the app or browsers (which)? If not can you try access it via a browser on the phone. Since it seem to be the phone what's the make and model?
Trying to access it through the browser on the phone.[quote="TechMedX, post:6, topic:54015, full:true"]
Since it seem to be the phone what's the make and model?
[/quote]
It's a Samsung Galaxy Note9
Now, I did double check and noticed my Mac address number i was inputting was wrong. When I corrected it I was able to find my hub. But it won't locate it automatically like it use to. And when I put the static IP in it does not find it.
So, to make things worse, my scheduled changes (rule machine) are not happening. And when mentioned earlier about the Mac address allowing me in, that still works but it takes me to a black screen on my phone. I still can access everything through my computer. Also any commands I had through Alexa no longer work. They say Device is unresponsive. Is there a way to "factory reset" HE? I guess I'll have to re-enter everything.
Morning,
It's very interesting to read about your issues; I have experienced the same. I have a Netgear D7000v2 router, which is essentially the same as yours.
For a long time I've struggled with wifi access from my phone (a Huawei View 20) ; wired connection from my desktop is fine, but wifi access from my phone is flaky at best.
However, last week I spotted two rules that were causing high resource utilisation due to being badly written (repeating actions that caused multiple instances of the same rule firing, which sometimes killed my zigbee network). I've since fixed them, and i've not had any wifi issues over the past 7 days or so.
It's perhaps too early to say that they're related, but i'm quietly hopeful - and would fit with your experiences.
So, I'm not 'AS' crazy as I thought I was. Maybe I'll start by removing and reinstalling some rules. My garage door, I know, would notify me twice for each action. Thank you for the information.
Does anyone else have the Cloud Connection is Unavailable notification?
So, I have seen in my logs that my Rachio irrigation was causing a Warn notice and Alexa has an Error notice. I've deleted Rachio from HE and removed Alexa from HE. I can't seem to re-connect Alexa back again. The Alexa app says she is unable to link the account. Im sure it's something to do with the wifi.
I've also noticed that my Zooz plug was giving 4 notices like every 10 minutes. I took that out.
My phone still has the same issues.
Ok... here is the latest. I switched my Netgear back to the Belkin and everything works better, not perfect, but much better. The one thing I noticed is now my HE hub ip address says its xxx.xxx.2.5. Netgear only does xxx.xxx.1.(1-100). But Belkin does xxx.xxx.2.(1-100). I know for a fact the hub was on .1.4 cause I set a static IP for it. Then it changed. Is it strange that the hub is picking the IP and not the router? The .1.4 was on Netgear when I first started setting it up. Then changed to .2.5. Then when I plugged it into Belkin it worked then changed it back to Netgear, then back to Belkin to check the IP address. Still .2.5.
Alright, after trying a few things and not trying the obvious, I have things up and running for now. Things I've tried... rebooting the hub, switching routers, rebooting the routers, factory reset of my Netgear, writing here and on the community page of Netgear, turning on and off different rules, pulling my hair out (even more), yelling at Alexa, and countless other things.
The fix... changing the Static IP Address to another number. (Sounds simple, just never thought of it).
My original IP address was xxx.xxx.1.4
When I had issues the IP Address said xxx.xxx.2.5. And even though the static said xxx.xxx.1.4 the hub read xxx.xxx.2.5. My problem was I was continuing to try and make it xxx.xxx.1.4.
Solution - changed it to xxx.xxx.1.24 and everything is fine.
For now...
Great to hear things are stable at least now.
Yep, With “the static said xxx.xxx.1.4 the hub read xxx.xxx.2.5 “ that’s a pretty good indication that something was screwy with your network.
Unless your subnet settings supported it, they were never going to communicate.
Ain’t Hindsight a wonderful thing ?
Anyways, it sounds like you’re sorted out now.
Yes, thank you. And I try to put a solution, if I have one, at the end in case someone else finds a similar issue.
1 Like
