I'm currently migrating from Lowe's Iris it seems there's a lot to digest. I just added my radio thermostat CT 101 and trying to create a working dashboard. I have it, but all it displays is the current temperature and does not allow me to make any changes to the temperature. I'd like to be able to be able to go through all of the controls with fan on or off, temperature up or down or a hold function.
Once I can accomplish this I'll move on to my door locks.
In the meantime, if you want to add up/down capability, you can do this by creating two virtual buttons, then some rules associated with them. Here's what I have:
Thanks for the quick reply. I was hoping the transition would be a little bit easier but I'll have to learn how to jump through some of these hoops. The good point is that it seems the community here is very active and helpful.
I'm pretty sure everyone wants this. Iris and Hubitat/SmartThings are a big change. Iris and Wink and others that have fallen to the wayside have tried to limit the user experience to ONLY what they, the developers, can do. No matter how dedicated and productive they are, ultimately they are unable to keep up. Hubitat followed SmartThings in this regard and neither try and prevent users from participating in improving their experience.
Because Hubitat and SmartThings have a common coding language and nearly identical API's all of the SmartThings community is inadvertently helping to improve Hubitat Migrating a SmartThings app or driver is usually quite easy. Many of us have migrated code in 2 mins or less. That's NOT to say every app or driver can migrate quickly, but many can and just as important, even if the code itself won't migrate, often the concepts do.
For many Iris users, there's a lot to acquaint oneself with.. first in terms of the UI. Automation has so much more potential, which always means too many options (using unfamiliar words.)
Had we known months in advance that Iris would slam shut with very little warning, we, the community might have been able to offer many more Step-by-Step suggestions (recipe?) We were caught by surprise too.
I just found your tip, and I have it working , kinda. I have a temp sensor and a switch for my heating for this thermostat. How can I link them to the thermostat?
I setup a virtual thermostat and used your example. my temp sensor is a device on a Arduino and there is a relay on the arduino to turn on a pump for a hot water system. They both are devices on the HE. How can the virtual thermostat read the temp and control the relay. I have been looking for a way to do this for a couple of weeks now.
I found a APP from Cobra Apps called AverageAll That allowed me to link the sensor to the Virtual Thermostat, so that is working. I just need to be able to turn the swtch on and off.
The Sharp Tools app seems to do what I want. It has been a bit of a bumpy ride so far but hopefully things smooth out. I "believe" that you have some of the first gen items so maybe things will be more of a P-N-P in time.
Use rule machine, probably two triggers. One when temp is below a certain level, turn on the relay. Second when temp is above a certain level, turn off the relay.
How would that work when the thermostat setpoint changes. set the rule to monitor the "status"? When it indicates heat turn on the relay and when it goes idle turn it off? That sounds like a plan in theory, now I need to wait until tonight before I can test it. Dang work!!
You were right Chris, a couple of triggered rules did the trick. The only issue and not a big one is that when dropping the temp down past the set point the relay will go from on to off about 3 times then finally off.
I guess I spoke too soon. Where do I 'LINK' the temperature sensor to the virtual thermostat? The temperature is always at 30 degrees. I like the new thermostat tile and probably will use that. Now that spring is here I probably won' t need this, but i live in Mich. so we could still get snow LOL
Iris and Hubitat/SmartThings are a big change. Iris and Wink and others that have fallen to the wayside have tried to limit the user experience to ONLY what they, the developers, can do. No matter how dedicated and productive they are, ultimately they are unable to keep up. Hubitat followed SmartThings in this regard and neither try and prevent users from participating in improving their experience.
