Few latest tasmota developer updates do not accept (EDM-1WAA-EU) template - Maxcio Rotary Dimmer #24185
Description
PROBLEM DESCRIPTION
Few latest tasmota developer updates do not accept (EDM-1WAA-EU) template - Maxcio Rotary Dimmer .
After entering the template EDM-1WAA-EU, the device restarts and automatically sets the first standard "Sonoff Basic" template without any GPIO settings. After restoring the settings from the file or setting the template EDM-1WAA-EU manually, the same thing happens: restart and "Sonoff Basic." For these dimmers, I reverted to the "release" version to continue using them.
This problem has been going on for several weeks.
https://templates.blakadder.com/maxcio_EDM-1WAA-EU.html
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
- Read the Contributing Guide and Policy and the Code of Conduct
- Searched the problem in issues
- Searched the problem in discussions
- Searched the problem in the docs
- Searched the problem in the chat
- Problem is not scripter related, in this case open a discussion and tag gemu2015
- Device used (e.g., Sonoff Basic): EDM-1WAA-EU
- Tasmota binary firmware version number used: developer 15.1.0.3 (43f4fad-tasmota)
- Pre-compiled
- Self-compiled
- Flashing tools used: OTA
- Provide the output of command:
Backlog Template; Module; GPIO 255:
{"NAME":"EDM-1WAA-EU","GPIO":[1,1,1,1,1,1,0,0,1,1,1,1,1,0],"FLAG":0,"BASE":54}
console
Backlog SetOption97 1; TuyaMCU 11,1; TuyaMCU 21,2; DimmerRange 10,1000
- If using rules, provide the output of this command:
Backlog Rule1; Rule2; Rule3:
Rules output here:
- Provide the output of this command:
Status 0:
STATUS 0 output here:
- Set
weblogto 4 and then, when you experience your issue, provide the output of the Console log:
Console output here:
TO REPRODUCE
firmware update
EXPECTED BEHAVIOUR
template accepted
SCREENSHOTS
ADDITIONAL CONTEXT
Among the many HA devices in my home, I have three such dimmers in constant use. Everything worked fine for several years, always on developer firmware. I update them quite often (These are some of the first pcb revisions, because I haven't had to replace the Wi-Fi modules, as far as I remember). Now, for several updates, the problem described above has been occurring. I'm currently using the release version (v15.1.0), which is older and doesn't crash the template.
(Please, remember to close the issue when the problem has been addressed)