Feature #289

Szenen via Webinterface programmieren

Added by Nina Meier almost 2 years ago. Updated 7 months ago.

Status:Closed Start date:02/08/2010
Priority:(P1) Urgent Due date:
Assignee:Miguel Rodriguez % Done:

0%

Category:-
Target version:0.9.0-alpha1
Severity:Normal
Story points-
Velocity based estimate-

Description

Klemmenparameter können ab dSS 0.9 abrufbar sein. Bis dahin werden Szenen "blind" programmiert.

Für jeden Raum und jede Farbgruppe pro Raum (vorerst nur Licht) werden die Szenen (nach Taster) aufgelistet. Diese können programmiert werden indem jedes Gerät einen Soll-Zustand erhält. Nach der Programmierung sind die Informationen vorübergehend nur noch auf den Geräten gespeichert. Beim nächsten Programmieren müste man wieder bei 0 anfangen.

Als Vorübergehende Lösung, könnte das Setup einer Szene auf dem dSS gespeichert werden, sofern danach nicht direkt am Taster programmiert wurde, könnenbeim nächsten Mal die programmierten Szenen weiterbearbeitet werden.

100204_szenen02.png (71.2 kB) Nina Meier, 02/08/2010 05:28 pm


Related issues

related to Feature #121: Read out scene values during startup Assigned 09/03/2009
related to Feature #392: Button to control a device Rejected 06/10/2010

History

Updated by Miguel Rodriguez almost 2 years ago

  • Assignee changed from Matias Fernandez to Miguel Rodriguez
  • Target version deleted (0.8.0-alpha1)

Updated by Miguel Rodriguez almost 2 years ago

  • Status changed from New to Assigned
  • Assignee changed from Miguel Rodriguez to Sergey Bostandzhyan
  • Target version set to 0.9.0-alpha1

The preferred solution is to use the information directly from dSM's see related ticket 121

Updated by Miguel Rodriguez over 1 year ago

  • Priority changed from (P3) Normal to (P1) Urgent

The following would be the flow of events for programming scenes:
1) User clicks in Scene tab: Scene tab opens up and shows a list to the left with all available zones
2) User selects a Zone: A subtree opens up showing the following scenes:
+ Light Scene 1
+ Light Scene 2
+ Light Scene 3
+ Light Scene 4
+ Leave home
+ Door bell
3) User selects a scene. The dSS calls the scene in the selected zone and then shows the devices on that zone filtered as follows:
+ For all light scene show only yellow klemme
+ For leave home scene show all colors
+ For Door bell scene show only green and yellow klemme
-- Dont show current scene values yet
-- For leave home and Door bell scenes add an "ignore" checkbox. On displaying the list set all checkboxes to ignore. This ignore function matches the "dont care" flag
4) Add 1 button to the top of the list: Save scene.
The user can modify the current scene either over the main taster or over the pop up window available from the color klemme. Once he has modified the scene he will click the "Save scene" button
5) If the Save Scene button is pressed send the save scene command to the dSM and present a Pop Up window: "scene saved"

Updated by Michael Troß over 1 year ago

The "pop up window available from the color klemme" could also make use of the device/setOutval call. This way the user may set the output value to a well defined state.

For a first step the implementation may be a simple "percentage" text input field and a "save to device" button.

An extension may be a slider to visualize and set the percentage value.

Updated by Michael Troß over 1 year ago

Detail redefined about the above device filtering:

... and then shows the devices on that zone filtered as follows:
+ For all light scene show only yellow klemme
+ For leave home and door bell scene show all colors

For all apartment scenes (like door bell or leave home) no device display filter should apply.

Updated by Sergey Bostandzhyan over 1 year ago

Implemented everything except for don't care handling. Don't care's will be done separately.

Updated by Sergey Bostandzhyan over 1 year ago

  • Status changed from Assigned to Resolved
  • Assignee changed from Sergey Bostandzhyan to Miguel Rodriguez

Setting issue to resolved, as discussed the don't care functionality will be added later. A separate ticket for remaining changes will be created.

Updated by Miguel Rodriguez over 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF