Jump to content
Sign in to follow this  
Automate

Connect to device

Recommended Posts

Automate

I like the "Connect" to device function that's available in the portal and phone apps.  A few suggestions for improvements.

 

  1. Instead of connecting to https://proxy.domotz.co/ it would be great if you could connect with https://mydevicename.proxy.domotz.co/  You could have a wildcard DNS that resolves any "mydevicename" back to the same domotz proxy server.  This will do two thing.  First, some of my devices require a login.  My browser currently gets confused with all the different logins because they all have the same URL.  If each device has a different URL then the browser will be able to store the appropriate username/password pair for each device URL.  Second, with a unique URL to each device you could save favorites in your browser or anywhere that would take you to a directly to a specific device.
  2. Some of my devices don't have a built-in web server but instead use a cloud service.  For instance I can't connect directly to my Nest Thermostat device, instead I connect to https://home.nest.com  It would be great if the user could manually enter this URL and domotz would associate it with the device.  Then when I try to connect to the device it actually sends my browser to the configured URL.
  3. Similarly, some devices host multiple "sites" on the same TCP port (usually 80)  for instance you might use \home to go to one site and \admin to go to another.  It would be nice if these could also be associated with the device like favorites so you could go directly to a specific site.
Edited by Automate

Share this post


Link to post
Share on other sites
Giancarlo

Good suggestions. We will took care of them putting in our backlog of activities. Not sure though when those could be realized.

 

Just one note, regarding second part of suggestion 1: we can't make that.

12 hours ago, Automate said:

Second, with a unique URL to each device you could save favorites in your browser or anywhere that would take you to a directly to a specific device.

 

Note that in order to make the process very safe and secure, we don't have the connection to your end-device always on, but the connection is created only FOR YOU, and only when you click on the button from the App or from the WebApp. Only the user which have the capability to create that connection (in this case you and whoever you will decide to let manage your agent - see collaboration from the WebApp) can create the connection to your end device (and will have the "rights" to use the path created to arrive to your device).

 

For instance, if you create an end connection to your Device "192.168.1.1" we might immagine to have an url like:

"https://192_168_1_1.proxy.domotz.com"but only you, at the time you have created the connection, will be able to use that URL. I.e. if you open a different browser and you paste that URL in the new browser, you will not have the "rights" to connect to it, just because you are not recognized as the one which established the connection.

 

Lately, all the connections outside your home to reach your end device are over HTTPS (secure TLS protocol). Of course if your end device has an http portal (non https) the communication internal to your home is not on that protocol. In this way, if through the "Domotz Connect" functionality (we friendly call it Click2Enter), you insert passwords on a portal (let's say from an Internet Cafe'), you can rely on the HTTPS protocol that your password will not been sniffed by anybody.

 

I hope you appreciate both of these two security feature.

Share this post


Link to post
Share on other sites
Giancarlo
On 12/2/2015, 5:21:25, Automate said:

Instead of connecting to https://proxy.domotz.co/ it would be great if you could connect with https://mydevicename.proxy.domotz.co/  You could have a wildcard DNS that resolves any "mydevicename" back to the same domotz proxy server.  This will do two thing.  First, some of my devices require a login.  My browser currently gets confused with all the different logins because they all have the same URL.  If each device has a different URL then the browser will be able to store the appropriate username/password pair for each device URL.  

 

This have been implemented in our backend: every device/port gets a different and unique ID.

 

Share this post


Link to post
Share on other sites
Automate
5 hours ago, Giancarlo said:

 

This have been implemented in our backend: every device/port gets a different and unique ID.

 

Thanks for adding this feature so quickly

Share this post


Link to post
Share on other sites
Giancarlo
3 hours ago, Automate said:

Thanks for adding this feature so quickly

 

We try to do our best for our users, and the functionality you suggested it's really a killing one! Thank you for suggesting it. This beta phase is very important to get feedback but also suggestions as this one.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...