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

[cag014 731]

Interesting ...

Here the latest beta release, says public release????

Please login or register to see this spoiler.

 

[Guest Benrive]

3 minutes ago, cag014 said:

Interesting ...

Here the latest beta release, says public release????

Please login or register to see this spoiler.

 

an error, the developers will have it.

[Guest Benrive]

On 4/5/2022 at 3:33 PM, Benrive said:

 

an error, the developers will have it.

 

Hello @cag014.

 

I already have the update that carries the zigbee beta, but I don't think it supports the device I want to buy Aqara Cube.

 

Please login or register to see this image.

/monthly_2022_04/image.png.2f71ca36032debb2cf5a4e356542cfcf.png" />

[cag014 731]

13 hours ago, Benrive said:

 

Hello @cag014.

 

I already have the update that carries the zigbee beta, but I don't think it supports the device I want to buy Aqara Cube.

 

Please login or register to see this link.

I think there is no support for Zigbee  remote controllers yet...

Here the primary list of supported Zigbee devices (Alpha release) 

 

Please login or register to see this attachment.

Edited April 8, 2022 by cag014

[cag014 731]

On 3/29/2022 at 11:44 PM, cag014 said:

 

By looking on your lines I think it's a good idea to add an option to use $geoUser keyword as part of the global variable name, so then the line could be very simple like:

Please login or register to see this code.

Current version doesn't support that , but will make the changes in AOQ and post it for test. 

@Benrive

As promised, here a version that supports key words variables as part of global variable name.

In addition this version supports ZigBee devices also.

Please try to use jM line above and let me know if it works.

Please login or register to see this attachment.

[SmartLifeSystems 20]

26 minutes ago, cag014 said:

@Benrive

As promised, here a version that supports key words variables as part of global variable name.

In addition this version supports ZigBee devices also.

Please try to use jM line above and let me know if it works.

Please login or register to see this attachment.

 

Hi cag,

 

I got the next message. My Alarm system is a Satel Integra.

 

Please login or register to see this attachment.

Please login or register to see this attachment.

[cag014 731]

6 minutes ago, SmartLifeSystems said:

 

Hi cag,

 

I got the next message. My Alarm system is a Satel Integra.

 

Please login or register to see this attachment.

Please login or register to see this attachment.

$actDay is not part of global keywords and probably defined as user keywords! Did it work on previous version?

There is $actDate global keyword....

[SmartLifeSystems 20]

Just now, cag014 said:

$actDay is not part of global keywords and probably defined as user keywords! Did it work on previous version?

There is $actDate global keyword....

 

 

Yes. That's my wrong! Sorry!

Just now, SmartLifeSystems said:

 

 

Yes. That's my wrong! Sorry!

 

I repaired now.

[Guest Benrive]

18 hours ago, cag014 said:

@Benrive

As promised, here a version that supports key words variables as part of global variable name.

In addition this version supports ZigBee devices also.

Please try to use jM line above and let me know if it works.

Please login or register to see this attachment.

 

Hey @cag014,

 

I just replaced the 3 change lines of the GPSxxx variable with the new one incorporated, much simpler by concatenating GPS and userName.

 

I inform you when I have the first change of state that it works. Sure good.?

 

Thanks for adding the zigbee part, but I don't have any devices yet.
I wanted to buy try the aqara cube but it is not supported at the moment.
As soon as I can try something from zigbee I'll let you know.

Thank you for your great work

[cag014 731]

48 minutes ago, Benrive said:

Thanks for adding the zigbee part, but I don't have any devices yet.

The Zigbee devices are very cheap comparing to Z-wave, so I suggest if you about to purchase more devices, take a look on Zigbee. (even at AliExpress) 

[Guest Benrive]

On 4/11/2022 at 12:49 PM, Benrive said:

 

Hey @cag014,

 

I just replaced the 3 change lines of the GPSxxx variable with the new one incorporated, much simpler by concatenating GPS and userName.

 

I inform you when I have the first change of state that it works. Sure good.?

 

Thanks for adding the zigbee part, but I don't have any devices yet.
I wanted to buy try the aqara cube but it is not supported at the moment.
As soon as I can try something from zigbee I'll let you know.

Thank you for your great work

Hello @cag014.

works perfectly.

thsnks 

[Guest Benrive]

Hello @cag014.

 

I have many problems with this line, no matter how much I change the times, it is getting worse and worse.

 

Please login or register to see this code.

