Hey,

For a long time I've run an AS to reduce the temp variable reported by NOAA to an integer,
e.g. 35.0 to 35, triggered by any change to it's variable.

Odd thing is now when it becomes for example 28.0 from any temp other than 28 it will work.
If it is 28 and it becomes 28.0 it apparently isn't seen as a change and the AS to reduce
it to an integer doesn't run.

Has something changed in v5 that would make it behave differently?

Thanks,

Carl

Yes, we added some changes recently so that if the values are numbers then they are compared as numbers in all cases (and not strings). So the trigger won't fire since 28 is numerically equivalent to 28.0.

A workaround for your case that I believe would work would be to create a new Indigo variable for the integral value. Then modify your trigger to read from the main value and put the truncated version into the new integral variable.

Thanks Matt. What I ended up doing was triggering off
any change in the last update variable...works fine.

Carl

Well, I thought it was working fine. Occasionally the temp will update without
any change to the Weather_Update_Time variable, which is what I've been triggering
the integer fix from.

Any chance that an option could be included sometime to look for ANY change to a variable?

Not sure I'm understanding you suggestion above about using a second variable.
If Indigo can't recognize the difference between a 10.0 or a 10 what should I be
triggering from?

Thanks,

Carl

ckeyes888 wrote:Not sure I'm understanding you suggestion above about using a second variable.

The point is to have 2 variables:

Weather_Temperature_F, which contains the raw real (floating point) precise number.

Weather_Temperature_F_int, which contains the integer version.

It sounds like you want the integer version for whatever reason, so everywhere that you are currently referencing (control pages?) Weather_Temperature_F you would instead reference Weather_Temperature_F_int.

Then all you have to do is create a trigger for whenever Weather_Temperature_F changes have it stuff the integer version of the variable into Weather_Temperature_F_int.

ckeyes888 wrote:If Indigo can't recognize the difference between a 10.0 or a 10 what should I be
triggering from?

In that case it doesn't matter if it doesn't trigger. Weather_Temperature_F_int will still have the correct integer value in it for the last time it did trigger (when there was a real change).

Yet another Doh! moment.

Thanks,

Carl

Guys, would you be able to advise how or what to set the Weather_Temperature_F_int variable

Then all you have to do is create a trigger for whenever Weather_Temperature_F changes have it stuff the integer version of the variable into Weather_Temperature_F_int.

In Python:

Code: Select all

intValue = int(float(indigo.variables[FLOAT_VAR_ID].value)) # ID of "Weather_Temperature_F"
indigo.variable.updateValue(INT_VAR_ID, intValue)           # ID of "Weather_Temperature_F_int"

In AppleScript:

Code: Select all

set intValue to value of variable "Weather_Temperature_F" as integer
set value of variable "Weather_Temperature_F_int" to intValue

Brilliant, thanks for that Jay...