Setting via json to Custom turns heating off

[billytkid]

Hi all,

I run a script at night that sets my evo home to a custom setting:
http://x.x.x.x:8080/json.htm?type=comma ... m&action=1

This has worked for ages but after the 2021.1 update (this may be a coincidence) Evohome first goes to custom, then turns off

The log shows this:
2021-04-27 10:08:51.535 (EvoHome) changed system status to Custom
2021-04-27 10:08:51.598 EvoHome: Heating (EvoTouch)
2021-04-27 10:09:22.160 (EvoHome) fetch data from server
2021-04-27 10:09:22.169 EvoHome: Heating (EvoTouch)

Any idea on how I can troubleshoot this further?

Thanks,

Will

[billytkid]

Hi all,

is anyone able to test this for me to see if it happens on their system too?

thanks

[waaren]

is anyone able to test this for me to see if it happens on their system too?

Yes. Same happens at my system. When I set it to custom the next cycle it is set to Off.

btw I do idea how to set custom settings within config of EvoHome or what to do with it and therefore also no idea how to troubleshoot this further.

[billytkid]

Thanks Waaren,

I use custom as a 'just gone to bed setting' where downstairs heating is turned off and bedrooms are all turned on lower - it basically accelerates the night time setting of the heating (after midnight all zones are in the same setting as custom anyway).

Do you see anything in Evohome to see why it's turning off, has their API changed?

thx

[wouters]

I have the same problems.

When setting the mode to Custom through either a lua script or through the switch, my evohome system switches to Off.
When setting the mode to Off, my evohome system goes to an Unknown mode and after a few minutes, it switches back to Auto again

Using Domoticz 2021.01 in docker on Synology NAS

[goedh452]

I have a similar issue with EvoHome. When I switch it to 'Heating off' in Domoticz, the EvoHome does nothing' and the status in Domoticz becomes "Unknown'. When I switch it to 'Away' the Evhome is switched to 'Normal'. This occurs since the 2021.1 update.

[billytkid]

Is there a way to investigate this via logging?

I'm assuming either the Evohome API has changed, or the Domoticz implementation of it has in the latest update

[billytkid]

As the winter is setting in this is becoming an issue, is anyone else seeing this?

thx

[Scotty]

I also have this problem. Evohome status just switching to 'unknown' a few seconds after I set the heating to off but it doesn't actually turn my heating off at home.

All other modes work as expected.

I'm wondering if the 'off' staus has changed in the API.

[billytkid]

Morning all, from a rather cold UK - partly because my heating keeps turning off!

Can anyone help on this issue?

thanks

[Scotty]

Well, this is frustrating. Still no signs of this working. I can't see anything in the logs that suggest why.

[MLS]

I have the same problem (EvoTouch V3). Setting it to Off does not do anything and the first web update retrieves the state 'Unknown' and much later I think it continues to Auto.
After a quick check, I see that it is a problem with the consistency of the index numbers in the Domoticz frontend/DB object against the definitions in the Evohome API.

The effects to my Evotouch are:
Normal -> Normal (works OK)
Economy -> Eco/Boost (works OK)
Away -> Away (works OK)
Day Off -> Day Off (works OK)
Day Off With Eco -> Custom (mismatch)
Custom -> Heating Off (mismatch)
Heating Off -> Unknown (mismatch)