|
|
|
|
|
|
Re: PaperUI rendering of channels? [message #1704161 is a reply to message #1704148] |
Fri, 07 August 2015 18:43 |
Chris Jackson Messages: 256 Registered: December 2013 |
Senior Member |
|
|
Quote:
I think in sitemaps the user has the change to define what how the UI should look like.
Ok - that makes sense - I keep forgetting that sitemaps are still around
Quote:
For hue it does, because the hue binding supports the OnOffType also for the color temperature channe
That's maybe not what I meant - while it's possible to make anything change when you click a button, that doesn't necessarily mean that some data types are things that are logically linked. In my mind (maybe wrong) an on/off switch isn't necessarily something I would think of if someone mentioned colour temperature, even if the Hue binding has chosen to implement it in this way...
Quote:
I think if the device is just a color bulb it should have just two channels like hue and LIFX.
This becomes a big problem for me In zwave, each of these 'channels' (brightness, colour, on/off) are all handled separately in different command classes. Currently, each command class is linked to a channel, and the channel configuration, and this link, is made in the channel properties. With this requirement that a channel should handle multiple different streams of data (on/off, brightness and colour for example), it means that I need to change the concept of how channels are defined since I can now no longer split them functionally. I need to somehow consolidate the multiple command classes into a single channel and work out how to send it to the different devices, depending on the device configuration.
I think I need to rethink how the zwave binding works if this how things are meant to work - I will effectively need to increase the amount of configuration so that I can deal with all the different types of data that might turn up in a channel
Chris
[Updated on: Fri, 07 August 2015 19:02] Report message to a moderator
|
|
|
Powered by
FUDForum. Page generated in 0.02097 seconds