You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the problem is.
On an ESP32 device (i.e. ESP32-S3-Zero), the location of the serial console port is not constant. Perhaps this is by design but not what I expected (or perhaps I have misunderstood the meaning & purpose of "Serial Tx/Rx" in the template?)
Scenario: GPIO pins are defined for Serial Tx/Rx (i.e. 43, 44); they work correctly (i.e. allow console commands to be issued) when the module is powered from a simple USB power block (i.e. no USB data connection). When the device is powered from a laptop and a USB data connection exists, the GPIO serial pins no longer respond; instead, console commands can only be issued from the USB serial device (e.g. /dev/ttyACM0). Thus the location of the console port is not constant.
Preferred solution: Provide a (new?) command that sets the location of the console port. This command could be used from either the webUI console or used in a rule with system#boot.
Thanks very much!
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:
Consoleoutputhere:
[N/A]
TO REPRODUCE
Steps to reproduce the behavior:
[Copied from Problem Description] Scenario: GPIO pins are defined for Serial Tx/Rx (i.e. 43, 44); they work correctly (i.e. allow console commands to be issued) when the module is powered from a simple USB power block (i.e. no USB data connection). When the device is powered from a laptop and a USB data connection exists, the GPIO serial pins no longer respond; instead, console commands can only be issued from the USB serial device (e.g. /dev/ttyACM0). Thus the location of the console port is not constant.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
[Copied from Problem Description] Preferred solution: Provide a (new?) command that sets the location of the console port. This command could be used from either the webUI console or used in a rule with system#boot.
Alternative 1: a (new) command which allows the relative priority of the serial Tx/Rx console vs the USB console (right now, USB console has priority and overrides the serial Tx/Rx).
Alternative 2: a #define directive which sets the relative priority of serial Tx/Rx console to be higher than USB console.
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:
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
On an ESP32 device (i.e. ESP32-S3-Zero), the location of the serial console port is not constant. Perhaps this is by design but not what I expected (or perhaps I have misunderstood the meaning & purpose of "Serial Tx/Rx" in the template?)
Scenario: GPIO pins are defined for Serial Tx/Rx (i.e. 43, 44); they work correctly (i.e. allow console commands to be issued) when the module is powered from a simple USB power block (i.e. no USB data connection). When the device is powered from a laptop and a USB data connection exists, the GPIO serial pins no longer respond; instead, console commands can only be issued from the USB serial device (e.g. /dev/ttyACM0). Thus the location of the console port is not constant.
Preferred solution: Provide a (new?) command that sets the location of the console port. This command could be used from either the webUI console or used in a rule with system#boot.
Thanks very much!
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
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
Steps to reproduce the behavior:
[Copied from Problem Description] Scenario: GPIO pins are defined for Serial Tx/Rx (i.e. 43, 44); they work correctly (i.e. allow console commands to be issued) when the module is powered from a simple USB power block (i.e. no USB data connection). When the device is powered from a laptop and a USB data connection exists, the GPIO serial pins no longer respond; instead, console commands can only be issued from the USB serial device (e.g. /dev/ttyACM0). Thus the location of the console port is not constant.
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
[Copied from Problem Description] Preferred solution: Provide a (new?) command that sets the location of the console port. This command could be used from either the webUI console or used in a rule with system#boot.
Alternative 1: a (new) command which allows the relative priority of the serial Tx/Rx console vs the USB console (right now, USB console has priority and overrides the serial Tx/Rx).
Alternative 2: a #define directive which sets the relative priority of serial Tx/Rx console to be higher than USB console.
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: