The Evohome App you always wanted!

[philchillbill]

FYI I've switched to using Mailgun for when the app needs to send you an email with e.g. a list of faults or to warn you that a ghost zone was detected. They handle all the DMARC, SPF and DKIM stuff to convince all the email clients out there that it's not spam, so there should be no more empty or missing mails from either smartskills.tech or evocontrol.eu.

[philchillbill]

New feature in the Setpoint Editor (thanks to Anthony for suggesting). You can double-click on any tile that currently has no associated overrides to initiate an override that extends the current setpoint (state in the case of DHW) until the 2nd next switchpoint in the current schedule. That effectively 'coasts over' the next scheduled change for the zone, doing what SkipOver does in schedule-shifting but via overrides instead of modifying the schedule.

The version has been bumped to 2.23. If the browser does not pick up the new files despite showing 2.23 is installed then clear the browser cache for the App and reload.

[philchillbill]

Fixed a bug where using Delayed Start with scene/activity triggering did not cross the midnight boundary correctly. Thanks to Anthony for raising the issue.

[Stevedh]

Hi, alexa is telling me my token is broken and I need to unlink, and relink, and to backup 1st... how do I backup please.

[philchillbill]

I think she’s more likely telling you to re-auth than to unlink/re-link. If not try then re-auth first anyway and see if the issue resolves.

The usage tips section of the website explains how to backup and restore, if needed.

[philchillbill]

I completely re-wrote and greatly extended the Alexa APL emulator at the heart of the PWA. Some of the changes:

• The APL viewer now saves the current screen while a new screen is being fetched and only swaps to the new view when it's already painted inside a 2nd invisible div. This means that the short-duration blank blue canvas between screen-updates is gone and screen transitions are much more fluid.
• The Login for the PWA has been moved into the PWA React code itself instead of relying on a redirect to the account-dashboard login page. This is much more robust. You will still need to login to the PWA the very first time you use it on Apple devices even though you just logged in to the web view in Safari/Chrome. This is because Apple devices open the PWA in a new WebView which does not share localStorage with 'regular' Safari/Chrome. Luckily, it's only once that this is needed.
• The very first time you run the PWA after installing, it displays the Evotouch-image splashscreen while your data is fetched from TCC. On subsequent use, your previous dashboard is cached on your device and that is shown in a darkened state with a spinner over it while your data refreshes from TCC.It used to be so that you always saw the Evotouch during fetch. So if significant time has elapsed between uses of the PWA you'll see the deltas in your zone temps from session to session.
• The PWA will now detect kiosk/fullscreen mode on a tablet and request the tablet not to go to sleep. This means if you dedicate e.g. a wall-mounted iPad to the PWA it will stay active indefinitely.
• iOS devices will now ask for permission to show you notifications only after a few uses of the PWA. Apple used to block this because the PWA asked upon install. If you say yes then the PWA icon will show badges whenever your Evohome system has any faults and you'll get a push notification if the PWA version updates.
• Inside the PWA the status-bar at the top (around the notch) is now dark blue instead of white but it will switch to red if your Evohome system is reporting faults
• The cropping of the nicknames-section on iOS (which strangely was not an issue on macOS or iPadOS) is resolved.
• The PWA now respects the bottom pull-up bar area on iOS devices so is very slightly less fullscreen.
• A rewrite of the service-worker means it's now much more resilient with caching resources and also reserves much less cache (now 6-10MB).

In addition to this, the back-end behind both the PWA and the Alexa skill has been improved:

• All screens with a Slider have been modified so that the +/- icons around the slider-proper are clickable buttons.
• Several animations have been improved so as to be faster.
• The burst-logic for querying TCC has been rewritten to improve speed-of-response. There are now way fewer incomplete fetches when TCC is slow to respond.
• All out-of-bounds conditions on APL views have been resolved. Some Echo devices were more tolerant of small errors than others so not everybody noticed e.g. clipping of certain visual elements but they're now fixed anyway.

All in all, everything is faster and much more robust. Let me know if any issues show up.

[Midland45]

I’ve had a good test on Windows11/iPod pro/iPhone all on the lastest software versions and can see a vast improvement on the speed of loading across all platforms.
So excellent work again Phil, looks excellent on all screens