when the status is true the lock open “unsecure”. (Cerradurapuerta), it takes about 4 seconds to open It’s well.  after that time I want turnOn “Salabrepuerta” for about 3 or 4 seconds and after that time “SalAbrepuerta” turnOff.  The problem is that the unsecure part makes it perfect but then it can take up to 10 or 15 seconds for “SalAbrepuerta “ to TurnOn and it does so in just 1 second.

 

some delay I do not understand or I am not using it well

[cag014 731]

1 hour ago, Benrive said:

Hello @cag014.

 

I have many problems with this line, no matter how much I change the times, it is getting worse and worse.

 

Please login or register to see this code.

when the status is true the lock open “unsecure”. (Cerradurapuerta), it takes about 4 seconds to open It’s well.  after that time I want turnOn “Salabrepuerta” for about 3 or 4 seconds and after that time “SalAbrepuerta” turnOff.  The problem is that the unsecure part makes it perfect but then it can take up to 10 or 15 seconds for “SalAbrepuerta “ to TurnOn and it does so in just 1 second.

 

some delay I do not understand or I am not using it well

As I understand the problem with the timing is to turnOff the SalAbrePuerta after it turns ON, correct?

It could be better idea to use WHEN conditions or to split that  to few more lines for this action.

1. using WHEN

{0,"`EntAbrePuerta`",{state="centralSceneSupport=1.Pressed#2",

trueAct={{"`cerraduraPuerta`","unsecure"},{"`SalAbrePuerta`","turnOn", "When {`cerraduraPuerta`:value=unsecured"},

{"`SalAbrePuerta`","turnOff","5","When {`SalAbrePuerta`:state=true"}}}},

 

