-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPIO1 and GPIO2 will be rewrited from Button to output from Tasmota #23157
Comments
You left out important details asked for in the form, to be able to see exact details of your gpio config. Trying to replicate with a small test on an ESP32-S2, gpio 1+2 configured as "Button" inputs, I can toggle both multiple times, without any issue. Your statement about "see in the gpio viewer that tasmota will rewrite both gpio to be an output instead of an input with pullup and it puts them to down" is not clear, as you do not tell what you see when you make that conclusion, and I can't recognize any of your issues. What I see in the gpio viewer is that both gpio 1 and 2 stays red (with text "High") after power-on boot with the gpio 1+2 config, and stays that way all the time, except when pushing either button, where the matching gpio indicator for each pin becomes green (with text "Low"), and pushing a button makes it appear as green while pushed. What I see is the expected behavior without any issues. |
Hello Thanks for coming back to my issue.The problem acours when you put the pins to GND. So not pushing the button in the gui.In addition to the gpio viewer. If you klick on a gpio a window pops up and say how the port is configured, like input with pull-up or output.ThanksAm 16.03.2025 um 17:33 schrieb sfromis ***@***.***>:
You left out important details asked for in the form, to be able to see exact details of your gpio config.
Trying to replicate with a small test on an ESP32-S2, gpio 1+2 configured as "Button" inputs, I can toggle both multiple times, without any issue.
Your statement about "see in the gpio viewer that tasmota will rewrite both gpio to be an output instead of an input with pullup and it puts them to down" is not clear, as you do not tell what you see when you make that conclusion, and I can't recognize any of your issues. When I have two other pins configured for output (Relay), the gpio viewer has no indication of pins being input or output, only if they are high or low.
What I see in the gpio viewer is that both gpio 1 and 2 stays red (with text "High") after power-on boot with the gpio 1+2 config, and stays that way all the time, except when pushing either button, where the matching gpio indicator for each pin becomes green (with text "Low"), and pushing a button makes it appear as green while pushed.
What I see is the expected behavior without any issues.—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
sfromis left a comment (arendst/Tasmota#23157)
You left out important details asked for in the form, to be able to see exact details of your gpio config.
Trying to replicate with a small test on an ESP32-S2, gpio 1+2 configured as "Button" inputs, I can toggle both multiple times, without any issue.
Your statement about "see in the gpio viewer that tasmota will rewrite both gpio to be an output instead of an input with pullup and it puts them to down" is not clear, as you do not tell what you see when you make that conclusion, and I can't recognize any of your issues. When I have two other pins configured for output (Relay), the gpio viewer has no indication of pins being input or output, only if they are high or low.
What I see in the gpio viewer is that both gpio 1 and 2 stays red (with text "High") after power-on boot with the gpio 1+2 config, and stays that way all the time, except when pushing either button, where the matching gpio indicator for each pin becomes green (with text "Low"), and pushing a button makes it appear as green while pushed.
What I see is the expected behavior without any issues.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
You are still not providing the details you "forgot" to add first time. That's important info to be able to see what Tasmota is doing. And again, when trying to replicate, I'm not seeing anything like the behavior you mention. That also goes for the content of the popup when clicking on a gpio dot in the gpio viewer. My input pins stays as "Pin Mode: Input with Pull-up" through several cycles of pushing my physical buttons. But as you did not provide the relevant details, no basis for speculating about what your situation is. |
PROBLEM DESCRIPTION
Tasmota overwrites input GPIO1 and GPIO2 to outputs when toggling one of them on ESP32S2
REQUESTED INFORMATION
Backlog Template; Module; GPIO 255
:Backlog Rule1; Rule2; Rule3
:Status 0
:weblog
to 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
I find that out with my shutter but if you take a blank esp32s2 configure the gpio1 and gpio2 as a button.
Than taglle them and you will see in the gpio viewer that tasmota will rewrite both gpio to be an output instead of an input with pullup and it puts them to down. It is no more longer able to be used as an input.
The ports stay to be an output also when your restart the esp.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
SCREENSHOTS
If applicable, add screenshots to help explain your problem.
ADDITIONAL CONTEXT
Add any other context about the problem here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: