-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Crash when PWM1i is defined when using command wakeup #9465
Comments
This issue has been automatically closed because the issue template is missing or incomplete. |
This issue has been automatically closed because the issue template is missing or incomplete. |
Feed back please in open Issue #9466 |
Define a GPIO with function PWM1i.
Use command
LedTable 1
andDimmer 3
after that fire commandwakeup
it crashes.Sometimes it already crashes with the
Dimmer
command.Compiling Tasmota @160Mhz for the ESP makes it even worse.
The issue is already discussed in Discord. The crash is proabably caused from the used PWM code.
Tasmota actual uses PR esp8266/Arduino#7022 for Tasmota core 2.7.4.1
( https://github.com/tasmota/Arduino/tree/2.7.4.1-tasmota )
With some! tests it seems the issue is fixed using PR esp8266/Arduino#7231 instead.
( https://github.com/tasmota/Arduino/tree/2.7.4.1-PR7231 )
The shutter part and the AC-Zero-Cross Dimmer needs testing for compability for the changed PWM part.
@stefanbode and everyone else is invited to do tests. Thx in advance for doing.
For doing this download the
provided platformio_override.ini.txt
. Rename it toplatformio_override.ini
and copy it to yourroot file of the Tasmota project folder. Rename your override file before ;-)
platformio_override.ini.txt
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
:(Please use
weblog 4
for more debug information)TO REPRODUCE
see above
EXPECTED BEHAVIOUR
no crash
The text was updated successfully, but these errors were encountered: