Evohome client (August 2017 update)

For heating/cooling related questions in Domoticz
fecus
Posts: 14
Joined: Monday 20 February 2017 16:24
Target OS: Linux
Domoticz version: 3.7708
Location: Hungary
Contact:

Re: Evohome client (June 2017 update)

Post by fecus » Sunday 18 June 2017 11:33

gordonb3 wrote:Right...

Just noticed you are running beta. You can also try the 'Evohome via Web API' instead of 'Evohome via Script'. It is essentially the same code but it uses a different json library to allow integration. It may not be vulnerable to whatever unexpected json values are returned for your installation.
I tried. The error message:

Code: Select all

 2017-06-18 11:30:55.789 (Honeywell) connect to Evohome server
2017-06-18 11:30:56.895 Error: (Honeywell) HTTP client error at retrieve user account info! 
The login and password is OK. I checked in web.

gordonb3
Posts: 567
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome client (June 2017 update)

Post by gordonb3 » Sunday 18 June 2017 16:18

fecus wrote:I tried. The error message:

Code: Select all

 2017-06-18 11:30:55.789 (Honeywell) connect to Evohome server
2017-06-18 11:30:56.895 Error: (Honeywell) HTTP client error at retrieve user account info! 
The login and password is OK. I checked in web.
I know. The code would not try to retrieve the user info if the login did not succeed. The error indicates a problem connecting to the server, which is strange because the initial connect was successful. Are you using a web proxy maybe? Connecting through VPN? You may want to try lower network properties MTU/MRU on your machine.
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000

fecus
Posts: 14
Joined: Monday 20 February 2017 16:24
Target OS: Linux
Domoticz version: 3.7708
Location: Hungary
Contact:

Re: Evohome client (June 2017 update)

Post by fecus » Sunday 18 June 2017 17:06

gordonb3 wrote: I know. The code would not try to retrieve the user info if the login did not succeed. The error indicates a problem connecting to the server, which is strange because the initial connect was successful. Are you using a web proxy maybe? Connecting through VPN? You may want to try lower network properties MTU/MRU on your machine.
First, thank you your help!
I haven't got proxy, VPN.
Cable Internet (PPPOE) -> Openwrt router -> default Ubuntu 16.04 headless server without special firewall.
I don't know how to change MTU/MRU in ubuntu.
Can I need to open some port? Can I test it from CLI when I see the error messages?

New error:

Code: Select all

 2017-06-18 16:41:48.236 (Honeywell) connect to Evohome server
2017-06-18 16:41:49.424 (Honeywell) logon fail treshold reached - trottling 

gordonb3
Posts: 567
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome client (June 2017 update)

Post by gordonb3 » Sunday 18 June 2017 17:46

You can use `ping` to find the maximum MTU/MRU size. Don't have any direct resources for you but Google should help you find some. Normal setting for PPPoE would be 1492, but I actually did have some problems with that setting myself when I went to fiber. Got mine at 1480 and it solved all my connection issues. Haven't worked with Debian type systems for a while, but I think you can set mtu as an interface property in /etc/network/interfaces.
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000

xAPPO
Posts: 2
Joined: Wednesday 17 August 2016 15:21
Target OS: Windows
Domoticz version:
Contact:

Re: Evohome client (June 2017 update)

Post by xAPPO » Tuesday 27 June 2017 15:34

I am getting a logon error - but the username (email) and password are definitely correct , I just checked on https://international.mytotalconnectcomfort.com

.... although I did originally enter the wrong password.

v 3.8.007 raspberry Pi

2017-06-27 13:11:42.055 (EvoHome) Worker started...
2017-06-27 13:11:52.056 (EvoHome) connect to Evohome server
2017-06-27 13:11:52.159 Error: (EvoHome) HTTP client error at login!
2017-06-27 13:12:06.161 (EvoHome) Worker stopped...

Any suggestions - or is this an MTU thing too ?

[update] I have a feeling the original password persisted. I restarted the Pi and Domoticz and all is now OK. Default MTU on the Pi is 1500 BTW

gordonb3
Posts: 567
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome client (June 2017 update)

Post by gordonb3 » Tuesday 27 June 2017 23:11

Nothing to do with the password. The error you got as it states really came from failing to connect to the (http) web portal. Can't really give you the why or the what.
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000

fecus
Posts: 14
Joined: Monday 20 February 2017 16:24
Target OS: Linux
Domoticz version: 3.7708
Location: Hungary
Contact:

Re: Evohome client (June 2017 update)

Post by fecus » Wednesday 28 June 2017 11:29

gordonb3 wrote:You can use `ping` to find the maximum MTU/MRU size. Don't have any direct resources for you but Google should help you find some. Normal setting for PPPoE would be 1492, but I actually did have some problems with that setting myself when I went to fiber. Got mine at 1480 and it solved all my connection issues. Haven't worked with Debian type systems for a while, but I think you can set mtu as an interface property in /etc/network/interfaces.
I tried everything. I tried in Ubuntu server. I tried in Raspberry PI. I took the raspberry pi to my company. I tried the program there. Same.
I change MTU in my server to 1464. Nothing.

Is there any settings in "https://international.mytotalconnectcomfort.com/" what I missed to set.

gordonb3
Posts: 567
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome client (June 2017 update)

Post by gordonb3 » Thursday 29 June 2017 12:41

None that I know of. The web client in this case is internal Domoticz and I can't really bugtrace that.

I did do a full rewrite of the stand alone client though, because as it turned out there were memory leaks in the used json library. It's essentially the same code as the internal Domoticz version now, but the web client implementation is slightly different. If that one also does not run correctly you could try e.g. tcpdump to watch for the actual answers given by the Honeywell web portal.
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000

fecus
Posts: 14
Joined: Monday 20 February 2017 16:24
Target OS: Linux
Domoticz version: 3.7708
Location: Hungary
Contact:

Re: Evohome client (June 2017 update)

Post by fecus » Thursday 27 July 2017 21:46

I updated evo-client to version 1.3.0. After init I start:
[email protected]:/usr/local/domoticz/scripts# ./evo-client -k
ERROR: multiple Evohome systems found - don't know which one to use for status
but I have only one RFG100. And no temperature from round thermostat.
What does it mean?

Kerel
Posts: 27
Joined: Friday 02 December 2016 9:38
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Evohome client (June 2017 update)

Post by Kerel » Friday 28 July 2017 18:39

Can't really get it to be compiled on my raspberry pi :(,

Any thoughts?

Image

gordonb3
Posts: 567
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome client (June 2017 update)

Post by gordonb3 » Friday 28 July 2017 23:46

fecus wrote:I updated evo-client to version 1.3.0. After init I start:
[email protected]:/usr/local/domoticz/scripts# ./evo-client -k
ERROR: multiple Evohome systems found - don't know which one to use for status
but I have only one RFG100. And no temperature from round thermostat.
What does it mean?
Apparently the server returns information for more than one installation. Obviously I can't tell why it does that if you only have one installation, but you can edit the config file to select one (location:0, gateway:0, controlsystem:0) and see what it returns then. Increment location if there is still no data returned or another error message is displayed saying that the chosen installation does not exist (which might happen if location 0 is empty and thus has no gateway and/or temperature controlsystem).
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000

gordonb3
Posts: 567
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome client (June 2017 update)

Post by gordonb3 » Friday 28 July 2017 23:53

Kerel wrote:Can't really get it to be compiled on my raspberry pi :(,

Any thoughts?
Likely an include that I missed but for some reason does not trigger this error on my machine. I'll have a look when I get back home. If you like to try fix it yourself, it's probably cstdlib. You may also delete the evohomeoldclient source files for a quick fix as these are actually not used by the main app.
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000

gordonb3
Posts: 567
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome client (June 2017 update)

Post by gordonb3 » Wednesday 09 August 2017 13:15

Compiler error on the Pi should be fixed in the main branch now (not a release yet). Don't know why the error does not show on my system. Probably depends on platform and/or compiler (version).
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000

gordonb3
Posts: 567
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome client (August 2017 update)

Post by gordonb3 » Wednesday 09 August 2017 16:53

New release: version 1.4.0

Should fix most if not all issues mentioned above
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000

fecus
Posts: 14
Joined: Monday 20 February 2017 16:24
Target OS: Linux
Domoticz version: 3.7708
Location: Hungary
Contact:

Re: Evohome client (August 2017 update)

Post by fecus » Tuesday 22 August 2017 13:11

gordonb3 wrote:
Wednesday 09 August 2017 16:53
New release: version 1.4.0

Should fix most if not all issues mentioned above
I deleted account at Honeywell site and renew with other email.
After upgrade client from 1.3.0 to 1.4.0.

