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

[SmartLifeSystems 20]

I think, the $24clock lines don't working. In the bug window I see, the line is run, but don't work the command.

[cag014 731]

3 hours ago, SmartLifeSystems said:

I think, the $24clock lines don't working. In the bug window I see, the line is run, but don't work the command.

Could you please post the line

Have verified that and it works just fine.

{"$24clock",{state="02:40", trueAct={"`light`","turnOn"}}},

Edited November 7, 2022 by cag014

[SmartLifeSystems 20]

14 hours ago, cag014 said:

Could you please post the line

Have verified that and it works just fine.

{"$24clock",{state="02:40", trueAct={"`light`","turnOn"}}},

 Hi cag,

 

This is my line:

 

{0, "$24clock",{state="value=15:41",onClock=true,trueAct={{"`leilaWP`","+setConfiguration,12,1,0",""},{"`leilaWP`","+setConfiguration,11,1,0",""}}}},

 

In the attached pictures, you see, the line is working, but don't do the command.

 

That is true every $24clock line.

Please login or register to see this attachment.

Please login or register to see this attachment.

 

[SmartLifeSystems 20]

21 minutes ago, SmartLifeSystems said:

 Hi cag,

 

This is my line:

 

{0, "$24clock",{state="value=15:41",onClock=true,trueAct={{"`leilaWP`","+setConfiguration,12,1,0",""},{"`leilaWP`","+setConfiguration,11,1,0",""}}}},

 

In the attached pictures, you see, the line is working, but don't do the command.

 

That is true every $24clock line.

Please login or register to see this attachment.

Please login or register to see this attachment.

 

 

OK, I see the "turnOn" command working fine. The "setHeatingThermostatSetpoint" and the "+setConfiguration" command don't working.

[Rover 47]

On 10/1/2022 at 8:28 PM, cag014 said:

@Rover

Please try attached version. Should support push notifications on all HC3 versions

 

 

 

Please login or register to see this attachment.

In 13.8 Pushover works, in 14.0 Pushover does not work.

[cag014 731]

2 hours ago, SmartLifeSystems said:

 

OK, I see the "turnOn" command working fine. The "setHeatingThermostatSetpoint" and the "+setConfiguration" command don't working.

Have found the problem in transferring arguments.

Working on that

[cag014 731]

@SmartLifeSystems

Fixed the bug, please try it.

 

 

@Rover

The code for push notification exactly the same as in 13.8

 

Please login or register to see this attachment.

Edited November 7, 2022 by cag014

[SmartLifeSystems 20]

4 minutes ago, cag014 said:

@SmartLifeSystems

Fixed the bug, please try it.

 

 

@Rover

The code for push notification exactly the same as in 13.8

Please login or register to see this attachment.

 I think some lines from the end is withered.

[cag014 731]

Yes, my bad.

Have updated the file, please download again (from the same previous post)

Edited November 7, 2022 by cag014

[SmartLifeSystems 20]

Looks like working fine.

 

Thanks cag!

[cag014 731]

4 minutes ago, SmartLifeSystems said:

Looks like working fine.

 

Thanks cag!

Thank you for taking time to test the code

Edited November 7, 2022 by cag014

[cag014 731]

@Rover

Have verified again and again, push notification works.

As far as I remember you have an issue with push on 13.8 as well.... maybe this is the same problem that you fixed before

 

[Rover 47]

18 hours ago, cag014 said:

@Rover

Have verified again and again, push notification works.

As far as I remember you have an issue with push on 13.8 as well.... maybe this is the same problem that you fixed before

 

Hi Cag,

Pushover works now in 14.1 ?, it looks indeed as a parameter transfer problem.  trueAct={"`Pushover`", '+Send_Pushover,json[["Pushover test","0","gamelan","DingDong"]]'},}},

Pushover is not the standaard iOS push notification, but a service packed in a QA.

 

I did not fix the push notification but i have bought a new iPhone. With the old iPhone 6 Plus with iOS 12 there is a push notification from AOQ problem, but with the iPhone 14 Pro Max with iOS 16 push notification from AOQ works ?.

Edited November 8, 2022 by Rover

[SmartLifeSystems 20]

Hi cag!

 

What is this warning message?

Please login or register to see this attachment.

Please login or register to see this attachment.

[cag014 731]

33 minutes ago, SmartLifeSystems said:

Hi cag!

 

