At the moment for example Morgen, Abend, Nacht are really “stupid buttons”. I have a SceneItem and if you press “Morgen” SceneItem receives command 1. Then a rule is triggered and the light will change to defined brightness in the rule, afterwards SceneItem will be updated directly to 0.
Scene “Tag” is the same, but considers more condition (for example the illuminance outside). And according this condition my blinds will go up and light turned off, etc… So, you have to press “Tag” maybe later in the day, if I like to open the blinds, because the first time it was too dark outside.
If you plan to stay active you have to check also if there was some user interaction on physical buttons. Until now, it was to much work for me . But it is planned. My user interface is now actually finished but still pretty dumb. So the big work is still to come.
I thought about using metadata to define an item beloging to a certain scene. Then when I the item receives a command from “another source”, you could disable all the scenes that an item belongs to.
and on the other hand I could disable all other scenes once a new scens receives a command. But then there are scenes that don’t overlap at all, so you’d have to consider for that. Either way will result in a lot of custom rules. I’m not there yet with my setup (still working on my presence rules), but already having this on my mind
I think I’m pretty much at the same stage as Mike; pretty far with the user interface but the scenes don’t have any intelligence behind them. For example my “Movie Start” item starts a scene, switches on the media center and lights (some on, some off, some dimmed) and then switches of the item again. It’s very much stand-alone though, doesn’t look at any current settings. I’m using a basic setup in Node-RED for this:
You’re both bringing up a lot of the same questions I’m looking at with scenes interacting with other scenes and how that affects the settings for an item. I’m looking at adding properties to items (for example a light color and brightness for day, evening and night, responsive to motion or not, etc.).
This is just a rough draft for how to set properties from a user point of view, have not implemented these properties yet and have no idea yet on how to have scenes interact with the item properties and each other.
I love this widget !!!
One question, the arrow-up / down, are they supposed to change the set-temperature? When I copied your code it takes me to a graph with the temperatures / humidity
OO… you are right, thanks! … since I’ve added the oh-link component, I’ve never tried the the arrows to change the set temperature. Please change the last line of the yaml:
how did you solve that with the windows and the closed blinds? Did you put the devices in groups? And how do you find out the number of windows or closed blinds?
I realy love your widgets! But I’ve a question regarding the status of the light: I suppose you do this via the Group Settings of an item? When I select SUM for Aggregation Function it give me a decimal value when I have dimmed light included in this group. Do you have another way?
My widget is not 100% correct with the blinds. I’ve put the rollershuter-items into a group with SUM aggregation. In the widget there is a floor operation. If now two blinds are closed by 51% each (SUM: 1.02), the widget will show only 1 complete closed blind.
Other possibility it to add a new Switch-Item to the Rollershutter-Control-channel (see picture):
For my lights, I’m using the Hue Binding. The binding provides two different channels for ON/OFF and Dimmer. I’ve put all Switch-Items into one group, (with SUM aggregation). If you only have dimmer-items or channels in your binding, you can proceed the same way as with the blinds above by adding a second switch-item to the dimmer-channel.
Kiosker app has a 7 day trial version (there are two different apps, the one with the trial is a monthly paid solution, the other is a on-time-buy-app (Kiosker Pro: Web Kiosk on the App Store (apple.com)). If I decide to use kiosker, I will buy the one-time-buy version. (here in switzerland it costs 29.90 swiss francs).
Looks quite good by now. Cool feature in kiosker is the screensaver with the clock (I’m not sure if I want to pay 30 bugs only for the clock ;), let’s see if there are some other advantages.