All-in-One Scene: How to do it Better

[SmartLifeSystems 20]

5 hours ago, cag014 said:

That's strange...

Could you please post properties of one of the thermostats?

 

Is this what do you think?

 

Please login or register to see this attachment.

[cag014 628]

2 hours ago, SmartLifeSystems said:

 

Is this what do you think?

 

Please login or register to see this attachment.

Yes, thank you.

I think I fixed the bug... please download

 

 

Please login or register to see this attachment.

Edited August 22, 2021 by cag014

[Rover 45]

9 hours ago, cag014 said:

Let's try something interesting... download attached version and define state property using "+" sign..

{"`wDimmer`", {state="+centralSceneSupport=2.Pressed", trueAct={....}}},

Let me know if it works...

 

 

Please login or register to see this attachment.

It works! ?

[SmartLifeSystems 20]

8 hours ago, cag014 said:

Yes, thank you.

I think I fixed the bug... please download

 

 

Please login or register to see this attachment.

Nice, it working fine!

 

Thanks!

[Rover 45]

On 8/22/2021 at 9:48 AM, Rover said:

It works! ?

Hi @cag014,

Is this feature also on the HC2 backlog?

What is at the moment the difference in functionality between AOQ and AOS?

Is AOR intended to replace AOS and AOQ?

[cag014 628]

On 8/23/2021 at 3:32 PM, Rover said:

Hi @cag014,

Is this feature also on the HC2 backlog?

What is at the moment the difference in functionality between AOQ and AOS?

Is AOR intended to replace AOS and AOQ?

Yes, right now I am testing that on HC2.

The only difference between AOS to AOQ, that AOS doesn't support slave controllers.

AOR same as AOQ, but runs on PC (or MAC). In addition you can define your own LUA functions using entire LUA library (like read/write files, execute programs and etc.)

[Rover 45]

On 8/17/2021 at 9:52 PM, Rover said:

@cag014 please advice.

?

[SmartLifeSystems 20]

Hi cag!

 

We can use Alexa for TTS message? What do you think?

[Rover 45]

Fibaro Switch 2 can operate double press etc.

Parameter 28: S1 switch - scenes sent This parameter determines which actions result in sending scene IDs assigned to them. Available settings: 1 - Key pressed 1 time 2 - Key pressed 2 times 4 - Key pressed 3 times 8 - Key Hold Down and Key Released Default setting: 15 (all) Parameter size: 1 [byte]

But in HC2 sceneActivation for this device is not accepted (and also not in the property interface). In a scene sceneActivation is accepted for this device.

Problem looks the same as with the Walli dimmer.

Edited August 27, 2021 by Rover

[Rover 45]

On 8/28/2021 at 1:18 AM, Rover said:

Fibaro Switch 2 can operate double press etc.

Parameter 28: S1 switch - scenes sent This parameter determines which actions result in sending scene IDs assigned to them. Available settings: 1 - Key pressed 1 time 2 - Key pressed 2 times 4 - Key pressed 3 times 8 - Key Hold Down and Key Released Default setting: 15 (all) Parameter size: 1 [byte]

But in HC2 sceneActivation for this device is not accepted (and also not in the property interface). In a scene sceneActivation is accepted for this device.

Problem looks the same as with the Walli dimmer.

Also Fibaro Switch 2 has a child device RemoteController, like Walli Dimmer, which has centralSceneSupport. Using this device for triggering is fully functional. So for me no adaptation for AOS or AOQ is needed.

Edited August 29, 2021 by Rover

[cag014 628]

On 8/26/2021 at 10:51 PM, SmartLifeSystems said:

Hi cag!

 

We can use Alexa for TTS message? What do you think?

There is a way to use Alexa, but  as far as I know you need QA and web server for that.

Please see 

I sill think using Android tablet or phone is a the simplest solution at home environment.

Edited August 29, 2021 by cag014

[Rover 45]

Please login or register to see this spoiler.

 

[cag014 628]

7 minutes ago, Rover said:

Please login or register to see this spoiler.

 

Edited September 16, 2021 by cag014

• Quote

[Rover 45]

2 hours ago, cag014 said:

Are you sure?

Could you please post device's API property?

Another point ,  how come the timestamp is earlier the previous?

Please login or register to see this spoiler.

Please login or register to see this attachment.

It is indeed peculiar that the timestamp is earlier than the previous. It is the visualisation of webEye, I have no idea.

[Rover 45]

Please login or register to see this spoiler.

 

Edited September 18, 2021 by Rover

[cag014 628]

Due to timeSlot definition, when the slot is started (in your case at 15:00 ) the line initialized (as at the program startup). 

Please login or register to see this spoiler.

 

Since you didn't post the entire jM line, I guess the falseAct executed.

To prevent initialization  by time range please define in jM line - InitOnStartup=false

To my opinion you should leave that as is,  because when the time reaches time range it should be initialized to the current values and not use last values as recorded at the end of the time slot ( at 22:00 day before, in your case)  to continue to work properly as defined by the jM line.

This is the same as you executed AOQ - you do expect that the lines will be updated to the current values of all devices in the system

 

Edited September 18, 2021 by cag014

[Rover 45]

17 hours ago, cag014 said:

Due to timeSlot definition, when the slot is started (in your case at 15:00 ) the line initialized (as at the program startup). 

Please login or register to see this spoiler.

I do not want to have the time range as trigger, but as condition!  The InitOnStartup=false has effect by rebooting AOQ (or not?). So how to prevent that the the time range is executed as trigger instead of condition ?

BTW, when the jM was triggert on time range no email was sent, but when the jM was triggert on light value the email was sent.

Edited September 19, 2021 by Rover

• Quote

[cag014 628]

3 hours ago, Rover said:

After putting all the light off manually, after reaching the light level, all lights have been turned on as desired:

Please login or register to see this spoiler.

It's written in user guides... and the option is there since the first release. The time range is not a trigger, just at the beginning of the time range the values refreshed... (as on startup) the reason for that while the line out of time range, the values of the devices not updated. When  the time range starts, the AOQ refreshes the devices to get their current values and execute the actions accordingly, otherwise it depends on changes and might miss the current status.

 

The time range is not considered as a condition, but as a time rule of the line. To set time range as a real condition, use conditions states. In this case the value of the devices are updated as usual.

In your case just add to lineState as follow

lineState=" if {$24clock:value=15:00~22:00 and ......

 

There are many options to set time range condition for actions, one of them to limit specific action to the time range like:

{"402","turnOn","15:00~22:00"} (instead of delay set time slot)

 

Of course you can set time range condition for every action table:

trueActState="if {$24clock:value=15:00~22:00}"

falseActState="if {$24clock:value=15:00~22:00}"

.....

....

 

 

 

 

 

 

[Rover 45]

12 hours ago, cag014 said:

It's written in user guides... and the option is there since the first release. The time range is not a trigger, just at the beginning of the time range the values refreshed... (as on startup) the reason for that while the line out of time range, the values of the devices not updated. When  the time range starts, the AOQ refreshes the devices to get their current values and execute the actions accordingly, otherwise it depends on changes and might miss the current status.

 

The time range is not considered as a condition, but as a time rule of the line. To set time range as a real condition, use conditions states. In this case the value of the devices are updated as usual.

In your case just add to lineState as follow

lineState=" if {$24clock:value=15:00~22:00 and ......

 

There are many options to set time range condition for actions, one of them to limit specific action to the time range like:

{"402","turnOn","15:00~22:00"} (instead of delay set time slot)

 

Of course you can set time range condition for every action table:

trueActState="if {$24clock:value=15:00~22:00}"

falseActState="if {$24clock:value=15:00~22:00}"

.....

....

 

 

 

 

 

 

TNX @cag014 for the extensive information about time range. Now it is clear to me. Also attention for the value of the prefixes is an eyeopener.

Even when using AOS and AOQ for a long time, you can still learn a lot ?

AOQ is a marvelous creation ?

Edited September 19, 2021 by Rover

[cag014 628]

Guys, have released the AOR ( Remote All-In-One) which runs on PC... waits for Fibaro's approval.

Although I do have HCL, but just with one device, so  may I ask HCL users to try it and give back feedback... finally you can use LUA including full functionality and library. (write/read files, execute programs on PC and etc.)

Edited October 17, 2021 by cag014