sfromis

The Berry language does allow such: `raise 'crashing'` Of course, also trivial runtime errors like division by zero `print(1/0)`

AFAICT, the "culprit" was the call hierarchy of > command handler > cheap_power.start > self.update > self.schedule_chosen > self.power > tasmota.set_power > Power command The thing is that issuing commands...

I'd say that support for multiple data sources would probably best be implemented by some sort of plug-in architecture, with the core functionality for controlling energy usage by optimum time...

In Berry, when you pass objects (including lists), it is always by reference, with the callee getting full access. The caller should not depend on it being unmodified. A more...

As I see what was suggested, it was adding Berry sample code for users to pick up, not having it "built into" Tasmota. And lots of users have published their...

I was not trying to "say what to do", but as mentioned in the beginning of this thread, many other personal projects using Tasmota+Berry are in separate Github repositories, where...

On 2023-07-09 I removed the unimplemented `%q` from the wiki markdown page [Chapter 7](https://github.com/berry-lang/berry/wiki/Chapter-7), which seems to be where the most recent docs are, instead of the `.rst` files in...

That syntax breaks existing use cases for the `Led` command, as `Led14 001000` currently means to set pixel number 14 to green. Common Tasmota command formats will separate values by...

The `PulseTime` example is very different, as the command syntax does not vary depending on factors not part of the command itself. Hence command parsing will always be the same,...

Better ask questions in "Discussions" instead of "Issues". Restarting after 40 seconds is a symptom of a gpio configured as a "Button" registering as pushed for 40 seconds straight. This...