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

[Rover 47]

7 hours ago, cag014 said:

Oops, my bad....

You need to define this global in AOQ Parameters definitions

debugHttp   = {["GET"]=false,["POST"]=false,["PUT"]=false}

That could help you to view http commands sent by AOQ in case you need to use it somewhere... (scene, browser and etc.)

or download attached version (fixed to set default if not defined by user)

 

Please login or register to see this attachment.

In 13.4 the local parameter problem has gone.

Thanx for the repair @cag014.

[SmartLifeSystems 20]

Hi cag!

 

I have a problem. Yesterday i updated the new beta version and the push notifications don’t working with this beta.

What do you think?

 

Thanks!

[cag014 731]

can you send push notification somewhere else, i mean not in AOQ

[SmartLifeSystems 20]

2 hours ago, cag014 said:

can you send push notification somewhere else, i mean not in AOQ

 

Yes i know, but I have more than 100 push notifications in the AOQ.

[cag014 731]

Have verified and looks like there is a bug in this version - push notification doesn't work.

I suggest to go back to previous version.

[SmartLifeSystems 20]

22 minutes ago, cag014 said:

Have verified and looks like there is a bug in this version - push notification doesn't work.

I suggest to go back to previous version.

 

Thanks your answere! I tryed the previous version, but the bug is left over.

 

I think, I have to wait for the next version.

Edited September 8, 2022 by SmartLifeSystems

[cag014 731]

I think have found what is going on....

Now the push notification uses user ID only and doesn't support  mobile ID anymore

Could you please change that in AOQ and see if it works.

For example if you're using to send push to user admin, change the mobile ID to 2 (and same for other users)

 

I have added to use users IDs long ago, so it should work just fine.

 

Please login or register to see this spoiler.

 

Edited September 8, 2022 by cag014

[cag014 731]

On 9/7/2022 at 9:53 PM, SmartLifeSystems said:

 

Yes i know, but I have more than 100 push notifications in the AOQ.

Have fixed the error by using push for userID and simplePush for mobile.

According to the ID (user or mobile) AOQ automatically sends correct type of notification.

No changes in user_data required.

 

Please login or register to see this attachment.

 

Let me know if it works...

 

BTW do you use interactive notification in AOQ?

 

Edited September 9, 2022 by cag014

[SmartLifeSystems 20]

16 hours ago, cag014 said:

Have fixed the error by using push for userID and simplePush for mobile.

According to the ID (user or mobile) AOQ automatically sends correct type of notification.

No changes in user_data required.

 

Please login or register to see this attachment.

 

Let me know if it works...

 

BTW do you use interactive notification in AOQ?

 

 

Hi cag, the push notifications working fine, very big thanks! But I got a new bug.

In the bug window, I got a bug message. This line is wrong, but the prev version that's working. I back the v13, and the bug is stayed. What do you think? What is the problem?

 

Here is the line and the in the picture the problem. 

 

{5, "`leilasRoomTemp`",{state="value>&LeilasroomThermostat",timeSlot="m=9~12;1~4;21:30~05:15",timeLoopAct={"`leilasRoomThermostat`","setHeatingThermostatSetpoint,&LeilasroomThermostat","","{@`leilasRoomThermostat`:heatingThermostatSetpoint>&LeilasroomThermostat}"}}},

Please login or register to see this attachment.

[cag014 731]

Hi,

While using in condition statement to compare value of the device no @ sign required. Like that

`leilasRoomThermostat`:heatingThermostatSetpoint>&LeilasroomThermostat

 

Only when you need to retrieve the value of the device  in formula or message the @ sign is required.

@`leilasRoomThermostat`>heatingThermostatSetpoint

for example:

trueAct={"","tts","the set point of room thermostat is @`leilasRoomThermostat`>heatingThermostatSetpoint"} (no comparation in the line)

 

 

Use that line

 

