I was referring specifically to controlling your desktop via a phone.
Please don't take my post as a "my solution is better than yours" type post. I was trying to define the differences between the 2 approaches for others that might be trying to decide on how to remotely access their HE hubs. I have used quite a few Remote Desktop applications over the years and think they are a great solution. Once I started using VPN, I realized it was the best solution for me and my needs.
Donāt flatter yourself I could care less about whoās is better I was clearing up the fact that whether your using Remote Desktop on mobile or pc there is no scrolling problems. I was simply correcting your false statement.
Ok...I was unaware that mobile phones were now able to capture a high resolution desktops in a way that did not require "zoom and scroll". I stand corrected.
Me too... Which is why I use VPN instead of RDP/teamviewer/chrome remote desktop... 4K desktop... 2K phone screen.... Either way even if I size to fit, everything is WAY too small for me to see the desktop without zooming/scrolling.
To each their own I donāt need any rasberryās, strawberries, or watermelons hahaha I just log in and get what I need done! Itās not like Iām performing surgery I just need it to check a rule or make a quick change when Iām away from home.
OpenVPN is built into my internet security UTM (Untangle), so only took me about 10s to setup. Ok maybe 3m including time to copy the OpenVPN config to my phone.
But I agree - each to their own. Whatever works for you in a way you can live with is the right answer for you.
The nice thing also about VPN access is on my phone I can run apps as if I connected directly to my LAN. Or access HE right in my Chrome browser on the phone or any other device's web portal for that matter. If you want total control over your devices through a secure connection its the way to go.
Also, a new, updated version of Hubitat Dashboard is in the works which should address many of the current shortcomings, like lack of a dedicated thermostat tile.
My recipe for exposing the Hubitat admin interface on the internet uses Dataplicity, a Raspberry Pi, and the Nginx web server acting as a proxy. This scheme has the advantage (or the security risk, depending on who you ask) that the admin interface is accessible like a normal web site on the internet without requiring a vpn client.
Here is the recipe:
Connect a Raspberry Pi (or comparable linux machine) to the same local network that the Hubitat is connected to.
On the Raspberry Pi, install Dataplicity (run the python bootstrapping installer from the url provided on the Dataplicity setup page).
On the Raspberry Pi, install Nginx (sudo apt-get install nginx).
Enable the Dataplicity wormhole mode (this is done on the Dataplicity device page).
Modify the nginx config file (/etc/nginx/sites-enabled/default) to look like this:
server {
listen 80 default_server;
listen [::]:80 default_server;
root /var/www/html;
index index.html index.htm index.nginx-debian.html;
server_name _;
location / {
#------------------------------------------------------------------
#| The below configuration assumes that the hubitat hub's web
#| interface is reachable on the local network at
#| "http(s)://hubitat" . Your configuration might vary. For
#| instance, if you have configured your hubitat hub to have a
#| static ip address and are not relying on dns, then you could
#| replace "hubitat" below with the ip address of your hubitat
#| hub.
#------------------------------------------------------------------
proxy_pass http://hubitat:80;
proxy_redirect default;
proxy_redirect http://hubitat/ /;
proxy_redirect https://hubitat/ /;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}
}
Once this is done, the Hubitat's admin interface should be accessible on the web at the wormhole URL provided by Dataplicity.