Otherwise, the other option was to create a scene action that does this automatically and let the user schedule it whenever they want…
Advantage: The user schedules it whenever they want, it’s powerful
Disadvantage: Less turnkey
1 Like
I think this part needs to be turnkey. However, can we
[quote="
Would it be a lot of work to send an MQTT message otherwise?
Given that it’s possible to listen to any MQTT message, that would be a compromise. Besides, it’s true that we should keep things as simple as possible rather than waste time getting sidetracked.
Let’s keep it simple!
1 Like
@pierre-gilles: Here is the result in « box » mode for the system configuration screen
What do you think?
I’ve just set the cron to run every Saturday at 9 AM. And I added this note in the description 
6 Likes
I think it’s super clean!
1 Like
Hyper clean @Lokkye !
1 Like
@pierre-gilles
The PR is ready:
2 Likes
Thanks for the PR
I left a review: Add warning system for battery level by callemand · Pull Request #1936 · GladysAssistant/Gladys · GitHub
@pierre-gilles : I didn’t have time to make the changes, you’ve already merged the branch. Should I open a small PR with the minor changes?
Hi, there was an error on my page, I reverted it afterwards! You can re-open the full PR!
@pierre-gilles: I couldn’t re-open the PR, so I just created another one:
Thanks!
I have a small issue when using it, the field is quite strange to use — it loses focus with every character typed. Example when going from 10% to 20% :
Yes, I noticed that too, but like the other fields on the same page they have the same behavior. I didn’t spend more time on it.
The problem comes from setState which forces a redraw and we lose focus.
I’ll investigate the problem a bit more.
[quote="Lokkye, post:35
Well, the problem comes from the disabled property which is « bound » to a state of the saved value. For the moment, by removing this « bind » everything is OK but there is no feedback regarding the save. But I have the impression that the other components that don’t use an input also don’t have feedback from the save.
Would that be OK with
Mmm, like that it’s hard to say how it looks — does it look good?
I’ve committed/pushed the code It will be clearer
Ok indeed it’s much better!
One more thing: the validation makes the usage feel weird, but I know it’s the same in other places in Gladys (on the dashboard, for example when editing a device’s name)
For example, if I have 20 and want to put 30, when I delete the 20 with « Backspace » twice, this happens (A 0 is inserted)
I don’t know what we could do to separate validation from input. A longer debounce?