EvoControl - custom Alexa skill for Evohome

[jweaver]

What happens if you delete a zone and re-add it? How does Smart Heat handle this? Would it even be aware that its been deleted if you recreate it with the same name?

Could you then use EvoControl to 'restore' the Schedule? To the new zone?

I have to do this and just wonder if I need to do anything on the EvoControl side after its done?

[bruce_miranda]

Normally, if you delete a zone and recreate it, the new zone gets created at the back of the queue with a new Zone ID, even if you give it the same name. Also the act of deleting the zone deletes the schedule too.
But your question is still interesting because if you have just a single zone slot free, the new zone ID would be the same so would deleting the zone and recreating it allow EvoControl to retain and restore its copy of the schedule for that zone.

[philchillbill]

[bruce_miranda]

I think here we are using the fact that EvoControl has its own copy of the schedule to our benefit. How often does EvoControl resync it's own copy of the schedule to what's on TCC automatically? Because if it didn't do that, then you could have a schedule conflict, couldn't you? The controller is only ever going to listen to what TCC tells it.

[philchillbill]

I think here we are using the fact that EvoControl has its own copy of the schedule to our benefit. How often does EvoControl resync it's own copy of the schedule to what's on TCC automatically? Because if it didn't do that, then you could have a schedule conflict, couldn't you? The controller is only ever going to listen to what TCC tells it.

It syncs the Live schedule every 90 secs. But it stores schedule A for you the first time you use the skill and holds that untouched.

[jweaver]

It syncs the Live schedule every 90 secs. But it stores schedule A for you the first time you use the skill and holds that untouched.

Going to be honest. I still don't really understand the schedules... And the A,B and C varients.. I was going to ask about this...

If I make a change on the Evohome to a schedule... What happens on Evoconnect? Do I need to sync it? If it happens automatically, do I need to "copy" it to 'A'?

[philchillbill]

Going to be honest. I still don't really understand the schedules... And the A,B and C varients.. I was going to ask about this...

If I make a change on the Evohome to a schedule... What happens on Evoconnect? Do I need to sync it? If it happens automatically, do I need to "copy" it to 'A'?

[philchillbill]

A few minor updates:

[jweaver]

I have just encountered my first "real world" problem.. I was getting ready for work, so activated an "activity" I created, just for a test (which is essentially all zones to 15 degrees).

As always, I fluffed my lines and couldn't get the syntax right, so I had to check what the Activity was called.. And stupidly I was saying the wrong activity name.. Easily fixed.. This time I said the right commands, but forgot to say "until", so now my system has all rooms at 15 degrees until the next setpoint change.

So I figured I would put it back to Automatic and start again. So I said "set mode to auto" and the command was accepted. But the controller still showed all zones at 15 degrees.

I went down to the Show and checked the UI and indeed, it was still running the activity.. So I said again "set mode to auto" and I saw all zones go back to their shedule.. I went back to what I was doing and a few mins later checked Evohome and the zones were still at 15..

So back to the Show and the UI now showed everything at 15 degrees.. Odd as I am 100% sure I saw them all go back to normal.. So I said again "set mode to auto" and again everything went back to the correct temperature.. But this time I watched it and a few seconds later they all went back to 15 again.

The upshot is that from where I am now (with an Activity running) I can't put the system back into Auto...

Am I doing something wrong?

[philchillbill]

I have just encountered my first "real world" problem.. I was getting ready for work, so activated an "activity" I created, just for a test (which is essentially all zones to 15 degrees).

As always, I fluffed my lines and couldn't get the syntax right, so I had to check what the Activity was called.. And stupidly I was saying the wrong activity name.. Easily fixed.. This time I said the right commands, but forgot to say "until", so now my system has all rooms at 15 degrees until the next setpoint change.

So I figured I would put it back to Automatic and start again. So I said "set mode to auto" and the command was accepted. But the controller still showed all zones at 15 degrees.

I went down to the Show and checked the UI and indeed, it was still running the activity.. So I said again "set mode to auto" and I saw all zones go back to their shedule.. I went back to what I was doing and a few mins later checked Evohome and the zones were still at 15..

So back to the Show and the UI now showed everything at 15 degrees.. Odd as I am 100% sure I saw them all go back to normal.. So I said again "set mode to auto" and again everything went back to the correct temperature.. But this time I watched it and a few seconds later they all went back to 15 again.

The upshot is that from where I am now (with an Activity running) I can't put the system back into Auto...

Am I doing something wrong?

An activity does not change the system mode. It changes the modes of all the zones, which is not the same thing.

You need to say “Set all zones to follow schedule”. You can also say “Reset the system mode” which is different by far to setting it to ‘auto’ as it uses the AutoWithReset mode that TCC supports but which your Evotouch cannot request.

EDIT: The reason you briefly saw the zones do what you wanted is because of a simulation I use to immediately reflect changes without having to wait for a 90 sec refresh from TCC. I'll take a look at tweaking that now that the standby activity is included in the mix as I have not yet done so. After the simulation, the next refresh is hurried to 15 sec and then shows the genuine situation on your Evotouch. I can't do it any sooner than 15s because TCC often takes a while to actually process a burst of changes sent via the API. The mobile app has a similar delay.

