Tasmota v13 cannot be used as source

Question

Tasmota v13 cannot be used as source

ThinkPadNL opened this issue a year ago · 9 comments

Hi,

Same issue as back in April #346
A new Tasmota release is out, but cannot be found as source.

Last time you edited a file, but i don't understand why you have it hardcoded (and thus requiring a change of code every time a new release is out). Why not remove this limit, or make something like a RegEx so it is dynamical?

Please fix so i can compile a new FW to update my devices. Thanks :)

Answer 1 · 2023-06-27T09:00:06.000Z

To understand why it is hardcoded I encourage you to read this threads:
#215 (comment)
arendst/Tasmota#12516
#305
#301 (reply in thread)

The beauty of OpenSorce is that you can fork TasmoCompiler source code and do whatever you need - including removal of Tasmota version boundaries.

Answer 2 · 2023-06-27T09:33:15.000Z

I didn't mean to be rude, sorry if it came across that way 😄
I now understand better what the problem is about. Fortunately, I know what the fix is (adjusting maxVersion in config.js) and so i was able to compile an updated FW this morning.

Answer 3 · 2023-06-27T10:03:01.000Z

Fortunately, I know what the fix is (adjusting maxVersion in config.js) and so i was able to compile an updated FW this morning

Exactly it is just one line to be changed. But it needs to be tested with couple of "config permutations" to be sure that TC is compatible with new Tasmota version before I release new TasmoCompiler.

I will reopen this issue to remind me that in a spare time I should take care on this and also to direct other Tasmota enthusiast that it is, let's say, "work in progress". I will close this issue when the new version (supporting Tasmova v13) will be released.

Answer 4 · 2023-06-27T10:08:42.000Z

Oh, and you do not need to be sorry - I just do not follow all the Tasmota changes and releases. It's good to have one to point me that new release is there and TC should be adjusted ;)

Answer 5 · 2023-07-01T09:52:48.000Z

Fortunately, I know what the fix is (adjusting maxVersion in config.js) and so i was able to compile an updated FW.

How can I change the "config.js"of the running container? No editor part of the image?
Thanks

Answer 6 · 2023-07-01T09:58:48.000Z

@Noschvie apt get update and then apt get install nano

nano config.js

Answer 7 · 2023-07-01T10:10:40.000Z

New version is released. Pull new docker image v11.0.0.

Answer 8 · 2023-07-01T12:35:53.000Z

Works perfect, thanks again!

Answer 9 · 2023-12-31T16:24:05.000Z

I will reopen this issue to remind me that in a spare time

Hmm, needs to be reopen again?
#382