Modules to do

[PoltoS]

Security Sunrise/sunset scene activation

Потом: 1) При задании имени модулю, давать такое же название виджетам 6) Модуль Trap Events создает виджеты кнопок для брелока, но при исключении брелока из сети, эти виджеты не удаляются.

Нужно добавить: 2) Названия виджетов вынести в заголовок виджета, это решит проблему с длиной названия и появится свободное место для других элементов, например на виджете термостата нужно разместить два выпадающих списка, или один выпадающис список для температуры и генерировать иконки для режимов.

Хотелки: 1) Добавить вертикальный слайдер для выбора яркости в виджете RGB 2) При создании световой сцены выбирать виджет RGB и пикером задавть цвет

[n0ahg]

Would you like sunrise/sunset scene activation added to the OpenWeather module?

[PoltoS]

No, it should be dedicated, imho. since you might want to have many weather for different locations

[n0ahg]

Calculated or pulled from an online source such as OpenWeatherMap.org or timeanddate.com? I had a play with suncalc but didn't manage to get it included in to a module using what I thought was standard js syntax. Works fine on NodeJS.

[pz1]

I agree it should be a dedicated module in the end, as it can be critical. You don't want to be dependent on the availability of an on-line source.

Just as a reference, this is what OpenRemote supports in "DateTime" protocol. Afaik mostly added on user request.

date (returns a date/time as string depending on the given formatter)
sunrise (returns the sunrise time as string depending on the given formatter)
sunset (returns the sunset time as string depending on the given formatter)
minutesUntilSunrise (returns an integer with the minutes until sunrise)
minutesUntilSunset (returns an integer with the minutes until sunset)
isDay (returns a boolean string)
isNight (returns a boolean string)

See ref: http://www.openremote.org/display/docs/OpenRemote+2.0+How+To+-+DateTime+Protocol

[PoltoS]

Do we need triggers at date/sunrise/sunset and mintestBefore/After/sunrise/sunset or variable to check it?

Just to clarify, trigger will initiate some action, while variable can be used in rules to test conditions.

I'm for events

[pz1]

I don't fully get the distinction "trigger/condition". Maybe it is a matter of language, maybe it is my OpenRemote background with Drools engine that works with production rules.

For example my sunshades only get the command to raise if:

• the shades are NOT yet docked and one or more of the following
• is night
• is raining
• is stormy This would only safely work if the state of docking(condition) would be known to be correct (or reassessed) if any of the other three changes. Similarly if you have a rule applying to a night situation, all the conditions have to be reassessed at a restart of the system.

PS: I do not intend to push the OR way, but rather refer to what other user communities have asked for

[PoltoS]

To make it clear: trigger or event is when to start rules tests. Condition is the test inside the rule to match current environment. If condition matches, the action is executed.

So, you mentioned "at a restart of the system" - this is trigger = start checking rules at boot. isNight in your case seems to be a condition.

Another example based on yours. If it started raining - this is event. is raining - is condition. So, specific point in time is trigger, test if time is < or > of something is condition.

Just want to understand if we need such conditions or only triggers

[pz1]

thanks