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

[cag014 731]

9 hours ago, SmartLifeSystems said:

 

 

So I think, I can't use this device with the HC3...

No

[Rover 47]

Hi @cag014,

 

• To receive the 'last modified' time of any property, add “Modified” to property name. For example, to get when the device was last changed, the property should be valueModified. Returned value is number of seconds from last change.

 

{"Deurbel","sendEmail,2","vorige bel: @`Deurbel`>valueModified"},

 

Content email:

Deurbel

vorige bel: 1174645

 

I do not think that 1174645 is Returned value in number of seconds from last change.

 

BTW, I am using email a lot in order to get the content of a value at a certain moment.

Addition of {"Debug", "text", {value.1, value.2, value.3} }  (value.x is the value of a device or a GV or a LV), putting this info in the AOQ debug list, would make the lives of us happy AOQ developers still even happier ?

Edited December 18, 2020 by Rover

[cag014 731]

2 hours ago, Rover said:

Hi @cag014,

 

BTW, I am using email a lot in order to get the content of a value at a certain moment.

Addition of {"Debug", "text", {value.1, value.2, value.3} }  (value.x is the value of a device or a GV or a LV), putting this info in the AOQ debug list, would make the lives of us happy AOQ developers still even happier ?

You mean to print this data in debug window?

 

If so, you just reading my mine, that's exactly what I'm working on...

 

[Rover 47]

45 minutes ago, cag014 said:

You mean to print this data in debug window?

 

If so, you just reading my mine, that's exactly what I'm working on...

 

Yes I ment the debug window.

[Rover 47]

2 hours ago, Rover said:

• To receive the 'last modified' time of any property, add “Modified” to property name. For example, to get when the device was last changed, the property should be valueModified. Returned value is number of seconds from last change.

 

{"Deurbel","sendEmail,2","vorige bel: @`Deurbel`>valueModified"},

 

Content email:

Deurbel

vorige bel: 1174645

 

I do not think that 1174645 is Returned value in number of seconds from last change.

Are you going to repair this?

[cag014 731]

On 12/18/2020 at 9:01 PM, Rover said:

Are you going to repair this?

I thought I've answered...

Have tested that several times and it works correctly, don't see any problem.

Are you sure that Deurbel properties parameter "value" has changed recently?

 

Edited December 20, 2020 by cag014

[Rover 47]

1 hour ago, cag014 said:

I thought I've answered...

Have tested that several times and it works correctly, don't see any problem.

Are you sure that Deurbel properties parameter "value" has changed recently?

 

Yes

 

Deurbel

vorige bel: 1174645

 

Deurbel

vorige bel: 1174642

Edited December 20, 2020 by Rover

[cag014 731]

Could you please go to

http://api/devices/<DevID>/properties/value

and post the value and modified data...

 

 

[Rover 47]

7 hours ago, cag014 said:

Could you please go to

http://api/devices/<DevID>/properties/value

and post the value and modified data...

 

 

It is a Fibaro D/W sensor 

Please login or register to see this spoiler.

 

[cag014 731]

7 minutes ago, Rover said:

It is a Fibaro D/W sensor 

Please login or register to see this spoiler.

and you still receive big number in valueModified ?

[Rover 47]

18 minutes ago, cag014 said:

and you still receive big number in valueModified ?

{"Deurbel","sendEmail,2","vorige bel: @`Deurbel`>valueModified"},

 

Deurbel

vorige bel: 126977

 

Deurbel

vorige bel: 127153

 

Deurbel

vorige bel: 127158

 

It is not the number of seconds from last change, but the time since last change (in seconds). I need the number of seconds from last change to be able to use it in lineState. It is not possible to calculate the time difference in lineState.

I need this function to be able to filter the bouncing of the doorbell button.

Edited December 20, 2020 by Rover

[cag014 731]

3 minutes ago, Rover said:

{"Deurbel","sendEmail,2","vorige bel: @`Deurbel`>valueModified"},

 

Deurbel

vorige bel: 126977

 

Deurbel

vorige bel: 127153

 

Deurbel

