What is the āBest Practiceā when it comes to using āblankā Pistons as section headers?
So far, Iāve just simply been going in, naming it how I want it so that it goes where I want in the alphabetical list, and thatās it. Should I be using any specific Piston type for this, or do anything else, or is that OK?
The Dimmer has 4 buttons, each with a possible state of Pushed or Held.
I donāt know how you all do those lovely screenshots, as my CoRE SmartApp looks nothing like that, but hereās what Iāve got
IF
Button 1 is Pushed
(when true)
Using Bedroom Lights... Turn On (only on state change)
OR
Button 4 is Pushed
(when true)
Using Bedroom lights... Turn Off (only on state change)
OR
Button 2 is Pushed
(when true)
Using Bedroom light... Adjust level by 10% (only on state change)
OR
Button 3 is Pushed
(when true)
Using Bedroom light... Adjust level by -10% (only on state change)
OR
Button 2 is Held
(when true)
Using Bedroom light... Adjust level by 5%
OR
Button 3 is Held
(when true)
Using Bedroom Light... Adjust level by 5%
THEN
Set variable x to 1
So they all seem to work individually, but when I do the HELD options, it only executes onceā¦ I had expected unchecking the (only execute on state change) option to mean it would keep executing it until the button was released.
How can I do this properly, so that Holding in buttons 2 and 3, will gradually dim the lights up and down, and then stop when I release the button?
The graphic views of the pistons youāre seeing is from the CoRE Dashboard, see link below.
Regarding your piston, the tasks associated with a held button doesnāt cycle as far as I know. It will only register the held once and will repeat if you release and hold again.
@eibyer is correct ā a held button doesnāt cycle. Button press/held events donāt register until AFTER the button is released, from what I can tell
Soā¦ I modified the DTH to throw a āheldā event at the same time itās logging that itās been held, and the piston is firing now for the duration that Iām holding the button.
Are the triggers edge based? In other words if the trigger comes on is the piston only evaluated once until the trigger goes off and back on or is it continually evaluated while the trigger is on?
Has anyone been able to get TTS working with CORE lately? I have not been able to get anything to work with CORE but I am able to get it to work with other smart apps.
@ady624 Iām still stuck on this one. I just canāt get the global variable to work, even on a boolean flag.
I think it all come down to where should I initialize global variables? I did try on the Global Variables section but if I try to use now() the data type is set to string. Same when I try to initialize a boolean variable, if I put either True or true, when I do save it, I can see the data type as string. How can I initialize them with proper data type?
Does the wol option need more than just he MAC address to work?
I have mine linked to a virtual sensor that is a routine. It doesnāt workZ but when I use a iOS app it does. Only difference is the iOS app allows IP address.