{5, "`leilasRoomTemp`",{state="value>&LeilasroomThermostat",timeSlot="m=9~12;1~4;21:30~05:15",timeLoopAct={"`leilasRoomThermostat`","setHeatingThermostatSetpoint,&LeilasroomThermostat","","{`leilasRoomThermostat`:heatingThermostatSetpoint>&LeilasroomThermostat}"}}},

Edited September 9, 2022 by cag014

[SmartLifeSystems 20]

23 hours ago, cag014 said:

Hi,

While using in condition statement to compare value of the device no @ sign required. Like that

`leilasRoomThermostat`:heatingThermostatSetpoint>&LeilasroomThermostat

 

Only when you need to retrieve the value of the device  in formula or message the @ sign is required.

@`leilasRoomThermostat`>heatingThermostatSetpoint

for example:

trueAct={"","tts","the set point of room thermostat is @`leilasRoomThermostat`>heatingThermostatSetpoint"} (no comparation in the line)

 

 

Use that line

 

{5, "`leilasRoomTemp`",{state="value>&LeilasroomThermostat",timeSlot="m=9~12;1~4;21:30~05:15",timeLoopAct={"`leilasRoomThermostat`","setHeatingThermostatSetpoint,&LeilasroomThermostat","","{`leilasRoomThermostat`:heatingThermostatSetpoint>&LeilasroomThermostat}"}}},

 

Thanks cag, I understand! The line is working fine.

[Sjekke 87]

Where can I find the latest version of AIO and a manual? 
 

Thx @cag014

[cag014 731]

55 minutes ago, Sjekke said:

Where can I find the latest version of AIO and a manual? 
 

Thx @cag014

At download

Please login or register to see this link.

for HC2

Please login or register to see this link.

 for HC3/HC3 lite and Yubii

Please login or register to see this link.

for PC/MAC

 

If you have an issue with notification (HC3 platform)

Please download file 

Please login or register to see this link.

[Rover 47]

Is 5.120.10 without issues with AOQ?

[cag014 731]

On 9/17/2022 at 5:51 PM, Rover said:

Is 5.120.10 without issues with AOQ?

No issues on my side... everything works

[Rover 47]

Please login or register to see this spoiler.

Hi cag,

What happened here? What is the meaning of (disarmedpoort)? The only device in $Achterpoort is really armed after the arming, so there is no failing arming.

Edited September 27, 2022 by Rover

[cag014 731]

 

On 9/25/2022 at 3:56 PM, Rover said:

Please login or register to see this spoiler.

 

What are the names of the alarm zones you have?

Might be you have alarm zones called Achter and Achterpoort? It could explain this problem

 

Please try version below

 

Please login or register to see this attachment.

 

Let me know if everything works fine...

Edited September 28, 2022 by cag014

[Rover 47]

11 hours ago, cag014 said:

 

 

What are the names of the alarm zones you have?

Might be you have alarm zones called Achter and Achterpoort? It could explain this problem

 

Please try version below

 

Please login or register to see this attachment.

 

Let me know if everything works fine...

Hi cag,

Yes your suspection was true: there is also a zone Achter. 

V13.7 executes the armAlarm statement in zone Achterpoort correct now, but breaching the sensor in zone Achterpoort does not trigger an alarm, while another (same type of) sensor in another zone does the triggering correctly.

BTW: v13.7 initiates the AOQ much faster than v13.4 ?

[cag014 731]

2 hours ago, Rover said:

Hi cag,

Yes your suspection was true: there is also a zone Achter. 

V13.7 executes the armAlarm statement in zone Achterpoort correct now, but breaching the sensor in zone Achterpoort does not trigger an alarm, while another (same type of) sensor in another zone does the triggering correctly.

BTW: v13.7 initiates the AOQ much faster than v13.4 ?

Is the same sensor defined in both zones?

[Rover 47]

1 hour ago, cag014 said:

Is the same sensor defined in both zones?

No, both zones &Achterpoort en $Deuren (not the zone $Achter) have one different Fibaro D/W sensor. Breaching $Deuren works, but breaching $Achterpoort does not work. These two devices are not defined in zone $Achter.

Edited September 28, 2022 by Rover