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

[Rover 47]

46 minutes ago, cag014 said:

Interesting question, but what kind of condition you think about with the email? if email equal/less/greater to what value?

Please elaborate more about that!?

What exactly you need...?

Yes, I want to release new version next Sunday...

If condition is true, then turnOff and I want an e-mail about the turnOff. But is the condition is not met, then I don't want the e-mail. How to implement?

 

I have a list (=alias) of all light devices per room and I have a list of all room lists with light devices.

That's easy in order to turnOff all light devices of the house. But this 2-deep nesting does not work. 1-deep nesting works.

 

"Yes, I want to release new version next Sunday..." ?

 

Keep on the good work, cag014 ?

 

[cag014 731]

Just add in sendEmail command same condition as in turnOff.

 

trueAct={{"`device`","turnOff","","{&Huisstatus:value=Weg}"},{"Weg: Lichten Uit","sendEmail[2]","Weg: Alle Lichten Uit","{&Huisstatus:value=Weg}"}}}},

 

I don't now how looks you entire line but here another option

{0,"&Huisstatus",{state="value=Weg", trueAct={{"`device`","turnOff",""},{"Weg: Lichten Uit","sendEmail[2]","Weg: Alle Lichten Uit","}}}},

[japasu 15]

Thank you very much for this QA.

I am starting to love it, however I am just a "copy and paste user" - not a programmer.

Can anyone help me to put a 15 seconds delay into my jM-line to make my Danalock wait a while to secure after the door sensor is safe.

My current line works, but it locks the door to soon after closing the door:)

    {0,"`DoorSensor`",{state="value=false",timeSlot="00:00~24:00",trueAct={"`Danalock`","secure",""}}},

[cag014 731]

The third field is the command delay in seconds.

 

{0,"`DoorSensor`",{state="value=false",timeSlot="00:00~24:00",trueAct={"`Danalock`","secure","15"}}},

Edited August 24, 2020 by cag014

[japasu 15]

Thank you, so much @cag014

I am thinking that I should have figured that out my self, but as I said, I am just a copy paster:)

 

Now I have a new problem: the Danalock secures if the door is open when it is opened within the 15 seconds.

I have read the quick start guide and I understand it can be a solution for this, but I can not understand how to put it into my line...

Could you please, help me out again?

[cag014 731]

You mean if you close the door and opened within 15 seconds it secures the door in any case?

Two options to solve the issue

1. Add falseAct when the door is closed - that's will removed the suspended trueAct (if you have some kind of  "unsecure" command)

{0,"`DoorSensor`",{state="value=false",timeSlot="00:00~24:00",trueAct={"`Danalock`","secure","15"}, falseAct={"`Danalock`","unsecure",""}}},

2. Add condition to trueAct{}

{0,"`DoorSensor`",{state="value=false",timeSlot="00:00~24:00",trueAct={"`Danalock`","secure","15","{`DoorSensor`:value=false}"}}},

It means to secure after 15 seconds if DoorSensor is false.

See what works best for you

Edited August 24, 2020 by cag014

[japasu 15]

Thank you, very much - again @cag014

Your work and support really enhances my use of Home Center 3.

I am using alternative 2 from your reply.

 

Best regards

[cag014 731]

You're welcome...

[cag014 731]

@japasu

I see you are setting timeSlot="00:00~24:00" means active always.

The default of the timeSlot is active always so you can remove timeSlot definition.

Like that:

{0,"`DoorSensor`",{state="value=false",trueAct={"`Danalock`","secure","15","{`DoorSensor`:value=false}"}}},

will work the same

 

 

[Rover 47]

Hi, @cag014,

With HC2 there is besides the automated way of starting a scene, always the possibility of starting a scene manual, via smartphone app or web app.

For instance I have a scene switching all lights on, 1 hour before sunset. If it is a cloudy day, I put the lights on manually starting the scene.

What is the best way to have the same functionality using AOS?

[japasu 15]

Hi, @cag014

I understand the usage of timeslot, but left it in the line for easy editing in case I want to use it. 
Thanks, again. 

[cag014 731]

9 hours ago, Rover said:

Hi, @cag014,

With HC2 there is besides the automated way of starting a scene, always the possibility of starting a scene manual, via smartphone app or web app.

For instance I have a scene switching all lights on, 1 hour before sunset. If it is a cloudy day, I put the lights on manually starting the scene.

What is the best way to have the same functionality using AOS?

Put the scene on manual mode constantly.

In AOS one hour before sunset start the scene with weather condition.

 

[Rover 47]

9 minutes ago, cag014 said:

Put the scene on manual mode constantly.

In AOS one hour before sunset start the scene with weather condition.

 

Can I start the AOS line from a scene?

"DimlevelOverdag","setGlobal","`DimmerHal`:value" gives result DimlevelOverdag:  174:value, so text not the integer value.

How can I create a sort of  "tonumber"?

[cag014 731]

AOS should run constantly. Why you need to started?

[Rover 47]

1 hour ago, cag014 said:

AOS should run constantly. Why you need to started?

There is no intention to restart AOS. The point is that if AOS controls the lighting, how can I manually lit lights apart from the automated rules of AOS?

One idea is to start the AOS rule, that is putting the lights on, by means of a scene (if that is possible, if yes:how).

Or I have to maintain the scene that puts the lights on, which scene is translated now into AOS.

 

Another issue: DimlevelOverdag","setGlobal","`DimmerHal`:value" gives result DimlevelOverdag:  174:value, so text not the integer value.

How can I create a sort of  "toNumber"?

[cag014 731]

Why you cannot turn the light by UI, webApp or wall switch?

Please describe exactly the scenario you're trying to implement..

[Rover 47]

Scenario: AOS controls lighting by timeSlot with JM-line with a lot of devices (refer to outstanding question about 2-deep nesting of devices).

If I want to lit the light manually at an earlier time than programmed in the timeSlot, I can:

1. Keep the HC2 scene that lit the lights for manual operation. Disadvantage: double construction: AOS (with 30 devices in AOS-notation) + HC2 scene (with the same 30 devices in LUA-notation). I went to AOS in order to get rid of scenes in order to migrate to HC3. So no profit of AOS, just doubling functionality.

2. Just keep a small scene in HC2, just for triggering an AOS-line. I made already a HC2 scene toggling a global parameter. It is so small that migration to HC3 will not be difficult.

The next AOS line happens to work ?: {0,"&LichtenAanManueel",{trigAct={"`GIA`","turnOn",""}}},

With every toggle of the global parameter the AOS-line is triggered.

So this problem has been solved.

 

Please @cag014, help me with another issue:

"&DimlevelOverdag","setGlobal","`DimmerHal`:value" gives result DimlevelOverdag = 174:value, so text and not the integer value of the `DimmerHal`:value.

How can I create a sort of  "toNumber"?

 

And: is 2-deep nesting of device ID's possible?

In jS2n no problem ( AlleLichten="`Huiskamer`|`Librije`|`Keukenlamp`|`Bijkeuken`|`LampHal`|`RaamGloriaLamp`|`Achtertuin`|`ZonneschermLicht`|`TuinFlood`",)

but in use gives `AlleLichten` problems.

 

 

[cag014 731]

2 hours ago, Rover said:

Scenario: AOS controls lighting by timeSlot with JM-line with a lot of devices (refer to outstanding question about 2-deep nesting of devices).

If I want to lit the light manually at an earlier time than programmed in the timeSlot, I can:

1. Keep the HC2 scene that lit the lights for manual operation. Disadvantage: double construction: AOS (with 30 devices in AOS-notation) + HC2 scene (with the same 30 devices in LUA-notation). I went to AOS in order to get rid of scenes in order to migrate to HC3. So no profit of AOS, just doubling functionality.

2. Just keep a small scene in HC2, just for triggering an AOS-line. I made already a HC2 scene toggling a global parameter. It is so small that migration to HC3 will not be difficult.

The next AOS line happens to work ?: {0,"&LichtenAanManueel",{trigAct={"`GIA`","turnOn",""}}},

With every toggle of the global parameter the AOS-line is triggered.

So this problem has been solved.

 

Please @cag014, help me with another issue:

"&DimlevelOverdag","setGlobal","`DimmerHal`:value" gives result DimlevelOverdag = 174:value, so text and not the integer value of the `DimmerHal`:value.

How can I create a sort of  "toNumber"?

 

And: is 2-deep nesting of device ID's possible?

In jS2n no problem ( AlleLichten="`Huiskamer`|`Librije`|`Keukenlamp`|`Bijkeuken`|`LampHal`|`RaamGloriaLamp`|`Achtertuin`|`ZonneschermLicht`|`TuinFlood`",)

but in use gives `AlleLichten` problems.

 

 

OK... great the lighting issue is solved.

Now to get value of any item in the system (device/global/) please use value format and not conditional format.

the value format is @[ID]>[property].

in your case

"&DimlevelOverdag","setGlobal","@`DimmerHal`>value"

 

Yes AOS supports 2-deep nesting of devices...

Please post JS2n and the error you receive on AlleLichten?

[Rover 47]

21 hours ago, cag014 said:

OK... great the lighting issue is solved.

Now to get value of any item in the system (device/global/) please use value format and not conditional format.

the value format is @[ID]>[property].

in your case

"&DimlevelOverdag","setGlobal","@`DimmerHal`>value"

 

Yes AOS supports 2-deep nesting of devices...

Please post JS2n and the error you receive on AlleLichten?

jS2n={
 --Hal
 TemperatuurHal=25, LampHal=227, KeyfobGloria=279, KeyfobHans=255, Deurbel=94, AlarmLadeUit=300, LichtHal=26, Meterkastslot=158, DimmerHal=174,
 BewegingHal=24, VoordeurSwitch=210, Voordeur=44, AlarmstatusRGB=86, Buzzer=163,
 --Librije
 LinksBoekenkast=102, BoekenkastRechts=241, BovenraamLibrije=62, Librije="`LinksBoekenkast`|`BoekenkastRechts`",
 --Huiskamer
 BewegingHuiskamer=19, LinksPiano=220, Kerstboom=42, BovenraamHaard=60, PortSwitch=263, LampenSchouw=237, BovenraamEetkamer=252, DimmerLeeslamp=123,
 TemperatuurPiano=233, HitteHuiskamer=232, Terrasdeur=48, LichtHuiskamer=21, LinksGobelin=216, RookHuiskamer=231, TempHuiskamer=20,
 Huiskamer="`LinksPiano`|`LampenSchouw`|`LinksGobelin`",
 --Keuken
 Keukenlamp=186, LichtKeuken=12, OmasKast=151, BewegingKeuken=10, Keukenraam=98, BovenraamKeuken=100, TemperatuurKeuken=11, OmasKast=151, RandomLight=290,
 --Bijkeuken
 PlafondBijkeuken=312, AanrechtBijkeuken=313, HitteBijkeuken=54, BovenraamBijkeuken=108, RookBijkeuken=52, TempBijkeuken=53,
 Bijkeuken="`PlafondBijkeuken`|`AanrechtBijkeuken`",
 --Overloop
 HitteOverloop=17, SpotsTrapOverloop=169, TemperatuurOverloop=16, LichtOverloop=31, OverloopSwitch=306, RookOverloop=15, TempOverloop=30,
 Schilderijspot=171, BewegingOverloop=29,
 --KamerHans
 GIA=212, TempKamerHans=58, VeluxKamerHans=56,
 --KamerGloria
 TempKamerGloria=66, VeluxKamerGloria=64, RaamGloriaLamp=229,
 --Badkamer
 TemperatuurBadkamer=74, VeluxBadkamer=72,
 --Garderobekamer
 TempGarderobekamer=78, VeluxGarderobekamer=76,
 --Schuur
 LichtSchuur=82, TemperatuurSchuur=81, SchuurdeurAchter=80, SchuurdeurVoor=50,
 --Achtertuin
 Gevelcontactdozen=283, TuinlichtKlein=206, ZonneschermLicht=135, TuinFlood=146, Tuinpomp=338, Veskys=308, Watervall=337,
 TerrashoekLicht=329, Belhoorn=147, TuinlichtGroot=208,
 Achtertuin="`Gevelcontactdozen`|`TuinlichtKlein`|`TerrashoekLicht`",
 --Oprit
 C2=265, Axis=39,
 --Alle lichten
 AlleLichten="`Huiskamer`|`Librije`|`Keukenlamp`|`Bijkeuken`|`LampHal`|`RaamGloriaLamp`|`Achtertuin`|`ZonneschermLicht`|`TuinFlood`",
}
jM={
--Test
---[[
{0, "$24clock",{state="value=0",timeSlot="18:30~",
      trueAct={{"`AlleLichten`","turnOn","",false}}}},

 

See error picture: alias LinksBoekenkast not found.

Please login or register to see this attachment.

[Rover 47]

21 hours ago, cag014 said:

OK... great the lighting issue is solved.

Now to get value of any item in the system (device/global/) please use value format and not conditional format.

the value format is @[ID]>[property].

in your case

"&DimlevelOverdag","setGlobal","@`DimmerHal`>value"

 

Yes AOS supports 2-deep nesting of devices...

Please post JS2n and the error you receive on AlleLichten?

 

 

"the value format is @[ID]>[property]" definition is not to be find in any AOS or AOQ guide. Maybe an addition for the future?

BTW thanks for this information, it has helped ?