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

[SmartLifeSystems 19]

For me working correctly the push messages. With this update, no send the push messages to my all phones, only for that one, which is in the JM line added.

Edited March 20, 2021 by SmartLifeSystems

[Rover 45]

No problems with 5.070?

[cag014 628]

3 hours ago, SmartLifeSystems said:

For me working correctly the push messages. With this update, no send the push messages to my all phones, only for that one, which is in the JM line added.

What do you mean only in the jM line?

 

[cag014 628]

50 minutes ago, Rover said:

No problems with 5.070?

Looks like push notifications work with mobile device ID only (user ID not supported in QA anymore)

Please after an update change push notification to mobile ID of the user.

Edited March 21, 2021 by cag014

[SmartLifeSystems 19]

10 hours ago, cag014 said:

What do you mean only in the jM line?

 

If I add in the line only my phone, only my phone get the notifications. For me was not so till now. Every phone got the notifications.

10 hours ago, Rover said:

No problems with 5.070?

Only problem, what I see, I can't change the Satel Integra alarm system icons.

[cag014 628]

2 hours ago, SmartLifeSystems said:

If I add in the line only my phone, only my phone get the notifications. For me was not so till now. Every phone got the notifications.

So it was a bug in the system!?

[SmartLifeSystems 19]

8 minutes ago, cag014 said:

So it was a bug in the system!?

 

Yes it was. I have 3 Iphones and not worked correctly.

[Dann 4]

Hi Cag014,

 

Hi Cag014,

 

I am having some issues and your recommendation is highly appreciated.

 

Simple jM command line I am using leads to the below error message.

My Dimmerlight is a dimmer ( ID 130 ) which I want to set at value 22.

 

Any suggestion is welcomed.

{0,"$24clock",{state="value=0",timeSlot="?$sunsetHour+2700?~,~?$sunriseHour-2700?",trueAct={"`Dimmerlights`","setValue,22","",false},falseAct={"`Dimmerlights`","turnOff","",false}}},

[23.03.2021] [21:42:04] [DEBUG] [AOQ1636]: _☠ [23 Mar 21:42:04] AOQ1636^9.5 jM hash table:7:~: {0, "$24clock"...}
{0,"$24clock",{"timeSlot"="?$sunsetHour+2700?~,~?$sunriseHour-2700?","trueAct"={"130","setValue,22","",false,false},"falseAct"={"130","turnOff","",false},"state"="value=0"}}

(8) Action 'setValue' not found for ID(130) Supported actions:

`Dimmerlights`Dimmer lights:130:Front court Device's actions are:
-
User Defined Actions:
- turnOn turnOff
AOQ Supported Actions: (11% in use)
- addRmd armAlarm debug delAllRmd delLogRmd delRmd
- disableScene disarmAlarm emitEvent enableScene error killScene
- logRmd poll powerOutage pressButton reboot rptAction
- runAction sendEmail sendNote sendPush sendSms sendiPush
- setConfiguration setGlobal setProfile setRmd setSlider setState
- setStateDelay setStateFormula setStateValue setTimeDrift setTimeSlot setTimeSpan
- shutdown startScene trace tts vacOff vacOn
- verify warning

[cag014 628]

3 hours ago, Dann said:

Hi Cag014,

 

Hi Cag014,

 

I am having some issues and your recommendation is highly appreciated.

 

Simple jM command line I am using leads to the below error message.

My Dimmerlight is a dimmer ( ID 130 ) which I want to set at value 22.

 

Strange... looks like AOQ cannot find any valid actions for the device.

Are you sure you're using correct device ID? I mean this is not a parent device...

Could you please post API of the device?

http://<hc3-IP>/api/devices/130

 

 

Edited March 23, 2021 by cag014

[Dann 4]

I am away from that location ( so no LAN connected for the moment ).

Anyhow, please see a shot of picture I took with the relevant datas.

Please login or register to see this attachment.

[Rover 45]

12 hours ago, Dann said:

Hi Cag014,

 

Hi Cag014,

 

I am having some issues and your recommendation is highly appreciated.

 

Simple jM command line I am using leads to the below error message.

My Dimmerlight is a dimmer ( ID 130 ) which I want to set at value 22.

 

Any suggestion is welcomed.

{0,"$24clock",{state="value=0",timeSlot="?$sunsetHour+2700?~,~?$sunriseHour-2700?",trueAct={"`Dimmerlights`","setValue,22","",false},falseAct={"`Dimmerlights`","turnOff","",false}}},