vorige bel: 127158

 

It is not the number of seconds from last change, but the time since last change (in seconds). I need the number of seconds from last change to be able to use it in lineState. It is not possible to calculate the time difference in lineState.

This is the time in seconds from the last change of value (either true or false).

 

[Rover 47]

16 minutes ago, cag014 said:

This is the time in seconds from the last change of value (either true or false).

 

O.K. the value does not change by pushing the doorbell button, just scene activation is useable.

Do you know a way to filter the bouncing of the doorbell button? Something with setValue?

I have tried to do it in this way, but calculation in lineState is not accepted: 

{0,"`Deurbel`",{trigAll=true,lineState={"{?@`Deurbel`>valueModified - &LaatsteBel:value? > 15}"},trigAct={ --Deurbel geluid (niet als herhaald binnen 15 seconden) 

      {"Deurbel","sendEmail,2","tijdverschil: ?@`Deurbel`>valueModified - &LaatsteBel?"},

      {"&LaatsteBel","setGlobal","@`Deurbel`>valueModified"}, --Bewaar tijd laatste bel

      {"Deurbel","sendEmail,2","vorige bel: @`Deurbel`>valueModified"},}}},

Edited December 20, 2020 by Rover

[cag014 731]

Let me see ...

Edited December 20, 2020 by cag014

[cag014 731]

1 hour ago, Rover said:

O.K. the value does not change by pushing the doorbell button, just scene activation is useable.

Do you know a way to filter the bouncing of the doorbell button? Something with setValue?

I have tried to do it in this way, but calculation in lineState is not accepted: 

{0,"`Deurbel`",{trigAll=true,lineState={"{?@`Deurbel`>valueModified - &LaatsteBel:value? > 15}"},trigAct={ --Deurbel geluid (niet als herhaald binnen 15 seconden) 

      {"Deurbel","sendEmail,2","tijdverschil: ?@`Deurbel`>valueModified - &LaatsteBel?"},

      {"&LaatsteBel","setGlobal","@`Deurbel`>valueModified"}, --Bewaar tijd laatste bel

      {"Deurbel","sendEmail,2","vorige bel: @`Deurbel`>valueModified"},}}},

An idea... move the calculation to the right side of the condition

{0,"`Deurbel`",{trigAll=true,lineState={"{`Deurbel`:valueModified > ?&LaatsteBel+ 15?}"},trigAct={ --Deurbel geluid (niet als herhaald binnen 15 seconden) 

 

What do you think?

Edited December 20, 2020 by cag014

[Rover 47]

3 hours ago, cag014 said:

An idea... move the calculation to the right side of the condition

{0,"`Deurbel`",{trigAll=true,lineState={"{`Deurbel`:valueModified > ?&LaatsteBel+ 15?}"},trigAct={ --Deurbel geluid (niet als herhaald binnen 15 seconden) 

 

What do you think?

 

AOQ accepts it and it works ?

You are still genious ?

[cag014 731]

To all, since upcoming HC3 new version doesn't support anymore api.get("/panels/events?type....)  please download attached version (using new api)

In addition this version includes all available debug commands... follow format

 

{"<string tag>","debug","message"}

{"<string tag>","error","message"}

{"<string tag>","warning","message"}

{"<string tag>","trace","message"}

 

You can leave the string tag empty  like {"","trace","message"} and standard tag (AOQ<DEVID>)  will be printed.

I do suggest to use string tag because it could be easily filtered in debug window.

The debug information printed in colors according to the type of the message.

Please login or register to see this spoiler.

 

Hopefully next release will support actions based on GPS location

 

 

Please login or register to see this attachment.

Edited December 22, 2020 by cag014

[gggizmo 6]

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

[cag014 731]

8 hours ago, 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

As far as I know there is a lot of problems with this beta.

My HC3 has an issue with Nice memory and I cannot update to this new beta version.

In any case, looks like the process to execute remote commands takes too long.

If you can, update to previous version. Let's wait for official release.

[SmartLifeSystems 20]

Hi Everybody!

 

I wish every user Merry Christmas!