Evohome error HTTP client error at retrieve user account info

[nuphar]

Hi,

We recently switched from EQ-3 Max! to Evohome and it's....great, I guess. But I haven't been able to get it working in Domoticz. Added the hardware (Evohome via Webapi), but I receive this error in the log:

Error: (Evohome) HTTP client error at retrieve user account info!

I have searched the forum and found others with the same issues, but none of the suggested solutions make any difference:
- I did try to change the language to Dutch, English, Hungarian, etc. Also changed the country. Perhaps I'm looking in the wrong setting in the website?
- I added a second user and used these credentials, same error.
- I installed Domoticz on a Windows PC, clean, just Evohome added: same error.

The user credentials are correct. If I change them (different password) I get a different error. I have read that the error says something about the client (my Domoticz), but I really can't figure it out.

I have Domoticz running on both Pi and Windows, both same issue. I tried installing the evohome-client on the Pi, but this didn't work yet. WIll try to figure this out.

Any suggestions on what to change, try?

Thanks a lot in advance,
Johan

[gordonb3]

You could try to enable debugging in Domoticz and maybe it will tell you what error it sees during the REST call. The thing here is: I don't know. I cannot replicate the issue on my system. The only tip I can give is if you installed stable (4.9700/4.9701) try beta. That, next to changing your Evohome portal language setting, seems to do the trick for most users.

[nuphar]

Thanks...already tried the beta on the Pi, will do so on the Windows machine.

Just to be sure: Changing the portal language settings...I changed my country to Hungray in my profile, language to Hungarian in my profile, but the web interface is still English (see attachment). Is this all as it should be? It's really driving me nuts...!

[gordonb3]

AFAIK Hungarian is the wrong setting. This is likely caused by Hungarian (and other languages) having non-ASCII-7 characters and the portal trying to reinterpret what it is receiving. Choose English.

[nuphar]

Tried all languages by now....Everything set to English and get more errors:-(

2018-11-03 12:37:25.542 Error: (Evohome) HTTP client error at retrieve installation!
2018-11-03 12:37:25.542 Error: (Evohome) failed to retrieve installation info from server

It's really driving me nuts...

[gordonb3]

Okay but that means you are now getting past retrieving the user info, so the headers must be passed on correctly. If you enable debugging (level: normal), does the Domoticz log show any HTTP errors?

[nuphar]

Nope, no other errors. Have set dzevents log level to debugging (everything).

[gordonb3]

Don't think that will do it. AFAIK the only way to enable debugging is by specifying it on the command line when starting Domoticz (using `-loglevel` and `-debuglevel`).

[nuphar]

Ok, so I really f#cked my whole Domoticz and pi up trying to enable debugging. Did a clean install, restored database, up and running again.

I know I have to add some arguments to domoticz.sh, but can't figure out what exactly. I tried several options, but they all resulted in either no logging at all, or no more erros.

What should I add to my domoticz.sh?

It currently looks like as attached (default after clean install).

Thanks a lot for the patience!

Johan

[gordonb3]

This should do it:

Code: Select all

DAEMON_ARGS="$DAEMON_ARGS -loglevel 15 -debuglevel normal"

[nuphar]

Excellent! Got debugging working and do receive the following:

Code: Select all

2018-11-04 17:30:06.059 Status: (Evohome) connect to Evohome server
2018-11-04 17:30:06.854 Debug: SQLH UpdateValueInt Electra HwID:22 DevID:1 Type:250 sType:1 nValue:0 sValue:51461;32572;14669;8057;487;0
2018-11-04 17:30:06.862 Debug: SQLH UpdateValueInt Voltage L1 HwID:22 DevID:00000001 Type:243 sType:8 nValue:0 sValue:224.000
2018-11-04 17:30:09.767 Error: (Evohome) HTTP client error at retrieve installation!
2018-11-04 17:30:09.767 Error: (Evohome) failed to retrieve installation info from server
2018-11-04 17:30:09.766 Debug: HTTP 403: Forbidden. The request is valid, but the server is refusing action
2018-11-04 17:30:09.851 Debug: SQLH UpdateValueInt Electra HwID:22 DevID:1 Type:250 sType:1 nValue:0 sValue:51461;32572;14669;8057;487;0

I think the "2018-11-04 17:30:09.766 Debug: HTTP 403: Forbidden. The request is valid, but the server is refusing action" part is linked to Evohome.

Not sure what to do though...

Thanks,
Johan

[nuphar]

OK, this was quite annoying...but there is progress!

Since most posts about this error indicated some issue with the account setting, I tried adding a different account. I tried several times, actually. Added an account through the initial account, followed link, activated, etc. No difference.

Deleted these addidtional accounts, tried again. And again. Long story short: Honeywell is not doing well with these accounts. I really had to create a different account on a different domain and following the links from a different mailclient and had to choose London/UK/English in the initial setup of these additional accounts.

Now I get the following in the logs:

Code: Select all

2018-11-04 17:59:31.899 Debug: SQLH UpdateValueInt Voltage L1 HwID:22 DevID:00000001 Type:243 sType:8 nValue:0 sValue:226.000
2018-11-04 17:59:32.399 (Evohome) fetch data from server
2018-11-04 17:59:32.410 (Evohome) Heating (EvoTouch)
2018-11-04 17:59:32.904 (P1 Smart Meter) P1 Smart Meter (Electra)
2018-11-04 17:59:32.906 (P1 Smart Meter) General/Voltage (Voltage L1)
2018-11-04 17:59:32.410 Status: (Evohome) register new zone 'My Home: Woonkamer'
2018-11-04 17:59:32.404 Debug: SQLH UpdateValueInt HwID:23 DevID:92001 Type:70 sType:0 nValue:0 sValue:0.0;0.0;Auto
2018-11-04 17:59:32.409 Debug: SQLH UpdateValueInt zone 1 HwID:23 DevID:4225220 Type:70 sType:0 nValue:0 sValue:21.0;21.0;TemporaryOverride;2018-11-04T21:00:00Z
2018-11-04 17:59:32.896 Debug: SQLH UpdateValueInt Electra HwID:22 DevID:1 Type:250 sType:1 nValue:0 sValue:51736;32572;14669;8057;477;0
2018-11-04 17:59:32.905 Debug: SQLH UpdateValueInt Voltage L1 HwID:22 DevID:00000001 Type:243 sType:8 nValue:0 sValue:226.000
2018-11-04 17:59:33.910 (P1 Smart Meter) P1 Smart Meter (Electra)
2018-11-04 17:59:33.912 (P1 Smart Meter) General/Voltage (Voltage L1)
2018-11-04 17:59:33.709 Status: (Evohome) register new zone 'My Home: Studeerkamer'
2018-11-04 17:59:33.715 Status: (Evohome) register new zone 'My Home: Slaapkamer'
2018-11-04 17:59:33.707 Debug: SQLH UpdateValueInt HwID:23 DevID:92002 Type:70 sType:0 nValue:0 sValue:0.0;0.0;Auto
2018-11-04 17:59:33.708 Debug: SQLH UpdateValueInt zone 2 HwID:23 DevID:4225548 Type:70 sType:0 nValue:0 sValue:20.0;18.0;Auto;2018-11-04T21:30:00Z
2018-11-04 17:59:33.713 Debug: SQLH UpdateValueInt HwID:23 DevID:92003 Type:70 sType:0 nValue:0 sValue:0.0;0.0;Auto
2018-11-04 17:59:33.714 Debug: SQLH UpdateValueInt zone 3 HwID:23 DevID:4225549 Type:70 sType:0 nValue:0 sValue:16.5;16.0;TemporaryOverride;2018-11-04T21:30:00Z
2018-11-04 17:59:33.902 Debug: SQLH UpdateValueInt Electra HwID:22 DevID:1 Type:250 sType:1 nValue:0 sValue:51736;32572;14669;8057;477;0
2018-11-04 17:59:33.911 Debug: SQLH UpdateValueInt Voltage L1 HwID:22 DevID:00000001 Type:243 sType:8 nValue:0 sValue:226.000
2018-11-04 17:59:34.901 (P1 Smart Meter) P1 Smart Meter (Electra)
2018-11-04 17:59:34.903 (P1 Smart Meter) General/Voltage (Voltage L1)
2018-11-04 17:59:34.945 Status: (Evohome) register new zone 'My Home: Kinderkamer'
2018-11-04 17:59:34.892 Debug: SQLH UpdateValueInt Electra HwID:22 DevID:1 Type:250 sType:1 n

Now I have the four zones and Evotouch! Happy:-) But there is something wierd going on with the registration process and the influence of the language chosen at inital setup of an account.

Thanks a lot for the help!
Johan

[gordonb3]

Hi Johan, Thanks for persisting in figuring this out and your report. This is very helpful, although I'm still wondering if this is something we can adapt to on our end.

Gordon

[patvandijk]

