Adding at least SmartConfig to enter credentials?

[rin67630]

Hi,
TasmoCompiler is a great resource to generate builds for devices no supported by the standard Tasmota builts.
The caveat is however that it generates a build with fixed credentials.

Integrating a credentials initialization like the standard builts may be too demanding, but could it be possible at least to include ESP's SmartConfig to make a build that can be distributed with variable credentials?

Thank you for considering.
Regards
Laszlo

[benzino77]

Hi Laszlo!

Glad to hear you found TasmoCompiler useful ;)

Can you elaborate more about "it generates a build with fixed credentials"? TasmoCompiler will:

• add your WiFi credentials only when you provide them during build (second step) - you DON'T need to provide them
• add your MQTT creds only when you put them via Custom parameters

[rin67630]

OK sorry, it was a misundestanding.
That was not clear to me.

[rin67630]

Just a question:
if one can enter the MQTT credentials via Custom parameters, maybe one can enter the timezone and the longitude/latitude too?

I have written a Python tool that patches ESP binaries and is able to automatically patch this information together with the WiFi credentials, then flash a ready to use ESP device, with all the user specific information already populated.

You may want to have a look at https://github.com/rin67630/ESP_Binary_patcher

[benzino77]

if one can enter the MQTT credentials via Custom parameters, maybe one can enter the timezone and the longitude/latitude too?

Custom parameters are for your own #define/#undef/#if/#ifndef/#endif's clauses which will be placed at the very end of user_config_override.h file before compilation starts. You can put there ANY #define/#undef/#if/#ifndef/#endif accepted by Tasmota.

You can download user_config_override.h file to see its content after the successful compilation by clicking appropriate button.

[rin67630]

Thank you, i will test if my Python patcher can be used / adapted to patch custom generated .bin files with user parameters.
The aim is to free end-users from any need to care about syntaxes.
The owner of the build populates the data with predefined dummies. then compiles and diestibutes the compiled .bin toether with PythonPatcher.py to the end-user.
That one just copies the generated .bin code into the PythonPatcher-py directory,. starts the Python patcher, choses the .bin file.
Then he gets asked about each user parameter one by one, the geo-data gets automatically pre populated,.
When all info is gathered, the file gets patched, saved and then uploaded into the ESP and the tasmota device is ready to use directly.

I will return once it is tested...