options for btnmatrix

[nagyrobi]

one_checked option from: https://docs.lvgl.io/8.3/widgets/core/btnmatrix.html#one-check

It's for making possible to check only one button from the matrix. When you toggle a button, the others will be "de-toggled".
It would also be nice to complement this feature with the select functionality.

also we need on_value trigger to retrieve in x the ID of the button that was pressed.

[clydebarrow]

one_checked option from: https://docs.lvgl.io/8.3/widgets/core/btnmatrix.html#one-check

Already implemented.

we need on_value trigger to retrieve in x the ID of the button that was pressed.

Why? Each button in a button matrix can have its own actions. Although internally they are different to regular buttons, this is masked via the yaml config.

[nagyrobi]

Why? Each button in a button matrix can have its own actions. Although internally they are different to regular buttons, this is masked via the yaml config.

For the users to easier implement something like key_collector to design an alarm input panel for example. With on_value you could use the same action to receive the different button presses...

It's like when you need to input a sequence of numbers like a pin code - without having to define complicated scripts to concatenate incoming strings located in global variables.
Actually, key_collector is a pretty well thought out component for this purpose. Maybe we could make btnmatrix work with it?

Also see #34 (comment)

[nagyrobi]

one_checked option from: https://docs.lvgl.io/8.3/widgets/core/btnmatrix.html#one-check

Already implemented.

Tested, config passes through the schema, but doesn't have any effect. Multiple buttons can stay checked.

[clydebarrow]

Actually, key_collector is a pretty well thought out component for this purpose. Maybe we could make btnmatrix work with it?

Or maybe make key_collector work with LVGL.

[clydebarrow]

ested, config passes through the schema, but doesn't have any effect. Multiple buttons can stay checked.

Fixed.

[nagyrobi]

Or maybe make key_collector work with LVGL.

I think both need to know about each other @ssieb

[ssieb]

If the btnmatrix provides the key_provider interface, then it will work automatically.

[nagyrobi]

@ssieb Can you point out a sample in the code?

[ssieb]

Check out the wiegand and matrix_keypad components for example. It's very simple.

[nagyrobi]

@clydebarrow maybe we could add a config option key_provider: true to btnmatrix root, and simply provide the texts put on the buttons to it as keys (and not allow symbols in this case).

[clydebarrow]

That will work, no need for the config option, and it will just send the first character of the button label (key_provider can only send single characters.)

[ssieb]

Symbols are fine. If you want to send more than a single character, then just call the send method multiple times.

[nagyrobi]

@ssieb symbols here are graphical elements, not just *# keys.

@clydebarrow I thought about config option because one may use multiple btnmatrix instances (eg page navigation etc) and likely wouldn't want to use key_provider with those.

[clydebarrow]

Symbols in the LVGL world are just Unicode strings.

The btnmatrix won't send any keys unless it's connected to a key_collector.

[ssieb]

The key interface only handles uint8_t right now because it originally came from the keypad component. It could be expanded, but I'm not sure how useful that would be. What would you be using the keys for?
This should probably be a discord discussion. :-)

[nagyrobi]

The btnmatrix won't send any keys unless it's connected to a key_collector.

Oh, you'd put at source_id the btnmatrix id?

[ssieb]

Yes. As with most things in esphome, if there's only one source, it will pick it up automatically, but otherwise, you need to specify the source id.

[clydebarrow]

If the btnmatrix provides the key_provider interface, then it will work automatically.

Done. Works a treat.

[nagyrobi]

Recipe ready for the Cookbook: https://deploy-preview-3510--esphome.netlify.app/cookbook/lvgl#a-numeric-input-keypad