Closed ejohb closed 1 month ago
@curzon01
Thanks a lot for addressing this. Just to check, the module value is now offset by -1
. Is this expected?
09:14:55.924 MQT: tasmota/device/bedroom-fan/stat/RESULT = {"Module":{"1":"Sonoff Basic"}}
Results in: "module": 0,
and Module 0
outputs 255
, etc.
yes, that's corect.
The json output contains the human readable content of the internal Tasmota settings struct (see decode-config .json format) and Tasmota handles these settings this way. The internally (Tasmota) processed data is not always the same as you are familiar with from Tasmota cmnd. That's why you got -1 for 0. But there are only a few settings data that differ in this way. The parameter for this data is corrected by decode-config when outputting in Tasmota cmnd format (param -T or ) by adjusting the described command parameter.
@curzon01 That's great. Many thanks for clarifying.
Describe the bug
The
module
value is not included in the JSON or command output.To Reproduce
config1.json
module 0
(previously it was 1)config2.json
Expected behavior
I would expect the see the module change reflected somewhere, but it isn't. Besides CRC and Boot Count values, the only change is this:
"last_module": 255,
In other words, it seems to include the last module, but not the current one.
Nor is there a
Module
command in the command output:decode-config.py --source moon.lan --output-format cmnd > config2.cmd
There is only the command:
Module2 1
Version Information
System' information of your Tasmota data