Z-Wave Thermostat incorrectly supports range of 0-100 for temp slider
Replaced slider UI with left/right arrow to change setpoints and made the
change methods a bit more robust.
Also replaced temperature tile with multi-attribute tile using thermometer icon.
Since we have been receiving a lot of reports and complaints about the
battery readings on the smartsense devices that received battery
updates (multi and motion), we are adding this code to smooth out the
readings so it doesn't constantly oscillate between two values. The
basic logic is, only create an event if we have two readings in a row
that are the same, or a reading is more than 100 millivolts off of the
current battery percentage.
* ICP-1103, ICP-1125, ICP-1194 CT Thermostat issues
- Added modes and changed mode names to reflect specification in thermostat capability
- Changed how device is initialized poll by sending all commands separated by 3 seconds
instead of sending a request and on its response send the next. This to give all
commands a chance in case one is dropped by the network.
- Reduced the time from 30 to 1 second between setting and requesting a setpoint
using the setHeating/setCooling method. This is now the same as changing using
the ST DTH tiles.
- Also modified the UI to use the multi attribute tile and using arrows instead of sliders
for changing setpoints.
* Update ct100-thermostat.groovy
ICP-1075, ICP-1215 Separate ZSMOKE from ZCOMBO and default detector DTH (assume supports smoke+CO if no explicit fingerprint), set initial states to clear
Adding support for dynamic thermostat and fan modes to TCC DTH.
Also replaced capability "Polling" with "Refresh" and runEvery5Minutes("refresh") as polling capability is unreliable.
Also removed capability "Relative Humidity Measurement" as Honeywell Z-Wave Thermostat (YTH8320ZW1007/U) doesn't support humidity.
Code brought oever from @varzac commit 8bcbe7b924
Original commit message:
> Fix sengled use of FF for max level
> This works around the fact that sengled element touches can get back
> into a state of reporting an invalid value (of FF) if the physical
> button on the bulb is used to cycle back to the 100% state. Here we
> interpret FF as FE for sengled and then issue a move to level command to
> put it in a state where it will report FE until the level is changed
> again.
>
> This resolves: https://smartthings.atlassian.net/browse/DVCSMP-2597
While the Classic does not have a physical button, since it does represent 100% as FF we want to always catch this.
