How to modify the AC tile from the auto template to work with the nest driver?

[ghurty]

I am trying to modify the auto generated v2 template for the dummy AC unit to work with the nest driver. I go the overlay page to work. THe place where I am having problems is with the tile.

How would I change the coding so that the up/down arrows will work for the different fields? I changed where the data is displayed, so that part works. But if I cant figure out how to change the arrows. All I was able to do was set it for one field (low set temp, for example), I cant make it dynamic.
Here is how I have it for one field.

Code:

// Ask the variable to move to the prev value
Devices::FieldWrite
    P1=Nest.IncrementTargetLowTemperature_Nest
    P2=1
    P3=True

Devices::FieldRead
    P1=Nest.TargetLowTemperature_Nest
    P2=GVar:ThermoTileVal
    P3=True

// Update the edit value display
ThermoTileVal::SetText
    P1=%(GVar:ThermoTileVal)

// If the new and org values are different, show the set button
If System::Equals
    P1=%(GVar:ThermoTileVal)
    P2=%(GVar:OrgThermoTileVal)
    P3=Case

ThermoSetButton::SetWidgetState
    P1=Hidden

Else
ThermoSetButton::SetWidgetState
    P1=Normal

End

Thanks

[Dean Roddey]

If you look at how the auto-generated content is doing it, it's storing the last selected value and its field in global variables, so it knows what to adjust later when the up/down and set buttons are pressed. So you'd have to do the same.

One way that is often convenient to do these things is to create one or more string variables with enumerated ranges, and put the values you want to cycle through in as the range values. Enumerated variables react to one of the variable target commands (forgetting the exact name) that asks them to move to the next/previous value (with our without wrap around.)

So you can create these variables, let the prev/next buttons just call that previous/next value command on the variables allowing them to wrap. That's an easy way to create those sorts of lists and run through them. I'm not in a position to look right now, but probably that's how I'm doing it in the auto-generated content.

[ghurty]

Thank you. I believe that is how you did it there.
Where do I create the string variables? And while that would work for modes, etc.. how would it work for numbers (temperatures)? It doesnt make sense to add all the possible temperatures as variables.

Thank yo

[Dean Roddey]

That same command will actually also work on a signed or unsigned numeric variable as long as it has a range limit on it.