ON/OFF Timing synced across multiple Aura's

[Quinton]

Hi Team,

I have an installation with multiple Aura’s.

These are in different areas of the same complex and have different scenes. General control by the user is via HTTP on touchpanels.

The manager would like them all to start and stop at exactly the same time (all areas are publicly visible).

If I setup a master AURA with the rest as slaves is it possible to control JUST intensity and NOT Cues via the master i.e. intensity255 will turn all lights on at 9am and intensity0 will turn all lights off at 6pm but the user will still have the facility to control the different scenes on the different Aura’s independently?

[Guertler]

Hello Quinton,

If you setup a Master/Slave configuration at the AURA, the Master will always syncs the playback of the scenes.

But you can create an HTTP application which will send the Intensity value respectively Play and Stop commands to muliple AURAs at the same time.

[Quinton]

Thanks Guertler

[Quinton]

Hi Guertler,

Do you have a http commands for synchronization (i.e. master/slave/on-off etc) ?

[Guertler]

Hello Quinton,

To enable or disable the Master/Slave mode at the AURA remotely via HTTP you can use the following command:

http://[IP]/config.shtml?synctype=[value]

* Value 1 = Sync. Type: Off
* Value 2 = Sync. Type: Master
* Value 3 = Sync. Type: Slave

That means if a AURA should be set to Master the command must be:
http://[IP]/config.shtml?synctype=2

Please note: This command is valid for AURA firmware 1.16. We can't guarantee that it will be always the same command in further AURA firmware releases.

[Quinton]

Great thanks Guertler

[Quinton]

Hi Guertler,

One other question, i could find in the documentation the http command to make a timer event ACTIVE and INACTIVE, would you mind sharing, i understand that this may be for just latest firmware.

[Schulze]

Hi Quinton,

Yes, this is also possible using the following command:

http://[IP]/timerdetails.cgi?index=[timer_index]&enable=[value]&submit=Ok

* [timer_index] is the list index, thus "1" is the first timer
* [value] can be either "n" (timer disabled) or "y" (timer enabled)
* The "submit" value should be always set to "Ok" in order to transmit the values.

Example:

Code: Select all

http://10.84.0.7/timerdetails.cgi?index=1&enable=y&submit=Ok

--> In this example the first timer is enabled.

Please note (same as for the other command): This command is valid for AURA firmware 1.16. We can't guarantee that it will be always the same command in further AURA firmware releases. Furthermore you are responsible for the consistency of the sent values.

[Quinton]

Many thanks Schulze