yvesracine
(Yves Racine)
July 21, 2020, 2:39pm
1207
pavichokche:
@yvesracine How would your app use my sensors to drive the thermostat while ignoring its own temperature reading? Does it constantly augment the hold set point based on the thermostat’s current reading so that it keeps the heating/cooling running long enough for my ST sensors to reach the desired temperature?
Also, what will happen to your app once the ST Classic platform gets shut down? In the next year or two?
Hi, everything is explained at the ST community wiki (under supported features and use case #1 ). For your use cases, you have to remove your remote sensors participation in the Night’s comfort settings and configure the ones you wish to use instead in the zoning smartapp.
https://thingsthataresmart.wiki/index.php?title=EcobeeSetZoneWithSchedule#Supported_Features
About your concerns about the ST classic mobile app, I believe that SmartThings will not totally shut down the ST classic mobile app as Smartthings itself relies on it for any hubAction related DTHs (Device Type Handlers).
All custom DTHs rely on the ST classic mobile app for the moment…
I’m also following the CLI thread, and hopefully, there will be a migration path for the custom DTHs.
Overview
At SmartThings we want to provide tooling to allow developers to get their device integrations working in the SmartThings app. These changes will allow an integrator to move from using custom commands and attributes to custom capabilities.
DTH Migration For Custom Capabilities
In order to follow along with the example set forth in this guide, you will want to have the CLI set up, so make sure that you take this step first.
You can download the CLI here from the releases tab and read more about it in the README .
It is also recommended that you familiarize yourself with the concepts:
Custom Capabilities
Capability Presentations
Walkthrough
We are going to walk through a simple example of updating our Device Type Handler (DTH) so that devices installed with the DTH will be …
Regards.