First time:

Code: Select all

[email protected]:/usr/local/domoticz/scripts#./evo-client  -i
evo-client start: 2017-07-31 20:03:28
connect to Domoticz server
got ID '11' for Evohome hardware with name 'RFG100'
init mode enabled
create hardware in Domoticz
create evohome controller in Domoticz
create hot water device in Domoticz
create heating device in Domoticz
create heating device in Domoticz
create heating device in Domoticz
create heating device in Domoticz
create heating device in Domoticz
create heating device in Domoticz
create heating device in Domoticz
create heating device in Domoticz
create heating device in Domoticz
create heating device in Domoticz
create heating device in Domoticz
create heating device in Domoticz
connect to Evohome server
retrieve Evohome installation info
ERROR: multiple Evohome systems found - don't know which one to use for status
Set config to 0,0,0 and after:

Code: Select all

[email protected]:/usr/local/domoticz/scripts# ./evo-client -k
terminate called after throwing an instance of 'std::invalid_argument'
  what():  login fail
Félbeszakítva (core készült) I think in English: Segmentation fault (core dumped)
The config:

Code: Select all

#fill in script root; e.g. script:///home/<user>/evohome-client script:///usr/local/bin etc
srt='script:///usr/local/domoticz/scripts'

#uncomment and complete the following line to enable logging to a file
logfile='evohome_log.txt'

#The following applies if you have multiple Evohome systems:

#uncomment the following lines if you like to use the first Evohome system returned
#change numbers to access different installations
location=0
gateway=0
controlsystem=0

#or supply the Evohome systemId
#;systemId='11'

#uncomment the following line if you want the hardware to be registered
#under a different name in Domoticz (default:evohome)
hwname='RFG100'
Reinstall (after domoticz daemon restart):

Code: Select all

[email protected]:/usr/local/domoticz/scripts# ./evo-client -i
terminate called after throwing an instance of 'std::invalid_argument'
  what():  login fail
Félbeszakítva (core készült)

gordonb3
Posts: 567
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome client (August 2017 update)

Post by gordonb3 » Tuesday 22 August 2017 14:04

Ah yes, probably not the nicest way to exit. That exception is deliberate but should be caught by the app. The reason is that the login to the Evohome portal fails. When you changed the config file to set which installation to use, did you touch or delete the lines holding your credentials?
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000

tonbor
Posts: 23
Joined: Monday 17 February 2014 10:12
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Evohome client (August 2017 update)

Post by tonbor » Tuesday 22 August 2017 14:23

2017-08-22 13:51:55.529 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 13:53:56.369 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 13:55:57.189 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 13:57:58.025 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 13:59:58.847 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 14:01:59.667 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 14:04:00.469 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 14:06:01.285 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 14:08:02.085 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 14:10:02.954 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 14:12:06.096 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 14:14:06.992 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 14:16:07.825 Error: (evohome) HTTP client error at retrieve user account info!

For two days now no login connection for Evohome. I did nothing, perhabs a faulty beta release? Before that no problem with script or later with the api. Others have lost connection too?

gordonb3
Posts: 567
Joined: Friday 22 January 2016 11:15
Target OS: Linux
Domoticz version: custom
Location: The Netherlands
Contact:

Re: Evohome client (August 2017 update)

Post by gordonb3 » Tuesday 22 August 2017 14:40

Not running latest, only thing I can say is that the portal is up and returning data.

When you say you did nothing, does that include not upgrading beta?
Excito B3 running Gentoo Linux, P1, Rfxtrx433 to read and control TFA, KaKu, EvoHome RFG100
Custom patched Domoticz v3.8000

tonbor
Posts: 23
Joined: Monday 17 February 2014 10:12
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Evohome client (August 2017 update)

Post by tonbor » Tuesday 22 August 2017 15:09

yes I auto ugraded to beta releases .....

2017-08-22 15:06:29.900 (evohome) connect to Evohome server
2017-08-22 15:06:30.719 Error: (evohome) HTTP client error at retrieve user account info!
2017-08-22 15:06:30.719 (evohome) logon fail treshold reached - trottling

tonbor
Posts: 23
Joined: Monday 17 February 2014 10:12
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Evohome client (August 2017 update)

Post by tonbor » Tuesday 22 August 2017 15:11

Over Domoticz
Version: 3.8346
Build Hash: 3bb9d25
Compile Date: 2017-08-22 08:53:10

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests