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

[Rover 47]

On 12/23/2020 at 6:47 AM, gggizmo said:

hi cag.

Merry Christmas and a new question to you:

 

i update to the last beta.

aoq 9.1 doesnt even start,

aoq 9.2 start very slowly with some strange debug lines

[23.12.2020] [06:42:47] [DEBUG] [AOQ1385]: local: HC3-MAIN HC3-00004002^5.061.36...[23.12.2020] [06:42:55] [WARNING] [AOQ1385]: TimeResp over 7 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D534 [23.12.2020] [06:43:01] [WARNING] [AOQ1385]: TimeResp over 6 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D764 [23.12.2020] [06:43:07] [WARNING] [AOQ1385]: TimeResp over 6 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D769 [23.12.2020] [06:43:14] [WARNING] [AOQ1385]: TimeResp over 6 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D1030 [23.12.2020] [06:43:20] [WARNING] [AOQ1385]: TimeResp over 6 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D1157 [23.12.2020] [06:43:26] [WARNING] [AOQ1385]: TimeResp over 6 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D1161 [23.12.2020] [06:43:32] [WARNING] [AOQ1385]: TimeResp over 6 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D1162 [23.12.2020] [06:43:38] [WARNING] [AOQ1385]: TimeResp over 6 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D1169 [23.12.2020] [06:43:45] [WARNING] [AOQ1385]: TimeResp over 7 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D1228 [23.12.2020] [06:43:51] [WARNING] [AOQ1385]: TimeResp over 6 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D1233 [23.12.2020] [06:43:57] [WARNING] [AOQ1385]: TimeResp over 6 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D1240 [23.12.2020] [06:44:03] [WARNING] [AOQ1385]: TimeResp over 6 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D1245 [23.12.2020] [06:44:13] [WARNING] [AOQ1385]: TimeResp over 6 sec. to execute /events/history%3FobjectType%3Ddevice%26%26numberOfRecords%3D1%26objectId%3D1324

 

Any hint

Went to 5.061.36 because I want to migrate from HC2:

[24.12.2020] [10:08:12] [WARNING] [AOQ205]: TimeResp over 12 sec. to execute /panels/event%3Ftype%3Did%26last%3D1%26deviceID%3D210

Cycling on [24.12.2020] [10:18:00] [DEBUG] [AOQ204]: 9.1Gathering information...23009 + next line local: name HC3

Both AOQs not startable, @cag014 please repair ?

[cag014 731]

2 hours ago, Rover said:

Went to 5.061.36 because I want to migrate from HC2:

[24.12.2020] [10:08:12] [WARNING] [AOQ205]: TimeResp over 12 sec. to execute /panels/event%3Ftype%3Did%26last%3D1%26deviceID%3D210

Cycling on [24.12.2020] [10:18:00] [DEBUG] [AOQ204]: 9.1Gathering information...23009 + next line local: name HC3

Both AOQs not startable, @cag014 please repair ?

As I mentioned I cannot upgrade my system to the new beta, but please try attached version with workaround

@gggizmo please try it also

let me know if it works

 

 

Please login or register to see this attachment.

[cag014 731]

By the way there is an issue with this beta with communication, see below

(As you cane the problems are not AOQ related...)

47 minutes ago, 10der said:

WARNING

 

two independed HC3 users (also me too) complain after beta on

- lost ZWave packets or something of the kind

- "mothion lights" works above 10sec

- delays in network. unsystematized.

 

from my end.

sometimes switch switched manually is not reflected in HC3 (lost packet also?)

delays....  confirmed

i can't run Zniffer right now cuz have a some urgent works with deadlines but will do a the evening.

 

omg omg omg omg omg omg 

 

Edited December 24, 2020 by cag014

[Rover 47]

On 12/24/2020 at 1:48 PM, cag014 said:

As I mentioned I cannot upgrade my system to the new beta, but please try attached version with workaround

@gggizmo please try it also

let me know if it works

 

 

Please login or register to see this attachment.

I am trapped in version 5.61.36 (and cannot back to previous version) so no other choice than to get AOQ working in this version. I did the migration from HC2 to HC3 and all devices were there ?. 

Firstly, AOQ 9.3 works! ?

Secondly, AOQ in this HC3 version works very fast and the CPU-load is between 1 and 10% ! Of course no HC2 slaves are active and that helps.

After a lot of work to change all the device ID's , AOQ complained about a lot of devices not knowing actions like turnOn. Soft reconfiguration of almost all devices made AOQ happy again.

This was the transition of AOQ1 (Lighting and controllers). AOQ2 transition (security) is the next project.

 

One issue here:

{0,"`Deurbel`",{trigAll=true,lineState={"{`Deurbel`:valueModified > ?&LaatsteBel + 15?}"},trigAct={

worked in AOQ 9.1, but now:

Please login or register to see this spoiler.

BTW there is no local 'r'.

[cag014 731]

32 minutes ago, Rover said:

I am trapped in version 5.61.36 (and cannot back to previous version) so no other choice than to get AOQ working in this version. I did the migration from HC2 to HC3 and all devices were there ?. 

Firstly, AOQ 9.3 works! ?

Secondly, AOQ in this HC3 version works very fast and the CPU-load is between 1 and 10% ! Of course no HC2 slaves are active and that helps.

After a lot of work to change all the device ID's , AOQ complained about a lot of devices not knowing actions like turnOn. Soft reconfiguration of almost all devices made AOQ happy again.

This was the transition of AOQ1 (Lighting and controllers). AOQ2 transition (security) is the next project.

 

One issue here:

{0,"`Deurbel`",{trigAll=true,lineState={"{`Deurbel`:valueModified > ?&LaatsteBel + 15?}"},trigAct={

worked in AOQ 9.1, but now:

Please login or register to see this spoiler.

There is no changes in calculation in v9.3.

Could you please tell me to what value you set &LaatsteBel  ?

[Rover 47]

10 hours ago, cag014 said:

There is no changes in calculation in v9.3.

Could you please tell me to what value you set &LaatsteBel  ?

global4local= {true,gVarName="aoqVar",varArray={LaatsteBel="",SonosRadio="5", Tuinpomp2uur="Uit", SonosVolume="", clock="", OldDimlevel="", Prio="", PushoverMessage="Welkom", PushoverSound="", PushoverTitle=""}}

Also global4local= {true,gVarName="aoqVar",varArray={LaatsteBel="0",SonosRadio="5", Tuinpomp2uur="Uit", SonosVolume="", clock="", OldDimlevel="", Prio="", PushoverMessage="Welkom", PushoverSound="", PushoverTitle=""}} 

results in the same problem. In the versions before: no problem.

Please login or register to see this spoiler.

 

Edited December 27, 2020 by Rover

[GaelP 0]

Good morning everyone,

Long time no post.

 

In the spirit of "how to do it better", I do have a question for you all: I have a bunch of lines (probably 50) that are dependant to a global variable. For now I have put a "if" condition in each of them but I wonder if they will not be a better way to do it. Better meaning: either more efficient from a cpu perspective or from a code reading perspective.

The use case is that I have a series of actions that I want to run or schedule based on the state of a variable (&vgRetraite). For now my jm looks like this:

{0,"$24clock",{state="value=07:15",trueAct={"`SecheServietteManoir`","turnOn","","if{&vgRetraite:value=1}"}}},

{0,"$24clock",{state="value=09:00",trueAct={"`SecheServietteManoir`","turnOff","","if{&vgRetraite:value=1}"}}},

 

{0,"$24clock",{state="value=$sunriseHour-1800",trueAct={"`RadiateurManoirSalon`","setValue,99","","if{&vgRetraite:value=1}"}}}, -- mode confort matin 30 mn avant lever soleil

{0,"$24clock",{state="value=09:15",trueAct={"`RadiateurManoirSalon`","setValue,25","","if{&vgRetraite:value=1}"}}}, -- mode eco en journé

{0,"$24clock",{state="value=$sunsetHour",trueAct={"`RadiateurManoirSalon`","setValue,99","","if{&vgRetraite:value=1}"}}},  -- mode confort soirée 

{0,"$24clock",{state="value=22:00",trueAct={"`RadiateurManoirSalon`","setValue,13","","if{&vgRetraite:value=1}"}}}, -- mode hors gel après 22h

 

{0,"$24clock",{state="value=06:30",trueAct={"`SecheServietteYoga`","turnOn","","if{&vgRetraite:value=1}"}}},

{0,"$24clock",{state="value=07:45",trueAct={"`SecheServietteYoga`","turnOff","","if{&vgRetraite:value=1}"}}},

{0,"$24clock",{state="value=18:00",trueAct={"`SecheServietteYoga`","turnOn","","if{&vgRetraite:value=1}"}}},

{0,"$24clock",{state="value=20:00",trueAct={"`SecheServietteYoga`","turnOff","","if{&vgRetraite:value=1}"}}},

 

etc...

[cag014 731]

 

@GaelP

You can do it in one single line, but I don't know if it is more readable....

May I ask you why turnOff actions depend on "if{&vgRetraite:value=1}"  ?

The reason to my question is, if you have turned on the device and from some reason variable &vgRetraite:value=0 don't you need to turn off the device in any case? Otherwise it will stay ON till next day, right?

 

 

 

 

14 hours ago, Rover said:

global4local= {true,gVarName="aoqVar",varArray={LaatsteBel="",SonosRadio="5", Tuinpomp2uur="Uit", SonosVolume="", clock="", OldDimlevel="", Prio="", PushoverMessage="Welkom", PushoverSound="", PushoverTitle=""}}

Also global4local= {true,gVarName="aoqVar",varArray={LaatsteBel="0",SonosRadio="5", Tuinpomp2uur="Uit", SonosVolume="", clock="", OldDimlevel="", Prio="", PushoverMessage="Welkom", PushoverSound="", PushoverTitle=""}} 

results in the same problem. In the versions before: no problem.

Please login or register to see this spoiler.

Based on definition above, you expect to perform calculation on empty string LaatsteBel="",

Can you set any initial value and test it!?

Edited December 27, 2020 by cag014

[GaelP 0]

The context is that I host people sometime at my place in a different building. They would typically stay with us for a few days.

I want to shut down the radiator, controlled ventilation, the electric tower rails etc... when there is now one staying with us (&vgRetraite = 0) and turn them on when we host people (&vgRetraite = 1). More exactly when we host people, I want to activate the various schedule like turning the tower rails from 6:30 till 7:45 and from 6pm till 8pm for instance or the radiator from sunrise -1800 till whatever... 

To your point indeed I don't need the condition for the turn-off: worst they will be turn-off even if they were already turned off. 

I hope this was clear?

[cag014 731]

22 minutes ago, GaelP said:

The context is that I host people sometime at my place in a different building. They would typically stay with us for a few days.

I want to shut down the radiator, controlled ventilation, the electric tower rails etc... when there is now one staying with us (&vgRetraite = 0) and turn them on when we host people (&vgRetraite = 1). More exactly when we host people, I want to activate the various schedule like turning the tower rails from 6:30 till 7:45 and from 6pm till 8pm for instance or the radiator from sunrise -1800 till whatever... 

To your point indeed I don't need the condition for the turn-off: worst they will be turn-off even if they were already turned off. 

I hope this was clear?

OK... 

If you prefer one single line, try like that

{0,"$blank",{lineState="if{&vgRetraite:value=1}"},timeSlot="true 07:15, true 09:00, true ?$sunriseHour-1800?,true 09:15", 

trueAct={{"`SecheServietteManoir`","turnOn","07:15"},{"`SecheServietteManoir`","turnOff","09:00"},{"`RadiateurManoirSalon`","setValue,99","?$sunriseHour-1800?"},{"`RadiateurManoirSalon`","setValue,25","09:00}}}},

 

and so on

I hope you understand the idea

[Rover 47]

2 hours ago, cag014 said:

Based on definition above, you expect to perform calculation on empty string LaatsteBel="",

Can you set any initial value and test it!?

Edited 1 hour ago by cag014

I have showed above the initial value "0" with the same problems as 0 or "1000" or "": &LaatsteBel is seen as boolean value (local 'r'). This was no problem in 9.1!

Edited December 27, 2020 by Rover

[Rover 47]

2 hours ago, Rover said:

I have showed above the initial value "0" with the same problems as 0 or "1000" or "": &LaatsteBel is seen as boolean value (local 'r'). This was no problem in 9.1!

Using a GV LaatsteBel with value 0 delivers the same problem result as using a LV.

3 minutes ago, Rover said:

Using a GV LaatsteBel with value 0 delivers the same problem result as using a LV.

But lineState={"{`Deurbel`:valueModified > ?(&LaatsteBel) + 15?}"} works!!!

[cag014 731]

4 hours ago, Rover said:

Using a GV LaatsteBel with value 0 delivers the same problem result as using a LV.

But lineState={"{`Deurbel`:valueModified > ?(&LaatsteBel) + 15?}"} works!!!

You mean when GV is in parentheses, it's working?

Can you post what is the GV value and I will try it also... thanks

[Rover 47]

58 minutes ago, cag014 said:

You mean when GV is in parentheses, it's working?

Can you post what is the GV value and I will try it also... thanks

 

58 minutes ago, cag014 said:

You mean when GV is in parentheses, it's working?

Can you post what is the GV value and I will try it also... thanks

Yes, when GV is in parentheses, it's working.

I took initial value "0", but I think if I had token "" it would work like before in 9.1 and before.

[cag014 731]

3 minutes ago, Rover said:

 

Yes, when GV is in parentheses, it's working.

I took initial value "0", but I think if I had token "" it would work like before in 9.1 and before.

Have tried using "0" (even "") and it does work without parentheses also...

[Rover 47]

1 minute ago, cag014 said:

Have tried using "0" (even "") and it does work without parentheses also...

I have showed what happened without parentheses, also...

[Rover 47]

8 hours ago, Rover said:

I have showed what happened without parentheses, also...

{0,"`Deurbel`",{trigAll=true,lineState={"{`Deurbel`:valueModified > ?(&LaatsteBel) + 15?}"},trigAct={   

did not function, so I try:

{0,"`Deurbel`",{trigAll=true,lineState={"{`Deurbel`:valueModified > ?(&LaatsteBel + 15)?}"},trigAct={

also accepted and hopefully function...

[Rover 47]

Please login or register to see this spoiler.

I see a not scheduled trigger by batterylevel ?‍♂️

[cag014 731]

You mean this event not listed in jM lines?

[Rover 47]

7 minutes ago, cag014 said:

You mean this event not listed in jM lines?

This jM lines was triggert: {0,"`VoordeurSwitch`",{trigAll=true,trigAct={{"VoordeurSwitchHC3","sendEmail,2","@`VoordeurSwitch`>sceneActivation"}}}},

but I was not aware that besides the desired sceneActivation triggers like  {0,"`VoordeurSwitch`",{state="sceneActivation=`But1Release`",trueAct={

also a trigger batterylevel could occur. Why? the trigger was 92 (and the VoordeurSwitch has 92% batterylevel indeed), but why a trigger?