[dss-developer] set functionID in sim.xml & last scene parameter
pstaehlin at futurelab.ch
Mon Jun 7 12:00:38 CEST 2010
On Wednesday 12 May 2010 13.08:05 Meier Dominik wrote:
> 1: Is it possible to set a functionID of a device in the sim.xml?
It's not possible as of now but might be possible soon . If your simulated
"getFunctionID" to return the desired function-id.
> 2: If I understood right, a last scene will be stored in a special scene
> number in the device. Is this right, which scene is it?
> A device is dimmed to 50% and will be switched of by a dSS generated
> event, what will be stored in the last scene scenario in the device?
At the moment the value will be stored in scene 63 for yellow devices (afaik).
We're not modelling that behaviour at the moment, as I'm not sure if that
behaviour will survive the CE certification. As far as I know a device must be
turned off if it gets plugged in and going back to the last known value might
violate such a constraint. But thats my own view on things.
> 3: I had an idea for a workaround to use user Groups. I thought, naming
> several devices with the same name e.g. "Fridge" would give the
> possibility to build a set by tag e.g. .tag('Fridge') . The result was,
> that only one device named as Fridge responded to the event. (I guess it
> was the one with the lower ID) Why does this not work??
You should tag those devices with 'Fridge'. The name is not included in the
> 4: Is there an error in the set syntax documentation?
> # By adding .kitchen the set gets restricted to "all devices within the
> group yellow which are # located in the zone named kitchen".
> -> From my point of few, the result would be "dev6" if your explanation
> means a conjunction like set = Kitchen AND Yellow. I think dev2, dev3 and
> dev6 are in the set, if your set is .yellow.
Yes, you're right. I've corrected it on the wiki page. Thank you!
Patrick Stählin Hardware Wrangler
futureLAB AG tel: +41 (0)52 260 22 22
Schwalmenackerstr. 4 fax: +41 (0)52 260 22 23
CH-8400 Winterthur mission: delivering tomorrow's applications today
More information about the dss-developer