Hello,
Please help: I'm trying to access the portal for my hub using a Windows PC (ethernet-connected) and getting this "Hmmm...Can't reach this page". I'm using the IP address from the app.
However, I'm able to load the Portal page on my iPad using the same IP (on Wi-Fi).
Any suggestions, please?
Define portal page? As in my.hubitat.com or going straight to the ip of the hub?
What is the IP address of the hub?
What is the IP address of your PC? Open a command prompt and type ipconfig followed by the enter key.
The portal page is the IP page of the hub. I can find my hub as registered in my account but when I click the Connect to Hub button, the page with Can't reach this page pops up,
The IP address of the hub is 192.168.68.60 and the PC's is 192.168.1.67
Depending on your Mask, most likely you need a router to get to your hub. From what I understand, the Hub only talks to hosts on it's Web UI from it's same network.
These are two different networks. You need to figure out why you have two networks, and then hopefully it will be easy to consolidate down to one single network.
What type of network hardware do you have? What is the Hubitat hub connected to? What is the PC connected to?
You may have an ISP provided router and your own personal router. If so, this is the source of the two networks. Please describe in more detail your home network setup. This will allow the community to provide better solutions.
I was just going to post the same question - but reading the replies here, solved my issue. (Thanks to all that helped out) The router I have was originally set up on another network. The modem that I was trying to connect to wirelessly from desktop, was on a different one - So the desktop view on PC wasn't connecting to same network HE was on. Connect your laptop/PC via WIRED to router that your HE is connected to, if you want to see it.
That may or may not be a solution for the OP.
We haven’t heard why there are two subnets on their LAN.
There’s no reason why the hub’s WiFi connection shouldn’t work just fine if the hub can be put on the same subnet as the device from which the user is logging into the hub.
That's exactly right: recently I switched from an ISP provided router to my own TP Link Deco router and this is when the problem has started. The ISP provided modem has stayed the same: it's just the router that I've replaced. My PC is connected to the same wired network as the HE.
So, how can I consolidate these two networks?
Plug the PC into the Deco router. Turn the ISP modem into Passthrough mode. Nothing but the Deco should be plugged into the ISP modem.
As as @Slate says, change your cable modem to passthrough, everything should go to the DECO router. On top of that, anything connected to the deco router until then is also going to be double NATed...
I put the modem to the bridge mode and it didn't help: I was seeing the status of the router as inactive on the router page, (see the screenshot).
Then I connected the HE to the modem through an unmanaged switch and I now can see the IP page of the HE.
Regarding the Slate's comment, I cannot physically connect the PC into the Deco as they are on different levels of the house and the option of having only DECO connected to the ISP modem is not possible either: the house is wired to the modem and I have multiple devices connected to the modem on different levels of the house like TVs, PCs.
I'm just gonna keep the HE at a new location where I can have it directly plugged into the modem.
I'd like to assign a permanent IP to it: is it better to do it through the IPS modem settings or hubitat network settings?
This type of topology can create all kinds of headaches for you (as you’ve already discovered), some of which may be difficult or impossible to resolve, if there’s really no way for you to put the ISP modem/router into bridge mode and connect only your TP Link router to the modem.
It’s very much not a recommended way to get all your devices connected to the internet while also allowing for some devices to communicate with one another locally on your LAN.
ETA: is moving the TP link router to the ISP router’s location definitely not an option?
The proper way to do what you want to do is put your isp router into passive/bridge mode. From your main router (you will need another router) You would plug the WAN port into the isp provided unit and NOTHING else. Anything else goes to the main router as that is handling things now.
This will not work properly. You would be exposing stuff to the internet. You need a router with a switch. Now if the main portion of the deco can act as a router you're golden. Everything should run to that then it's wan port to your cable router. That would likely put everything on the same subnet and clean things up...
My router is in the bridge mode and the TP Link directly connected to the IPS modem. And the router is connected to the switch.
I've figured it out why I couldn't see the IP page of the HE (not exactly me-with help of friend): the ethernet port which the Deco was connected to was not a DHCP port and didn't provide an IP address for the router. I plugged the HE into a different port, and now I can access the IP page.
What you are suggesting is that the HE should be directly plugged into the Deco instead of into unmanaged switch which is connected to the Deco?
the question is if the deco is on a seperate subnet or vlan
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Download the Hubitat app
