Page 1 of 1

evohome randomly setting heating override

Posted: Tuesday 01 February 2022 10:05
by roadkill
Hi i recently setup domoticz to try and understand how my house is heating and cooling and so far it seems to be doing that
An issue i have found on a couple of nights is that the living room zone has still been heating way after its supposed to have set back for over night when i look its had an override set but there are only 2 of us in the house and neither of us think we have set it! in fact im pretty damn sure neither of us have set it. but im sure this has only started since i set domoticz up. is there any way to see what app, controller, domoticz or aliens has set the override?

also why cant i see 3 days history on the temp sensors i have options for 1H 3 H 1D and 3D when i click 3D it changes the picture but to about 10am-8:30pm

also is there anyway to go through multiple days of detailed temps and or a way to compare multiple days so compare living room Tuesday this week to Tuesday last week and the week before? (maybe a few years worth)

i assume not and the answer would be extract it to csv and make my on graphs but can i download the detailed data to csv for previous days?

cheers

Re: evohome randomly setting heating override

Posted: Tuesday 01 February 2022 10:10
by MikeyMan
What kind of thermostats do you have? Are you combining old and new Honeywell Rounds? This resulted in strange effects with me.

Re: evohome randomly setting heating override

Posted: Tuesday 01 February 2022 10:24
by waltervl
roadkill wrote: Tuesday 01 February 2022 10:05 also why cant i see 3 days history on the temp sensors i have options for 1H 3 H 1D and 3D when i click 3D it changes the picture but to about 10am-8:30pm

also is there anyway to go through multiple days of detailed temps and or a way to compare multiple days so compare living room Tuesday this week to Tuesday last week and the week before? (maybe a few years worth)

i assume not and the answer would be extract it to csv and make my on graphs but can i download the detailed data to csv for previous days?

cheers
1. Check short log settings in menu setup - settings - short log: https://www.domoticz.com/wiki/Applicati ... og_History
Standard 1 day but can be up to max 7 days (and will increase database size)

2. See Custom graph functionality in the device log page.
https://www.domoticz.com/wiki/Managing_ ... Device_Log

3. If you want detailed temperature info stored for weeks or even months than you should sent the data to influxdb ( https://www.domoticz.com/wiki/Influxdb) and make nice graphs with Grafana.
Domoticz is transferring short log data to compressed daily summary data to keep the database size under control.

Re: evohome randomly setting heating override

Posted: Tuesday 01 February 2022 13:31
by roadkill
MikeyMan wrote: Tuesday 01 February 2022 10:10 What kind of thermostats do you have? Are you combining old and new Honeywell Rounds? This resulted in strange effects with me.
living room is trv and the evotouch controller some rooms are dts92e1020 (2 at the moment another 2 on their way) and one has a t87rf

Re: evohome randomly setting heating override

Posted: Tuesday 01 February 2022 13:32
by roadkill
waltervl wrote: Tuesday 01 February 2022 10:24
roadkill wrote: Tuesday 01 February 2022 10:05 also why cant i see 3 days history on the temp sensors i have options for 1H 3 H 1D and 3D when i click 3D it changes the picture but to about 10am-8:30pm

also is there anyway to go through multiple days of detailed temps and or a way to compare multiple days so compare living room Tuesday this week to Tuesday last week and the week before? (maybe a few years worth)

i assume not and the answer would be extract it to csv and make my on graphs but can i download the detailed data to csv for previous days?

cheers
1. Check short log settings in menu setup - settings - short log: https://www.domoticz.com/wiki/Applicati ... og_History
Standard 1 day but can be up to max 7 days (and will increase database size)

2. See Custom graph functionality in the device log page.
https://www.domoticz.com/wiki/Managing_ ... Device_Log

3. If you want detailed temperature info stored for weeks or even months than you should sent the data to influxdb ( https://www.domoticz.com/wiki/Influxdb) and make nice graphs with Grafana.
Domoticz is transferring short log data to compressed daily summary data to keep the database size under control.
cheers updated short logs

will check out the influxdb then cheers. i mean this isnt required but would be nice to see :)

Re: evohome randomly setting heating override

Posted: Tuesday 01 February 2022 14:32
by MikeyMan
roadkill wrote: Tuesday 01 February 2022 13:31
MikeyMan wrote: Tuesday 01 February 2022 10:10 What kind of thermostats do you have? Are you combining old and new Honeywell Rounds? This resulted in strange effects with me.
living room is trv and the evotouch controller some rooms are dts92e1020 (2 at the moment another 2 on their way) and one has a t87rf
Like i said, the issues started when i tried to combine older (T87G) and newer thermostats. Is it specific to one of the types here?

Changing the old version to a newer one fixed my issue here.

Re: evohome randomly setting heating override

Posted: Friday 04 February 2022 12:10
by randomusername
roadkill wrote: Tuesday 01 February 2022 10:05
An issue i have found on a couple of nights is that the living room zone has still been heating way after its supposed to have set back for over night when i look its had an override set but there are only 2 of us in the house and neither of us think we have set it! in fact im pretty damn sure neither of us have set it. but im sure this has only started since i set domoticz up. is there any way to see what app, controller, domoticz or aliens has set the override?
I actually have the same issue - one room will have a temporary override set to 5C almost constantly - if you look at the history graph you can see Evohome setting it to a normal temperature on it's schedule, then 10-20 mins later it will be set back to 5C.

All valves are the same/round type, it all worked perfectly up until about June last year when this behaviour started, which may have coincided to an upgrade to 2021.1. Just upgraded to 2022.1 and it still persists. I've not figured out what's causing it yet either!