Berry newbie - Trivial example fails on custom build Tasmota 14.1.0 - what am I missing?

[mi-hol]

tried https://tasmota.github.io/docs/Berry-Cookbook/#adding-commands-to-tasmota via copy&paste from the web page but it reports a syntax error.
Simple commands work though.

Am I missing something?

[barbudor]

You are adding a Tasmota command to be called from the Tasmota console, not from Berry console

[sfromis]

Commands you create can be invoked via the Tasmota console (not Berry), MQTT, serial, rules, Berry tasmota.cmd and so on.

[mi-hol]

Right, coming from other shells I missed the part "Then in Tasmota Console:"
Thank you so much!

Was I the only newbie to struggle with this from my view uncommon separation of consoles?

[mi-hol]

Was I the only newbie to struggle with this from my view uncommon separation of consoles?

#22327 (comment) is showing a similar confusion

[mi-hol]

@barbudor @sfromis learning a bit more I found a way to simplify the tutorial, thereby avoiding potential confusion.
Simplify via using tasmota.cmd instead of closing Berry Console and opening Tasmota Console.

How about changing the tutorial to only use Berry console?
I'd be happy to provide a PR if you agree to above proposal

[mi-hol]

Adding a command and then using tasmota.cmd() to use it from Berry is non-sense.

@barbudor I did more looking around and found that my proposed technique is actually used in at least one of the featured solutions.
Maybe you could elaborate on the reasons this approach would be "non-sense"?

[barbudor]

Where?

[barbudor]

And I already explained the purpose of 'tasmota.add_cmd'

[sfromis]

While a couple of the Berry cookbook examples does use tasmota.cmd for the purpose of executing existing Tasmota commands as part of automating something, that is a very different usage from defining your own command, and then suggesting how it technically can (even if not the intended way) be executed from inside of Berry. The purpose of defining something as a command, instead of a function or a Berry module, would generally be to be able to invoke it from outside of Berry. Like from the console, MQTT, etc.

[mi-hol]

for the purpose of executing existing Tasmota commands as part of automating something

is my use-case, manually switching between Berry to define a command and console to run and test it, is what I would call non-sense. It seems to result in getting the best out of 2 different tools.
As so often the "correct approach" depends on several factors, there is no single right approach.
Lets leave it at that understanding.

[sfromis]

I'd say that suggesting to execute the command form inside Berry is actually more of a "non-sense" approach, as going to the Tasmota console serves to illustrate the point of defining a command, how it is meant to be used.