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

[cag014 731]

1 hour ago, Rover said:

Range= ?

 

Another question:

I want to create a flash light for alarm status, so the repeat cycle should be short, like 1 second. But Time Span has as minimum 1 minute and it should be an integer number. So how to repeat fast?

Please login or register to see this spoiler.

 

The best option to do it, is just to buy blinking lamp and turn it on/off by Z-wave switch.

for example

Please login or register to see this link.

 

 

Edited September 21, 2020 by cag014

• Quote

[Rover 47]

4 hours ago, cag014 said:

Range? I mean range of numbers in random for example random(5,9) will repeat same number several times.

Please login or register to see this spoiler.

does nothing. Why?

Edited September 21, 2020 by Rover

[Rover 47]

4 hours ago, cag014 said:

Is your device has turn On/Off command?

If so, the workable option (to my opinion) will be something like that:

{0.02,"&Statuslicht",{state="value=Alarm",timeLoopAct={"`StatusLEDs`","turnOff;else;trunOn","","{`StatusLEDs`:value=true}"}}},

Homestly I don't think this is a good idea because it will overload your HC3 with endless Zwave commands, till &Statuslicht = Alarm.

The constellation works fine already for many years in HC2.

The reason I do not use turn On/Off is that I am using the color white in Fibaro RGBW for siren and outdoor flashdevice and not in the steering the indoor LED-array. Thats why the fourth number (White) is always 255 (so color red of indoor LED array = (255,0,0,255)). The white color is made of combining RGB (255,255,255,255). This is also the reason that I cannot use a programmed flash of the RGBW device, but have to make a homemade flash (so works fine in HC2). Now the task of making it workable in AOQ.

[cag014 731]

27 minutes ago, Rover said:

Please login or register to see this spoiler.

the timeLoopAct executed after 5 minutes from the moment when "value=Alarm".

 

[Rover 47]

7 hours ago, cag014 said:

10 hours ago, Rover said:

Hi @cag014

If

Please login or register to see this spoiler.

This has nothing to do with random range, it is just turnoff lights by $24clock.

How can one $24clock trigger repeats several times in more seconds than the ~value?

• Quote

[cag014 731]

25 minutes ago, Rover said:

This has nothing to do with random range, it is just turnoff lights by $24clock.

How can one $24clock trigger repeats several times in more seconds than the ~value?

This is not $24clock, this is the random of the timeSlot.

While you have same value (status is true) the timeSlot is moving. As you can see it repeats every minute, not a second.

Since AOQ checks every line very fast you have 100% of opportunity to have right random timeSlot every single minute after 03:00. It will repeat for entire hour

Please explain what you're trying to do here?

Edited September 21, 2020 by cag014

[Rover 47]

51 minutes ago, cag014 said:

1 hour ago, Rover said:

This has nothing to do with random range, it is just turnoff lights by $24clock.

How can one $24clock trigger repeats several times in more seconds than the ~value?

This is not $24clock, this is the random of the timeSlot.

While you have same value (status is true) the timeSlot is moving. As you can see it repeats every minute, not a second.

Since AOQ checks every line very fast you have 100% of opportunity to have right random timeSlot every single minute after 03:00. It will repeat for entire hour

Please explain what you're trying to do here?

I think we have a misunderstanding.

Please login or register to see this spoiler.

 

Edited September 21, 2020 by Rover

[cag014 731]

32 minutes ago, Rover said:

I think we have a misunderstanding.

Please login or register to see this spoiler.

No... that's exactly what I said,

You have define

timeSlot="?3:00+(random(`RandomMinTijd`,`RandomMaxTijd`)*60)?~",

means to execute trueAct at 03:00 +random value, correct?

AOQ interprets this line several times in one second! so it 100% garanties that within one minute it will be the same time and tru Act executed.

 

There is nothing to do to $24clock definition.  $24clock will never be "value=0". The trigger is combination of tilde in timeSlot definition XX:XX~ and the time

 

Edited September 21, 2020 by cag014

[Rover 47]

11 minutes ago, cag014 said:

You have define

timeSlot="?3:00+(random(`RandomMinTijd`,`RandomMaxTijd`)*60)?~",

means to execute trueAct at 03:00 +random value, correct?

Yes, that is what I want, but just one time.

Your explanation is still not clear to me, but you can help me with showing how to turnOff the 5 random lights at 03:00 +random value, just 1x.

[cag014 731]

There is an very complicated solution, but I have an idea how to make it simple.

Will post new version to support your request.

Edited September 22, 2020 by cag014

[cag014 731]

OK, download attached version

Please change your line as follow...

{0, "$24clock",{state="value=02:55",  trueAct={

{"$lineId","setTimeSlot","?3:00+(random(`RandomMinTijd`,`RandomMaxTijd`)*60)?~","{$24clock:value=02:55}"},

{"`XRandomLichten`","setGlobal","stop","{$24clock:value>02:59}"},

{"RandomLichten","sendEmail,2","Stop","{$24clock:value>02:59}"},

{"`RandomLichten`","turnOff","","{$24clock:value>02:59}"}}}},

The idea that every day at 02:55 the setTimeSlot will be executed and will set the timeSlot to 03:00 + random. While your original actions have condition to be executed after 02:59...

 

To all, the attached version is the final version which I intend to post on Wednesday , so any feedback or suggestions will be appreciated. Thanks for your time and efforts so far....

 

 

Please login or register to see this attachment.

Edited September 22, 2020 by cag014

[Rover 47]

10 hours ago, cag014 said:

There is an very complicated solution, but I have an idea how to make it simple.

TNX @cag014!

This solution is so "simple" that I could not have invented it in 100 years ?

 

 

On 9/19/2020 at 10:10 AM, Rover said:

Please login or register to see this spoiler.

It would be nice for the final version as everywhere device names are to be seen.

Edited September 22, 2020 by Rover

[cag014 731]

4 hours ago, Rover said:

It would be nice for the final version as everywhere device names are to be seen.

What do you mean by device names?

To see device real name or alias as defined in jS2n?

Question: is your device 174'hc2 defined in jS2n? 

 

[Rover 47]

3 hours ago, cag014 said:

What do you mean by device names?

To see device real name or alias as defined in jS2n?

Question: is your device 174'hc2 defined in jS2n? 

 

To see device real name or alias as defined in jS2n? Yes, so "turnOff(DimmerHal)" instead of "turnOff(174'hc2)", just like "turnOff (Schilderijspot,SpotsTrapOverloop)" in the line above.

jS2n:

Please login or register to see this spoiler.

 

[Rover 47]

Please login or register to see this spoiler.

acts as OR relation.

How to specify an AND relation?

[cag014 731]

1 hour ago, Rover said:

Please login or register to see this spoiler.

lineState={"{&Alarmtest:value=Aan|&Statuslicht:value=Alarm}"}

In general condition format is

"{...|...|...}" means AND

"{...}{...} means OR

You can combine as much as you need.

{"..|..}{...|...|..}{..}"

[Rover 47]

On 9/22/2020 at 4:01 AM, cag014 said:

OK, download attached version

Please change your line as follow...

{0, "$24clock",{state="value=02:55",  trueAct={

{"$lineId","setTimeSlot","?3:00+(random(`RandomMinTijd`,`RandomMaxTijd`)*60)?~","{$24clock:value=02:55}"},

{"`XRandomLichten`","setGlobal","stop","{$24clock:value>02:59}"},

{"RandomLichten","sendEmail,2","Stop","{$24clock:value>02:59}"},

{"`RandomLichten`","turnOff","","{$24clock:value>02:59}"}}}},

The idea that every day at 02:55 the setTimeSlot will be executed and will set the timeSlot to 03:00 + random. While your original actions have condition to be executed after 02:59...

 

To all, the attached version is the final version which I intend to post on Wednesday , so any feedback or suggestions will be appreciated. Thanks for your time and efforts so far....

 

 

Please login or register to see this attachment.

It works great ?

[gggizmo 6]

On 9/22/2020 at 4:01 AM, cag014 said:

 

 

To all, the attached version is the final version which I intend to post on Wednesday , so any feedback or suggestions will be appreciated. Thanks for your time and efforts so far....

 

 

Please login or register to see this attachment.

Cag14. Tnx, i'm out for work these days and i'll send you feedback asap. Sorry but for me this week is "homeautomation free".

[cag014 731]

@gggizmo

No problem, do anything you need to prevent divorce ?

@Rover

Attached last version with bug fix (device name always shown).

To all, since HC3 and mobile app have options for different color themes, I have added to main code option to change some colors of the table (like false/true status, items and etc...) and printed lines on debug window.

Please use it for best view on your theme.

 

Please login or register to see this attachment.

Edited September 23, 2020 by cag014

[SmartLifeSystems 20]

Hi cag,

 

I downloaded the 2.8 version. I have got a Nice gate, and and this command open/close, but with the new release this don't working.

What's the problem? Can you help me?

 

[2020-09-23] [17:18:06] [DEBUG] [AOQ3681]: Global not defined. Local variables ("my_Var" "onState") won't be saved for next run...[2020-09-23] [17:18:06] [DEBUG] [AOQ3681]: Global not defined. Reminders won't be saved for next run...[2020-09-23] [17:18:07] [DEBUG] [AOQ3681]: Parsing jM[149] hash table data... <25 sec.[2020-09-23] [17:18:10] [DEBUG] [AOQ3681]:  _☠ [23 Sep 17:18:09] /opt/fibaro/AOQ3681.jM hash table:25:~: {0, "`bedroomButton`"...}
{0,"166",{"state"="centralSceneSupport=1.Pressed","trueAct"={"468","close","","{420:value=true}"}}}

(99) Action close not supported.
AOQ Supported Actions: (32% in use)
- addRmd armAlarm delAllRmd delLogRmd delRmd disableScene
- disarmAlarm emitEvent enableScene killScene logRmd poll
- powerOutage pressButton reboot runAction sendEmail sendNote
- sendPush sendSms sendiPush setColor setConfiguration setGlobal
- setProfile setRmd setSlider setState setStateDelay setStateFormula
- setStateValue setTimeDrift setTimeSlot setTimeSpan setValue shutdown
- startScene tts turnOff turnOn vacOff vacOn
- verify [2020-09-23] [17:18:10] [ERROR] [QUICKAPP3681]: QuickApp crashed