-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Multi-level Rule Trigger Crashes Device #8757
Comments
After the restart, on |
Exception 0 is normally a power issue. Other than that I cannot reproduce as mine just keeps on running:
|
Mine is a Sonoff Basic that I flashed long ago with 6.x and migrated recently by I was using it today as a testing device. But it normally runs in my house on a lamp and has been in service for almost 2 years. Without the rule active, I can send @sfromis - what kind of device are you using? And how was it flashed? |
My test device was a Sonoff S20, flashed a long time ago, and repeatedly OTA upgraded. Just did the same test on a NodeMCU, flashed using the builtin USB/serial interface, and also upgraded a few times. Again: Does not seem like a power issue is among the more likely explanations. |
The logo on the flash chip of the S20 looks like "XTX", id |
Same flash chip ID on my Sonoff Basic. |
Just reproduced on a sonoff basic too ending in exception 0. Must be a power issue while scanning the rule. Nice issue! |
Also, the crash is immediate. I turned on |
Here's what I see with
|
Great fun! In addition to exception 9 I now also see Hardware Watchdogs on both sonoff and wemos.
My my my how did we get here? |
Interesting that the rule does what's intended (per both of your logs) and then falls off a cliff. I wonder if the string (the 4 octet period delimited value) assigned to the Var has anything to do with the behavior? I'm just grasping at straws obviously. |
Any straw is welcome. Personally I think it has someting to do with recently introduced possibility to have a rule trigger on a status line. Investigating... |
Fix rules related exception or watchdog by adding a rules mutex solving possible rule loops as in case of Var/Mem/Add/Sub/Mult and Scale (#8757)
I think I've solved it. Give it a try! |
My NodeMCU no longer crashed on |
My Sonoff Basic on Thanks for the quick repair ;-) Mike |
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
Tasmota reboots when a rule triggers that uses a multi-level JSON trigger.
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
Steps to reproduce the behavior:
When
Status 5
is executed,Tasmota reboots.
I also tried
STATUS5#StatusNET#IPAddress
. In this case it doesn't reboot but the rule also does not trigger. So I think this trigger is not correctly specified.EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
Return the value of the specified trigger in
Var1
and not restart.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: