Page 40 of 47 FirstFirst ... 303536373839404142434445 ... LastLast
Results 391 to 400 of 470

Thread: Decoded - EvoHome API access to control remotely.

  1. #391
    Automated Home Jr Member
    Join Date
    Jun 2017
    Posts
    48

    Default

    There is no pump with the heating from the solar PV, excess power is diverted to the immersion heater.

    Regardless, I can't see any explenation for the small variations, then large step. If the small variations are correct, there is no way the water could jump by 10 degrees in a minute or two.

  2. #392
    Automated Home Legend
    Join Date
    Sep 2014
    Location
    Scotland
    Posts
    2,193

    Default

    Quote Originally Posted by RichardP View Post
    There is no pump with the heating from the solar PV, excess power is diverted to the immersion heater.

    Regardless, I can't see any explenation for the small variations, then large step. If the small variations are correct, there is no way the water could jump by 10 degrees in a minute or two.
    I'm out of ideas then. I don't see any small oscillations in my hot water data, and I've looked over the data as a CSV.

  3. #393
    Automated Home Legend
    Join Date
    Jul 2014
    Posts
    1,308

    Default

    If it is any help, I see these variations as well when solar is heating the water using the immersion heater. I never see these fluctuations when the HW is heated by Evohome and the boiler.

  4. #394
    Automated Home Jr Member
    Join Date
    Jun 2017
    Posts
    48

    Default

    Quote Originally Posted by bruce_miranda View Post
    If it is any help, I see these variations as well when solar is heating the water using the immersion heater. I never see these fluctuations when the HW is heated by Evohome and the boiler.
    Interesting. I see the variations at night, when there is obviously no heat input so it can't be as simple as being related to an alternate heat source.

    The ImmerSUN that I have uses some sort of sin wave modulation to allow the immersion heater element to be fed variable amounts of power, up to its rated power, depending on how much excess solar energy there is that would otherwise be exported. I wonder if there is some sort of interference that's being picked up by the sensor in the cylinder? I'll try turning the ImmerSUN completely off and see if the variations still exist. I should say that I also get similar variations on the other zones, but these don't stand out as anomalies as the reporting interval is much shorter.

  5. #395
    Automated Home Jr Member
    Join Date
    Jun 2017
    Posts
    48

    Default

    Just to keep the thread updated, I've found the reason for the jitters on the recorded temperatures.

    It seems that the old Evohome client for the V1 API does not like being logged into too frequently. As I had two PCs running and my code was logging in for every query, that was too much for it and the login failed. Under those conditions the V2 API temperature was used which, unless the actual temperature was exactly on the degree or half degree caused a difference in the reading. On the next read the V1 API login succeeded and so another difference was logged. The V2 API login does not appear to have the same login limit, unless the two are linked as the V1 login was done after the V2 login.

  6. #396
    Automated Home Legend
    Join Date
    Sep 2014
    Location
    Scotland
    Posts
    2,193

    Default

    Quote Originally Posted by RichardP View Post
    Just to keep the thread updated, I've found the reason for the jitters on the recorded temperatures.

    It seems that the old Evohome client for the V1 API does not like being logged into too frequently. As I had two PCs running and my code was logging in for every query, that was too much for it and the login failed. Under those conditions the V2 API temperature was used which, unless the actual temperature was exactly on the degree or half degree caused a difference in the reading. On the next read the V1 API login succeeded and so another difference was logged. The V2 API login does not appear to have the same login limit, unless the two are linked as the V1 login was done after the V2 login.
    Interesting.

    How often are you calling the API ? On my graphing I only poll for temperatures once every 5 minutes. (Well, twice every 5 minutes actually as I graph independently with both Munin and Domoticz)

    Also are you calling the API separately for every zone or just making a single API call for all zones ? The munin plugin I use uses local caching so that the first zone the plugin queries calls the API and saves the results in a cache for 4 minutes, the remaining zones that are queried a moment later read their data directly from the cache without additional API calls. I think Domoticz does something similar too.

    Ideally you should limit your API calls to each API to no more than one call every 5 minutes.

  7. #397
    Automated Home Guru
    Join Date
    Dec 2016
    Posts
    181

    Default

    Don't really understand. Why do you do a login for every request for information? How often do you do it?

    The python scripts that link to Domoticz prevent you from contacting the server within less than a minute from the previous contact. I've not heard anyone stating they had similar issues as you. As these scripts are single run instances, these users have no choice. You on the other hand are running some service like application and I'm just realizing you said something before about destroying the Class. Don't! Keep the Class loaded. You can re-use the session (and login) information for a full hour. All you need to do is refresh the changed information: in the UK/EMEA API that is get_status() and in the US 'v1' API full_information(). My suggestion is that you do not wait for Honeywell to tell you that the session ID is no longer valid though. Set a timer and rerun the login() method just before it ends.

  8. #398
    Automated Home Jr Member
    Join Date
    Jun 2017
    Posts
    48

    Default

    My initial implementation created the Evohome objects and destroyed them every minute, running on 2 devices that's 2 logins on each API every minute. I did it like that initially because the older version of the Evohomeclient object threw if you tried to get the status and the session had timed out. It was just easier at the time and not meant to stay that way.

    I've now changed the code so it detects when the sessions have timed out and logs in again. Now I don't have the issue with the old API saying too many log in requests even with 2 devices running.

    Just giving a bit of information that might help others.

  9. #399
    Automated Home Legend
    Join Date
    Sep 2014
    Location
    Scotland
    Posts
    2,193

    Default

    Polling every minute still seems a bit excessive. How far do you think the temperatures will change in one minute ? I'm pretty sure I've seen a post on here before from a Honeywell employee asking for the API to not be queried more than every 5 minutes.

    Keep in mind that temperature sensors in the system (apart from the built in sensor in the Evotouch) only report in to the controller once about every 4 minutes. So you won't see changes in temperature every minute even if the room is in the process of heating up or cooling down.
    Last edited by DBMandrake; 1st July 2017 at 08:27 PM.

  10. #400
    Automated Home Jr Member
    Join Date
    Jun 2017
    Posts
    48

    Default

    I agree that temperatures are unlikely to change much in a minute, but things like overrides can be set at any time. So to log the current state you have to poll frequently. That's the inherent problem with a polling system, to catch random events you have to poll far more frequently than might be desirable on the server end. Some sort of local multicast or targeted UDP would be more efficient for a local monitoring station.

    However, remember I've only had the program successfully receiving data for about a week, there is bound to be plenty of fine tuning required.

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
  •