Indigo Domotics

At the moment, if you want an action based on a specific number e.g. set a true/false variable if the temperature is above 15C, you need three triggers, one for greater than, one for less than and one for equal. Having a greater than or equal and a less than or equal would solve this.

Based on your example, I'm not sure I understand. Regardless, I'd suggest doing all this with one trigger using a Python conditional.

I'd be happy to help you write one.

pnm wrote:

At the moment, if you want an action based on a specific number e.g. set a true/false variable if the temperature is above 15C, you need three triggers, one for greater than, one for less than and one for equal. Having a greater than or equal and a less than or equal would solve this.

I think you only need 2: one with a condition of greater than 14 (which will include 15 and above) and one less than 15 (which will catch everything 14 and below). Right?

In any event, as@ DaveL17 suggests a simple Python script would probably be best with just a single trigger.

It was this part of the GUI I was referring to:



So I want the variable true if over 15 or false if 15 or less. A Becomes Less Than or Equal would mean I just need two triggers

You can do it in 2 by using Becomes Less Than 16...

Thanks

As an aside, I was using a trigger as I couldn't work out the syntax to get the value from the device using indigo.devices["System..Weather.ForecastToday"], this is the structure

Right-click on the device and select Print Device Details to Event Log. Then copy/paste the text (not a picture) from the Event Log into a reply and we can figure out how to get the value out in a script.

Thanks for your help, I've got the answer from another post, I'd missed the second set of brackets so it should be:

indigo.devices["System,Weather.ForecastToday"].states["tempmax"]

.

You should use the ID of the device, not the name, in case you change the name in the future (the ID will never change).