Results 1 to 5 of 5

Thread: Evohome API Changes and Broken iOS App

  1. #1
    Automated Home Jr Member WiteWulf's Avatar
    Join Date
    Mar 2016
    Location
    Leicestershire
    Posts
    40

    Question Evohome API Changes and Broken iOS App

    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"...

  2. #2

    Default

    The only user fix is to delete the location from the web-based account and then add it back. Seems to be some kind of server-side corruption to the account location.

  3. #3
    Automated Home Jr Member WiteWulf's Avatar
    Join Date
    Mar 2016
    Location
    Leicestershire
    Posts
    40

    Thumbs up

    Quote Originally Posted by SensibleHeatUK View Post
    The only user fix is to delete the location from the web-based account and then add it back. Seems to be some kind of server-side corruption to the account location.
    Thanks for the quick reply.

    That's no fix (from an IT point of view), but I'm not the DBA so I'll have to make the most of it and set everything up again. What a PITA!

    *edit*

    That worked perfectly, thanks again, and the existing "proper" zones all maintained their same index values so I've not had to update my polling script or logging/graphing system. Much less work than I was anticipating
    Last edited by WiteWulf; 22nd February 2017 at 07:49 PM. Reason: updated work

  4. #4

    Default

    No need to set anything back up - delete the location, then add it back (keep a note of the MAC and CRC) - should take less than a minute.

  5. #5
    Automated Home Legend
    Join Date
    Sep 2014
    Location
    Scotland
    Posts
    1,804

    Default

    Incidentally, just so that your script knows how to handle it if you see it in the future, a "measured temperature" of 128 is a valid response from the server - it means the temperature of the zone is currently unknown.

    This would happen after a controller reboot before fresh readings have been received from the sensors, which shows an hour glass on the controller or a double dash (--) on the phone app. (It would also happen if communication to the temperature sensor is lost for a long time due to a flat battery) The API reports 128 under these circumstances, so you probably don't want to try to graph 128 degrees literally.

    (I updated the evohome munin plugin to report heating zone measured values above 50 as NaN so 128 doesn't get graphed as a huge spike and auto scale the graph)
    Last edited by DBMandrake; 24th February 2017 at 09:41 AM.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •