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

[cag014 731]

Just now, Rover said:

And now I got his present ?

Yea ?

[Rover 47]

global4local= {false,gVarName="",varArray={Achterkant="",

What is the advantage of using a system GV in gVarName instead of ""?

[cag014 731]

15 minutes ago, Rover said:

global4local= {false,gVarName="",varArray={Achterkant="",

What is the advantage of using a system GV in gVarName instead of ""?

When using AOQ internal GV, on every restart it's start from default value as defined in varArray.

By using system's GV all values are stored and retrieved on every AOQ restart.

For example: you have defined variable for alarm

global4local= {false,gVarName="",varArray={Alarm="disarmed",

now in some point you have armed the alarm and Alarm="armed".

If you restart AOQ, the Alarm will be set again to disarmed, but if you're using system GV the last value is stored and retrieved on restart. So in this case even after restart Alarm value is armed.

By the way to use system GV you need to set not ony gVarName, but to set the first value true as well.

global4local= {true,gVarName="AOQtank",varArray={Alarm="disarmed",

 

Please define GV in system before usage (AOQ doesn't create the GV)

Edited October 23, 2020 by cag014

[cag014 731]

Another use for system GV is for reminders (if you're using them).

global4rmd  = {false,gVarName=""} 

If you're using reminders it is strongly recommended to define system GV.

In example: washing machine has finished and you have set reminder for that ( to remind every 20 min. to move laundry to dryer..) till dryer has started.

If you'll restart AOQ the reminder will be initialized (deleted).

By using system GV, the reminder will be retrieved on AOQ restart and continue to remind you....

Do not set same system GV for variables and reminders...

[Rover 47]

6 minutes ago, cag014 said:

Another use for system GV is for reminders (if you're using them).

global4rmd  = {false,gVarName=""} 

If you're using reminders it is strongly recommended to define system GV.

In example: washing machine has finished and you have set reminder for that ( to remind every 20 min. to move laundry to dryer..) till dryer has started.

If you'll restart AOQ the reminder will be initialized (deleted).

By using system GV, the reminder will be retrieved on AOQ restart and continue to remind you....

Do not set same system GV for variables and reminders...

That is clearly explained, TNX!

[Rover 47]

Please login or register to see this spoiler.

Zwave Me wall switch did not react, only after 6 times pushing button.

Edited October 23, 2020 by Rover

[cag014 731]

11 hours ago, Rover said:

Please login or register to see this spoiler.

Are you sure it's not Zwave Me. I have same device and when a battery goes low it takes few presses to activated. Have drilled a hole to see the Led. (when works it's flashing green)

Edited October 23, 2020 by cag014

[cag014 731]

Please upgrade urgently...

Have found Some issue with os.date() and fixed...  keyword $24clock has been impacted...

and faster reaction

 

Please login or register to see this attachment.

Edited October 23, 2020 by cag014

[Sjakie 156]

Cag,

By using system GV, the reminder will be retrieved on AOQ restart and continue to remind you....

This I dont want, thanks for your explanation.

1)

hoofdSlaapKamerlader true will trigger the GV DagRitme Bedtijd and false is Opstaan how to do?

2)

[23.10.2020] [07:56:01] [ERROR] [QUICKAPP314]: QuickApp crashed

was a slave wallplug deleted and installed again

3)

[23.10.2020] [08:04:28] [ERROR] [QUICKAPP297]: POST http://192.168.1.15/api/devices/1079/action/turnOff {"args":[{}]} Bad file descriptor

This is a Fibaro dubble relais

4)

Alarm???

If I go to HC3 alarm I dont see all my slave sensor doors 2 out of 9???  

5)

jSlave={     hc2={user="sjaak>>>> if this is enabled thus that mean HC2 will do nothing and waits for order from HC3?

Because HC2 is doing nothing only id HC3 is off? or due to oveload?

 

Sorry to have so manny questions ,

Please advice,

//Sjakie

 

[Rover 47]

Please login or register to see this spoiler.

 

[Sjakie 156]

Cag,

Fibaro did an emergency restore??? Started all over again with AOS

This problem is solved I see them now!!

4)

Alarm???

If I go to HC3 alarm I dont see all my slave sensor doors 2 out of 9???  

 

//Sjakie

 

[Rover 47]

1 hour ago, Rover said:

Please login or register to see this spoiler.

 

iClock did not function this night, so a lot of lights still were on at awakening time this morning.

It looks like the High REST API response time is quiet with v5.5.

AOQ initiation is very fast ?

Edited October 23, 2020 by Rover

[cag014 731]

2 hours ago, Rover said:

 

iClock did not function this night, so a lot of lights still were on at awakening time this morning.

It looks like the High REST API response time is quiet with v5.5.

AOQ initiation is very fast ?

Yes, the 5.2/3/4 has an issue with os.date().

What about 5.5?

[Rover 47]

16 minutes ago, cag014 said:

Yes, the 5.2/3/4 has an issue with os.date().

What about 5.5?

I can see this on the end of the day.

The  High REST API response time is still quiet.

Edited October 23, 2020 by Rover

[SmartLifeSystems 20]

1 hour ago, cag014 said:

Yes, the 5.2/3/4 has an issue with os.date().

What about 5.5?

 

I think, the 5.5 working fine. No problem with the os.date.

[SmartLifeSystems 20]

Not only the os.date was the problem. I have some lines for my thermostat heads battery level checking but the "batteryLevel" code did'n work. What i can see now, is working fine with the 5.5.

Edited October 23, 2020 by SmartLifeSystems

[Rover 47]

Please login or register to see this spoiler.

The  High REST API response time has started again...

[SmartLifeSystems 20]

3 hours ago, SmartLifeSystems said:

Not only the os.date was the problem. I have some lines for my thermostat heads battery level checking but the "batteryLevel" code did'n work. What i can see now, is working fine with the 5.5.

 

I think, the @<devID>>lastBreached code don't working.

Edited October 23, 2020 by SmartLifeSystems

[Rover 47]

Please login or register to see this spoiler.

 

[Rover 47]

In Advanced User's Guide 4.0:  1. In case property is sceneActivation or CentralSceneSupport, trigAll set to true by default.

But trigAll is not functioning with CentralSceneSupport at all, even if trigAll has been added explicitly:

{0,"`PortSwitch`",{initOnStartup=false,trigAll=true,state="centralSceneSupport=6.Pressed",trueAct={

Only pressing button once is working, until another button has been pressed.