Hardcoding some commands during compiling

[NsinghP]

Hello, I have loaded Tasmota on RGB LED Bulb based on ESP8285 module. Now Using Tasmocompiler I want to hardcode following console commands:

SetOption65 1
SetOption37 46
and
Setoption92 1

I have tried compiling with following custom lines, but lines 3,4 and 5 are not working: (Please note that I have added line numbers for convenience, the actual code does not have the line numbers):

1#define MODULE            USER_MODULE
2#define USER_TEMPLATE "{\"NAME\":\"RGB-NS9001-Bulb\",\"GPIO\":[0,0,0,0,416,419,0,0,417,420,418,0,0,0],\"FLAG\":0,\"BASE\":18}"

3#define LIGHT_PWM_CT_MODE      false
4#define SETOPTION37_DEFAULT 46
5#define SO65_FAST_POWER_CYCLE_RECOVERY 1

6#define EMULATION         EMUL_HUE
7#define USE_EMULATION_HUE

What am I doing wrong? Kindly help in formatting the custom commands for hardcoding in a .bin file.

Thanks,

Navi

[Jason2866]

You can see which defines are possible in general and which SetOption this will be
https://github.com/arendst/Tasmota/blob/development/tasmota/my_user_config.h
Not every SetOption has a corresponding #define

[NsinghP]

You can see which defines are possible in general and which SetOption this will be
https://github.com/arendst/Tasmota/blob/development/tasmota/my_user_config.h
Not every SetOption has a corresponding #define

Jason Thanks for your quick reply and for pointing me in the right direction. I was able to figure out 2 out of the three commands but was not able to figure out how to hardcode Setoption37 as follows:
----Changed Commands----

3#define LIGHT_PWM_CT_MODE      true <-----Working
4#define SETOPTION37 46    <-----------------Does not work)
5#define APP_DISABLE_POWERCYCLE true <---Working

Setoption37 is not mentioned anywhere in the my_user_config.h file that you linked to. Please give me some more pointers on how to format the command correctly. Thanks in advance for your time.

--Navi

[sfromis]

Since SetOption37 was indeed not mentioned there, there simply is no #define symbol allowing you to hardcode a starting value; guessing at names is not useful.

In many cases (not all), you can instead use the USER_BACKLOG string (as mentioned in the same file) with one or more commands to be executed once only, first boot after a full reset (or initial install).

This will not have effect after doing a normal upgrade of the binary, and neither is the case for other defaults you can change via commands, with or without #define symbols available.

In most cases, you can just configure after having installed, as most such values are saved persistently across restarts and upgrades.

[NsinghP]

Jason and sformis Thanks for your help. I was going through Sfromis's @sfromis previous posts/replies and as per the information there I tried the following code:

1#define MODULE USER_MODULE
2#define USER_TEMPLATE "{"CMND":"SetOption37 46","NAME":"Wipro-RGB-NS9001","GPIO": [0,0,0,0,416,419,0,0,417,420,418,0,0,0],"FLAG":0,"BASE":18}"
<---This worked for "SetOption37"
3#define LIGHT_PWM_CT_MODE true
4#define SETOPTION37 46 <-Removed from code
5#define APP_DISABLE_POWERCYCLE true
6#define EMULATION EMUL_HUE
7#define USE_EMULATION_HUE

Final code that worked is as follows:

#define MODULE            USER_MODULE
#define USER_TEMPLATE "{\"CMND\":\"SetOption37 46\",\"NAME\":\"Wipro-RGB-NS9001\",\"GPIO\":[0,0,0,0,416,419,0,0,417,420,418,0,0,0],\"FLAG\":0,\"BASE\":18}"
#define LIGHT_PWM_CT_MODE      true
#define APP_DISABLE_POWERCYCLE true
#define EMULATION         EMUL_HUE
#define USE_EMULATION_HUE

Now the Bulb is working as intended!
--Regards and Thanks for your time.