My Notes on remote access for UI6

Developer's Corner General Dev Discussions
#46

bringing some life back to this post, I am trying to get this working for UI7, but had a few questions:

I obtained the JSON for the AuthToken & AuthSigToken, but I am not sure I have the right response. my mustache template:

{{Identity}}~{{IdentitySignature}}~{{Server_Account}}

returns over 3,000 bytes. I know that the notes mentioned ‘long’ strings, but is that what I should expect?

I’m trying to build a web hook from which I can get an updated “SessionToken” to make calls to Vera from a micro controller, but handling all of that… I don’t know if my MCU will be able to handle that and actually perform some functions.

Or… are my Identity and IdentitySignature actually static, and could I just refresh the SessionToken with the same call (I can then offload that call to my web hook tool)?

I believe I understand the process to get this working, I just don’t really know a lot about this kind of message signing enough to get a flavor if I can get this all on my MCU.

#47

Although this is excellent work, I’m still baffled that not a single official piece of documentation has been published surrounding these changes… or am I just missing them?

#48

I received a document from them … but I have never seen it published.
It was a good document describing their API … but was still lacking … which is why I posted my notes.

#49

I know this is old, but I’ve also created a test python script to show how to do authentication and run requests remotely.

#50

Hope someone s still watching this thread…

I have got remote access working… except I seem to be getting quite a bit of failures from te AUTH servers… I’m not sure if this is a temporary issue, or just me…

https://us-autha.mios.com/autha/auth/username/?SHA1Password=886649f0d6116c97910877ef9ba7304cfbd9e340&PK_Oem=1

is the url I’m caling… it’s dynamic, so the above is a composed url.
I orignially used autha11, then tried autha12 servers… then decided to use the failoverurl (think its’ probably better anyway)…

What’s’ happening is that randomly, I get success, but a failure on the next call… the failure is allways the same:

ERROR: Connection to server

I am not sure what this even means… The only theory I have is that somehow this is a error, because of to many calls to the server?

I have been testing my app quite a bit, and this seemed to have cropped up now…

Any insight would be super…

Thx T

#51

You should always use the URL with the trailing numbers in the host name.

The reason is that the MCV protocol calls for the ODD numbers to be the primary connection and the ODD number + 1 to be the fail over connection.

So autha11 is the primary and autha12 is the failover.

#52

Hi everyone,

First, thanks for your help. I have been trying to use a VeraLite for several days, and I must admit that the doc is quite hard to find.

I still can achieve the first step of this long process. My controller runs the last version of the firmware. I am trying to connect to : (my username is only lowercase)

https://vera-us-oem-autha11.mios.com/autha/auth/username/myUsername?SHA1Password=sha1(myUserName myPassword oZ7QE6LcLJp6fiWzdqZc)&PK_Oem=1

I am always getting the answer “ERROR:No data”
I used my browser and also tried with the php and the python libraries shared in previous answers (thanks again for these).

I know it is a bit vague, but do you have an idea about where the problem could come from?

Please ask for all the details I didn’t mentioned, I don’t really know what could be important.

Thanks (you would really make my day, maybe even my week),
Victor

#53

I am afraid it’s much more complicated than you understand.
Most of the document is Pseudo code … you need to implement the pseudo code in the language/tools of your choice.

SHA1()

Is pseudo code … you will have to more reading to find out how to actually create an SHA1 hash of the string concatenation of the 3 specified strings.

If you read my notes carefully this will be a string that looks like:
b30bcbdd4408c8bec91c1c03b7801efc0c4733db

Of course it will be a different/unique value for every user!

#54

Yes I understood. I didn’t specified, but in my url :
https://vera-us-oem-autha11.mios.com/autha/auth/username/myUsername?SHA1Password=sha1(myUserName myPassword oZ7QE6LcLJp6fiWzdqZc)&PK_Oem=1
“myUsername” and “sha1(myUserName myPassword oZ7QE6LcLJp6fiWzdqZc)” are in fact replaced by their values. I just didn’t want to put them on the forum.

Your notes are extremely clear. I used the openssl command to create the hash. I also tried with the php library, which uses the sha1 php function.

#55

