I’m ready to confirm that you must erase the chip before loading the firmware. I flashed about 200 pieces and there were cases when the chip did not communicate without erasing.

When flashing for the first time, it is recommended to choose firmware that ends with factory.bin

Now I checked again, the situation repeated itself.
And then I checked it on another ESP32, to which 3 of the same sensors are connected and everything is fine on them. It turns out that the problem is in the sensor. But why he reacts this way to the new firmware is surprising.

It was updated and my room temperature sensor gradually increased by 5 degrees. I returned to the previous firmware, the temperature returned to normal. I didn’t change anything in the settings, I just uploaded the firmware. The temperature sensor is 20 cm away from the module and hangs freely in th...

Thank you for your participation. The problem turned out to be on my side and was solved by updating the firmware again. At first I had 20231225_collection_C and it did not want to work as I described. Then I installed 20231225_normal , the problem went away. After your message I went back to 202312...

Is the SetLevel version of that command working as intended?

yes

And how is the Level plugin configured?

Do you have other rules that set the Hysteresis to a different value?

no

On Dom#pid Do
TaskEnable,pid
config,task,pid,SetLevel,%eventvalue%
config,task,pid,SetHysteresis,1
Save
Endon

ESP_Easy_mega_20231225_collection_C_ESP32_4M316k, the command doesn't work config,task,<taskname>,SetHysteresis,<value|calculation>.
Everything is fine in build ESP_Easy_mega_20231225_normal_ESP32_4M316k.

It turned out to be implemented by handling the event.
%eventvalue% is used as the WifiSSID argument, but under one condition.
The passed value must start with a digit.
Therefore, I added a number in front of the text transmitted value, and then

Is it possible to somehow pass a new WifiSSID and WifiKey value to EspEasy using MQTT?

That's wonderful!
Now a simple electrician can change the temperature sensor!

That would be what need!

It's a pity.
I used EspEasy on 28 tobacco drying chambers and sometimes I have to change the modules, and register the old sensor in the settings. This work can be difficult for service personnel, especially at night.
Thank you for the work you and your colleagues are doing.

I'll try to formulate it differently. If one sensor is connected to the GPIO and you do not need to select the sensor address in the "Number Output Values:Single" task, it is already only one. If several sensors are connected to one contact, then everything works as before. Sorry, my "...

Is it possible to modify the P004 plugin so that when only one sensor is connected to the gpio, the plugin does not require the selection of the sensor address from the list and would be connected automatically? Just like it is implemented in Sonoff TN.