New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connect jarvis over Internet / Cloud (Fernzugriff) #71
Comments
I really like to idea of a connection outside the local network and also of a monetization. Obviously the first goal is to create a sufficient user basis to make the previous effort worth. |
What's the current status of "fernzugriff" feature? Or is there any existent way to open Jarvis from an app or via internet ? |
I use the intigrated VPN from my FritzBox. I have created a bookmark for Jarvis at my iPhone and added the bookmark to the iPhone destkop. If i have activated the VPN at my phone, i can connect to Jarvis with this bookmark. |
same as I do, but I thought there should be a integrated version? thats just a workaround... |
In my opinion this is the only way to do it if you care about your network and security. Edit: |
I currently use vis and I have it exposued to the itnernet via reverseProxy and secured with a client cert. I was about to evaluate to switch to something more modern and had a look at jarvis. However, that issue kills it for me. |
after a while of usage, I am fine with the VPN version. I am using jarvis very rarely via remote. So that absolutely ok. |
Let me take a wild stab: The reverse proxy is running in your local net behind your router? |
You can configure Jarvis with reverse proxy on port 8400. That shouldn't be a problem? |
Currently jarvis can only be used inside the LAN oder via VPN. The possibility to use jarvis outside of the local network would be a big improvement. Users with an iobroker.pro license could then use jarvis everywhere.
@Zefau I'm not sure about your plans for earning money with jarvis, but I see potential for monetize this feature. I would definatelly pay for it. What do you think?
The text was updated successfully, but these errors were encountered: