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

[hellower 3]

10 hours ago, cag014 said:

I am trying to understand your definition and that's what looks like you did

{true and '&alwaysZero:value=0' or '&alwaysZero:value>0')

First of all, the entire statement should be in double quotes and not parts of conditions.  When using or conditions the statements between should be within brackets {} or {}.

The and conditions used in the same brackets {... and ... and ...} or {.... and ... }

Another question, what do you mean just by true?

Please tr as below

("_55","startScene", "{&alwaysZero:value=0} or {y &alwaysZero:value>0}"

By the way in case your property is value you can skip that

("_55","startScene", "{&alwaysZero=0} or {&alwaysZero>0}"

 

Still don't understand where/why you are using Boolean true?

May I suggest shorter option

("_55","startScene", "{&alwaysZero>-1}"

 

 

 

 

Thanks. Really, I forgot brackets. But it's still don't work - scene not launching at selected time
Also about my way: I use lua variables on the top of the script because looking them in the user variables section is annoying because a lot of code has to be scrolled. It's really easy to change one variable on the beginning of the script from true to false and change huge part of logic.

As I understand this code:

 

{0,"$blank",{

  timeSlot="9:40~9:41",

  trueAct={

    {"_55","startScene"}

  }

}}

 

...should launch scene 55 (which is enabled and launch mode set to "manual") at 9:40 but it don't

[cag014 731]

9 hours ago, hellower said:

 

Thanks. Really, I forgot brackets. But it's still don't work - scene not launching at selected time
Also about my way: I use lua variables on the top of the script because looking them in the user variables section is annoying because a lot of code has to be scrolled. It's really easy to change one variable on the beginning of the script from true to false and change huge part of logic.

As I understand this code:

 

{0,"$blank",{

  timeSlot="9:40~9:41",

  trueAct={

    {"_55","startScene"}

  }

}}

 

...should launch scene 55 (which is enabled and launch mode set to "manual") at 9:40 but it don't

Yes, it makes the change easy. but what equals to true? You must have some variable to compare!

Regrading timeslot, your format just sets the timeSlot range between 9:40 to 9:41

To execute trueAct please define 09:40~ or true09:40

timeSlot="09:40~"

or

timeSlot="true09:40"

 

[mjahed 3]

Dear @

Please login or register to see this link.

i am on V15.2, trying to add Jsalve hcl while this HCL on slave mode,

but i am getting below error all the time.

HCLxxx={user="xxx",passwd="xxxx",ip="172.16.10.12"},   

i am 100% sure from ip connectivity and credentials. 

 

what could be the problem?

thanks in advance

 

 

Please login or register to see this attachment.

[cag014 731]

It means user, password or IP are incorrect

please make sure you can access HCL at browser using same credentials

 

[mjahed 3]

1 hour ago, cag014 said:

It means user, password or IP are incorrect

please make sure you can access HCL at browser using same credentials

 

i am sure from user and password, and connectivity status.

have anything todo with HCL3 being in slave mode?

[PatrickBrigger 1]

 

 

I really love your all-in-one scene, it is brilliant!

 

2) I would like to run the following command only if the luminance is less than 100. How to include this?

 

{0,"`motionSensor`,`luminanceSensor`",{state="true",timeSlot="07:00~23:30",trueAct={{"`lightBathroom`","turnOn",""},{"`lightBathroom`","turnOff","","={`motionSensor`:valueModified>3|`motionSensor`:value=false}"}}}},

 

Thanks so much in advance!

 

Patrick

[cag014 731]

1 hour ago, mjahed said:

i am sure from user and password, and connectivity status.

have anything todo with HCL3 being in slave mode?

Sorry, but never tested on HCL at slave mode.... might be this is a problem.

By the way if HCL at slave mode, why you need access directly to HCL? You can control HCL devices at master, right?

1 hour ago, PatrickBrigger said:

 

 

 

I really love your all-in-one scene, it is brilliant!

 

2) I would like to run the following command only if the luminance is less than 100. How to include this?

 

{0,"`motionSensor`,`luminanceSensor`",{state="true",timeSlot="07:00~23:30",trueAct={{"`lightBathroom`","turnOn",""},{"`lightBathroom`","turnOff","","={`motionSensor`:valueModified>3|`motionSensor`:value=false}"}}}},

 

Thanks so much in advance!

 

Patrick

Have sent an answer in private message...

[mjahed 3]

5 hours ago, cag014 said:

Sorry, but never tested on HCL at slave mode.... might be this is a problem.

By the way if HCL at slave mode, why you need access directly to HCL? You can control HCL devices at master, right?

Have sent an answer in private message...

to monitor the network connectivity between master and slaves.

[Rover 47]

On 12/25/2022 at 1:19 AM, cag014 said:

Please login or register to see this attachment.

 

Please backup your working code 😀

Let me know if it works and looks better. Your feedback appreciated.

Hi cag014,

I appreciate your work in making AOQ more perfect and easier to use, but the "Major "face lifting" for debug information (feels and looks like code)" is a step too far for me in order to comprehence what I see. Things like "if not" and the new signs are unclear. Please add some documentation on what I see now.

Edited January 16, 2023 by Rover

[SmartLifeSystems 20]

On 11/17/2022 at 6:15 PM, cag014 said:

API commands slow execution... could be your LAN or HC3 is a little bit overloaded/busy.

It could be that at this particular point of time the connection is slow (just for a short period of time)

 

You can set the response time in USER Global Parameters 

slaveApiTime= 600 ''

 

in addition, it could be set for each system in user_data file

home={user="xxx",passwd="xxx",ip="xxx", slaveApiTime=600} 

 

The default value is 600 msec.

The idea is to provide heads up, that something is not normal.

 

Questions:

Do you have dead devices in the system?

Do you have devices that located far away from the hub or blocked by the walls (or another obstacle) that cause unstable Zwave communication?

 

It could explain the warning....

 

You can see also an updated table with response times 

Please login or register to see this spoiler.

 

Hi cag,

 

This problem is alive for me continiously. Every devices is working correctly, but random I got a warning messages from the AOQ.

 The response time is very high.

I don't understand what is the problem. I wrote a message for the FIBARO support. For some weeks his watch my HUB, but can't find any problem.

The FIBARO support send me another HUB, but the problem is alive.

What do you think? What is the problem.

When this problem is alive, after some time the HUB is crashed and rebooting.

 

Please login or register to see this attachment.

Please login or register to see this attachment.

[cag014 731]

@SmartLifeSystems

That means that your hub responds too slow. Could be that some device slows down your hub. It could be from many reasons like device sends too much information or physical location of the device causes poor communication.

Is it happening all the time? I mean when you restart the hub, is works properly (at least for a while?)

What about your RAM and CPU loads?

 

When this happening, could you try to access any device via API and see if the response is slow also...

 

[SmartLifeSystems 20]

7 minutes ago, cag014 said:

@SmartLifeSystems

That means that your hub responds too slow. Could be that some device slows down your hub. It could be from many reasons like device sends too much information or physical location of the device causes poor communication.

Is it happening all the time? I mean when you restart the hub, is works properly (at least for a while?)

What about your RAM and CPU loads?

 

When this happening, could you try to access any device via API and see if the response is slow also...

 

 

"Is it happening all the time? I mean when you restart the hub, is works properly (at least for a while?)" - Yes, every time. The problem is randomly, and I can't attached any event.

 

"or physical location of the device causes poor communication." - I haven't new device, and what I only change is the HUB and the AOQ updates.

 

No information in the history tab, and I send more log file for the Fibaro support, but hes can't find anything. What the Fibaro see, only some API problem.

Edited January 17, 2023 by SmartLifeSystems

[SmartLifeSystems 20]

6 minutes ago, SmartLifeSystems said:

 

"Is it happening all the time? I mean when you restart the hub, is works properly (at least for a while?)" - Yes, every time. The problem is randomly, and I can't attached any event.

 

"or physical location of the device causes poor communication." - I haven't new device, and what I only change is the HUB and the AOQ updates.

 

No information in the history tab, and I send more log file for the Fibaro support, but hes can't find anything. What the Fibaro see, only some API problem.

 

 

More information. When the AOQ's warning API message alive, I can control my devices until the hub is crash, but the AOQ don't working.

[cag014 731]

10 minutes ago, SmartLifeSystems said:

 

 

More information. When the AOQ's warning API message alive, I can control my devices until the hub is crash, but the AOQ don't working.

That's strange, AOQ shows a warning only everything else should work, unless refresh State API does not received...

Could you please change slaveApiTime to 5000. It should stop the warnings and let's see if AOQ continues to work. 

 

topActive   = 15 --number (0-30) of top active slave devices. 0-disable. Default 10

topZwave    = 15 --number (0-30) of top active master devices. 0-disable. Default 10 

slaveApiTime= 5000 -- max. hub response time (milliseconds), warning shown if greater detected.

 

dbgInfo     = true -- display line and action states condition according to dbgTrueState/dbgFalseState 

dbgTrueState= true -- display line, action states and executed command when condition is true

dbgFalseState=true -- display line and action states when condition is false

[cag014 731]

@SmartLifeSystems

DO you have any idea when your hub started to crash? What SW version you are on?

 

BY the way, did you add or change any QA devices or scenes?

Do you use

Please login or register to see this link.

emulating HC2 devices on HC3?

 

Edited January 17, 2023 by cag014

[SmartLifeSystems 20]

57 minutes ago, cag014 said:

@SmartLifeSystems

DO you have any idea when your hub started to crash? What SW version you are on?

 

BY the way, did you add or change any QA devices or scenes?

Do you use

Please login or register to see this link.

emulating HC2 devices on HC3?

 

 

I don't remember the version number, but the first crash was in september.

Since than I have made only some QA that change global variables.

 

I don't know if it has significances, but those days in the Satel Integra alarm system, the system has benn separated into more particions. However it was also then when in the HUB softwere update happened.

4 minutes ago, SmartLifeSystems said:

 

 

Edited January 17, 2023 by SmartLifeSystems

[SmartLifeSystems 20]

10 minutes ago, SmartLifeSystems said:

 

I don't remember the version number, but the first crash was in september.

Since than I have made only some QA that change global variables.

 

I don't know if it has significances, but those days in the Satel Integra alarm system, the system has benn separated into more particions. However it was also then when in the HUB softwere update happened.

 

 

I changed the slaveApi time to 5000, but the problem is started, when I restart the AOQ.

 

Please login or register to see this attachment.

Please login or register to see this attachment.

 

Please login or register to see this attachment.

Edited January 17, 2023 by SmartLifeSystems

[SmartLifeSystems 20]

Now is the problem continiously. I restart the AOQ and after some minutes again started the problem.

[cag014 731]

21 hours ago, SmartLifeSystems said:

 

I changed the slaveApi time to 5000, but the problem is started, when I restart the AOQ.

 

Please login or register to see this attachment.

Please login or register to see this attachment.

 

Please login or register to see this attachment.

1. Wow, your CPU load is very high, it explains slow reaction of the hub.

     I suggest to shutdown QA, scenes one by one to find out who causes that load.

     Here as an example of my CPU load

 

Please login or register to see this spoiler.

 

 

 

Edited January 18, 2023 by cag014

[cag014 731]

On 1/16/2023 at 8:26 PM, Rover said:

Hi cag014,

I appreciate your work in making AOQ more perfect and easier to use, but the "Major "face lifting" for debug information (feels and looks like code)" is a step too far for me in order to comprehence what I see. Things like "if not" and the new signs are unclear. Please add some documentation on what I see now.

The debug information is the same, just added if before condition statements and then after.

When the condition failed added if not and the command shown with strikethrough. Means If not then skip the command. Like in the real code.

 

The main change that the same triggered line doesn't display again and again and again.... but all commands related to this line are shown below. Easy to spot the chain of commands.

 

for example

Please login or register to see this spoiler.

 

When the same line repeatedly displayed, I find it's hard to follow the flow of the commands... too many same info to read

Edited January 18, 2023 by cag014