What is this warning message?

Please login or register to see this attachment.

Please login or register to see this attachment.

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.

 

Edited November 17, 2022 by cag014

[AR27690 19]

Hi cag014

Firs of all for a new AOS release - hopefully AOQ and AOR will follow with the new features.😀

I do like the debug information shown on the console, but sometimes is too much and too hard to find what I need to monitor.

May I ask you to have same debug options for every line?

Let me explain -

I want to see the line when the conditions are false, an easy way to see if my conditions are OK. But from other hand, I have some trigAct ad loops and they just filling-in my entire  console history... I mean every change on value in trigAct and have loops of 1 minute.  So I want to be able just for those lines to set dbgCmdFalse and dbgFalseState to set to false. Now I will see only when they are executed....

 

Another idea , is to set global dbgInfo to false and just for specific lines to defined as true. Now I will see only these lines. I think this is very useful for debugging.

 

Is anyone of All-In_One users finds that useful also?

 

Thank you for your good work.

 

Edited November 27, 2022 by AR27690

[cag014 731]

15 hours ago, AR27690 said:

Hi cag014

Firs of all for a new AOS release - hopefully AOQ and AOR will follow with the new features.😀

I do like the debug information shown on the console, but sometimes is too much and too hard to find what I need to monitor.

May I ask you to have same debug options for every line?

Let me explain -

I want to see the line when the conditions are false, an easy way to see if my conditions are OK. But from other hand, I have some trigAct ad loops and they just filling-in my entire  console history... I mean every change on value in trigAct and have loops of 1 minute.  So I want to be able just for those lines to set dbgCmdFalse and dbgFalseState to set to false. Now I will see only when they are executed....

 

Another idea , is to set global dbgInfo to false and just for specific lines to defined as true. Now I will see only these lines. I think this is very useful for debugging.

 

Is anyone of All-In_One users finds that useful also?

 

Thank you for your good work.

 

Sounds as a useful debugging option.

Done for AOQ and will be released soon. 

Will update AOS and AOR as well.

 

[cag014 731]

To all attached AOQ version that includes debugging settings in jM lines. Please read below how to use

1. Debugging levels

(Boolean true or false).

There are 5 global debugging levels available

dbgInfo -- enable/disable all global debugging levels below

dbgTrueState -- display

Please login or register to see this link.

and executed command when all conditions are true.

dbgFalseState -- display

Please login or register to see this link.

when conditions are false

dbgInitState -- display not executed commands (conditions are false) during initialization

dbgCmdFalse -- display command when command’s conditions are false

 

When dbgInfo set to false, all global debug levels are set to false also regardless their setup.

By default every jM line inherits global definitions of debugging levels.
Moreover, debugging levels could be redefined for every jM line inside the line itself.

The levels defined in jM line are override global levels for the specific line.

However inline defined dbgInfo will set all levels to defined value (true/false) for this line regardless global definitions.

For example:

1. The global levels defined as following

dbgInfo =false

dbgTrueState =true

dbgFalseState =true

dbgInitState =true

dbgCmdFalse =true

 

Since global dbgInfo in this example is false, all debug levels will be set to false, that means no debug information displayed for all jM lines.

To set all debugging levels to true for the specific jM line, add dbgInfo=true.

JM={ {“motion”,{state=”true”,dbgInfo=true, trueAct={“light”,”turnOn”},falseAct={“light”,”turnOff”}}}, }

 

To set specific level for the specific line, add [required level]=true.

JM={{“motion”,{state=”true”,dbgInfo=false, dbgTrueState=true, trueAct={“light”,”turnOn”}}},}

2. The global levels defined as following

dbgInfo =true

dbgTrueState =true

dbgFalseState =false

dbgInitState =true

dbgCmdFalse =false

 

Levels above are valid for all jM lines.

To set additional level for the specific jM line, add [required level] = true.

JM={ {“motion”,{state=”true”,dbgFalseState=true, trueAct={“light”,”turnOn”},falseAct={“light”,”turnOff”}}}, }

 

To remove specific level for specific jM line, add [required level] = false.

JM={ {“motion”,{state=”true”,dbgTrueState=false, trueAct={“light”,”turnOn”},falseAct={“light”,”turnOff”}}}, }

 

To ignore all debugging levels, add dbgInfo=false.

JM={ {“motion”,{state=”true”,dbgInfo=false, trueAct={“light”,”turnOn”},falseAct={“light”,”turnOff”}}}, }

 

 

 

 

In addition, during initialization in previous version (bugs???)

1. action states (like trueActState, falseActState ...) haven't been validated

2. devices that have been activated during init (like turnOn, turnOff, setValue...) and their state on previous jM line haven't been validated again.

 

So please note that some changes could be seen during initialization.

 

Please login or register to see this attachment.

 

Let me know if it works OK.

Edited December 1, 2022 by cag014

[Rover 47]

5 hours ago, cag014 said:

To all attached AOQ version that includes debugging settings in jM lines. Please read below how to use

1. Debugging levels

(Boolean true or false).

There are 5 global debugging levels available

dbgInfo -- enable/disable all global debugging levels below

dbgTrueState -- display

Please login or register to see this link.

and executed command when all conditions are true.

dbgFalseState -- display

Please login or register to see this link.

when conditions are false

dbgInitState -- display not executed commands (conditions are false) during initialization

dbgCmdFalse -- display command when command’s conditions are false

 

When dbgInfo set to false, all global debug levels are set to false also regardless their setup.

By default every jM line inherits global definitions of debugging levels.
Moreover, debugging levels could be redefined for every jM line inside the line itself.

The levels defined in jM line are override global levels for the specific line.

However inline defined dbgInfo will set all levels to defined value (true/false) for this line regardless global definitions.

For example:

1. The global levels defined as following

dbgInfo =false

dbgTrueState =true

dbgFalseState =true

dbgInitState =true

dbgCmdFalse =true

 

Since global dbgInfo in this example is false, all debug levels will be set to false, that means no debug information displayed for all jM lines.

To set all debugging levels to true for the specific jM line, add dbgInfo=true.

JM={ {“motion”,{state=”true”,dbgInfo=true, trueAct={“light”,”turnOn”},falseAct={“light”,”turnOff”}}}, }

 

To set specific level for the specific line, add [required level]=true.

JM={{“motion”,{state=”true”,dbgInfo=false, dbgTrueState=true, trueAct={“light”,”turnOn”}}},}

2. The global levels defined as following

dbgInfo =true

dbgTrueState =true

dbgFalseState =false

dbgInitState =true

dbgCmdFalse =false

 

Levels above are valid for all jM lines.

To set additional level for the specific jM line, add [required level] = true.

JM={ {“motion”,{state=”true”,dbgFalseState=true, trueAct={“light”,”turnOn”},falseAct={“light”,”turnOff”}}}, }

 

To remove specific level for specific jM line, add [required level] = false.

JM={ {“motion”,{state=”true”,dbgTrueState=false, trueAct={“light”,”turnOn”},falseAct={“light”,”turnOff”}}}, }

 

To ignore all debugging levels, add dbgInfo=false.

JM={ {“motion”,{state=”true”,dbgInfo=false, trueAct={“light”,”turnOn”},falseAct={“light”,”turnOff”}}}, }

 

 

Please login or register to see this attachment.

 

In addition during initialization in previous version (bugs???)

1. action states (like trueActState, falseActState ...) haven't been validated

2. devices that have been activated during init (like turnOn, turnOff, setValue...) and their state on previous jM line haven't been validated again.

 

So please note that some changes could be seen during initialization.

 

Let me know if it works OK.

I think you have to set the global debugging parameters in the AOQ parameters?

What is the default value of the debugging parameters (value if not defined globally)?

Edited December 1, 2022 by Rover

[cag014 731]

7 hours ago, Rover said:

I think you have to set the global debugging parameters in the AOQ parameters?

What is the default value of the debugging parameters (value if not defined globally)?

If global not defined then is nil, means false. with one exception for dbgInitState, if not defined then set to true.

 

What do you think it should be set to if not defined?

 

By the way, for shortcut lovers, you can use shortcut for each level in jM line (case sensitive)

 

dbgInfo -> dIf

dbgTruestate -> dTs

dbgFalseSTate -> dFs

dbgInitState -> dIs

dbgCmdFalse -> dCf

 

for example - instead 

JM={{“motion”,{state=”true”,dbgInfo=false, dbgTrueState=true, trueAct={“light”,”turnOn”}}},}

you can use

JM={{“motion”,{state=”true”,dIf=false, dTs=true, trueAct={“light”,”turnOn”}}},}