Well, it doesn't work for me...
Keep getting errors like this
2018-11-08 09:52:25.641 Error: (EvoHome) HTTP client error at login!
2018-11-08 09:58:27.454 Error: (EvoHome) login failed with message: attempt_limit_exceeded
2018-11-08 10:05:25.245 Error: (EvoHome) HTTP client error at login!
2018-11-08 10:07:27.512 Error: (EvoHome) HTTP client error at login!
2018-11-08 10:09:29.644 Error: (EvoHome) HTTP client error at login!
2018-11-08 10:13:34.622 Error: (EvoHome) HTTP client error at retrieve user account info!
2018-11-08 10:19:39.143 Error: (EvoHome) HTTP client error at retrieve user account info!
2018-11-08 10:27:41.317 Error: (EvoHome) HTTP client error at login!

Created a new account with location in the UK, Cambridge, checked English as the language...
Also installed the latest beta.

[gordonb3]

Please enable debug. There's really not enough information in these log lines because internally the client only returns success or failure. The only thing that can be derived from this is that apparently your credentials are good because some of these messages can only be returned after login.

That said: it appears that Honeywell made some changes to the portal and people have been reporting `new` messages like the `attempt_limit_exceeded`, but starting this month I've also seen `Authorize error` and `Request count limitation exceeded, please try again later.` pop up in my own logs from time to time. To my knowledge there has been no statement from Honeywell as to why these errors are occurring and what action the user is supposed to take from there.

[patvandijk]

Well, I don't see anything usable in the 'debug' log, only these errors in de 'problem' log.

2018-11-08 13:35:53.233 Error: (EvoHome) HTTP client error at login!
2018-11-08 13:51:58.909 Error: (EvoHome) HTTP client error at retrieve user account info!
2018-11-08 14:10:07.370 Error: (EvoHome) HTTP client error at retrieve user account info!


2018-11-08 14:52:13.215 Error: (EvoHome) HTTP client error at login!

Only messages like:
2018-11-08 14:52:16.654 Debug: SQLH UpdateValueInt.....

[gordonb3]

I'm afraid that means that the problem is most likely local to your machine. Probably related to either curl or ssl not behaving correctly. Are you running a prebuilt version of Domoticz? You may try solve the issue by building it from source.

[patvandijk]

Is there anything I can try manually? from a command line?

In source code
https://github.com/domoticz/domoticz/bl ... omeWeb.cpp
I see
pdata << "&Host=rs.alarmnet.com%2F";

When I perform this

curl -X POST -H "Content-Type: application/json" -d '{
"username": "<myusername>",
"password": "<mypassword>",
"ApplicationId": "91db1612-73fd-4500-91b2-e63b069b185c"
}' 'https://rs.alarmnet.com/TotalConnectCom ... pi/Session'

I get

<head><body> This object may be found <a HREF="https://mytotalconnectcomfort.com/portal">here</a> </body>pi@domoticzpi /var/log $

Not sure what that means.
On the other hand, it seems it is able to connect as sometimes I get in de log

2018-11-08 15:42:21.852 Error: (EvoHome) HTTP client error at retrieve user account info!

But maybe that is related to the invalid login.

And I am unable to login to this site
https://mytotalconnectcomfort.com/portal/

But can login to this one
https://international.mytotalconnectcomfort.com/

Seem they have two different sites?
Perhaps due to EU regulations?
EU data should reside in the EU?
Just guessing...

[patvandijk]

When I perform

curl -X POST -H "Content-Type: application/json" -d '{
"username": "<myusername>",
"password": "<mypassword>",
"ApplicationId": "91db1612-73fd-4500-91b2-e63b069b185c"
}' 'https://tccna.honeywell.com/WebAPI/api/Session'

I do get a proper response!

{
"sessionId": "806639F5-68C4-4D92-B1A7-9896AA1E693F",
"userInfo": {
"userID": xxxx,
"username": "<myusername>",
"firstname": "<myfirstname>",
"lastname": "<mylastname>",
"streetAddress": "<yes...>",
"city": "<indeed>",
"zipcode": "<iscorrect>",
"country": "<yep>",
"telephone": "",
"userLanguage": "nl-NL",
"isActivated": true,
"deviceCount": 0,
"tenantID": 5,
"securityQuestion1": "NotUsed",
"securityQuestion2": "NotUsed",
"securityQuestion3": "NotUsed",
"latestEulaAccepted": false
}

[patvandijk]

Perhaps this site gives more information as well

https://github.com/willdollman/perl-tot ... t/issues/2

Especially this response from Joe Zwack on December 22nd, 2016

Hi!

A few things to follow on above.

Our API keys and accounts are actually logically separated by region in TCC. Those of you with US TCC accounts and devices won't be able to use an API key from a UK app and vice versa. Some of the API resources may work, but the ones with /emea/ in the URI are designed for UK products.

Ideally, I'd like to get you your own API key(s) and use the OAuth login functionality instead of the sessions API or the mobile API wrapper.