Sorry you will have to figure this out on your own … unless you want to create a public account and share the account name and password … and the actual SHA1 you computed.

Do you have any white space (i.e. CRLF) in your SHA generation ?

#56

Just wanted to pop in and say that this info was still very helpful in 2017 for UI7. Thank you.

Here is an example bash script (using curl and jq) that authenticates, gets a session token, and retrieves devices:

1 Like
#57

Hi,

I am pretty new with Vera, but it is little bit confusing when I want to configure access to Vera remotely through the MiOS servers.

The idea of access described on the wiki http://wiki.micasaverde.com/index.php/Luup_Requests#device sound very simple, but as I can see, comment says that proposed method is obsolete…

Accessing Vera remotely through the MiOS servers * Obsolete on UI7

The MiOS servers provide a secure way to remotely access and control your Vera system using the HTTP interface. Everything you can do locally with Vera on port 3480, you can do remotely with MiOS using the exact same syntax. You only need to pass the MiOS account username and password on the URL to the remote access server, along with the serial number of the unit (ie. 30012345). For example, the user_data request syntax over the Internet through the MiOS servers is:

https://fwdX.mios.com/demovera/myvera123/30012345/data_request?id=user_data

assuming demovera is the MiOS account username and myvera123 is the password. Note that since the request is https, the username and password are encrypted because https encrypts the URL’s as well as the contents of the page.


It seems that this wiki is not updated for a while.

I have tens of Vera Edges with latest firmware, and I would like to find as simple as it is possible way to do remote Luup Requests. Security is not my issue at this moment. Is there any wiki or tutorial that simplifies this? After all, is it possible just to execute few scenes remotely calling a web URL remotely?

#58

Requests are NOT simple … You need to authenticate first … The notes for this post are still accurate.

#59

Digging this up wondering if something has changed recently.

I’m having issues with using the “/locator/locator/locator” service to get local device information. It seems that the MMSSession is not valid for the us-authd11.mios.com.

I’m asking if something has changed as I can access us-autha11 to authenticate and then use that information to then auth against us-authd11 to get the Session Token but then the Token doesn’t work against the same server but with the locator URL.

For fully remote systems I have unpacked the AuthToken and I can auth and get devices and relay servers through the Server_Account servers and that all works fine.

Since I can access the relay server to get the device list then my auth is working fine. I’m just needing to the local locator working to have the local IP to do a check if local or remote and which way to communicate. I’m going to go through my code again and again to re-check but it’s odd where hitting one server and the tokens and session token are good but against another they are not. I’m probably missing something really simple.

#60

From querying https://vera-us-oem-autha11.mios.com I get the Server_Account and PK_Account … at the same time as I get the Identity and IdentiySignature

I query the Server_Account with /account/account/account/{{PK_Account}}/devices"
From there I get the Remote Gateway AND LOCAL IP Addresses of all of the devices.

I have used the Locator in the past … but since I do not use it … I never wrote down the tricks.

#61

[quote=“RichardTSchaefer, post:60, topic:181032”]From querying https://vera-us-oem-autha11.mios.com I get the Server_Account and PK_Account … at the same time as I get the Identity and IdentiySignature

I query the Server_Account with /account/account/account/{{PK_Account}}/devices"
From there I get the Remote Gateway AND LOCAL IP Addresses of all of the devices.

I have used the Locator in the past … but since I do not use it … I never wrote down the tricks.[/quote]

Rich, Thanks for the info. I went that route as well. It took me some time of playing with things but I got it all worked out.

#62

For me this script worked with errors like:
parse error: Invalid numeric literal at line 1, column 20

But i get another solution:

#63

I’m reading through the discussion topic but can’t seem to find Richard’s notes addressing the remote access issue. Does anyone have it still? I’d really appreciate if someone could email me the notes (alysonfs@gmail.com) or attach them here somewhere.
Thank you!!

#64

This is from old forum, not all files made it across

http://forum.micasaverde.com/index.php/topic,24942.0.html
here is a copy of the txt file if you do not have a login for old forum.
UI6Connect.txt.zip (3.2 KB)

#65

Thank you so much! I didn’t have access to old forum…