Request for customizable buttons

[Prof_Techno]

In the configuration page, I don’t know if it’s possible, but it would be interesting if the menus were dynamic. For example, if I select « push button », only the options corresponding to this type of button would be proposed. And so on for the other types of buttons.

This is mainly a question of user comfort, but it could also prevent certain configuration errors likely to cause bugs.

Regarding the different buttons, I encountered several problems during my tests:

1. On/Off Switch

• The colors don’t work.
• If you click too quickly several times on the button, it eventually crashes. The problem even seems to affect all other buttons.
• After a few dozen seconds, everything returns to normal, but you then no longer know the actual position of the button after its recovery.

2. Tempo Button

• Same problem regarding colors: they don’t work.

3. Selector

• The colors don’t work either.
• The problem of too quick clicks also occurs. The selector eventually stops responding and displays the message: « The action failed. »

That’s all for the different problems encountered during my tests.

[lmilcent]

Thank you @Prof_Techno for these very precise tests, they helped find the real cause! It’s in the v0.1.6: Release v0.1.6 · LM1LC3N7/gladys-virtual-buttons · GitHub (it will arrive in the store at the next indexer update).

Rapid clicks that freeze all buttons

The cause is partly in Gladys: an integration is allowed 30 presses and 30 card reads per minute, and Gladys reads each open card after each press. Beyond that, Gladys refuses for up to a minute: all cards remain frozen and display “The action failed”. That’s what you saw, including the false state during this time.

The integration added to this: it requested an extra read with each press, read the cards every 15 seconds during a timeout, and limited your presses to 20 per minute (a limit designed to prevent looping scenes). This is fixed: a press now only costs what Gladys imposes, cards are read once per minute, your presses are no longer limited to 20, and it’s always the last press that wins.

In normal use (around 15 presses per minute, two cards, one timeout in progress), no presses are refused. However, Gladys’ limit remains: approximately 30 presses per minute, 15 with two open “Buttons” cards, 10 with three. A very rapid burst beyond this still freezes the cards for a minute, then everything returns with the correct state.

The colors

On the switch and the tempo, the indicator lights worked fine for me: you saw them remain frozen because the cards were locked by the burst. The selector, on the other hand, had no indicator at all, so its colors were not displayed anywhere: it now has an indicator, in the “Indicator On” color, which shows its position (“Eco”, “Position: 4”…).

A form that only displays the options of the chosen type

Not possible in Gladys for now: an integration’s form always displays all its fields, without being able to hide them based on a choice. Fields that are not used by the chosen type are simply ignored.

Let me know if it’s better on your side!

[Prof_Techno]

A small clarification regarding my previous feedback.

Indeed, during my tests, I click quite quickly on the buttons. I have therefore certainly reached the system’s limits. In normal use, this problem should probably not occur, unless perhaps if the buttons are used by several people, for example in „visitors“ mode.

Regarding the colors, I may have expressed myself poorly: the icons do change color, there is no problem on that side. On the other hand, it is the buttons themselves (the large areas you press) that do not change color. That is the point I wanted to report.

[lmilcent]

Thanks @Prof_Techno for the precision and screenshots, I misunderstood: it was indeed the buttons themselves. It’s in the v0.1.7: Release v0.1.7 · LM1LC3N7/gladys-virtual-buttons · GitHub (it will arrive in the store at the next indexer update).

Buttons now follow the indicator colors… when Gladys allows it

For an action button, Gladys only offers three backgrounds: solid blue, pale red, and neutral (gray). The green background is reserved for another type of button, the one that directly displays the value of a device, and orange doesn’t exist. The integration therefore does its best for the switch, the timer, and the selector:

• when on, the button takes red or blue if the indicator is red or blue (light blue gives blue); with a green, orange, or gray indicator, it keeps the color chosen for the button;
• when off, it takes the blue, red, or gray of the indicator, otherwise gray;
• the two states never look alike: if the off button would look like the on button, it stays gray. The checkmark also remains on the on button.

With your settings „green when on, blue when off“, you won’t see any change, since green isn’t possible and blue when off would look like the on button. Try for example „red when on, blue when off“ (or vice versa) in „Modify a button“: there, the two states are clearly distinct, both in light and dark mode.

To have a real green on these buttons, a small evolution of Gladys itself would be needed: I’ll note it, but I can’t promise when.

Good remark also for the visitor mode: when multiple people press, the presses add up, and Gladys’ limit (about 30 presses per minute) can be reached faster.

Let me know how it goes for you!

[Prof_Techno]

I can’t delete the buttons just by selecting from the dropdown list.

So I haven’t tested the rest yet

[lmilcent]

Thanks @Prof_Techno, you were right: deleting by selecting only from the list didn’t work. This is fixed in v0.1.8: Release v0.1.8 · LM1LC3N7/gladys-virtual-buttons · GitHub (it will arrive in the store at the next indexer run).

• Delete a button: selecting it from the list is now enough; typing its name is optional.
• List and name referring to two different buttons: deletion is refused and nothing changes. A turned-on switch stays on.
• Both fields empty: a clear message states that nothing was deleted, instead of the raw error.

A case that the integration cannot avoid: if you select a button then go back to the empty option in the list, it’s Gladys that displays a technical message. Nothing is deleted in this case.

Your feedback on the rest is welcome when you have time.