These little buttons don’t come from the Gladys app, but from your browser, which reacts because it’s an input of type « number ». On mobile it should be easier I think, it all depends on your browser ![]()
Awesome! Thanks for your support ![]()
These little buttons don’t come from the Gladys app, but from your browser, which reacts because it’s an input of type « number ». On mobile it should be easier I think, it all depends on your browser ![]()
Awesome! Thanks for your support ![]()
Ok I’ll test it tonight on my tablet to see how it behaves. Thanks again.
So I tested it on my phone but I’m not really a fan because my browser opens the numeric keypad.
I’d rather have something like what @jgcb00 suggested with a - button and a + button.
However, each time I refresh the page I lose the value and have to enter it again.
Second small point: in a scene it should be possible to adjust by 0.5°C like on the Dashboard. When you move the slider the temperature changes by 1°C.
Given that by default in scenes you can’t specify a decimal value. It’s probably related.
Ah, I didn’t know, I’d never encountered that before.
But that’s probably the reason.
Thanks for the info
Thanks for your feedback @_Will_71
I’ll look into that on my next « Gladys day » ![]()
I’ll see about maybe adding a - and + button; otherwise, it’s already a good start as is!
That, on the other hand, is not normal! Is your MQTT integration functioning and configured correctly?
I’ll look into that. Otherwise, I tested with the keyboard — you can do increments of 0.5 ![]()
You can!
Yes and no.
Yes, you can in the trigger conditions. No, you cannot in the « continue only if » conditions (test here: impossible to set 6.5°C).
I know, but we were talking about the other field ![]()
My bad ![]()
I won’t hold it against you if it’s not perfect. I can be satisfied at first with this version; the important thing is that this type of device is functional… the rest are graphical details.
Yes, good catch, that must be it. I just, as a test, put your image on my 2nd Raspberry Pi with my database. But I didn’t plug in my Zigbee dongle. I’ll try again.
Hi @_Will_71 !
I’ve made progress on this to improve the display ![]()
I think it will be easier to use:

I’ve updated the PR! I think I’ll merge this into PROD fairly quickly and do a release ![]()
That looks good!
In general, is it better to increment in steps of 0.5 or more finely, in steps of 0.1?
Some thermostats will allow 0.5 and no finer, but others may allow increments as fine as 0.1°C?
0.1 it seems annoying to me, who really sees a difference between 19.2 and 19.5°C? that’s 10 clicks to increase by one degree, I find that cumbersome ![]()
I also had that thought about the clicks in the interface.
And accepting an input of 0.1 but only using increments of 0.5°C — is that a viable solution?
That’s the case right now
You can type 21.4 on
Ah ok, perfect!
That way we keep the interface simple, without blocking particular situations.
Generally the heating step is 0.5.
My wife ![]()
See? ![]()
Thanks, that’s great!
![]()
The first iteration of this development is available in Gladys Assistant v4.11.2 ![]()