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

[cag014 731]

19 hours ago, Sjekke said:

What would be my ideal scenario.

• 1 light can always turnOn when motion is detected
• 1 light may always switch on when motion is detected, but only when LUX is lower than 50Lux
• The 2 HUE lamps can only be switched on when motion is detected, but only between sunset and 04:00 at night
• All lights should turnOff after 600sec unless there is motion detection.

Regrading which and how many lights to turn ON, it depends on yours and your family needs (ask your wife ?).

By the way in my case, it depends on TV state also. If TV is ON, I don't turn ON all the lights and on some of them, I use dimmer to prevent lights reflection on TV. 

I always prefer to use LUX value to turn the lights ON.

Since you have two motion sensors, I suggest using time loop and not falseAct() with delay to turn lights OFF. (to avoid time conflicts between the sensors delays)

Something like that:

{2,"$timeLoop", {state="inLoop", timeLoopAct={"`allLivingLampLights`","turnOff", "if {`livingRoomMotionFront`,`livingRoomMotionBack`:value=false and `livingRoomMotionFront`,`livingRoomMotionBack`:valueModified>600}"}}},

It means check every 2 minutes if both sensors are safe and last state change is greater than 600 seconds on both sensors.

 

I have very similar scenario also, but my delay is 1800 sec. (30 minutes) and I turn OFF lights, TV, sound bar and few other appliances.

Since I have TTS system, so before turning everything OFF, I generate an announcement like:  "No presence detected at living room, turning off all devices in a moment" and after a minute if still no motion detected, everything is turned OFF. The idea behind that, is to give a chance if someone for example reading the book or watching TV without movement to cancel shutting OFF the devices by move himself for a second...?

 

Edited October 3, 2022 by cag014

[Rover 47]

5 hours ago, cag014 said:

Strange, works perfectly on my system...

Could you please post the block scene?

Please login or register to see this spoiler.

 

[cag014 731]

1 hour ago, Rover said:

Please login or register to see this spoiler.

Please try version below

 

Please login or register to see this attachment.

[Rover 47]

54 minutes ago, cag014 said:

Please try version below

 

Please login or register to see this attachment.

First:

[03.10.2022] [18:45:57] [DEBUG] [AOQ386]: Arranging data table...

[03.10.2022] [18:46:17] [WARNING] [AOQ386]: local: TimeResp over 16 sec. to execute api_get( /globalVariables/tSoundCDR ) <

[03.10.2022] [18:46:17] [ERROR] [QUICKAPP386]: QuickApp crashed

[03.10.2022] [18:46:17] [ERROR] [QUICKAPP386]: main.lua:2485: unexpected symbol near '='

Second QA initiation was successful.

Only push notification from scene but not from AOQ.

[cag014 731]

24 minutes ago, Rover said:

 

Only push notification from scene but not from AOQ.

It works just fine, but I do using Android phone.

Could you please disable the Block scene and try AOQ only?

 

[Rover 47]

28 minutes ago, cag014 said:

It works just fine, but I do using Android phone.

Could you please disable the Block scene and try AOQ only?

 

Giving Block Scene and AOQ a different trigger parameter value, so triggering Block Scene and AOQ not together: Block Scene push works and AOQ push does not.

[cag014 731]

22 hours ago, Rover said:

Giving Block Scene and AOQ a different trigger parameter value, so triggering Block Scene and AOQ not together: Block Scene push works and AOQ push does not.

Just for test have set push command as was before (v13.4) the changes, please try it...

Please login or register to see this attachment.

All others please do not download this version.

 

Since you are still using old Fibaro version, could you convert the block scene to LUA and post it...  

 

Edited October 4, 2022 by cag014

[Rover 47]

11 minutes ago, cag014 said:

Just for test have set push command as was before (v13.4) the changes, please try it...

Please login or register to see this attachment.

All others please do not download this version.

 

Since you are still using old Fibaro version, could you convert the block scene to LUA and post it...  

 

Hi cag, still no push message from AOQ.

Please login or register to see this spoiler.

 

[cag014 731]

4 hours ago, Rover said:

Hi cag, still no push message from AOQ.

Please login or register to see this spoiler.

That's exactly the command I use...

JUst tested that on my daughter's iPhone and it works fine 

[SmartLifeSystems 20]

Hi cag!

 

I think, this line don't working.

 

{0, "$RAM",{state="value>85",trueAct={{"RAM>85%","sendNote","Warning. \nSystem memory is $RAM%, rebooting... ",true},{"|$lineId|","setStateValue","80"}},falseAct={{"|$lineId|","setStateValue","85"},{"RAM<80%","sendNote","System memory is $RAM%"}}}},

 

What do you think?

 

Thanks!

[cag014 731]

5 hours ago, SmartLifeSystems said:

Hi cag!

 

I think, this line don't working.

 

{0, "$RAM",{state="value>85",trueAct={{"RAM>85%","sendNote","Warning. \nSystem memory is $RAM%, rebooting... ",true},{"|$lineId|","setStateValue","80"}},falseAct={{"|$lineId|","setStateValue","85"},{"RAM<80%","sendNote","System memory is $RAM%"}}}},

 

What do you think?

 

Thanks!

What doesn't work? No notification received?

During latest upgrades, Fibaro changed the push notification concept, so if you have a problem you need to download the latest AOQ as published here (few topics before)

[SmartLifeSystems 20]

On 10/21/2022 at 2:55 AM, cag014 said:

What doesn't work? No notification received?

During latest upgrades, Fibaro changed the push notification concept, so if you have a problem you need to download the latest AOQ as published here (few topics before)

 

This line. I updated to the 13.9. My RAM usage is very high (I don't know why, but was high everytime). In the last few weeks my HC3 is random turns into one wich cannot be reached. I don' understand why. I have a line what reboot the HC3, when the RAM is very high, but this line don't working and I think the reason of the unavailability this. The line doesn't reboot my HC3. No warning message, no nothing in the history.

 

Have you any idea this problem?

[Sjekke 87]

11 hours ago, SmartLifeSystems said:

 

This line. I updated to the 13.9. My RAM usage is very high (I don't know why, but was high everytime). In the last few weeks my HC3 is random turns into one wich cannot be reached. I don' understand why. I have a line what reboot the HC3, when the RAM is very high, but this line don't working and I think the reason of the unavailability this. The line doesn't reboot my HC3. No warning message, no nothing in the history.

 

Have you any idea this problem?

Same here … 73% ram usage for almost nothing… respons is also very slow …

[cag014 731]

11 hours ago, SmartLifeSystems said:

 

This line. I updated to the 13.9. My RAM usage is very high (I don't know why, but was high everytime). In the last few weeks my HC3 is random turns into one wich cannot be reached. I don' understand why. I have a line what reboot the HC3, when the RAM is very high, but this line don't working and I think the reason of the unavailability this. The line doesn't reboot my HC3. No warning message, no nothing in the history.

 

Have you any idea this problem?

Could you please post your updated line?

Again, could you please tell me what doesn't work exactly?

 

15 minutes ago, Sjekke said:

Same here … 73% ram usage for almost nothing… respons is also very slow …

What is your cache percentage? The cache memory is always available for use, so the actual RAM available for usage is RAM value minus cache percentage.

Is the response slow for every device? Devices that have poor communication (located faraway or blocked by something) could be very slow. 

I have found that sometime if your device located near to power line it could strongly interfere Zwave communication.

[SmartLifeSystems 20]

1 hour ago, cag014 said:

Could you please post your updated line?

Again, could you please tell me what doesn't work exactly?

 

I think the AOQ can't read the RAM usage.

 

But I don't know, if this problem will be solved to my HC3 random unreaching.

I think my problem is the high RAM usage, and my line can't reboot my HC3.

 

Here is the line:

 

{15, "$RAM",{state="value>85#30",timeLoopAct={{"Sherwood","sendPush,5404","For the system need rebooting, because the RAM is $RAM %.","{$Entrance_Door:value=armed}"},{"","reboot","10","{$Entrance_Door:value=armed}"}}}},

[SmartLifeSystems 20]

1 hour ago, Sjekke said:

Same here … 73% ram usage for almost nothing… respons is also very slow …

 

My RAM usage is over than 85-86%. My HC3 is gets lost sometimes. I can't see nothing. Only random don't working the HC3 and I can't see nothing in my mobile app.

[cag014 731]

1 hour ago, SmartLifeSystems said:

I think the AOQ can't read the RAM usage.

 

But I don't know, if this problem will be solved to my HC3 random unreaching.

I think my problem is the high RAM usage, and my line can't reboot my HC3.

 

Here is the line:

 

{15, "$RAM",{state="value>85#30",timeLoopAct={{"Sherwood","sendPush,5404","For the system need rebooting, because the RAM is $RAM %.","{$Entrance_Door:value=armed}"},{"","reboot","10","{$Entrance_Door:value=armed}"}}}},

It does read the RAM, but the actual RAM in use is a different from what you see in diagnostic graph.

Please try as follow

execute in browser

http:/<IP-Address>/api/diagnostics

Please login or register to see this spoiler.

Please try also http:/<IP-Address>/api/diagnostics and verify your fee memory number.

Did you add recently any new Z-wave device? It could explain slow response if the device keeps HC3 busy due to poor communication.

[Rover 47]

Hi Cag,

I see that the tracing time in my two running AOQ's is one hour later then the real time. It seems that AOQ did not notice the change to wintertime.

[Rover 47]

7 hours ago, Rover said:

Hi Cag,

I see that the tracing time in my two running AOQ's is one hour later then the real time. It seems that AOQ did not notice the change to wintertime.

After initiation of the AOQ, the time is getting right.

[cag014 731]

To all users... I intend to release new AOQ next week and would like to share/test the code before official release.

Main changes are

1. API actions execution method changed from GET to POST to accelerate code execution.

 

2. Dead/WakeUp messages shown on the console 

 

3. Added an option to use icon number or icon name in setIcon command.

 

4. Per user's request - During initialization (on startup) action where  init disabled are shown also on the console. Looks like in some cases you can forget about init state and wondaring why the commands are not executed ? . In order to skip that, please define new user parameter dbgInitState=false

Please login or register to see this spoiler.

 

Bug fix

Values of keywords with identical beginning (like $alarm and $alarmNight) could be mishandled.

During latest Fibaro release the push notification for mobile phones has been changed. Added auto handler to identify email or mobile ID and to execute correc type of push notification.

Cosmetic changes

Minor bug fix 

 

 

Please login or register to see this attachment.