[bruce_miranda]

All I would say is that once you start using EvoControl you should leave the app and controller alone. You could get your bits in a knot if you attempt to be too hasty. Remember, any Evohome action can take up to 4mins to take effect. So patience is part of the design of this ecosystem

[jweaver]

All I would say is that once you start using EvoControl you should leave the app and controller alone. You could get your bits in a knot if you attempt to be too hasty. Remember, any Evohome action can take up to 4mins to take effect. So patience is part of the design of this ecosystem

I may not have explained myself very well.. Was rushing about trying to get work... I am not using Evohome, other than in a "read only" capacity.. Let me try to explain (but I am going to get the syntax slightly wrong, but I am sure you understand what I am trying to do):

I issued the command "set activity out" (and forgot to say "until") - Where "out" is an activity which sets all zones to 15 degrees

I realised my mistake, so then said "set mode to automatic" which Alexa accepted and repeated.

I then carried on with my morning for 10 mins or so, and then checked the Evohome and noticed that all zones were still at 15 degrees (inline with my "out" activity).

I then went down to the Show to bring up the UI and all of the zones were still showing 15 degrees. This is odd as I am 100% sure I gave the 'automatic' command and it was accepted.

So i said "set mode to auto" again got verbal confirmation and watched the Smart Heat GUI reflect this...

I then went up to the Evohome controller and watched.. And nothing happened.. Still at 15 degrees..

So i went back down to the Show and everything was 15 degrees again, even though I am 100% sure I saw it change back to "automatic".

I said again "set mode to auto" and watched and all zones go to to their normal temperatures.. But then a few seconds later go back to 15 degrees again.


Everytime I tell Smart Heat to go auto, it accepts the commands.. The GUI reflects it... But then it goes back to 15 degrees again


I am starting to think that the "auto" command is broken.. As to fix this I said "set standby until 2pm" (which then put the whole house to 5 degrees).. And then as a test did "set mode to automatic".. And again, the GUI showed normal temperatures and then immediately went back to 5 degrees again.

For me, this was constantly reproducible, but I will do some more testing later.. But is it possible that there is a problem with the "automatic" feature?

[philchillbill]

I may not have explained myself very well.. Was rushing about trying to get work... I am not using Evohome, other than in a "read only" capacity.. Let me try to explain (but I am going to get the syntax slightly wrong, but I am sure you understand what I am trying to do):

I issued the command "set activity out" (and forgot to say "until") - Where "out" is an activity which sets all zones to 15 degrees

I realised my mistake, so then said "set mode to automatic" which Alexa accepted and repeated.

I then carried on with my morning for 10 mins or so, and then checked the Evohome and noticed that all zones were still at 15 degrees (inline with my "out" activity).

I then went down to the Show to bring up the UI and all of the zones were still showing 15 degrees. This is odd as I am 100% sure I gave the 'automatic' command and it was accepted.

So i said "set mode to auto" again got verbal confirmation and watched the Smart Heat GUI reflect this...

I then went up to the Evohome controller and watched.. And nothing happened.. Still at 15 degrees..

So i went back down to the Show and everything was 15 degrees again, even though I am 100% sure I saw it change back to "automatic".

I said again "set mode to auto" and watched and all zones go to to their normal temperatures.. But then a few seconds later go back to 15 degrees again.


Everytime I tell Smart Heat to go auto, it accepts the commands.. The GUI reflects it... But then it goes back to 15 degrees again


I am starting to think that the "auto" command is broken.. As to fix this I said "set standby until 2pm" (which then put the whole house to 5 degrees).. And then as a test did "set mode to automatic".. And again, the GUI showed normal temperatures and then immediately went back to 5 degrees again.

For me, this was constantly reproducible, but I will do some more testing later.. But is it possible that there is a problem with the "automatic" feature?

[jweaver]

Looks like you missed my post just before Bruce’s.

you are right.. I did.. It rolled onto a different page... This is totally my fault.. I assumed putting it back to "automatic" was what I wanted.... I understand now. Many thanks.

[jweaver]

I have a feature request. Is there anything you can to do make the UI a little more readable... I have 12 zones so everything is crammed onto 1 page.

I am thinking of a couple of ideas

1. Offer a 2 screen view where zones are across 2 screens.

2. Have the ability to have some zones fully displayed as they are now. And some minimized.. For example I have 6 "main" zones and 6 I don't really care about.. So I would be happy to see the 6 zones as they are today.. And then have the other 6 shown smaller or with less info.

3. Just make the font a bit bigger? It might not be as tidy? But there might be room to increase them a little.


Also.. What about the icons at the bottom.. Could they not be a bit bigger... there is plenty of space and not only are they hard to see/read.. They are tiny so touching them accurately with my sausage fingers is difficult.


This is only a non-urgent, minor request, so its by no means a criticism.

Jon