This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

Step +/- button
#1
Hi!

Is it possible to make a button step a value up or down with a certain step? Like a spinner-widget, but without a value (and yes, I understand I can hide the value with css)?
Reply
#2
Only dimmer is like that but it is for 4bit object, you could make a script which send steps based on dimming steps.
The sliders alos have steps.
------------------------------
Ctrl+F5
Reply
#3
Ok, thanks! I have a challenge that I would like some input on. I'm not sure if it's actually solvable. This will be long, sorry about that.

First a rant; I have from my first start with KNX 12 years ago been very unhappy with the concept of deadband and heating/cooling switchover with all KNX Room Temperature Controllers I have tried. I understand and appreciate the concept of deadband, but for the life of me I can't understand why the setpoint have to change when the RTC switches between heating and cooling. If I have a symmetrical deadband of 1 degree, roomtemperature of 21 degrees and I set the setpoint at 22 degrees, I would expect it to heat up to 22 degrees, then stop. And then either start cooling at 22,5 untill it reaches 22 again, or restart heating when temperature drops to 21,5. This is with relative setpoint presetting. With absolute presetting it works as I want, except you don't get automatic failover between heating and cooling - and I have not yet found a way to script this reliably while taking different modes into account (comfort, standby, night and frost/heat protection).

Anyways, back to my challenge. To hide for the user that the setpoint changes between heating and cooling, I want to use what my RTC (Gira) calls "Basic setpoint" - which is a base from which all other setpoints are calculated. So with the same numbers as my previous example, I set the (basic) setpoint to 22, and while the actual setpoint will be either 21,5 or 22,5 - that will be hidden to the user. "Problem" is that the basic setpoint doesn't reflect the changes in setpoint when changing operation mode (comfort, standby, night, frost/heat protection).

I have made a script that reflect this, so when mode is "comfort", basic setpoint is written to a GA (say 36/0/2), and if not "comfort" the actual setpoint is written to the same GA. So far so good, but if I want to change the basic setpoint, I would like the spinner to reflect the value of 36/0/2. I have not found a way to do that, especially not considering that I use the spinner in compact mode. I could probably hide the value in the spinner with css and have a "Numeric value display" widget there instead, but I don't know how to do it when the widget is "opened".

This was terribly long, hopefully someone understand what I'm trying to achieve and have a solution.

On a sidenote, it would not help my issue, but I find it odd that none of the temperature widgets allow for the regular KNX setpoint shift out of the box, that scripting is required to do that... A solution that would help that AND my issue would be if the spinner would have a separate GA for "display" in addition to the control and status...
Reply
#4
Funny enough, noone ever requested setpoint change by shift. Maybe other brand thermostats are bit smarter Smile
Droping a spinner on custom widget and numeric value display on top of spinner value would do the trick, no need for any css.
------------------------------
Ctrl+F5
Reply


Forum Jump: