There is some confusion on my end, I want to remove my IoT devices like all my KASA powerstrips, plugs, and LED lightstrips, LiFX bulbs, rachio, wiz bulbs off my network and migrate to a stand alone hub that never reaches out to the WAN, freeing up my network.
After getting the app for Kasa, scanning and finding my 62 devices, I see no way in which to migrate them to the hub, and it seems I always need to be connected to the LAN.
Ok no problem, I will go out and by ANOTHER appliance/ wifi device to do just this, but wait! I have a crappy T-mobile Nokia router which has little to none managed options, cant set static IP's. My T-mobile router is feeding an older Orbi mesh system, and when this is configured this way I lose a lot of management capability. Anyhow when I remove the T mobile router connection from Orbi my LAN is still broadcasting, of course now nothing will connect to it because it has no WAN connection. All of the hubitat devices disappear as well (in the phone app & browser connection)
After some testing, If I disconnect the WAN from the LAN which I am abled to do in my network, all of the hubitat is dead in the water. This is not what is promised by hubitat, so someone please tell me where I completely misunderstood sales jargon, or if this is just not possible. Thank You
First thing to understand is that while the hub is designed to operate without connecting to the internet, if the devices you pick to use with it require an internet connection to work the hub can’t change that. So, rule number one, only select devices that you know will work locally - usually these are Zwave+ or Zigbee, some Matter and a very few WiFi; do your research before buying. Rule number two, while the hub can operate completely on its own without a LAN connection, if you want to manually operate devices through it or use dashboards it will need a LAN connection for you to reach it.
Hey I appreciate your response. Thank you " thebearmay "
I had suspected this possibly to be the case, but was clicking my heals for magic.
I also was wondering, now if I have to go buy 62 new appliances to do this automation work, for which I want to work on an antiquated 5 yr old mesh system that never connects to WAN. Will Zwave+ or Zigbee be the end all be all solution? I am not new to integration, and I understand I am trying to do things on the very cheap avoiding control4, extron, and Crestron. I do wish hubitat to be my solution, for the same reasons everyone else here in this community does as well. I am assuming to get this to work on LAN only I need to set a static IP up in " the hubitat " itself with multiple DNS? If there is no WAN I can not understand why DNS is valid.
Also curious how folks still connect to the LAN, from their device like tablets, phones, and laptops when there is no WAN for DNS to resolve. I am not a network engineer, but know enough to be dangerous and stupid. Thank You
You can still use a local DNS to configure local server names.... E.g. your HE and alike... You can also setup a local network with reserved ip addresses in a router.
My T-mobile router has ZERO management capability, and when I use the ORBI mesh behind the T-mobile router I lose all ability again to manage and set these fields up. I would need a managed device in the middle of tmobile router and Orbi
I'm guessing a basic router or even a diy solution shouldn't be too expensive or difficult to configure, but I'm not the guy to recommend what to do in that space.
Yeah copy. This was the plan anyhow, migrate IoT stuff away from T-mobile, small client with two nics to DNS filter and work as a firewall, and then I realise at the end of the day I can just get another t mobile router and WAN connection cheaper than my ideas. thank you for your time.
My post is marked as "solution" ? Interesting. I have some wiz products only that seem to integrate with hubitat off WAN, and all the other call home products technically do not work with hubitat without WAN as promised. All good. I wanted this to be a solution, and it is not unless I re-appliance the whole setup, which goes against the word integrate/ in integration.
If anyone knows how to jailbreak kasa products to reload a Unix/ Linux ARM/ OS I'm all ears. Thanks again for those who helped.
Yes, using the KASA app inside of hubitat, this did work ( all my KASA ) is legacy. but NONE of it works without WAN connection which was my sole reason to purchase hubitat. I guess (my ignorance) I was thinking that hubitat would become the NEW LAN for IoT devices only. I guess it is for Zwave+ or Zigbee. Meh all good. I realized one day all of it would be a complete waste of money, and consume my bandwidth. I will try to build a client that acts as Kasa's Call home server and responds back with the actual control. Once again I was hoping hubitat could do this. Thanks for your responses.
I have several Kasa devices, all of which are controlled locally on the LAN via Hubitat. My Kasa devices are actually blocked from accessing the WAN (internet) by firewall rules. So the Kasa mobile app cannot control them.
I find your description of your home network setup to be very confusing and incomplete. I wish you could provide a network diagram/description with IP addresses assigned on the LAN.
For instance, here's my setup:
Dual-WAN:
AT&T fiber (WAN address 45.x.x.x) - fiber gateway is in bridge mode
T-Mobile 5G internet (CGNAT address 192.168.12.x)
Router:
Unifi Cloud Gateway Max (192.168.0.1)
LAN 192.168.0.0/24
Hubitat (192.168.0.6) - can access the WAN for cloud integrations (Alexa & GPS)
KASA Plugs are all in the 192.168.0.0/24 subnet (WAN access blocked)
Static IP addresses / DHCP reservation. Highly recommended that these be used for smooth operation. If IP address changes, the device will die until you run configure. (Next release will address this better). I tested configure today and it does reconnect to a device with a changed IP address.
Hey all, thank you. Yes, I read ALL the instructions. Yes, I disconnected cloud binding. Yes, I went through all the settings. Yes, I'm able to write scripts for automation. And yes, I've already boxed this up. I'm just going to return it. I already have these capabilities. without hubitat.
To the person that wanted all my I. P assignments no thanks. I appreciate you trying to help. Go ahead and close me out. No more responses to this. I have no use for this anymore.
I appreciate you all for your time. this is not a viable solution for me, not even close. Thank you
I all depends on the devices that you have, and what protocols they speak - Sounds like others are commenting around the KASA devices - I do know that HE has and supports local access to LIFX bulbs on a LAN only configuration (as I have 6 of those bulbs, and they work fine when the WAN is down, the local LIFX phone app, obviously does not work in that case).
By design, Matter, Z-Wave, and Zigbee devices are going to work locally (LAN or other local wireless protocols, thread, etc.). - As for devices on you LAN/Wifi - It's going to be very device dependant on what has a local API, and what does not. - I can't comment on Wiz or Rachio - But without some more specifics around model #'s, it's hard to say which of your 62 devices will work locally, and which will not.
While here is no "magic" network access - But you can fairly cheaply setup a second redundant/failover WAN connection via a different provider (DSL, Cable Model, Wireless, Starlink, etc.) if WAN access is required for some of your devices. -
Personally, I worry more about privacy and companies going out of business and/or orphaning devices. YMMV
Agreed - I have Kasa plugs (for energy monitoring) and all my lamps have LIFX bulbs. They're all controlled locally. And actually, I'm sufficiently paranoid that a firmware update from TP-Link or LIFX will remove LAN access that I firewall all of them from WAN access.
I continue to find the OP's description of their setup to be incomplete and confusing. They have a CGNAT setup (T-Mobile/Nokia). That gateway is also a router and cannot be put into bridge mode; I know - I use T-Mobile for my backup internet source. They have the gateway connected to an Orbi Mesh - it remains very unclear what LAN subnets each of these advertises, and what their devices are connected to.
Adding to this, @dwmind is apparently of the opinion that disclosing their (non-routable) LAN addresses might make them vulnerable to attack; at least that's my interpretation of this statement:
There's no "one platform fits all" automation solution. Clearly, this platform and community were not the right choice for @dwmind.
