Ok I understand, my bad — I had forgotten one case ![]()
Always the little design tweaks that take the most time
Especially when it’s not testable locally and you have to go back and forth, but hey, you’re pretty available now so it goes quickly
Ok I understand, my bad — I had forgotten one case ![]()
Always the little design tweaks that take the most time
Especially when it’s not testable locally and you have to go back and forth, but hey, you’re pretty available now so it goes quickly
The fix is live at the same branch URL: https://fix-responsive-thermostat-co.gladys-plus.pages.dev/. Remember to do at least a quick refresh to make sure you have the correct version ![]()
No side effects on my end ![]()
Ok, so I went back to work I won’t be able to retest on my PC before tonight
Thanks.
I know that side of it, when I have development to do on a screen at my workplace, my sales colleagues they say it’s fine no problem we already did a simple copy-paste in 5 minutes it’s sorted, except they don’t think about screen resolutions which aren’t always the same. In an HMI + ECU project it’s always the HMI part for me that’s the longest to set up.
Hello everyone, I want to use this thermostat to turn off a radiator based on the temperature relative to the setpoint. I was planning to use a scene with a « continue if and only if » action, however the second operand of this action seems to be only a constant. Is there a workaround or do I have to go through Node-RED?
@lmilcent proposed something using an HTTP request to perform a calculation with the math.js API in scenes.
I’m not as enthusiastic as you, I don’t think it looks good in your screenshot, it’s a shame that all the lines are offset while only the thermostat is wide on its right side…
I’m thinking about reworking the overall behavior of this box, maybe to avoid aligning each line (to test whether it looks good or not) ![]()
The thermostat should be independent within the box, or alternatively a box dedicated to the thermostat.
I’m working on it and I’ll get back to you.
@_Will_71 Actually I’m really not satisfied with the solution I proposed, it’s kind of a hack that only works in your case but for other users it doesn’t work!
For example, someone with a wide screen could still end up with the thermostat « compressed » even though there’s plenty of room:
I think we need to rethink how this box works!
No worries. I agree that if this doesn’t work in all cases, it’s better to review the overall functioning of this box.
There’s still the idea of a custom box for this type of device.
Actually this is really more general feedback on the « room devices » box than on the thermostat, the problem was already there before the thermostat existed ![]()
For the per-room box, it’s an evolution for later. For now, step 1 is only direct control (it’s in any case a prerequisite for what’s next! )
Salut @laguiche, sorry your message got a bit lost among the many posts!
As it stands you’ll have to go through Node-RED, no workaround ![]()
I think I managed — actually instead of limiting the name size, I give a minimum size to the thermostat when it’s in « horizontal » mode
It seems pretty silly as a solution, but I tried stuff for 2 hours before I got it to work ![]()
If you can create a link, I can test it when I get home around 1 p.m.
The link => https://77ebb252.gladys-plus.pages.dev ![]()
It’s fine on my phone. I’ll get back to you later about my other devices (PC/tablet)
Tested and approved on my mobile phone (in landscape and portrait) and on my laptop’s browser (by resizing the window to observe the behavior).
Tested on Firefox 106.1.0 on my mobile phone (Android)
Tested on Microsoft Edge Version 105.0.1343.33 (Official build) (64-bit) (Windows 10)