M5Dial V1 (not V1.1) BtnA not responding (too low of priority?)
-
Greetings,
Background:
- using M5Dial V1.0 because they are on sale for less than $23 USD (I know slow processor)
- using UIFLOW2 because I am new to the M5Stack and don't know python yet
- creating a thermostat using the EVNIII sensor
- using v2.3.9 of firmware (because v2.4.0 has a bug in my experiences with ESP-NOW)
Problem:
- pressing the built-in button on the ring (BtnA) will sometimes "function"
- pressing the software buttons will respond quickly without problem
- if I remove the "DisplaySensorValues" call then BtnA works expected
What I think is the problem:
- it seems that the software buttons from UIFLOW2 has a higher priority than hardware BtnA
- this problem does not exist with the newer M5Dial V1.1 with a faster processor
Thoughts:
- am I missing something easy?
- is there a way to make the BtnA "faster"
Workarounds:
- I will look at not updating the display as often by adding a delay by counting ticks
- upgrade to the M5Dial V1.1 (ugh, I need 5 more so not the best solution)
Thanks-Brian
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login