[23.03.2021] [21:42:04] [DEBUG] [AOQ1636]: _☠ [23 Mar 21:42:04] AOQ1636^9.5 jM hash table:7:~: {0, "$24clock"...}
{0,"$24clock",{"timeSlot"="?$sunsetHour+2700?~,~?$sunriseHour-2700?","trueAct"={"130","setValue,22","",false,false},"falseAct"={"130","turnOff","",false},"state"="value=0"}}

(8) Action 'setValue' not found for ID(130) Supported actions:

`Dimmerlights`Dimmer lights:130:Front court Device's actions are:
-
User Defined Actions:
- turnOn turnOff
AOQ Supported Actions: (11% in use)
- addRmd armAlarm debug delAllRmd delLogRmd delRmd
- disableScene disarmAlarm emitEvent enableScene error killScene
- logRmd poll powerOutage pressButton reboot rptAction
- runAction sendEmail sendNote sendPush sendSms sendiPush
- setConfiguration setGlobal setProfile setRmd setSlider setState
- setStateDelay setStateFormula setStateValue setTimeDrift setTimeSlot setTimeSpan
- shutdown startScene trace tts vacOff vacOn
- verify warning

After transition of devices from HC2 to HC3 a lot of actions are not valid anymore. Soft reconfiguration helps.

Even if you did not came from HC2 soft reconfiguration could help.

[Dann 4]

Thanks Rover,

 

Indeed, after soft reconfigure on ID 130 ( I did not came from HC2 ) now is working.

 

[Rover 45]

Surprise, surprise, we got an Easter present from @cag014 ?: AOQ version 11.3 in the Downloads.

Especially the new State features in conditional settings are super useful ?

Have a look at the updated Advanced User Guide.

Edited March 31, 2021 by Rover

[Rover 45]

Hi @cag,

No GV conditions possible in trueActState?

[cag014 628]

4 hours ago, Rover said:

Hi @cag,

No GV conditions possible in trueActState?

Strange.. it does work for me

Could you please post an example?

[Rover 45]

3 minutes ago, cag014 said:

Strange.. it does work for me

Could you please post an example?

Please login or register to see this spoiler.

 

[cag014 628]

Have tested your line and it works fine..

Could you please explain what exactly doesn't work

[Rover 45]

14 hours ago, cag014 said:

Have tested your line and it works fine..

Could you please explain what exactly doesn't work

Please login or register to see this spoiler.

 

[cag014 628]

Now  I can see the syntax errors:

1.

trueActState={”&Huisstatus:value=Weg”}, 

Should be 

trueActState={”{&Huisstatus:value=Weg}”}, 

or 

trueActState="{&Huisstatus:value=Weg}", 

 

The format of actions state is the same as lineState or in command condition.

 

2. Another issue at the end of the line there are too many commas and curly brackets (not the correct order):

{"$geoAction", {state="enter", lineState={"if {&Geofencing:value=Aan and &BlockGeofencing:value=Uit and &Huisstatus:value=Weg}"}, 

 trueAct={ {"Geofencing","sendEmail,2","Komt er aan","if{&Statuslicht:value<>Disarming}"}, {"&SwitchScene","setGlobal","Disarm"}, 

    {"&PushoverMessage","setGlobal","Geofencing","if{&Statuslicht:value<>Disarming}"}, }, }},

 

 

 

[Rover 45]

1 hour ago, cag014 said:

Now  I can see the syntax errors:

1.

trueActState={”&Huisstatus:value=Weg”}, 

Should be 

trueActState={”{&Huisstatus:value=Weg}”}, 

or 

trueActState="{&Huisstatus:value=Weg}", 

 

The format of actions state is the same as lineState or in command condition.

 

2. Another issue at the end of the line there are too many commas and curly brackets (not the correct order):

{"$geoAction", {state="enter", lineState={"if {&Geofencing:value=Aan and &BlockGeofencing:value=Uit and &Huisstatus:value=Weg}"}, 

 trueAct={ {"Geofencing","sendEmail,2","Komt er aan","if{&Statuslicht:value<>Disarming}"}, {"&SwitchScene","setGlobal","Disarm"}, 

    {"&PushoverMessage","setGlobal","Geofencing","if{&Statuslicht:value<>Disarming}"}, }, }},

 

 

 

I have been trapped again by copying text of the Advanced User Guide: {0,”400”,{ trueActState=”{600:power<60}” etc. : the quotes are of the wrong kind.

Please update all quotes in the Advanced User Guide in order to help everyone not becoming the same errors.

trueActState={”{&Huisstatus:value=Weg}”}, works: TNX cag.

 

What do you mean with point 2: too many commas and curly brackets (not the correct order):

- The number of curly brackets is OK

- The order is correct

- What about too many commas? I am using the commas the make clear what the end is of f.i. trueAct section. The commas do not make trouble, your parsing is fine!

 

Edited April 2, 2021 by Rover