1. Split the lines (might be these devices used somewhere else differently, so lineState could be used

{0,"`EntAbrePuerta`",{state="centralSceneSupport=1.Pressed#2",trueAct={{"`cerraduraPuerta`","unsecure"}}},

{0,"`cerraduraPuerta`",{ lineState="if {`EntAbrePuerta`:centralSupport=1.Pressed}", state="unsecured", trueAct={"`SalAbrePuerta`","turnOn"}}},

{0,"`SalAbrePuerta`",{lineState="if {`EntAbrePuerta`:centralSupport=1.Pressed}",state="true", trueAct={"`SalAbrePuerta`","turnOff","5"}}}

 

 

Edited April 12, 2022 by cag014

[Guest Benrive]

2 hours ago, cag014 said:

As I understand the problem with the timing is to turnOff the SalAbrePuerta after it turns ON, correct?

It could be better idea to use WHEN conditions or to split that  to few more lines for this action.

1. using WHEN

{0,"`EntAbrePuerta`",{state="centralSceneSupport=1.Pressed#2",

trueAct={{"`cerraduraPuerta`","unsecure"},{"`SalAbrePuerta`","turnOn", "When {`cerraduraPuerta`:value=unsecured"},

{"`SalAbrePuerta`","turnOff","5","When {`SalAbrePuerta`:state=true"}}}},

 

1. Split the lines (might be these devices used somewhere else differently, so lineState could be used

{0,"`EntAbrePuerta`",{state="centralSceneSupport=1.Pressed#2",trueAct={{"`cerraduraPuerta`","unsecure"}}},

{0,"`cerraduraPuerta`",{ lineState="if {`EntAbrePuerta`:centralSupport=1.Pressed}", state="unsecured", trueAct={"`SalAbrePuerta`","turnOn"}}},

{0,"`SalAbrePuerta`",{lineState="if {`EntAbrePuerta`:centralSupport=1.Pressed}",state="true", trueAct={"`SalAbrePuerta`","turnOff","5"}}}

 

 

ok, I'm going to try the options you give me and I'll let you know. Although there is an error in the status update of the danalock lock, it doesn't always update or it doesn't do it right.

For this I have the Global LockStatus variable.  What I do to give the correct state is to force it to close “secure” and update the variable to 1 when the door is closed and there is no movement for 2 minutes.

 

when I send unsecure I update the variable lockststus to 0.

 

I'm going to test what you're saying by substituting the status of the lock for that of the lockstatus variable.
 

I'll try tomorrow and let you know
 

thanks 

[Guest Benrive]

15 hours ago, Benrive said:

ok, I'm going to try the options you give me and I'll let you know. Although there is an error in the status update of the danalock lock, it doesn't always update or it doesn't do it right.

For this I have the Global LockStatus variable.  What I do to give the correct state is to force it to close “secure” and update the variable to 1 when the door is closed and there is no movement for 2 minutes.

 

when I send unsecure I update the variable lockststus to 0.

 

I'm going to test what you're saying by substituting the status of the lock for that of the lockstatus variable.
 

I'll try tomorrow and let you know
 

thanks 

 

Ok, It's better but a i have a question witch a conditions.

 

{"`SalAbrePuerta`","turnOn","when {&GPSMariAsun:value=2}{&GPSBenja:value=2}{&GPSSofia:value=2} and {`cerraduraPuerta`:value=false}"}

 

I need the condition it's

 

When (&GPSMariAsun:value=2 or GPSBenja:value=2 or GPSSofia:value=2 ) And (`cerraduraPuerta`:value=false) 

It's true when cerraduraPuerta:value=false and any of the GPS variables = 2

 

What am I doing wrong?

 

You can see the webeye. All conditions are considered OR.

 

Please login or register to see this image.

/monthly_2022_04/image.png.41d97385787421c69390ca1733b33ea1.png" />

 

Edited April 13, 2022 by Benrive

[cag014 731]

The "and" condition should be inside the brackets. Any additional condition in brackets is "or" state.

Since {`cerraduraPuerta`:value=false}"} is the common "must" condition I suggest to add lineState, but since I don't have your entire line it could be wrong.

 

lineState="if{`cerraduraPuerta`:value=false}", {"`SalAbrePuerta`","turnOn","when {&GPSMariAsun:value=2} or {&GPSBenja:value=2} or {&GPSSofia:value=2}}

 

Another question Why use use WHEN condition? It should be "IF", isin't?

 

Please post entire line and if you can expalin what exactly you need to achieve I can provide some other options...

[Guest Benrive]

On 4/13/2022 at 4:23 PM, cag014 said:

The "and" condition should be inside the brackets. Any additional condition in brackets is "or" state.

Since {`cerraduraPuerta`:value=false}"} is the common "must" condition I suggest to add lineState, but since I don't have your entire line it could be wrong.

 

lineState="if{`cerraduraPuerta`:value=false}", {"`SalAbrePuerta`","turnOn","when {&GPSMariAsun:value=2} or {&GPSBenja:value=2} or {&GPSSofia:value=2}}

 

Another question Why use use WHEN condition? It should be "IF", isin't?

 

Please post entire line and if you can expalin what exactly you need to achieve I can provide some other options...

 

Hi @cag014,

 

The complete line

This is the sequence that's driving me crazy, there's really no way for the door opening behavior to be effective.

 

For one thing, I use a variable instead of the state of the lock (because it fails a lot). &LockStatus
I use a line with TrueAct to change the state of the variable.

 

cerraduraPuerta is a lock danalock

Please login or register to see this code.

To make sure of the state I use a timeLoopAct line every 10 minutes to update the variable.

Please login or register to see this code.

 

I use When because it must wait for the lockstatus variable to have that state.

I change its state when it is detected that the lock is True or False.
I use a separate line simply for better understanding

 

Please login or register to see this code.

 

 

 

 

 

 

Edited April 18, 2022 by Benrive

[cag014 731]

I'm wondering why you're using +value for 

 

Please login or register to see this code.

Is it means property value is not available for cerraduraPuerta? Interesting...

Could you post API data of cerraduraPuerta when it's closed and one when it's open?

 

 

 

Edited April 18, 2022 by cag014

[Guest Benrive]

2 hours ago, cag014 said:

Is it means property value is not available for cerraduraPuerta? Interesting...

yes, it is because it does not support it and in this way I can know more or less if it is true or false although the status fails a lot.  It is something that I imagine they will fix in future Danalock updates

 

2 hours ago, cag014 said:

Could you post API data of cerraduraPuerta when it's closed and one when it's open?

Danalock Locked

Please login or register to see this code.

Danalock Unlocked

Please login or register to see this code.

 

Edited April 18, 2022 by Benrive

[cag014 731]

Looks like property value does exists... and no need to use +value.

As I understand you have an issue when the lock is open or close, I mean it takes uncertain time, correct?

Another observation, there is a property call secured. When the lock is open the secured=0. When lock closed secured=255.

May be, just may be this property could help you. I mean may be during the lock/unlock process the value of secured changed till reaches the final result  ( or 255), worth to try.

Please login or register to see this code.

Edited April 19, 2022 by cag014