Your comments

we'll add the event with corrected name, the previous one (with typo) will also work.For the moment u must use the event with typo

we'll add the event with corrected name, the previous one (with typo) will also work.

For the moment u must use the event with typo

It is not possible.

Push notification can be sent from Server to i3 pro via 2 cloud services: iRidium Cloud and Apple(Google) Push service.

With iRidium Transfer it is not possible to relate the Server with the list of control panels of some object that receives the notification. It is not possible to know what panels have to receive the notifications. With the client projects there is the same problem.

The needed relations between Server and Panels could be created only via iRIdium Cloud.

The rools of use of notificatins are available in the documentation.

Добрый день, камера мобильного устройства не включена постоянно, а датчик приближения выдает только значения 0 или 1, реагируя только на крайние значения освещенности.
Пожалуйста, используйте для реализации этой задачи датчики освещенности системы автоматизации.

[2th thing]

sunrise / sunset.. maybe it is better to add it like external JS modules for those who need it.

It is not about timezone, but the latitude and longitude.

We don't plan to add it in the next update of Schedulers, it is better to start with the more popular requests



[ 1th thing]

The first step is already planned.

You will not be able to change a global repetition pronciple, it is not possible - the list of channels (setings) cannot change on project already started on panel.

How it is planned:

// .Enabled  (always available) 
Schedule 1.Weekend // how it works right now

// Start (always available)
Schedule 1.Weekend.Start.Day 
Schedule 1.Weekend.Start.Month
Schedule 1.Weekend.Start.Year
Schedule 1.Weekend.Start.Hour
Schedule 1.Weekend.Start.Minute

// Finish (always available)
Schedule 1.Weekend.Finish.Day 
Schedule 1.Weekend.Finish.Month
Schedule 1.Weekend.Finish.Year
Schedule 1.Weekend.Finish.Hour
Schedule 1.Weekend.Finish.Minute

// End (available only when turned on in Scheduler settings)
Schedule 1.Weekend.End.Day // сами парсим значение
Schedule 1.Weekend.End.Month
Schedule 1.Weekend.End.Year

// Repeat: EveryDay, Week, Mnth, ... - doesn't have a repetition settings

// Repeat: Custom - the list of settings depends on repetition type
// Repetition types:

// By Days
Schedule 1.Weekend.Repeat.ByDays.CycleInDays // every N days
// By Weeks
Schedule 1.Weekend.Repeat.ByWeeks.CycleInWeeks  // every N weeks
Schedule 1.Weekend.Repeat.ByWeeks.Sunday // activity in some day
Schedule 1.Weekend.Repeat.ByWeeks.Monday
Schedule 1.Weekend.Repeat.ByWeeks.Tuesday
Schedule 1.Weekend.Repeat.ByWeeks.Wednesday
Schedule 1.Weekend.Repeat.ByWeeks.Thursday
Schedule 1.Weekend.Repeat.ByWeeks.Friday
Schedule 1.Weekend.Repeat.ByWeeks.Saturday
// By Months
Schedule 1.Weekend.Repeat.ByMonths.CycleInMonths // every N months
Schedule 1.Weekend.Repeat.ByMonths.Dates // 0100...01 (31) in one of 31 days, binary format
// или
Schedule 1.Weekend.Repeat.ByMonths.CycleInMonths // every N months
Schedule 1.Weekend.Repeat.ByMonths.WeekOfMonth // 1..5
Schedule 1.Weekend.Repeat.ByMonths.DayOfWeek // 1..7
// By Years
Schedule 1.Weekend.Repeat.ByYears.CycleInYears // every N yesrs
Schedule 1.Weekend.Repeat.ByYears.Months // 010...001 (12) in one of 12 months, binary format
// only if turned on:
Schedule 1.Weekend.Repeat.ByYears.WeekOfMonth // 1..5
Schedule 1.Weekend.Repeat.ByYears.DayOfWeek // 1..7

// Status of scheduler (In process / Not in process)
Schedule 1.Weekend.Status // read only

in iRidium Server driver it will be available as a folder with channels for each scheduler:

+ iRidium Server
        + Schedulers
              + Weekend
                  + Commands (19)
                      - Schedule 1.Weekend
                      - Schedule 1.Weekend.Start.Day
                      - Schedule 1.Weekend.Start.Month
                      - Schedule 1.Weekend.Start.Year
                      - Schedule 1.Weekend.Start.Hour
                      - Schedule 1.Weekend.Start.Minute
                      - Schedule 1.Weekend.Finish.Day 
                      - Schedule 1.Weekend.Finish.Month
                      - Schedule 1.Weekend.Finish.Year
                      - Schedule 1.Weekend.Finish.Hour
                      - Schedule 1.Weekend.Finish.Minute
                      - Schedule 1.Weekend.Repeat.ByWeeks.CycleInWeeks
                      - Schedule 1.Weekend.Repeat.ByWeeks.Sunday
                      - Schedule 1.Weekend.Repeat.ByWeeks.Monday
                      - Schedule 1.Weekend.Repeat.ByWeeks.Tuesday
                      - Schedule 1.Weekend.Repeat.ByWeeks.Wednesday
                      - Schedule 1.Weekend.Repeat.ByWeeks.Thursday
                      - Schedule 1.Weekend.Repeat.ByWeeks.Friday
                      - Schedule 1.Weekend.Repeat.ByWeeks.Saturday
                  + Feedback (20)
                      - --||-- // the same as commands
                      - Schedule 1.Weekend.Status

In the new iRidium version you are able to convert TP5 files, please download Setup file from the web site

Hello

http://dev.iridiummobile.net/Drivers_API/en#.Set

you can find a syntax in samples:

// Domintell. "Domintell Network (UDP)" - name of network
// "DDIM01" - name of Device in Network, "Channel 1" - name of Channel, 100 - value to send
IR.GetDevice("Domintell Network (UDP)").Set("DDIM01:Channel 1", 100);
        

it works the same with the other JS methods

Network - as a device, Subdevice:Channel - as a chennel

In case of work with Hours in Schedule there should be 3 types of repetition:

  1. Every Hour
  2. Every [X] Hours
  3. Every [X] Days in [Y, Z, W] Hours


Every Hour (Template)

event will be in process from 28-th to 29-th minute of each hour, every day.

[17:28 ... 17: 29] > [18:28 ... 18: 29] > [19:28 ... 19: 29] > [20:28 ... 20: 29] > ...


Every [X] Hours (Custom > By Hours)

event will be in process from 28-th to 29-th minute of hour with some interval in hours

[17:28 ... 17: 29] > [19:28 ... 19: 29] > [21:28 ... 21: 29] > ...


Every [X] Days in [Y, Z, W] Hours (Custom > By Days > On specified hours)

event will be in process from 28-th to 29-th minute of specified hours of a day with some interval in days


22.03 --- [07:00 ... 07: 05] > [12:00 ... 12: 05] > [18:00 ... 18: 05] > [22:00 ... 22: 05]

23.03 --- no events

24.03 --- [07:00 ... 07: 05] > [12:00 ... 12: 05] > [18:00 ... 18: 05] > [22:00 ... 22: 05]

25.03 --- no events



Limitations

if the option "Finish: [ ] Specify the date" is active (start and finish of event occurs in a different days) you cannot use a repetition by Hours (as a template or periodicity option).


----

PS1: This is how we are able to do it. If you have any comments or requests please write it here

PS2: The images is made in Paint as a sample, do not search for this settings in Studio yet