I do not want to take your time since the issue is not imperative at the moment, but I am not sure what I could change on my end.
—App Version is latest and I have redownloaded multiple times from store. (And yes I am using the new, “Mostly Green” version of the App).
—I have tried running the beta version.
—My network has absolutely no custom rules to prevent inter communication and I actually have no VLANs (well; obviously just one) setup in this particular network at the moment….I know the security implications of that but this is a custom network for specific usage and not my normal home network
—Hubitat Hub is hardwired
—iPhone Settings allow Local Device and Background App Refresh
I am not particularly knowledgeably in the Hubitat arena, but I am trained in network management and topology so I really do not think I am missing something unless there is some obscure setting in the Hubitat App.
I am completely open—and actually welcome correction!—to being told I am doing something wrong…..I just cannot see what that might be.
But again @jtp10181 , I know you troubleshoot a lot so if you have other priorities feel free to push this way down the list
I would start by checking these two IPs, this is one of the ways the app determines the local vs cloud and if they are being detected incorrectly it could be throwing it off.
The hub IP should be coming from (and match) the hub IP listed in the hub details at my.hubitat.com > Registered hubs.
There was something up with the way the app was requesting local network permission on iOS for a while, which explained the cloud/local problem some people were seeing.
But like Jeff mentioned that was resolved, and you’ve confirmed local access is applied anyway.
Are you able to see and control devices from the devices or dashboards tabs while the app is in cloud mode?
Hub IP in Hubitat App does show the same as registered.
X.X.X.010 is Hub and iPhone X.X.X.131, both on same subnet.
In the App I can control devices so it does appear to be working (presumably through the cloud). When I attempt to add a device it says that you can do not that in iCloud mode.
Is it a Class C network (like 192.168.x.x / 255.255.255.0) ?
If so, then no idea what the issue might be. All I know is the app uses the hub IP and first does some logic to determine if it might be able to reach the hub locally based on the IP's, which yours should pass. Then from there it tries to reach the hub somehow, not sure if it does a ping or just goes right to the http port, or might even use the websocket or something.
Hmm... do you possibly have SSL only enabled on your hub? That could possibly break the apps local connection feature.
Well, I rarely think of network classes anymore, but technically it is a Class B network (172.16.1.X), although it has a subnet mask of 255.255.255.0 so the IP range is limited anyway.
Not sure why that would make a difference as they are both definitely on the same subnet. I can access (and login) to the Hub from a web browser on my phone so it definitely can reach/see the Hub from my phone.
SSL is not enabled although I do have Hub Login Security enabled.
It shouldn't make a difference, but I do not know the exact details of how they are determining the local connection with different LAN setups. There was some screwy stuff going on at one point, but like I said I thought it was all resolved by now.
It sounds like you have a typical flat home network on a /24 so it should in theory cause no issues. I just wanted to make sure you did not have something out of the ordinary like a /23 or higher.
@jtp10181 Understood. I appreciate the brainstorming.
I do find it weird, but luckily I have no plans to use the App at the moment as long as I can add Wave LR on Desktop (which did work perfectly yesterday—>and was actually easy enough). If the App is useful I may want to use an iPad at some point so maybe I will put some brain power towards this, but I thought I would check with you all in case it was still a bug or something (....or maybe something I should report).
I appreciate all the help! For now, my biggest problem was resolved.
Thought I would update to say that as of last night the HE App all of a sudden was working correctly and connected locally instead of through the cloud.
I made no changes on either my network or the phone, so I have no idea what the issue was. Funny enough, I was actually opening the App to log out before deleting….and I noticed for the first time it said “local”!
So if anybody has a similar issue on their iPhone/phone, restarting the Hub—not sure if restarting had anything to do with it…BUT it is the only variable I really cannot test as to whether or not it made a difference—and maybe just giving it several hours/a day.
You can not add a LR z-wave device as LR without using smartstart which is only available in the app. If you add it via the desktop interface, it pairs as standard z-wave
As @hydro311 mentioned, with the full DSK you can add ZWave LR devices through the desktop web UI.
—>You can get the full DSK by reading and copying the QR code on your phone as @velvetfoot mentioned, although in my case with the Zen15, the string returned by the QR code had extra numerals padding on the front and end, so you would have to know how to properly extract/decipher the actual DSK and the PIN. A lot of devices have the DSK written somewhere in the original box of the device so you can also look there, BUT not all do.
—>It was actually a bit accidental that I figured out you could add an LR device on the desktop interface of HE.....so I am not sure if this is actually documented (/formally explained somewhere), but these were the steps I took as I did not find it formally mentioned. You need to have Smart Start Manager already installed as others have mentioned:
Go to the Apps —> Smart Start Manager —> Edit/Add SmartStart Entries
— From here, you would need to select "Add New" and then fill in all the appropriate fields including the full DSK which will start with the devices PIN.
**FINALLY, you have to switch boot mode from the default 'SmartStart Mesh' to 'SmartStart LR'
For whatever reason the first time I added the device it toggled back to SmartStart Mesh and I wound up having to remove the device and re-add.
NOTE: I have attached a picture of my device (at least as of June 2025 that is what it looks like). You can confirm that the device is actually LR by looking at the node (if I understand correctly normal ZWave will only be two characters....apologies as I read that somewhere but with all my jumping back and forth not exactly sure who to thank!) but also I see the last field which reads 'Long Rang' so everything seems in order.
