Feature #242

Propagate device value changes as high level event

Added by Sandro Curcio about 2 years ago. Updated 7 months ago.

Status:Rejected Start date:12/07/2009
Priority:(P2) High Due date:
Assignee:Miguel Rodriguez % Done:

0%
Category:dSS
Target version:0.8.0-rc1
Severity:Normal
Story points-
Velocity based estimate-

Description

When the value of a device changes, the new value should be propagated as a high level event json and soap clients can subscribe to.
Event name: 'devicevalue_changed'
Event Parameters: 'dsid=${dsid};value=${value}'

Related issues

related to Feature #225: raise an Highlevelevent when a scene call is happening Closed 11/25/2009
related to Feature #121: Read out scene values during startup Assigned 09/03/2009

History

#1
Updated by Miguel Rodriguez about 2 years ago

  • Status changed from New to Assigned
  • Assignee set to Patrick Stählin
  • Target version set to 0.8.0-alpha1

#2
Updated by Miguel Rodriguez about 2 years ago

  • Target version changed from 0.8.0-alpha1 to 0.7.5

#3
Updated by Miguel Rodriguez about 2 years ago

  • Assignee changed from Patrick Stählin to Sandro Curcio

Please add more details on the devices meant, and look into issue 225 and how it relates to it

#4
Updated by Sandro Curcio about 2 years ago

Some dSS clients (i.e. the mivune Gateway) don't call scenen but set the value of the devices directly.
These clients also need to be notified whenever the value of any device changes, whether it's changed
from another client or from a dSM independently from the action performed (callScene, setValue, turnOn, turnOff, increaseValue, decreaseValue, ...).

#5
Updated by Sandro Curcio about 2 years ago

Sandro Curcio wrote:

Some dSS clients (i.e. the mivune Gateway) don't call scenes but set the value of the devices directly.
These clients also need to be notified whenever the value of any device changes, whether it's changed
from another client or from a dSM independently from the action performed (callScene, setValue, turnOn, turnOff, increaseValue, decreaseValue, ...).

#6
Updated by Michael Troß about 2 years ago

  • Priority changed from (P2) High to (P3) Normal

#7
Updated by Miguel Rodriguez about 2 years ago

  • Assignee changed from Sandro Curcio to Patrick Stählin
  • Target version changed from 0.7.5 to 0.8.0-alpha1

#8
Updated by Miguel Rodriguez almost 2 years ago

  • Status changed from Assigned to Feedback
  • Assignee changed from Patrick Stählin to Michael Troß
  • Priority changed from (P3) Normal to (P2) High

#9
Updated by Miguel Rodriguez almost 2 years ago

  • Target version changed from 0.8.0-alpha1 to 0.8.0-rc1

#10
Updated by Michael Troß over 1 year ago

  • Status changed from Feedback to Rejected
  • Assignee changed from Michael Troß to Miguel Rodriguez

Once #121 is ready, there is no need to have special event subscriptions for device value changes. The scene high level events are sufficient be notified of and to evaluate the changed device state.

Also available in: Atom PDF