multiAttributeTile : VALUE_CONTROL

[RBoy (www.rboyapps.com - Making SmartThings Easy!)]

Earlier behavior and workaround:

Android 2.0.8 - Release Notes - 1/26/2016

Here are issues I’ve reported already for reference: Okay so here are MORE bugs: When using the VALUE_CONTROL type “thermostat” tileAttribute("device.temperature", key: "VALUE_CONTROL") { attributeState("default", action: "setTemperature") } Now it finally shows up (it wasn’t in 2.0.7) but it behaves differently from iOS. iOS return 0 or 1, Android returns a +ve or -ve value depending upon how many times it’s been called! How the heck is a developer supposed to write an app when the same function behaves differently on 2 different OS’s and there’s no documentation on it. I can’t even identify if the app is iOS or Android programatically in the app. This is really the height. @Jim looping you, please document the expected behavior of VALUE_CONTROL

Android 2.0.8 - Release Notes - 1/26/2016

A temporary hack: // Determine OS intended behaviors based on value behaviors (urrgghhh.....ST!) def upLevel if (!state.lastLevelUpDown) state.lastLevelUpDown = 0 // If it isn't defined lets baseline it if ((state.lastLevelUpDown == 1) && (value == 1)) // Last time it was 1 and again it's 1 its increase upLevel = true else if ((state.lastLevelUpDown == 0) && (value == 0)) // Last time it was 0 and again it's 0 then it's decrease upLevel = false else if ((state.lastLevelUpDown == -1) && (value == -1)) // Last time it was -1 and again it's -1 then it's decrease upLevel = false else if ((value - state.lastLevelUpDown) > 0) // If it's increasing then it's up upLevel = true else if ((value - state.lastLevelUpDown) < 0) // If it's dec…