1) Give a description of the problem
I am transitioning from CoRE to WebCoRE, but one particular piston works in CoRE but not in WebCoRE
2) What is the expected behavior?
A double click on a fibaro switch should toggle a group of lights
3) What is happening/not happening?
Nothing seem to happen with this WebCore piston
4) Post a Green Snapshot of the piston
FYI, in CoRE, this works:
@Robin: I am using the “codersaur : Fibaro Dimmer 2” DH.
@WCmore: that wouldn’t be appropriate since the double click should turn them on if they are off and off if they are on. It works fine with CoRE
Does this log help?
_9/15/2018, 3:31:54 PM +805ms_
_+1ms +Received event [Lights Kitchen].scene = 14 with a delay of 91ms_
_+86ms ¦RunTime Analysis CS > 13ms > PS > 64ms > PE > 9ms > CE_
_+88ms ¦Runtime (37030 bytes) successfully initialized in 64ms (v0.3.107.20180806) (86ms)_
_+89ms ¦+Execution stage started_
_+101ms ¦¦Comparison (string) 14 is_equal_to (integer) 14 = true (2ms)_
_+103ms ¦¦Condition #4 evaluated true (7ms)_
_+104ms ¦¦Condition group #1 evaluated true (state did not change) (9ms)_
_+107ms ¦¦Cancelling statement #2's schedules..._
_+129ms ¦¦Executed physical command [Kitchen Hob 1].setLevel([0]) (14ms)_
_+130ms ¦¦Executed virtual command [Kitchen Hob 1].toggleLevel (18ms)_
_+147ms ¦¦Executed physical command [Kitchen Hob 2].setLevel([0]) (12ms)_
_+148ms ¦¦Executed virtual command [Kitchen Hob 2].toggleLevel (16ms)_
_+151ms ¦+Execution stage complete. (62ms)_
_+152ms +Event processed successfully (153ms)_
_9/15/2018, 3:31:31 PM +698ms_
_+1ms +Received event [46 Independent Place].test = 1537021891695 with a delay of 2ms_
_+114ms ¦RunTime Analysis CS > 23ms > PS > 75ms > PE > 16ms > CE_
_+117ms ¦Runtime (37047 bytes) successfully initialized in 75ms (v0.3.107.20180806) (114ms)_
_+119ms ¦+Execution stage started_
_+141ms ¦¦Comparison (string) 14 is_equal_to (integer) 14 = true (2ms)_
_+144ms ¦¦Condition #4 evaluated true (14ms)_
_+146ms ¦¦Condition group #1 evaluated true (state did not change) (17ms)_
_+149ms ¦¦Cancelling statement #2's schedules..._
_+175ms ¦¦Executed physical command [Kitchen Hob 1].setLevel([0]) (13ms)_
_+177ms ¦¦Executed virtual command [Kitchen Hob 1].toggleLevel (19ms)_
_+195ms ¦¦Executed physical command [Kitchen Hob 2].setLevel([0]) (13ms)_
_+197ms ¦¦Executed virtual command [Kitchen Hob 2].toggleLevel (17ms)_
_+203ms ¦+Execution stage complete. (85ms)_
_+205ms +Event processed successfully (206ms)_For starters, using ‘changes to 14’ is causing issues with repeated double clicks, as the 2nd time you double click, the scene is already 14 and therefore the piston wont fire… I prefer to use ‘on events’ + ‘switch’ cases for my dimmer scenes.
To toggle lights with a single scene ID, I like to use conditions, so if both lights are on, turn them off, otherwise turn them on. If a single light is on, it turns on the other one… using toggle could just invert which light is turned on.
Example piston below:
The above piston can monitor all of your scenes in a single piston…
