Evening all, it seems something has changed in the evohome API that not only is sending weird data out when queried through the (unofficial) API but also screwing with the iOS app (for me, at least).

I have a python script, based on work from this forum, that polls data from honeywell and logs it to an elasticsearch database. The script is still polling back the values for my named zones, but has also started pulling back a load of phantom zones with the temp all set at 62degC

Code:
22-02-2017 18:02:38 2512567  128.0 62.0
22-02-2017 18:02:38 2512569  128.0 62.0
22-02-2017 18:02:38 2512570  128.0 62.0
22-02-2017 18:02:38 2512571  128.0 62.0
22-02-2017 18:02:38 2512572  128.0 62.0
22-02-2017 18:02:38 2512573  128.0 62.0
22-02-2017 18:02:38 2512574  128.0 62.0
22-02-2017 18:02:38 2512575  128.0 62.0
22-02-2017 18:02:38 1673183 Boudoir 18.32 18.0
22-02-2017 18:02:38 1698354 Family+Dining 20.62 21.0
22-02-2017 18:02:38 1699881 Hall+Landing 18.97 18.0
22-02-2017 18:02:38 1673178 Kitchen 21.05 20.0
22-02-2017 18:02:38 1673176 Lounge 16.9 15.0
22-02-2017 18:02:38 1673179 Main Bedroom 17.66 18.0
22-02-2017 18:02:38 1673180 Spare Room 16.5 15.0
22-02-2017 18:02:38 1673182 Tom's Room 20.08 20.0
My database is ignoring the 'new' lines and only logging the valid data, but the iOS app is a little dumber, and is trying to parse those first 8 zones. As a consequence I get this:

evohome_borkage.jpg

I've tried uninstalling the iOS app and reinstalling it, but the issue is obviously at the Honeywell end.

Any suggestions? It's suspicious that it comes at the same time as their scheduled "maintenance"...