JSON user ID and password?

[frankc]

When using a JSON request to my Homeseer HS3 computer, I am prompted by 'Edge' on Windows 10 to enter a user ID and password as follows:

"The server "www.server.net" is asking for your user name and password. The server reports that it is from HomeSeer0.

Warning: Your user name and password will be sent using basic authentication on a connection that isn't secure"

Is there a way to include a user name and password within the JSON request?

e.g.

//serverort/JSON?user=frank&pass=secret&request=speak &phrase=hello&host=HOST

thanks

[rmiles7721]

This is how it's supposed to work:

https://server:port/JSON?user=demo@homeseer.com&pass=demo100&request=getstatus

However, I have the same problem as you with Chrome on Android. Haven't reported it yet as I am having major problems getting HStouch to work that's I'm trying to figure out without having to reinstal everything.

[frankc]

I just tried that scheme on Chrome and on Edge and in both cases, I am asked for a password and user name.

I've got all my other scripts converted from HS2 to HS3. But so far, no luck with remote controls such as this.

tenHsServer works great on HS2 for control and it allows the use of a password and user name.

[Rupp]

Are you running this command locally or remotely? I just tried it locally and it return the expected JSON.

[rmiles7721]

Are you running this command locally or remotely? I just tried it locally and it return the expected JSON.

Personally I'm trying it remotely. There's no need for the username/password locally.

[Rupp]

Remotely I use https://connected2.homeseer.com/ which utilizes myHS connection.

ie https://connected2.homeseer.com/JSON...om&pass=******

[rmiles7721]

Remotely I use https://connected2.homeseer.com/ which utilizes myHS connection.

Awesome. Just tried that instead of my url and it worked. Just out of curiosity, any reason it doesn't work using my url? I would rather not depend on someone else's server being up to be able to log in to mine. Might as well be using Wink then (not really but it is an appropriate example)

[Rupp]

Awesome. Just tried that instead of my url and it worked. Just out of curiosity, any reason it doesn't work using my url? I would rather not depend on someone else's server being up to be able to log in to mine. Might as well be using Wink then (not really but it is an appropriate example)

It's a browser thing. Most all new browsers no longer allow username and passwords to be sent on the URL.

[frankc]

Are you running this command locally or remotely? I just tried it locally and it return the expected JSON.

Like Rmiles, I am running the command remotely. Works OK locally.

A week or so ago, I was accessing HS2 remotely using tenHsServer on Chrome, IE, and FF with a user name and password from any computer. That always worked fine. But tenHsServer hasn't been written for HS3.

I will try definitely try the Homeseer server today! Thanks!

Is there something fundamentally different about the HS3 architecture that would render an application very similar to tenHsServer but written for HS3, not to allow a user name and password to be entered remotely?

Thank you for the help folks!

[Romac]

Running into the same issue and found this thread.

I'm trying to connect to Homeseer from a third party control system and want to download all status information from Homeseer in a json format. This has always worked when the Homeseer server was on the same subnet but now that it is moved to another subnet, Homeseer is requesting user and password.

I have been able to work around this by using MyHS as described above, but I like to find a way to keep traffic on my own network, just flowing between two subnets.

I have been using:

https://server:port/JSON?user=demo@homeseer.com&pass=demo100&request=getstatus

but that does not work. User and password are not accepted. Is there another way to pass userid and password or disable userid and password all together?

ps. I know I can always move the HS server back to the same subnet.....

[mwolter]

Try http://user***@serverort/JSON?request=getstatus if you have version 3.0.0.399 https should work but havent tried it on anything other than the web interface, witch works well!

[Romac]

Thanks! This works perfect using http after updating to the last stable release 3.0.0.368.