I also have a question: I have two controllers but I cannot seem to select both it always gives me the first location although I select 1 or 2 or ... It creates those zones.
I use the Evohome via Web Api. Do I have to change something else?
Evohome client (August 2017 update)
Moderator: leecollings
-
- Posts: 29
- Joined: Saturday 05 November 2016 16:54
- Target OS: -
- Domoticz version:
- Contact:
-
- Posts: 29
- Joined: Saturday 05 November 2016 16:54
- Target OS: -
- Domoticz version:
- Contact:
Re: Evohome client (August 2017 update)
Settings are saved and it gets the information. It just seem to ignore the location setting
-
- Posts: 29
- Joined: Saturday 05 November 2016 16:54
- Target OS: -
- Domoticz version:
- Contact:
Re: Evohome client (August 2017 update)
So nothing I can do probably?
-
- Posts: 29
- Joined: Saturday 05 November 2016 16:54
- Target OS: -
- Domoticz version:
- Contact:
Re: Evohome client (August 2017 update)
Guess I'll have to wait a bit until it reaches the stable version. I'm using docker so I can't update to the beta .
- waaren
- Posts: 6028
- Joined: Tuesday 03 January 2017 14:18
- Target OS: Linux
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: Evohome client (August 2017 update)
With every new Domoticz Beta version following 8627 is get the following error
2017-11-24 17:02:49.230 (Evohome) connect to Evohome server
2017-11-24 17:02:49.389 Error: (Evohome) HTTP client error at login!
I compile from source using a spare RPI. If I try to update using the updatebeta script I got segmentation fault (when run from command line) or Fatal signal 11 (daemon)
If I copy my version 8627 back it will connect and update my temperatures and setpoints so I assume settings in domoticz database are correct.
Is there a way to solve this ?
2017-11-24 17:02:49.230 (Evohome) connect to Evohome server
2017-11-24 17:02:49.389 Error: (Evohome) HTTP client error at login!
I compile from source using a spare RPI. If I try to update using the updatebeta script I got segmentation fault (when run from command line) or Fatal signal 11 (daemon)
If I copy my version 8627 back it will connect and update my temperatures and setpoints so I assume settings in domoticz database are correct.
Is there a way to solve this ?
Debian buster, bullseye on RPI-4, Intel NUC.
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
dz Beta, Z-Wave, RFLink, RFXtrx433e, P1, Youless, Hue, Yeelight, Xiaomi, MQTT
==>> dzVents wiki
-
- Posts: 9
- Joined: Friday 17 August 2018 20:14
- Target OS: Raspberry Pi / ODroid
- Domoticz version: latest
- Location: Barneveld
- Contact:
Re: Evohome client (August 2017 update)
I to had the issue of wrong login. After several attempt fixing the issue I logged in into totalconnect website. Edited my profile by changing the hungarian language to dutch. Hungarian is a good default honeywell!
After that I stopped and started the web api device in domoticz and it started connected my home
After that I stopped and started the web api device in domoticz and it started connected my home
Who is online
Users browsing this forum: No registered users and 0 guests