I think you may be confusing what VPN service is needed. You don't need one of the paid VPN service that anonymize you browsing. You need to setup VPN access into you home network. A lot of modern routers have this capability baked in. You can also set up a Rpi to be your VPN server.
I looked into that as well. Having all my mobile/laptop traffic go thru a VPN server set at my home means that all the traffic (when I am not home) gets sent to my home router over the measly 10mbps uplink that my very expensive comcast connection provides (there are no other providers in my area. Yayyy for capitalism).
I do not port forward. To access my hub from WAN I use teamviewer. If I access a dashboard I have WAN ticked and use a pin.
I have your exact limitation and I simply do not leave my VPN connected when I don't need it. I connect when I need access to my home network...ie to administer HE, look at dashboards or look at my ip cams. I use Tasker (android app) to make this as simple as possible. I have an icon that when tapped will connect to my home VPN and open the HE home page. Another icon that connects and opens tinycam with my camera dashboard....etc. I also have a disconnect icon. It all really seamless for me.
1 Like
I do it a similar way... Connect to my OpenVPN when I need to do home stuff, turn it off when done... Took about 5 minutes to setup since my router already supported OpenVPN.
1 Like
stephack, JasonJoel: I think your approaches are quite reasonable (and maybe even slightly safer) as well. But, I had to device something which works seamlessly for my wife as well as other guests visiting the home. I use SPT (android app) to keep a persistent tunnel open which meant the dashboard always worked before
I am not using ssh. I am just grabbing the web link from the dashboard and using it.
You can always enable use legacy dashboards and go back or roll back firmware
I think you do not have to route all traffic through an openVPN.. just the subnet or ip you want. See "route-nopull" for the client which overrides forwarding all traffic.
Something like this:
route-nopull
route [Local HE Hub IP Address] 255.255.255.255
Which would set up a route just to the HE. I have not done this so cannot verify it works but you might want to look into it..
So here you can see I am connected directly to the hub website, looking at the dashboard and clocking in certain lights will result in the hourglass icon.
You are pulling that link from the dashboard section not the dashboard app config.. My url looks something like this:
http://10.10.3.93/apps/api/13/dashboard/404?access_token=xxxxxxxxxxxxxxx&local=true
Don't know if that makes a difference or not.
If it stays on an hourglass after clicking that means the device did not return a changed state. Confirm by doing the same command in the hub UI device details.
Otherwise the connection to the hub websocket was disconnected and didn't reconnect. There will be some improvement to this failover to polling in the next release.
1 Like
The switch is changing state, the events are being logged but the driver state is not updating.
- deviceType: 17495
- inClusters: 0x26,0x2B,0x2C,0x27,0x73,0x70,0x86,0x72
- deviceId: 12340
- manufacturer: 335
I am using the generic zwave dimmer driver.
I don't believe I was having issues on the old dashboard. Have the zwave dimmer drivers changed?
What is the device?
I need to take off the face plate to see what brand it is, but it is a zwave dimmer switch.
Sounds like an older non-updating pre lutron patent expired dimmer. Try the z-wave poller app to get it to poll for updates.
Looks like the latest platform update fixed the issue for me and it works as before (actually better as I like dashboard v2 better). Thanks so much Patrick and hubitat team!
Hi Patrick...I'm new to the forum and to Hubitat. I just received my hub yesterday and I'm configuring my network devices. All of my GE and Cree network (Zigbee) bulbs work flawlessly. I don't have the background in "Z-Wave" that others have. I am also experiencing the "hourglass" problem when using the Dashboard only...the light changes state but the hourglass remains. If I refresh the URL, the dashboard shows the change and the hourglass disappears. If I got directly to the device from the device menu It works as expected.
Unfortunately Patrick no longer works at Hubitat... So he may/may not get that message.
May want to direct it to support@hubutat.com ...
