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
The issue is caused by lack of call to analogAttach() for used LED gpio on ANY ESP32.
Implementing this is tricky as there are 8 possible "attach point" of which the first x (up to 5) are being used by configured PWM channels. The last attach point is reserved for the buzzer.
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
When attempting to use the LedPwmMode command on an ESP32 Solo1 based WIFI Smart Light Switch, the system crashes and reboots after a core panic
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:
Flash latest dev solo1 bin
Connect to wifi and set options
backlog devicename TESTBENCH ; FriendlyName1 TESTBENCH; Hostname TESTBENCH; timezone 99; TimeDST 0,2,3,1,2,-240; TimeSTD 0,1,11,1,2,-300; SO8 1; SO55 1; SO59 1; ssid1 xxxxxxxx; password1 xxxxx;
Create template and set module 0
backlog template {"NAME":"Linkind Switch ESP32Solo WS240010008","GPIO":[0,0,0,0,0,224,1,1,0,0,320,0,1,1,0,0,0,0,0,0,0,576,289,0,0,0,0,0,33,32,0,0,0,0,0,0],"FLAG":0,"BASE":1}; module 0;
Set MQTT settings
backlog0 mqtthost 192.168.50.25; topic TESTBENCH; mqttuser xxxxx; mqttpassword xxxxxx;
Set LedPwmMode
LedPwmMode1 1
CRASH
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
LedPwmMode1 set to ON and the ability to use LedPwmOff and LedPwmOn to set brightness values for LED
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: