ok looking at those logs you haven’t deployed the Device Handlers only the smartapp. please follow the instructions int he the following link on how to correctly install the smart app and device handlers.
FYI
I have the following in my kit, so i don’t think you will have any issues,
1 x Extension Kit
2 x Smart Thermostat
7 x Radiator Valves
1 x AC Thermostat
as for you @mrsbaaa in regards to your feature request regarding Fan speed on the AC device, i am aware of the shortcoming of the device handler when setting temp this will reset the Fan to either High or Automatic dependant on the device capability. there would be a need of another function to check the existing fan speed and substitute that value. to be completely blunt, i have no time available to work on this or test for the foreseeable future due to other commitments. but you are welcome to modify/amend the code as you see fit, if you wish to have your changes submitted to the main repo once you have tested, please create a pull request in Github and i will review/test and give credit to the source code notes.
FYI, In the past 3 years, I have built the ScheduleTstatZones & ecobeeSetZoneWithSchedule smartapps which allow you to create zones inside your home for more targeted heating/cooling.
I’ve recently modified ScheduleTstatZones & ecobeeSetZoneWithSchedule to be able to control more effectively any room eTRVs with the standard thermostat capabilities.
In the ScheduleTstatZones smartapp, you can configure your rooms/zones/schedules. You then associate your zone/room thermostats to your zones and schedule your zones during the day.
In your home, you don’t always want to heat/cool all your rooms. In the evenings or at night for instance, you may want to direct more heat to your bedrooms.
The smartapp lets you choose a master thermostat which controls other slave (zone/room) thermostats in terms of mode and setpoints. The thermostats need to follow the ST standard capabilities.
You can also define enter some delta temp adjustments to make some specific zoned rooms cooler or hotter. You can also use your room’s motion sensor to take into account if the room is occupied or not. The occupied threshold can be defined on a room by room basis for more flexibility.
There are many other features, refer to the ST community wiki for more details:
True, already using the sensors in Webcore. However first try, I had some error activating the auto mode. Could be due to connection loss. Using ifttt now to set the heatpoint.
Something I would like to implement in my system is set the heatpoint to +1 degree above dewpoint for away mode. I can set dewpoint, but can’t find how to add a safe offset. For now, I’m stuck with a fixed average dewpoint temperature. Anyone an idea how to implement basic math in webcore or force an offset? Not that it will make a huge difference, but it’s what a smart system should do.
Ignore post above. Think I just finally figured it out myself. Should check every 15 minutes to keep the lowest possible temp without risking dew. For some misterious reason, plus in the expression box didn’t work. Not understanding what I did wrong, using a double negative did the trick.
Will give the direct actions another shot in this one and lay off IFTTT. So far so good, much faster responsetimes.
Sorry if this question seems stupid. I am fairly new to this. Is there anyway to set-up heating automation? My tado is in the hall but I really like the heating to be controlled by the temperature in the living room. Can I leave a motion sensor in the living room, if the temperature drops below a certain degree, Tado switch on the heating and vice versa.
Hi, just to let you know, there is no way to implement the concept of rooms/zones & schedules in webcore the way I did it in ScheduleTstatZones (even if the rule engine is quite powerful) as my smartapp has close to 5000 lines of code…
This logic is impossible to reproduce in a smart rule engine, and the performance would not match ScheduleTstatZones in any case.
Would it be possible to add the other “Manual” option that tado uses? when in the app I can set it if manual mode is activated it will return to automatic after 30 minutes? We use actiontiles and I don’t want to kids setting the heating high and then it just being left at a high temperature.
@SamB the reason i didnt put this in was because ST has easy way to select different timeframes (as the default values for settings dont work) for the method, and if say for example i chose an arbitary value such as an hour without having an override then this would not be right for a lot of people. and if i provide a way to override the default timeframe in the smartapp there would be no way for me to set a default value as this option doesn’t work in ST’s groovy code (admittedly i havent checked this recently but AFAIK this is still a bug). and if people dont have timer selected as the mode they want to reset then i think it introduces a usability issue forcing them to select a timeframe for a setting they dont use before they can install the application.
so thats why i introduced Tado_Mode as the option so if you use the tado schedule predominantly this allows you revert back to the tado schedule when the mode changes in that schedule.
however if you want to enforce an override to have a blanket change to override the mode change back then this can be done using other tools for example webcore can run the endManualControl function on the Tado Thermostat when the TadoMode attribute has been “MANUAL” for more than x minutes.
this would have the desired effect for your use case
Is there a bug in the current smartapp code? I publish the smartapp and when I start it up in the SmartThings app, I get the window asking me for Tado login information and after submitting that I just have a blank white screen, and a error message:
