How many Nested EVENTS?

[toffel969]

The rule engine currently processes at three levels max. However, the protection mechanism didn't work properly on the Mega where we have multiple rule sets and it crashed the system because of to many open files. The dev branch has been updated. It now stops processing before a new file handle is opened.
Exceeding nesting level should give a logged warning.

Hi Martinus

Just a question on that. Does the nesting limitation also apply the workaround using multiple events? Or are you referring to the new feature of boolean nesting within one event?

[Martinus]

It's true that the boolean checks are also limited to three according to the wiki.

But this is about calling events from an event. Technically this is a recursive function call with all the usual challenges. Each level occupies stack space and also has a file handle open to SPIFFS. This has never been thoroughly tested and it mail fail due to lack of resources like file handles and RAM. The current limit of 3 could well work on a bare unit and still fail when many RAM hungry tasks/plugins are loaded.

[toffel969]

It's true that the boolean checks are also limited to three according to the wiki.

But this is about calling events from an event. Technically this is a recursive function call with all the usual challenges. Each level occupies stack space and also has a file handle open to SPIFFS. This has never been thoroughly tested and it mail fail due to lack of resources like file handles and RAM. The current limit of 3 could well work on a bare unit and still fail when many RAM hungry tasks/plugins are loaded.

Thanks for making that clear. Maybe we should add a warning to the wiki. I will do so when I find time

[TD-er]

[...]
I update the MQTT import1 values through OPENHAB MQTT.

Result: after few updates the unit crashes on this line of code: core_esp8266_main.cpp:98 __yield
[...]

That error may occur when yield, or delay is being called from outside setup() or loop().
That's only possible when using events (that's why I know this, see last updates to the WiFi code )
So somewhere an event handler function is calling some command which does eventually call yield().
Maybe somewhere in the PubSubClient library (handling MQTT) ???

[kimot]

Are you compile itself or using .bin file.
I see NESTED parameters define in source code, but you never know setting for your bin. file

[leel1967l]

I am using the .bin file.
I do not compile myself.

[kimot]

So you must try how many nested is compiled.
I think three with my _dev13