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

[cag014 632]

On 4/24/2023 at 10:31 AM, Rover said:

Hi @cag014,

Please login or register to see this spoiler.

sendEmail disabled by default to avoid sending emails or notification on each startup.

To enable this, please add true (Boolean) at the end of the command in the tables (trueAct, falseAct and etc.)

trueAct={{"Apparaten Aan","sendEmail,2","Stroomprijs: @`zonEnergie`>userDescription",true},

 

By the way you can define initAct{} table, in this case any command in the table is executed on startup.

 

Please use latest version 16.7(posted in this topic)

Edited May 4, 2023 by cag014

[Rover 46]

Please login or register to see this spoiler.

What to do to decrease the API POST time? It is high already for a long time.

[PSi 6]

Hi, 

I have some Elero blinds in place and when I add them to my config, the log displays the following error:

(35) Item ID 25 not found in the system.

 

There also seems to be an issue with sunset/sunrise. Potentially following line leads to errors in the logs:

[09.05.2023] [08:51:06] [ERROR] [QUICKAPP98]: main.lua:839: attempt to index a nil value (field '?')

 

        timeSlot="?$sunsetHour-(60*60)?~?$sunriseHour+(60*60)?", 

[cag014 632]

18 minutes ago, PSi said:

Hi, 

I have some Elero blinds in place and when I add them to my config, the log displays the following error:

(35) Item ID 25 not found in the system.

 

There also seems to be an issue with sunset/sunrise. Potentially following line leads to errors in the logs:

[09.05.2023] [08:51:06] [ERROR] [QUICKAPP98]: main.lua:839: attempt to index a nil value (field '?')

 

        timeSlot="?$sunsetHour-(60*60)?~?$sunriseHour+(60*60)?", 

1. Are you sure you have device id 25? Could you please post the device API data?

2. timeSlot works just fine, no issue found. Please post the entire line...

[cag014 632]

2 hours ago, Rover said:

Please login or register to see this spoiler.

Honestly never happened in my HC3. Could be CPU load, did you try to reboot?

[Rover 46]

On 4/29/2023 at 10:34 AM, Rover said:

I looks like there is still a problem:

Please login or register to see this spoiler.

Hi @cag014, can you solve this?

[cag014 632]

18 hours ago, Rover said:

Hi @cag014, can you solve this?

Don't follow you, what delay you're talking about?

[Rover 46]

12 minutes ago, cag014 said:

Don't follow you, what delay you're talking about?

    {"`NEST21`", '+NEST21',"if {&Verwarming:value=19} or {&Verwarming:value=21}"}, 

    {"`NEST19`", '+NEST19',"timerHeatOn,900","if {&Verwarming:value=19 and &Huisstatus=Thuis and `gasPrijs`:value>&cheapGas}"},

The execution of the second line should be postponed for 15 minutes (the timer function), but it has been executed right after the first line showed:

[29.04.2023] [09:00:42] [TRACE] [AOQ387]: jM{10}T  &SwitchScene:Global[Disarm] ↪ NEST21{NEST21) if{&Verwarming=19} or {&Verwarming(19)=21}

[29.04.2023] [09:00:42] [TRACE] [AOQ387]: jM{10}T  &SwitchScene:Global[Disarm] ↪ NEST19{NEST19) if{&Verwarming=19 and &Huisstatus=Thuis and gasPrijs(1.1)>0.8&:cheapGas}

[Rover 46]

21 hours ago, cag014 said:

Honestly never happened in my HC3. Could be CPU load, did you try to reboot?

Please login or register to see this spoiler.

After reboot HC3. Still pretty high isn't it?

[cag014 632]

41 minutes ago, Rover said:

Please login or register to see this spoiler.

 

• Quote

[Rover 46]

3 hours ago, Rover said:

Please login or register to see this spoiler.

Could the existance of some dead devices cause these slowness?

[cag014 632]

1 hour ago, Rover said:

Could the existance of some dead devices cause these slowness?

Once the dead device detected the system suspends any communication with the device, but if somehow the code or user wakes up the device, it will resume the communication and will slow the system.

Worst case scenario, that you have devices that sometime dead and wakeup over and over.

 

The bottom line please do not wake up dead device, unless something has been done to solve the problem.

 

 

[cag014 632]

6 hours ago, Rover said:

    {"`NEST21`", '+NEST21',"if {&Verwarming:value=19} or {&Verwarming:value=21}"}, 

    {"`NEST19`", '+NEST19',"timerHeatOn,900","if {&Verwarming:value=19 and &Huisstatus=Thuis and `gasPrijs`:value>&cheapGas}"},

The execution of the second line should be postponed for 15 minutes (the timer function), but it has been executed right after the first line showed:

[29.04.2023] [09:00:42] [TRACE] [AOQ387]: jM{10}T  &SwitchScene:Global[Disarm] ↪ NEST21{NEST21) if{&Verwarming=19} or {&Verwarming(19)=21}

[29.04.2023] [09:00:42] [TRACE] [AOQ387]: jM{10}T  &SwitchScene:Global[Disarm] ↪ NEST19{NEST19) if{&Verwarming=19 and &Huisstatus=Thuis and gasPrijs(1.1)>0.8&:cheapGas}

Sorry, very stupid typo error , my bad

Try attached

Please login or register to see this attachment.

 

[Rover 46]

21 hours ago, cag014 said:

Once the dead device detected the system suspends any communication with the device, but if somehow the code or user wakes up the device, it will resume the communication and will slow the system.

Worst case scenario, that you have devices that sometime dead and wakeup over and over.

 

The bottom line please do not wake up dead device, unless something has been done to solve the problem.

 

 

Please login or register to see this spoiler.

The devices Licht1 and Licht2 are Fibaro wall switches. They are not always in the wall (Christmas light), but I want them working when put in the wall.

[Rover 46]

On 5/10/2023 at 5:44 PM, cag014 said:

Sorry, very stupid typo error , my bad

Try attached

Please login or register to see this attachment.

 

It works! Thanx for the repair Cag.

[cag014 632]

On 5/11/2023 at 3:30 PM, Rover said:

Please login or register to see this spoiler.

AOQ will try to wake up any dead device that included in the jM lines to maintain proper control of the automation.

If your device is dead occasionally, I suggest to solve the problem somehow. May be to add Zwave repeater or to use ZigBee wall switch, which has better coverage (based on my experience)

If your switch in use for Christmas only, it might be a good idea to remove it from jM configuration when not in use. You can suspend the line w/o actually to delete it, so in the future you don't need to recall how it was configured.

Edited May 15, 2023 by cag014

[Rover 46]

19 hours ago, cag014 said:

AOQ will try to wake up any dead device that included in the jM lines to maintain proper control of the automation.

If your device is dead occasionally, I suggest to solve the problem somehow. May be to add Zwave repeater or to use ZigBee wall switch, which has better coverage (based on my experience)

If your switch in use for Christmas only, it might be a good idea to remove it from jM configuration when not in use. You can suspend the line w/o actually to delete it, so in the future you don't need to recall how it was configured.

It is nice that AOQ tries to wake up any dead device. But if you deliberately remove a wall switch, it should not wake up.

Removal from jM configuration when not in use is a very poor solution with a WAF of 2 points. Christmas time: "the Christmas lights are not functioning, can you repair this?", "Yes dear, I have to change the programme." 😟

Better solutions than removal from jM configuration:

1- Wall switches are not waked up.

2- Devices are not waked up by: jS2n: Kerstboom="62",notWakeup

3- AOQ PARAMETERS: notWakeup = 62,316,398 (3 deviceID's)

[PSi 6]

On 5/9/2023 at 2:51 PM, cag014 said:

1. Are you sure you have device id 25? Could you please post the device API data?

2. timeSlot works just fine, no issue found. Please post the entire line...

Hi, here are my replies:

1. yes, this is the ID of the blind, json attached: 

Please login or register to see this image.

/monthly_2023_05/image.png.401d947aff75f1d87f30954e35923115.png" />

 

2. perhaps this is related to bad timnig? I have a movement sensor that switches on the lights in defined times. Issues seems to arise when switching off is scheduled to happen after this slot.

 

    {"`motionSensor`",

        {state="true",  

        timeSlot="?$sunsetHour-(60*60)?~?$sunriseHour+(60*60)?", 

        trueAct={"`light`","turnOn"}, 

        falseAct={"`light`","turnOff", "timerLight,90"}}},

 

Please login or register to see this attachment.

[cag014 632]

1 hour ago, PSi said:

Hi, here are my replies:

1. yes, this is the ID of the blind, json attached: 

Please login or register to see this link.

 

2. perhaps this is related to bad timnig? I have a movement sensor that switches on the lights in defined times. Issues seems to arise when switching off is scheduled to happen after this slot.

 

    {"`motionSensor`",

        {state="true",  

        timeSlot="?$sunsetHour-(60*60)?~?$sunriseHour+(60*60)?", 

        trueAct={"`light`","turnOn"}, 

        falseAct={"`light`","turnOff", "timerLight,90"}}},

 

Please login or register to see this attachment.

Is it nice device?

[cag014 632]

4 hours ago, Rover said:

It is nice that AOQ tries to wake up any dead device. But if you deliberately remove a wall switch, it should not wake up.

Removal from jM configuration when not in use is a very poor solution with a WAF of 2 points. Christmas time: "the Christmas lights are not functioning, can you repair this?", "Yes dear, I have to change the programme." 😟

Better solutions than removal from jM configuration:

1- Wall switches are not waked up.

2- Devices are not waked up by: jS2n: Kerstboom="62",notWakeup

3- AOQ PARAMETERS: notWakeup = 62,316,398 (3 deviceID's)

So, you want to be able to define list of devices that should be skipped during the wake-up process? You do understand that the devices that are dead won't respond to the commands? In other words, AOQ won't be able to operate correctly with these devices!