I have three hubs, and have wanted to move them, and all other IOT devices, over to a specific VLAN dedicated to IOT only. I have one of these hubs connected to a hub (unmanagaed switch) that connects to all VLANs, and when I try to set a static IP, save, and reboot, it NEVER works. This is not what happens with any of my other devices that allow a static IP. They all just take it, and off we go.
So... What's wrong here? Does static IP just not work on Hubitat?
You are trying to use an unmanaged switch to connect devices to a specific vlan.. You have to tag the vlans, so you will need a managed switch.
VLANs require "managed" switches to pass the VLAN tags across the network. If you place an unmanaged switch in the middle, the unmanaged switch (depending on the Manufacturer) usually does not pass the tags and just drops them. As far as the static IP, I prefer to manage ALL of my static IP's in the router DHCP server by making a static reservation using the device MAC address in the DHCP reservation table and manage it that way. That keeps all of my static assignments in one place and the router assigns the appropriate IP address to the device. If you change devices you can manage that at the router. If you decide to change IP schemes its all in the router.
All of the above is correct. To directly address this question:
Yes, it works fine. Although I will point out that it does not support changing the subnet mask, so it is fixed at 255.255.255.0 (as it explicitly states on the network configuration screen on the hub).
Well, that makes sense. I updated the title to reflect this.
I think I might just end up using a wifi dongle, as the closest AP allows any of the SSIDs and associated VLANS to be reached. Frankly, this lack of built-in wifi is proving to be a minor nuisance, as the building where this particular hub is located is connected via ethernet back to the main router, with the small, unmanaged switch inside the building, where the hub is the only thing on that IOT VLAN. I knew there was a reason I moved away from ethernet for anything (else) where wifi could be used... Just so much easier... I'd pay a few bucks more for a future version that included wifi.
Anyway, thanks. A bit boneheaded in my thinking there.
Wifi IS supported, you just need to purchase the proper adapter. They are fairly inexpensive, they seem to be about $15 or so. There is a list of supported Wifi devices in the Settings tab, Networking menu.
I personally prefer ethernet, and wouldn't want to pay more for a feature I don't use. So I am glad this is an option that can be used if someone needs it.
Yes, I know it's supported. I just want it all inside the shell. I'll end up buying a dongle, I think.
Mostly, I'm just whining. If it weren't me, I'd just ignore it. The world will go on just fine with me having to buy a dongle.
Or you can get a 5 port managed switch for $25-$35.
I'm sure you know this, but I like to point out the obvious sometimes. If you go WiFi whatever SSID you connect to still has to be on the right VLAN too - no different than an Ethernet port.
Yes, but I need it to be POE in this location, for another device (the AP, a Pepwave One Mini). For that matter, I could probably just leave it on the existing VLAN and not have a big worry. But with all the cybersecurity threats that now exist, I'm trying to segregate various things a bit better, including all IOT devices.
Yeah, POE is a bit more ($60 for a cheap tplink 5 port). Sometimes a cheap managed switch + a couple of POE injectors is still cheaper, but you're right in thinking that wifi may easier in that case.
Again, assuming you have/can make a wifi SSID on your AP on the proper VLAN. But I'll point out that if the AP is connected to that same unmanaged switch (which it sounds like it is based on your POE comment above), you STILL can't do VLANs even if that AP supports them (as the unmanaged switch is the limiting factor). Everything going through an unmanaged switch will (typically) be assigned to whatever VLAN the 1st port on the 1st managed switch it connects to makes it (typically 1 if nothing else is configured).
In the end you may still need to upgrade the unmanaged switch, or just leave everything on one VLAN with or without multiple subnets.
You can have more than one subnet on a single VLAN... Many IT people traditionally think in terms of 1 VLAN = 1 subnet because it keeps things simple, but in reality that is a coincidence, not a requirement as VLANs are a Layer 2 construct - not Layer 3. Although I will say that setting up multiple subnets in a single VLAN on some network devices is rather a pain as you need secondary/virtual IPs on the VLAN config.
For example on cisco devices multiple subnets on a single VLAN looks something like this (a perfectly valid [albeit atypical] config for long term use):
interface Vlan2
ip address 192.168.3.1 255.255.255.0
ip address 192.168.4.1 255.255.255.0 secondary
Good luck in any case!
Download the Hubitat app
