This is the forum archive of Homey. For more information about Homey, visit the Official Homey website.

The Homey Community has been moved to https://community.athom.com.

This forum is now read-only for archive purposes.

Tado thermostat

18910111214»

Comments

  • OpenMind_NLOpenMind_NL Member
    edited February 2018
    jpcouprie said:
    Tested the 2.0 version.
    I have created the following flow see attachement
    To let is work I have to use the NOT in the condition.
    So the the part is done when I select the NOT in the condition


    Edit: function not stable, after making a change in the condition it works or not,.
    Some flows are working normally and someneed the NOT.


    Question: Which temperature setting is used : the value before the trigger is fired or the value #temp (trigger tag)

    Assuming that the 'Verwarming...' devices in the trigger, condition and action cards are all for the same tado-zone...

    -  Your flow is triggered once when the target temperature setting is changed.
    - The flow-condition will be true when this target temperature is NOT between 6...21 degrees. So the upper flow-actions will only be activated when you set the target temperature to 5 degrees or to 22 degrees or higher. Any temperature setting from 6 to 21 degreees will activate the lower (Anders) flow-actions.

    The temperature that is used by the trigger will be the temperature that you set it to. 

    So when you change the  temperature setting from 23 to 21 degrees, the flow-token '#Temperature' will offer the number 21.
    ... the condition-card will activate the lower actions (Anders) in your flow. 
    21 = between 6 and 21, but the check mark in the condition card makes it valid when the value is NOT between 6 and 21.
    When you set the temperature again, for example to 19 degrees, the flow will trigger again, and again the lower actions will be activated. When you then set the temperature back to 23, the flow will trigger, but this time the upper actions will be triggered. (setting is not between 6 and 21)

    So... as I read your flow...
    - If you set the temperature somewhere between 6 and 21 degrees, the zone 'Verwarmin...' in the lower actions (Anders) will be switched off (= set to 5 degrees). If that is the same zone as the zone for the trigger card, it will switch ITSELF to 5 degrees!
    Then the flow will trigger again because of the 5 degrees setting... and activate the upper action cards... because now the setting is NOT between 6 and 21 anymore, which makes the condition card valid.

    Also: the number variable 'Verwarming E(ntree?)' will NEVER get the values 6 to 21 because the upper actions will only be activated when the temperature is set to 5 or to 22 (or higher) (= not between 6 and 21).
  • @OpenMind_NL ;
    Thx for the info. Restructuring flows. Till now no errors.
  • ok, i will change to 200 meters for test in the tado-app.

    status at the moment:
    homey app distance home area in homey-app: 115 meters
    and
    in tado-app: 400 meters

    i get simultan push mesages by homey with this 

    so when i will make 200 meters in the tado-app it should be a little bit before homeys own push message.

    i will test ;-)
  • OpenMind_NLOpenMind_NL Member
    edited February 2018

    NOTE:

    This isn't mentioned in the app's documentation but in case you didn't discover it yet... There are some Insights available for mobile devices. You'll not find them with the 'Home' device but with the 'tado' device. Because of a small imperfection of Homey it is not possible to show these Insights with the 'Home' device (yet?).

    As soon as the Location-based control for a phone/tablet is enabled, the logs for that device will be created and appear at Insights... and stay available as long as the mobile device is registered with your tado account. 

    The Insights for a mobile device will be deleted when you remove the device from your tado account at `Settings - People - YourAccount - Mobile Devices`
  • edited March 2018
    It seems to me this app is showing some weird behavior... After installing it on a Freshly installed Homey (did a factory reset this morning) I can see the CPU load of the homey increasing heavily...

    When I install the "Homey Logger" app it shows output like you can see below, and it just keeps on going and going and going and going.... Perhaps the developer of the app can change the polling intervals or something? Don't think it's necessary to poll the Tado devices so frequently (look at the timestamps!)

    ////edit: 

    After uninstalling the app the cpu load is decreased a lot.
    Hope this problem can be investigated because I do like the app :-)

    Date and timeComponentEventDetails
    3/10/2018 1:43:41 PM.099slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:40 PM.827slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:40 PM.823bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:40 PM.741woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:40 PM.084slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:39 PM.934Devices managerDevice.updateundefined
    3/10/2018 1:43:39 PM.932slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:39 PM.929bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:39 PM.921woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:38 PM.981slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:38 PM.633slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:38 PM.563bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:38 PM.256woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:37 PM.972slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:37 PM.604slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:37 PM.547bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:37 PM.249woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:36 PM.964slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:36 PM.595slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:36 PM.536bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:36 PM.234woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:35 PM.943slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:35 PM.586slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:35 PM.536bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:35 PM.226woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:34 PM.934slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:34 PM.581slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:34 PM.521bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:34 PM.218woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:33 PM.925slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:33 PM.581slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:33 PM.510bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:33 PM.208woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:32 PM.914slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:32 PM.575slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:32 PM.509bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:32 PM.341Devices managerDevice.updateundefined
    3/10/2018 1:43:32 PM.196woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:31 PM.915slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:31 PM.562slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:31 PM.442bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:31 PM.198woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:30 PM.903slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:30 PM.558slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:30 PM.424bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:30 PM.240woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:29 PM.886slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:29 PM.551slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:29 PM.411bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:29 PM.178woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:28 PM.878slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:28 PM.538slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:28 PM.403bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:28 PM.169woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:27 PM.867slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:27 PM.532slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:27 PM.401bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:27 PM.107woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:26 PM.857slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:26 PM.524slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:26 PM.385bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:26 PM.090woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:25 PM.839slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:25 PM.510slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:25 PM.374bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:25 PM.361Devices managerDevice.updateundefined
    3/10/2018 1:43:25 PM.086woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:24 PM.828slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:24 PM.492slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:24 PM.356bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:24 PM.078woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:23 PM.817slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:23 PM.486slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:23 PM.346bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:23 PM.061woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:22 PM.804slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:22 PM.486slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:22 PM.341bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:22 PM.058woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:21 PM.741slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:21 PM.473slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:21 PM.332bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:21 PM.046woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:20 PM.698slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:20 PM.465slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:20 PM.322bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:20 PM.036woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:19 PM.677slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:19 PM.453slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:19 PM.320bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:19 PM.022woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:18 PM.659slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:18 PM.438slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:18 PM.425Devices managerDevice.updateundefined
    3/10/2018 1:43:18 PM.296bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:18 PM.023woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:17 PM.645slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:17 PM.379slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:17 PM.288bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:17 PM.002woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:16 PM.632slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:16 PM.318slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:16 PM.277bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:15 PM.994woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:15 PM.700slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:15 PM.287slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:15 PM.223bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:14 PM.974woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:14 PM.615slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:14 PM.217slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:14 PM.200bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:13 PM.970woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:13 PM.606slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:13 PM.207slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:13 PM.188bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:12 PM.950woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:12 PM.596slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:12 PM.194slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:12 PM.178bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:11 PM.939woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:11 PM.579slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:11 PM.343Devices managerDevice.updateundefined
    3/10/2018 1:43:11 PM.184slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:11 PM.168bijkeuken (Thuis)Measure_battery30
    3/10/2018 1:43:10 PM.931woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:10 PM.576slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:10 PM.179slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:10 PM.164bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:09 PM.873woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:09 PM.562slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:09 PM.162slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:09 PM.123bijkeuken (Thuis)Measure_battery30
  • Polling interval unit (seconds vs milliseconds) error?
  • OpenMind_NLOpenMind_NL Member
    edited March 2018
    ////edit: 

    After uninstalling the app the cpu load is decreased a lot.
    Hope this problem can be investigated because I do like the app :-)


    Hey Robert,

    Could it be that you didn't remove all the devices (from an older version) when you installed v2.0.0?
    I can imagine that this could cause this strange behavior because things have changed in the device-polling.
    Nevertheless... I'm glad it seems to be working ok now.  B)

    Some extra information about the polling behavior of the tado-app:
    - Polling for Device data (like temperature) is done every 7 seconds
    - Device batteries: Every 60 seconds.
    - Home device, weather info: Every 30 seconds.
    - Home device, mobile phone/tablet data: Every 7 seconds, at the same time as device data.

    I choose the longer poll-intervals for less important data like batteries and weather to relieve Homey's CPU a little bit.
    tado's own web-app (https://my.tado.com/) seems to poll all data every 10 seconds. The 'Empty battery' email-warnings from tado are sent automaticly as soon as LOW is detected. Because Homey polls the batteries every 60 seconds, it is not unusual that you may get an email from tado before Homey detects a LOW... but it will always be within a minute.


  • Hi @OpenMind_NL, thanks for your response. The issue isn't gone, I just removed the app from my Homey... 

    I did not remove any devices before installing the app because it was a freshly installed homey (did a factory reset before). I have just installed the Tado app again and the frequent polling is still going on, the Homey logger app is being flooded with battery measurement events from the Tado app.

    Also when I check my devices the battery status keeps blinking from 30% to 0% to 30% to 0%.

    Do you've got any clue about what's going on? Or perhaps I can do some things for you so you can get additional logging, like run the app from the Atom CLI ? 
  • Also when I check my devices the battery status keeps blinking from 30% to 0% to 30% to 0%.

    Do you've got any clue about what's going on? Or perhaps I can do some things for you so you can get additional logging, like run the app from the Atom CLI ? 
    I just took another look at your first log and suddenly realized what's going on.
    This is what is logged every second:
    3/10/2018 1:43:10 PM.931woonkamer (Thuis)Measure_battery
    3/10/2018 1:43:10 PM.576slaapkamer achter (Thuis)Measure_battery
    3/10/2018 1:43:10 PM.179slaapkamer voor (Thuis)Measure_battery
    3/10/2018 1:43:10 PM.164bijkeuken (Thuis)Measure_battery
    3/10/2018 1:43:09 PM.873woonkamer (Thuis)Measure_battery30
    3/10/2018 1:43:09 PM.562slaapkamer achter (Thuis)Measure_battery30
    3/10/2018 1:43:09 PM.162slaapkamer voor (Thuis)Measure_battery30
    3/10/2018 1:43:09 PM.123bijkeuken (Thuis)Measure_battery30

    That is the blinking of the battey indicators!
    tado does not report an acurate battery status but only 'NORMAL' an 'LOW'. When the batteries get 'LOW', there's energy left for about a week (or a little longer).
    I made the battery indicator blink once a second between 0 and 30% to indicate this LOW-status.

    So:
    You have (almost) empty batteries in bijkeuken, woonkamer and two slaapkamers. 
  • Strange.... a light-blink causes a message to be send? Then better turn that blinking down to once every 30 seconds?
  • bvdbos said:
    Strange.... a light-blink causes a message to be send? Then better turn that blinking down to once every 30 seconds?
    The blinking is a change of the `measure-battery` capability every second. (0 - 30 - 0 - 30 etc.)
    A change once every minute would be confusing... you could think that the batteries are ok if you don't look at it for a minute.
    I used this blinking as a warning because the batteries are almost empty and really need to be changed.
    tado has no indication for batteries that are completely empty... it's just NORMAL or LOW. So if you wait too long, you might think that the batteries are almost empty when in fact they are totally empty.
  • The downside of this approach is the app is flooding Homey with messages, causing a big increase of cpu load when you have to replace batteries on multiple devices like I am gonna have to do right now...

    I think since you can't get a "real" battery percentage from the Tado API it would be best to just go with the information Tado provides you: normal, or low. 

    Just like you stated in your earlier reply: Tado is gonna send you e-mails to replace the batteries anyways so why don't leave it with that for now?

    We could make an improvement suggestion to Tado to provide percentages instead of "normal or low" status in their API of course.
  • OpenMind_NLOpenMind_NL Member
    edited March 2018
    I did it this way out of my own experience.
    I had almost empty batteries for one of my valves and decided to wait a while before changing them... and then forgot about them. The continues blinking battery indicator in the Homey app kept reminding me.

    I will see if I can think of another solution as I don't expect tado to change their battery notice to a percentage or something like that.
    I'm affraid I can only change this to a LOW or NORMAL indicator, which would mean a sudden change from full green to full red.

    About 'flooding': The battery-blink is just one very small data message for each device that has almost empty batteries, once every second. I would not call this flooding. When batteries are NORMAL, the blinking stops and data exchange will return to the usual intervals.
  • @RobertLijkendijk
    Could you check: https://developer.athom.com/tools/app-profiling and select `com.tado`?
    This will show you the CPU-use for the app during blinking. At this moment I have a value of about 2.5% in my Homey during normal use (no empty batteries)
  • @OpenMind_NL the app-profiling shows a cpu usage of 2,4% for the app... Although the app seems to have a low cpu usage it does seems to have a big impact on the cpu load of the Homey. 

    I use the Prometheus app to export Homey data and visualize it with Grafana. Have a look at the increased CPU usage after installing the Tado app (around 18:30), and the decrease after uninstalling it (at 18:50):


  • OpenMind_NLOpenMind_NL Member
    edited March 2018
    @OpenMind_NL the app-profiling shows a cpu usage of 2,4% for the app... Although the app seems to have a low cpu usage it does seems to have a big impact on the cpu load of the Homey. 
    I do not think the chart is really alarming. In spite of this, I think I will soon replace the blinking battery indicator with a steady green or red (100% or 0%).
  • Well you can see it going up from a pretty stable 0.5 to 1.5 and still increasing... You notice it in the responsiveness of the Homey interface as well... I am gonna make sure I'll replace my batteries but I think it would be good to just go with the information Tado provides <span>:smile:</span>
  • Does anybody faces this problem? As soon as Homey changed the temperature it sets a "manual" temperature. Which means the smart schedulde in Tado gets deactivated. I created a flow now to activate the Smart Schedule again after 2 hours. However I would like to set the temperature "Till the next automatic change" like the app does. I can't make a Flow which sets the "preset temperature till next automatic change" did anyone?
  • jovinkjovink Member
    Will it be possible to add flow card with “if hot water turns on/off”  to mesmerise the time of use of hot water? And maybe a And flow card as well? 
  • Update to 2.0.1  and I get a app failure, restarted the app, still in the app list, but all pairing is lost between Homey and Tado. And I only can add the Home and hot water zones, no tado room zones are found.

    In the release notes nothing about what is changed between version 2.0.0 and 2.0.1 .

    How can I roll back the Tado app version to 2.0.0?
    Or is something changed on Tado side?

    (Homey is currently also very slow, seems related, but don't know for sure).


  • @_Marco_

    I did have the same troubles, all connections were lost. 

    My follow up procedure:

    De-install Tado app
    Restart Homey
    Install Tado app
    Create devices in separate rooms

    It's ugly, I'm aware but couldn't find any other solution.

    Good luck
  • Same error again:  Too many memwarns received Usage:125MB
    This is the Candy app which notifies me from an app restart. And Homey which tells me that the tado app is crashed.
Sign In or Register to comment.