[Feature Request]: Enabled canned messages on T1000-e

[willhubs]

Platform

NRF52

Description

The T1000-E has a button. This button could be used to enable sending of canned messages.

Example, single press of the existing button plus a 1 second press sends the first canned message.
Two single presses of the existing button plus a 1 second press sends the second canned message.

This would allow simple communications without having to take out and turn on a phone for simple communications between devices.

Edit:
Obviously there would have to be a timeout, so if you press the button three times without a long press, it will after a period of time go back to the first canned message with the first button press.
Also, if the device has a buzzer like the T1000-e does, it can be enabled for button feedback so you know when you are pressing the button(optional setting).

Example sequences.
Example: short press, short press
Result: nothing, there was no long press, so nothing happens, and no message is sent.

Example: short press, short press, long press
Result: canned message number 2 gets sent from the device to the primary channel.

Example: short press, short press, extra long pause, short press, long press
Result: canned message number 1 gets sent from the device to the primary channel.

[willhubs]

Thinking more about this, it wouldn't only apply to the T1000-e but any device with a single button and no screen.

[PID-and-Me]

Yes, I've been trying to get this to work on my T1000 and Musi R1 with no luck. It would actually give a purpose to those User Buttons besides just on/off

[garthvh]

Canned messages without a screen is likely to mostly send messages accidentally.

[thebentern]

We also already have pretty solidified behavior with the double click send position and triple click GPS toggle. This would interfere with the existing functionality and create inconsistency.

[willhubs]

Canned messages without a screen is likely to mostly send messages accidentally.

I believe the longer press would avoid that as it wouldn't be a single accidental press, it would require the long press afterwards. Double click and triple click are already implemented, so accidentally pressing that button would already have an effect.

We also already have pretty solidified behavior with the double click send position and triple click GPS toggle. This would interfere with the existing functionality and create inconsistency.

That makes sense, though it would only change the behavior if the canned message module is specifically enabled or? Those are also already customizable in the radio configuration, you can disable that functionality.

[sendingstrings]

I think it would be helpful to add a activation action before this.

4-5 clicks would activate a specific input mode for a period of time. There would be a tone/LED feedback for this.
While active, you would have an additional set of button action mappings to use.
After 5-10s or a button action, this mode would end. Additional tone/LED feedback optional.

[mjpowersjr]

Hello,
I was forwarded to this thread after posting a related question on reddit ( https://www.reddit.com/r/meshtastic/comments/1o71a61/customize_the_user_button_behavior_on_t1000e_or/ ).

I picked up a Wishmesh Tag and a T1000e - both are working well overall. I also appreciate the consistency in behavior for the user button between the two devices.

That being said, I just wanted to chime in with my thoughts.

---

For my use case - I'm giving these devices to children during a upcoming camping trip. In my perfect world - I would be able to send a message or bell to these devices, and some basic combination of button presses would allow the user to send a canned acknowledge message back over a channel. I understand that is somewhat specific to my use case, but did see others wanting similar behavior on reddit and related GitHub issues.

---

Outside of the ability to customize button presses to do my bidding - I think it's worth considering that the current user button behavior might not be an ideal UX - specifically around using a double press to send a location update VS triple click to toggle GPS on/off.

I think it would be easy for anyone (but especially younger users or less technical users) to mistakenly turn off GPS - and not realize it. I suppose similar arguments could be made from an accessibility standpoint for users who may have various mobility challenges.

---

Just some thoughts for your consideration. Thanks for everyone who has worked hard to build meshtastic into the awesome tech & community that it is!

[sendingstrings]

I would very much agree with @mjpowersjr sentiments.
-Desire to have button functionality that improves the value/function of the device. Specifically for less technical users.
-That the current button behavior is not a great UX period.

I purchased some additional T1000-E units in August, and was thrilled to see that the LED seems to have at least 2 colors. Red and Green. This seems like a great way to provide both additional device status to the user as well as feedback for more complex button interactions.
The red LED also seems way brighter than the green.