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

[gggizmo 6]

22 hours ago, cag014 said:

I have initial release, but still have some issues with alarm zone control, everything else looks working fine.

Since I don't have many devices connected to HC3 and I cannot test all options I sent a copy to

@SmartLifeSystems and we are working on bugs.

Please let me know if you want to join to test it

 

 

Ok for me, if i can help...

 

[bbolgar 5]

On 7/25/2020 at 8:08 PM, cag014 said:

Sorry about late reply...

Question what for you're using sunset and sunrise hour?

Please test line below

Please login or register to see this code.

Let me know if it works

Hi cag014,

 

Thank you - it's working fine!

 

I use the sunset + sunrise, so that the switching will only occurs during the evening hours.

 

Another question I have - is there a method to make the lights switch on to 100% when I use the manual switch, (to where the device 188 is connected)?

[cag014 731]

14 hours ago, bbolgar said:

Hi cag014,

 

Another question I have - is there a method to make the lights switch on to 100% when I use the manual switch, (to where the device 188 is connected)?

You can do it by defining a new line for that.

For example:

Assume wallSw device id is 400 (change it according to your real ID)

JS2n={wallSw=400}

Please login or register to see this code.

Notice that any time at the day by turning ON manual switch the light value will be 99% and by turning OFF the light is off.

[bbolgar 5]

7 minutes ago, cag014 said:

You can do it by defining a new line for that.

For example:

Assume wallSw device id is 400 (change it according to your real ID)

JS2n={wallSw=400}

Please login or register to see this code.

Notice that any time at the day by turning ON manual switch the light value will be 99% and by turning OFF the light is off.

Thanks - unfortunately the wallswitch is a standard, non z-wave switch - it doesn't have an ID! I was thinking along the lines, that when the light turns off, switch to 99% and then instantly off. Unfortunately, if I put this to the falseAct part, the ligths will go on when they shouldn't.

 

 

[cag014 731]

OK... interesting...

try next line

The idea is when the light goes on and no motion detected then set value to 99%.

you can add more conditions like light  sensor value or time slot (during the day set 99%, during the night set 20%)

Please login or register to see this code.

 

[bbolgar 5]

2 hours ago, cag014 said:

OK... interesting...

try next line

The idea is when the light goes on and no motion detected then set value to 99%.

you can add more conditions like light  sensor value or time slot (during the day set 99%, during the night set 20%)

Please login or register to see this code.

 

 

Thanks - I'll test this tonight to see how it works!

 

So far I found, that the device (Qubino Flush Dimmer) reports it's 'value' really slowly to the Fibaro HC2, so I rather use the power value (gets updated much faster):

Please login or register to see this code.

 

[SmartLifeSystems 20]

On 7/27/2020 at 10:12 PM, cag014 said:

I have initial release, but still have some issues with alarm zone control, everything else looks working fine.

Since I don't have many devices connected to HC3 and I cannot test all options I sent a copy to

@SmartLifeSystems and we are working on bugs.

Please let me know if you want to join to test it

 

 

Thank you for the opportunity for testing!

[bbolgar 5]

Hi @cag014,

 

One thing I noticed with the following code, is that the light turns on at sunset by itself. Any idea why?

 

Please login or register to see this code.

 

[cag014 731]

That's what defined here  $sunsetHour~

It means to run trueAct{} at sunset.

What for exactly you need sunset and sunrise hours?

If you want that this line will be active only during the night then change the line as follow

Please login or register to see this code.

[bbolgar 5]

5 hours ago, cag014 said:

That's what defined here  $sunsetHour~

It means to run trueAct{} at sunset.

What for exactly you need sunset and sunrise hours?

If you want that this line will be active only during the night then change the line as follow

Please login or register to see this code.

Hi cag14,

 

Thanks for the suggestion, I'll try it out!

 

Can you help me understand the difference between these two expressions?

 

timeSlot="$sunsetHour~,~$sunriseHour"

and

timeSlot="$sunsetHour~$sunriseHour"

 

 

[cag014 731]

Time stamp ended with tilde sign (~) executes trueAct{} actions at this specific time

Time stamp started with tilde sign (~) executes falseAct{} actions at this specific time

Tilde sign (~)  between two timestamps, means this line is active only while it this time slot range

 

"$sunsetHour~,  ~$sunriseHour"  - this means execute trueAct{} at sunsetHour and execute falseAct{} at sunsetHour

"$sunsetHour~$sunriseHour"  - means all actions in this line are working only between sunsetHour to sunsetHour. Out of this time slot the line is suspended and no actions taken.

[bbolgar 5]

9 hours ago, cag014 said:

Time stamp ended with tilde sign (~) executes trueAct{} actions at this specific time

Time stamp started with tilde sign (~) executes falseAct{} actions at this specific time

Tilde sign (~)  between two timestamps, means this line is active only while it this time slot range

 

"$sunsetHour~,  ~$sunriseHour"  - this means execute trueAct{} at sunsetHour and execute falseAct{} at sunsetHour

"$sunsetHour~$sunriseHour"  - means all actions in this line are working only between sunsetHour to sunsetHour. Out of this time slot the line is suspended and no actions taken.

Thanks for the explanation! 

[Rover 47]

Hi @cag014

I am going to migrate from HC2 to HC3.

The idea is that converting as much as possible to AOS (3.1) the migration will be faster. Fast is paramount because after transition of all devices from HC2 to HC3 nothing is working anymore, WAF:-(

The first test is

jM=
{0, "$24clock",{state="value=0",timeSlot="11:01~11:03",
      trueAct={{"Testaan","sendEmail[2]","Waterval aan"}},
      falseAct={{"Testuit","sendEmail[2]","Waterval uit"}}}}

The result is only a falseAct e-mail. Also state="value=true" only delivers a falseAct e-mail.

Can you help me in the beginners phase?

[Rover 47]

Hi @cag014,

 

How will Pushover be best implemented on AOS?

[cag014 731]

Did you ever use AOS on HC2?

Is it your first attempt to use it?

Your example works fine and does exactly what it needs to do. Sending false action when the current time entering the time slot?

$24clock keyword value is the current time in 24 hours format (e.g. 12:34).

Please try below

jM=
{0, "$24clock",{state="value=12:30",
      trueAct={{"Testaan","sendEmail[2]","Waterval aan"}},
      falseAct={{"Testuit","sendEmail[2]","Waterval uit"}}}}

In this case at 12:30 trueAct executed and at 12:31 falseAct executed.

 

To migrate to HC3 you need to install AOQ (All-in-One QA).

Copy jM{} table from HC2 to AOQ.

Copy jN2s{} table and changed device IDs according to HC3...

That's all.... for devices.

Please make sure to remove VD commands as (like buttons, sliders,values)  they're not supported in HC3

 

Edited August 21, 2020 by cag014

[Rover 47]

No, this is the first time using AOS on HC2.

Problem is that I have expected a trueAct e-mail on 11:01 and a falseAct e-mail on 11:03. But I have got only a falseAct e-mail on 11:01.

[cag014 731]

OK, now I understand the confusion.

You have defined time slot when this line is active timeSlot="11:01~11:03",

To execute what you want change the timeSlot to follow

timeSlot="11:01~,~11:03",

Now that defines two actions, at 11:01 execute true and at 11:03 false.

 

Edited August 21, 2020 by cag014

[cag014 731]

@Rover

May I ask you what you gonna do with HC2?

I have an interesting idea that you can continue to use HC2 for devices which located faraway from controller, but if you don't have these problems then it useless fro you

[AR27690 19]

Just now, cag014 said:

@Rover

May I ask you what you gonna do with HC2?

I have an interesting idea that you can continue to use HC2 for devices which located faraway from controller, but if you don't have these problems then it useless fro you

Hi cag014

I do have some problems with the Z-wave coverage... some devices don't respond well (in attic) either with HC2 or HC3.

In addition I have few very useful VDs that I want to keep. HC3 QA are not functional well right now especially with sliders.

What is the idea?

[Rover 47]

@cag014,

 

The intention is to give the HC2 to my son to automate his house too.

But I am still curious in your idea of an alternative use of HC2.

17 minutes ago, cag014 said:

OK, now I understand the confusion.

You have defined time slot when this line is active timeSlot="11:01~11:03",

To execute what you want change the timeSlot to follow

timeSlot="11:01~,~11:03",

Now that defines two actions, at 11:01 execute true and at 11:03 false.

 

Splendid!

TNX, cag014