WiFi-Dimmer-Script.txt

>D
sw=0
tmp=0
cnt=0
tmr=0
hold=0
powert=0
slider=0
dim=""
shortprl=2 ;short press lo limit
shortpru=10;short press up limit
dimdir=0   ;dim direction 0/1
dimmlp=2.2 ;dim multiplier 1..2.55
dimstp=2   ;dim step/speed 1..5
dimll=15   ;dim lower limit min. 0
dimul=95   ;dim upper limit max. 100
dimval=70  ;start dim level 0..100

>B
=>print > WiFi-Dimmer-Script-v1.0 <
=>Counter1 0
=>Baudrate 9600
; boot sequence
=#senddim(dimval)
delay(1000)
=#senddim(0)

>F
cnt=pc[1]
if chg[cnt]>0
; sw pressed
then sw=1
else sw=0
; sw not pressed
endif

; 100ms timer
tmr+=1
; short press
if sw==0
and tmr>shortprl
and tmr<shortpru
then
powert^=1
; change light on/off
if powert==1
then
=#senddim(dimval)
else
=#senddim(0)
endif
endif

; long press
if sw>0
then
if hold==0
then
; change dim direction
dimdir^=1
endif
if tmr>shortpru
then
hold=1
if powert>0
; dim when on & hold
then
if dimdir>0
then
; increase dim level
dimval+=dimstp
if dimval>dimul
then
; upper limit
dimval=dimul
endif
=#senddim(dimval)
else
; decrease dim level
dimval-=dimstp
if dimval<dimll
then
; lower limit
dimval=dimll
endif
=#senddim(dimval)
endif
endif
endif
else
tmr=0
hold=0
endif

>E
slider=Dimmer
; slider change
if chg[slider]>0
then
; dim according slider
if slider>0
then
dimval=slider
else
powert=0
endif
endif

if pwr[1]==1
; on/off webui
then
powert=1
=#senddim(dimval)
else
powert=0
=#senddim(0)
endif

; subroutine dim
#senddim(tmp)
dim="FF55"+hn(tmp*dimmlp)+"05DC0A"
=>SerialSend5 %dim%
=>Dimmer %tmp%
#

Thank you!

:)

Thanks for the script. I modified it a bit. I fixed a bug that did not allow me to turn on the dimmer immediately with the desired brightness by wifi. And he did so that after turning off the power, the previously set brightness was restored. Unfortunately, I do not know how to put the code here so that the site does not spoil it. Well, at least so:

>D
sw=0
tmp=0
cnt=0
tmr=0
hold=0
powert=0
slider=0
dim=""
shortprl=1 ;short press lo limit
shortpru=10;short press up limit
dimdir=0 ;dim direction 0/1
dimmlp=2.55 ;dim multiplier 1..2.55
dimstp=2 ;dim step/speed 1..5
dimll=10 ;dim lower limit min. 0
dimul=100 ;dim upper limit max. 100
p:dimval=20 ;start dim level 0..100

>B
=>print > WiFi-Dimmer-Script-v1.1 <
=>Counter1 0
=>Baudrate 9600
; boot sequence
=#senddim(dimval)
delay(1000)

>F
cnt=pc[1]
if chg[cnt]>0
; sw pressed
then sw=1
else sw=0
; sw not pressed
endif

; 100ms timer
tmr+=1
; short press
if sw==0
and tmr>shortprl
and tmr<shortpru
then
powert^=1
; change light on/off
if powert==1
then
=#senddim(dimval)
=>Power 1
else
=#senddim(0)
=>Power 0
endif
endif

; long press
if sw>0
then
if hold==0
then
; change dim direction
dimdir^=1
endif
if tmr>shortpru
then
hold=1
if powert>0
; dim when on & hold
then
if dimdir>0
then
; increase dim level
dimval+=dimstp
if dimval>dimul
then
; upper limit
dimval=dimul
endif
else
; decrease dim level
dimval-=dimstp
if dimval<dimll
then
; lower limit
dimval=dimll
endif
endif
=#senddim(dimval)
=>Dimmer %dimval%
endif
endif
else
tmr=0
if(hold>0)
then
hold=0
svars
endif
endif

>E
slider=Dimmer
; slider change
if chg[slider]>0
then
; dim according slider
if slider>0
then
dimval=slider
else
powert=0
endif
endif

if pwr[1]==1
; on/off webui
then
powert=1
=#senddim(dimval)
svars
else
powert=0
=#senddim(0)
endif

; subroutine dim
#senddim(tmp)
dim="FF55"+hn(tmp*dimmlp)+"05DC0A"
=>SerialSend5 %dim%
#

Thanks @askold2,
but it's more a feature than a bug :)

personally, I don't like "Light ON" after power failure / reset / restart...

There is a PowerOnState command for this. It works great in my version of the script.

Great work! Thanks for the script.

When powered off, the attached light bulb (halogen 40w E27 screw fitting) sometimes starts to glow faintly.
When sending the serial command to power off (=dimlevel 0%) the bulb turns off again, but only for a while and then start to glow faintly again.
Do you guys recognize this behaviour?

I fixed this by adding a few lines to the script and by basically repeating the serial command every few seconds when in off state.
Not the most elegant way I must say.

Looks like whenever the ESP MCU is transmitting over wifi, this somehow influences the secondary MCU.

Out of interest, what have people seen their loadAvg to be when using this solution? My devices are working fine - and when off, the loadAvg is very low. But when the light is on, the loadAvg rises to 999 and stays there:

22:34:19 MQT: light/tele/STATE = {"Time":"2019-11-21T22:34:19","Uptime":"0T01:20:15","UptimeSec":4815,"Heap":27,"SleepMode":"Normal","Sleep":250,"LoadAvg":3,"MqttCount":1,"POWER":"OFF","Dimmer":0,"Fade":"OFF","Speed":1,"LedTable":"ON","Wifi":{"AP":1,"SSId":"xxxxxx","BSSId":"xxxxxxx","Channel":11,"RSSI":48,"LinkCount":1,"Downtime":"0T00:00:10"}}

Turned light on, then...

22:44:24 MQT: hall_light/tele/STATE = {"Time":"2019-11-21T22:44:24","Uptime":"0T01:30:20","UptimeSec":5420,"Heap":27,"SleepMode":"Normal","Sleep":0,"LoadAvg":273,"MqttCount":2,"POWER":"ON","Dimmer":70,"Fade":"OFF","Speed":1,"LedTable":"ON","Wifi":{"AP":1,"SSId":"xxxx","BSSId":"xxxx","Channel":11,"RSSI":48,"LinkCount":1,"Downtime":"0T00:00:10"}}

This doesn't seem to affect performance....

@thxthx0 this is great!

Yesterday I reflashed a Tuya dimmer OTA with tuya-convert. Worked like expected (did some Tuya switches before). Then upgrade to newest version (OTA, thehackbox.org) and uploaded the scriptenabled Tasmota (https://github.com/arendst/Tasmota/files/3776333/Tasmota-v7.0.0.1-w-Scripting-2.6.x-1MB.zip) to one of my own servers (took the .bin out of it). Upgraded (OTA) to that version and the device was 'bricked'.

So, took a soldering iron, opened the box en flashed it using serial. Tried upgrading using 'file upload' and got an error. THEN I used Google (should have done that before) and 'upgraded' to the minimal version of Tasmota FIRST and the uploaded the scriptable version. That is running fine now! I still have to template the device, run the script and make it MQTT, but some questions first:

1. Is the scriptable version maintained regularily and can that version be used to update the devices using tasmoAdmin
2. The docs of Tasmota state that the minimal version is used intermediately when flashing a version that is to big to fit in the remaining flash. In my case (using my own webserver) that did not work. Does someone know how that can be achived?

@keesdekraker
Here a reference to the other comment for all: arendst/Tasmota#5737 (comment)

@dbrb2
interesting, same here, I didn't notice "LoadAvg":999 before.
Maybe "just a kind of" software issue processing the LoadAvg value,

in new Tasmota 7.0.0.6 version it shows "LoadAvg":99 instead of 999

The temperature and power consumption of the ESP8266 doesn't really increase,
and as you mentioned, no effect to the performance.

@RalphMeuse

and the device was 'bricked'.

I'm afraid it's because of changing Cores (2.6.0 -> 2.6.1 -> pre2.6)
without Reset 5 or full erase always a risky operation.

1. So the scriptable version is already outdated and cannot be maintained directly,
   (blakadder doesn't like too many PRs at the Templates Repo ;) )
   but it's easy to compile (GitPod / TasmoCompiler / Portable VSC)

2. That can be achived when using direct web update via OTA-URL (http://thehackbox.org/tasmota/...)
   it's called OTA Magic :) https://github.com/arendst/Tasmota/wiki/Upgrading#upgrade-by-web-server
   but no idea how it could work at your own webserver.

Hej, I would like to thank you as well.

I have 8 dimmers and 7 of them have done spooky things like turning off without any action taken or glowing like @keesdekraker reported above. Only an accidentically WLAN-Downtime solved this problems. But ok, a Wifi Dimmer that only works if Wifi is off doesn't make a lot of sense or fun.....based on your and blakaddder great work I was able to flash them via tuya-convert and adding your script.....what should I say: Working, no problems!! 😀😀😀ThxThx....

As an addditional info: The linked firmware can't be flashed via OTA/tuya-convert as it is greater than 512kb which is the maximum for OTA (half of the flash). I have compiled the actual 7.0.0.6 version on Gitpod with scripting, mqtt, Hue, web & timers included which is below 512kb so that I can be flashed via tuya-convert/OTA. If anybody is interested, let me know.

Thanks again👍👍👍

ah, just forgotten: I know what the variable powert does, but could you tell what powert stands for? regs

@sqw534, I have resolved the issue by reverting back to a Tasmota build from the current master branche.
No more sudden dimming actions without commands. It seems it is firmware related after all.
Still having some stability issues with Tasmota though (crashes after some time of Tasmota).

I am very interested in your precompiled binary file. Could you share this bin file plz?

BTW: there is a minimal pre-compiled version of Tasmota, which can be used for two step OTA.
Just OTA flash the minimal binary first using the WebUI and then flash the bigger sized binary using the WebUI.

@sqw534, I'm also very interested in your pre-compiled version 7.0.0.6. I had MAJOR stability issues (WiFi?) with the supplied Tasmota-v7.0.0.1-w-Scripting-2.6.x-1MB.zip. Using GetPod I compiled a 6.7.1 (2.3.0 core) version and running tests on a Sonoff Basic now. Because I kept losing connection with the Tuya Dimmer using 7.0.0.1 it took a lot of time and I need to be sure that my version (using GitPod for the first time) is stable enough to use it on the Dimmer.
One more question to you all: I just started converting my Tuya switches (and now the first Dimmer) to Tasmota and use Home Assistant as automation platform. Does the version with scripting also support MQTT and how should a Dimmer be defined in Home Assistant?
And did someone already convert a smart light (white or dimmable or colored/dimmable) or a LED strip or smart socket from Tuya to Tasmota? Very interested in your experiences. In Holland the firm Action sells LSC smart lights and sockets for nice prices and I would like to convert them all. Anyone interested in joining in to the project?

@sqw534, are you still running your build without any stability or dimming issues?
My wife is getting annoyed by the fact that the living room light isn't doing what it's suppose to be doing and is getting ready to rip out wall switches now.

Could you share your build? I really could ue some good news, as this dimmer is giving me quite a few headaches.
Many thanks in advance!

Hej,

@keesdekraker & @RalphMeuse: Yes, I am still running the build and will share it.

I also have added the ability to dim up if the dimmer is off and fading on/off to the script. Will share this as well. This is only tested on the QS-Wifi D01 Dimmer (https://blakadder.github.io/templates/qs-wifi_D01_dimmer.html) So I can‘t tell you if it it is working on other tuya dimmer.

@RalphMeuse: Yes I have compiled mqtt and scripting and Hue within the build. Hue is unfortunately not stable when using Alexa.

I just have tried to recompile my 7.0.0.6 version, but it fails on gitpod. So I have recompiled it on 7.1.1.1. First tests runs ok but no long term tests right now...

I have compiled it without any wifi settings, so device will come up in AP mode. Just connect to the Wifi tasmota-xxxx and open http://192.168.4.1. You now can connect it to your own Wifi. Device will use DHCP so you have to find your local IP after the reboot. (ping tasmota-xxxx worked in my environment)
After reboot you have to configure the module as described on blakadders site. Finally you need to Edit Script to get the button presses running. Script either from thxthx0 (again thanks for it!!) or use the attached script which includes dim-up from 0 when powered off and fading in/out (configurable within the script fading=0/1). Do not forget to hit the "script enabled" check box

I have added the file my_user_config.h as well, so if you want to change the bin or preconfigure your Wifi/IP on gitpod (Have a look at: https://github.com/arendst/Tasmota/wiki/Compiling-Tasmota-on-Gitpod) just upload this one.

I described the steps a little bit more detailed, just in case somebody else find this post..

Would be great if you could share, if this runs for you or otherwise share your device type and the misbehaviour. We might can work together on this.

Files are located here:
https://github.com/sqw534/QS-Wifi-D01-Tasmota

Enjoy testing...

@RalphMeuse Just to answer your other questions: I do not use HomeAssitent, I am on openhab, so I can't help you on the configuration. Mqtt is enabled within the bin. So you could use it. I have read something about the LSC while searching on the dimmer. There should already be some information around, but can't point you to a specific link.

Best regards

@sqw534 MANY thanks for sharing. I hope to find time in the weekend to try it.

The last week I invested (many and frustrating) hours to find what the problem with my device is. I think I found my problem: if the WiFi signal is low, the minute I activate PWM1 on GPIO14 (or GPIO2 for that matter) I loose connection to the device. I have to move it closer to the WiFi point and issue some http:... cm?cmnd=reset 5 to reset the device so the PWM is deactivated and then the WiFi runs fine again.

The device is a 'real' QS-WiFi-D01-TRIAC (from MOES). I read somewhere that the 'clones' have WiFi stability issues when (software) PWM is used.

So, the next question is: do I have to active a PWM at all? Or will it work without it, because of the separate CPU? And will MQTT work automatically then (probably not) or should I implement that in the script?

I'm very willing to share. I have to find the time to test and also ordered some more devices, in case I brick one...

I have 5 of these dimmers in my house (next to about 20 switches) and it would be GREAT if working with MQTT/HA, because the time delay from Tuya to HA when the state changes is between 5 and 30 seconds. And my wife has the same feelings about that as Kees'es :)

Best regards

@RalphMeuse: I started with these dimmers around a year ago as there havn't been any other (cheap) Wifi-Dimmer available. I have had as well a lot of trouble. Bulbs starts glimming, turned sometime sporadically off and sometimes often off.
My first Test-order-Dimmer works as expected, the following 8 didn't. The only difference was the firmware delivered from 1.0.0 to 1.0.1.

This all stopped as a friend of my daughter accidentically turn our WLAN off by tapping on button of router. No more glimming, turning off...so I decided to connect the dimmer to another/old router and turn this router off. This dramatically reduces the annoyance of my wife ;)....No more voice control via alexa, but the lights are still dimmable and stays on/off as expected. So there is a problem with the firmware-wifi combination. In my case, tasmota solved this issue.

Looking back (and seeing your comment about frustrating hours) it should have waited for the Shelly Dimmers. They are on the market now, much easier to handle, works out of the box, having much more features, costs are simliar small (20€), having support from manufacturer are prepared to be flashed serial via easy accessable pins. I even think I would have exchanged all of the 9 QS-Wifi-D01 with shellys if blakadder and thxthx0 hadn't had the idea to research and share this.

I have learned a lot regarding openhab, tasmota, programming, electrical installations, LEDs, etc while I have tried solving this problem. But I might have been even nice to grab a good book or doing something else as spending time on a more or less faulty product.

So keep on testing, but stay happy!
Otherwise: Exchange them with shellys.

@sqw534
"powert" is my short for power toggle, but I think you already know,
because of your deep dive into this 👍

@RalphMeuse
PWM1 is needed for the slider and (easy) home automation integration
(Push-button operation is possible without a slider/PWM1).

To improve WiFi you could try Reset 3 (and then disconnect/connect power) to calibrate WiFi.
And you can set WifiPower up to 20.5 (default 17dBm)

There are already some LSC templates at https://blakadder.github.io/templates/
and some info here: arendst/Tasmota#6495

@sqw534 and @thxthx0
This is REALLY awesome!!!!!!!!
The 7.1.1.1 build from @sqw534 is definitely different from mine! For starters: it works! Activating PWM does NOT disconnect the device from the WiFi and the size! Perfect! No need for intermediate -minimal.bin. Just flash it after Tuya-convert (-basic.bin) and BANG! Find AP, WiFi parameters -> ready. THANKS A LOT!
Few remarks about this build:

• HUE emulation is default on (I do not use it)
• Something strange is happening with MQTT (state) message: The POWER value is sent as a separate topic, but the Dimmer value is embedded in a json packet that is sent to the RESULT topic (POWER is also in this json packet, BTW). Is it possible to send the Dimmer value to it's own topic? It makes is easier for me to integrate it into HA (and gBridge for Google support).

Maybe this is Tasmota default behaviour. Then I have to find a way to automatically copy the right json part from the packet to it's own topic. Node-RED?
Thanks again for the support and special thanks from my wife. She loves you guys :)

Hej, great that is working for you.

Regarding the build/hue/mqtt:

This seems to be the tasmota default settings/behaviour.

I json statement in result differs if you send a dimmer value (contains Dimmer) or a Power on/off command (doesn‘t contain Dimmer). In openhab I could use jsonpath transformation but the missing Dimmer value causes an error within openhab. I takes me as well a little bit to get an openhab rule for
that. I don‘t know HA, so I can‘t help you on this.

@thxthx0 Thanks for your reply. Indeed I realized that a little bit later.

Best regards.

@sqw534 I made a Node-RED flow that (in case the MQTT Dimmer member is supplied) the json properties Dimmer and POWER are copied over to .../stat/.../Dimmer and .../stat/.../POWER topics. Those topics are used in my HA configuration. And also by Google (using gBridge.io). Seems to work fine that way... BTW: the copiïng of the POWER value seems necessary, because when the Tasmota Dimmer is off and the SLIDER is used to turn it on, the RESULT json indicates POWER ON, but the POWER topic is still OFF. Don't know if this is Tasmota default or a flaw in the script...

Made one addition to the Node-RED flow: when the physical switch is used (and the light fades out) in the end the json in the RESULT topic states "OFF", but the POWER topic is NOT set to "OFF". So HA (and Google) doesn't know it's off. Added it to the flow and now it works as expected!

@sqw534 is it possible to compile a version that supports more possible characters for the script? I ordered a 2 gang dimmer and would like to try to make that work. But with 40 chars left...

Hej,

@RalphMeuse: I have noticed the difference between the Power-state values as well. Setting the SetOption59 to 1 Tasmota updates the telemetry topic on each power/dimmer change. The works quite reliable, as I can use a JSONPath transform within openhab 2.4 which elsewise breaks if a value isn't included in the RESULT topic. Increases the traffic a little bit, but that's ok for me.

Regarding the available characters in the scipting editor: Yes, that would be great as I even want to implement fading when switching via Alexa/Google/WebUI/MQtt. But this isn't related to the build. As far as I have recognized this has @gemu2015 reused the available RAM from rules. So a change of available RAM for the script editor would need a rearrangement of the available RAM within the tasmota project.

If you use the script from thxthx0 you will loose fading but gains more characters left. Dimming-Up could be realized with a couple of lines.
There is a Fade Option within Tasmota which supports Fade-In (not out). Havn't played with this yet.

@gemu2015: Perhaps you might help us by answering the question if it this would be possible to gain more RAM for the script editor?

Best regards

@RalphMeuse: Just one question: I have realized that when the light is off and I send a value to the Dimmer (via mqtt/Alexa or via the console: Dimmer 20) the light turns on but doesn't use the value I have entered. Doing this twice the value is used.
i.e.: Power on-> Set Dimming level to 70 -->Power OFF -->Setting Dimmer level to 10 (via console/Alexa/mqtt) -->Light turns on dimming level 70 -->Setting Dimmer level to 10 (2nd time) -->Light dims to 10.

It would be great if you could test this as well before I raise an issue on github to exclude an error within my local infrastructure.
Best regards

@sqw534
in principle there would be enough flash to expand the script buffer if @arends would provide the space for it.

i myself and a couple of users expand the buffer with a cheap i2c EEPROM (https://www.ebay.de/itm/AT24C256-Serial-EEPROM-I2C-Interface-EEPROM-Data-Storage-Module-for-Arduino-NEU/233026828988?hash=item36417b3abc:g:tq4AAOSwMO9cALBC)
then defaults to 4k buffer.

@gemu2015
Sorry than I messed something up. Does "enough flash" means the area where the configuration is stored?

I have recently tried the decode-config.py and there are a lot values within regarding other modules which I do not need/use. If I clear this out of the config, I would be able to add more characters to the script on upload it to the device?

@sqw534
in the config memory space (which is a subsection of the flash) there is dedicated room for rules buffers (which script uses also)
one could expand this space if needed. this would slightly decrease the space for program memory.

@sqw534
I have the same issue if I only send the Dimmer value. The Tasmota turns on with the old Dimmer value. The POWER state is reported back as ON, although no POWER command ON is issued (still OFF). This happens when using MQTT directly or Google. When using HA the POWER/ON command is ALSO sent. And then it works like expected! (don't know which one comes first...)

@thxthx0 Hej, as you night have seen did I have compiled a slim (<512k) version of the 7.1.1.1 tasmota branch. Here I observe that by sending i.e. „Dimmer 30“ via the console while power is off the light comes up ignoring the given value and uses the last given value before powering off. Afterwards the command is executed as expected. I have tested this with your script as well. Same behaviour.
Now there might be either a bug in my build or within tasmota. Before raising an issue on the tasmota project it would be very kind if you could verify or decline my observings by testing this on your build. Test might be something like this: On Console: Dimmer 50–> Dimmer 0–> Dimmer 10. If everything works the light should come up with a dimming level of 10. In my case it comes up with a dimming level of 50.
Best regards

@sqw534, a bug with incorrect setting of the dimmer level is fixed in my version of the script given in the 4th post of this topic

Hello I hope someone can help me. I'm looking for a script or rule for Tasmota to be able to dim an RGB strip with a button (MagicHome, Shelly RGBW2). for example: 1x press on / off; hold: dimming up and down; Press twice to choose a color (#ffffff). It would also be nice if when switching on / off a relay also switches that the large power supply is not always on. Unfortunately I don't know anything about Rule / Script at Tasmota.

@DpunktS Hej, sorry can‘t help you as I do not have an RGB Dimmer. regs Sven

Hallo an alle,

ich habe ein kleines Problem! ich habe alles, wie in der Anleitung beschrieben, gemacht. wenn ich eine LED 230V dort anschließe funktioniert alles, wenn ich eine Halogen anschließe geht auch alles, wenn ich aber 9 LEDs 230V anschließe geht es über den Taster S aber über MQTT geht es nicht mehr.

Hello everyone,

I have a small problem! I did everything as described in the instructions. If I display a LED 230V, everything works, if I display a halogen, everything works, but if I display 9 LEDs 230V, you can use the S button, but you can no longer use MQTT

@OlfrygtACAB Hej, does it work if you use the web-interface? Up to how many LEDs are working? regs

Im working on a script that is working with two dimmers.
But its the first time writing script for Tasmota.
What does "sld1=Dimmer" do? Is Dimmer refering to the WebUi slider? and the PWM1?
What is the reference to PWM2?

This is what I got so far

>D
sw1=0
sw2=0
pw=0
cnt=0
tmr1=0
tmr2=0
hld1=0
hld2=0
tgl1=0
tgl2=0
sld1=0
sld2=0
dcmd=""
shtpl=2
shtpu=10
dd1=0
dd2=0
dmp=2.2
dsp=2
dll=15
dul=95
dv1=70
dv2=70

>B
=>Counter1 0
=>Counter2 0
=>Baudrate 9600
=#sd1(0)
=#sd2(0)

>F
cnt1=pc[1]
cnt2=pc[2]
if chg[cnt1]>0
then sw1=1
else sw1=0
endif
if chg[cnt2]>0
then sw2=1
else sw2=0
endif

tmr1+=1
tmr2+=1

if sw1==0
and tmr1>shtpl
and tmr1<shtpu
then
tgl1^=1
if tgl1==1
then
=#sd1(dv1)
else
=#sd1(0)
endif
endif

if sw2==0
and tmr2>shtpl
and tmr2<shtpu
then
tgl2^=1
if tgl2==1
then
=#sd2(dv2)
else
=#sd2(0)
endif
endif

if sw1>0
then
if hld1==0
then
dd1^=1
endif
if tmr1>shtpu
then
hld1=1
if tgl1>0
then
if dd1>0
then
dv1+=dsp
if dv1>dul
then
dv1=dul
endif
=#sd1(dv1)
else
dv1-=dsp
if dv1<dll
then
dv1=dll
endif
=#sd1(dv1)
endif
endif
endif
else
tmr1=0
hld1=0
endif

if sw2>0
then
if hld2==0
then
dd2^=1
endif
if tmr2>shtpu
then
hld2=1
if tgl2>0
then
if dd2>0
then
dv2+=dsp
if dv2>dul
then
dv2=dul
endif
=#sd2(dv2)
else
dv2-=dsp
if dv2<dll
then
dv2=dll
endif
=#sd2(dv2)
endif
endif
endif
else
tmr2=0
hld2=0
endif

>E
sld1=Dimmer
if chg[sld1]>0
then
if sld1>0
then
dv1=sld1
else
tgl1=0
endif
endif

sld2=Dimmer
if chg[sld2]>0
then
if sld2>0
then
dv2=sld2
else
tgl2=0
endif
endif

if pwr[1]==1
then
tgl1=1
=#sd1(dv1)
else
tgl1=0
=#sd1(0)
endif

if pwr[2]==1
then
tgl2=1
=#sd2(dv2)
else
tgl2=0
=#sd2(0)
endif

#sd1(pw)
dcmd="FF5501"+hn(pw*dmp)+"3005DC0A"
=>SerialSend5 %dcmd%
=>Dimmer %pw%
#

#sd2(pw)
dcmd="FF5502"+hn(pw*dmp)+"3005DC0A"
=>SerialSend5 %dcmd%
=>Dimmer %pw%
#

But its to long.

Can you pass two parameters to one sub?

@ressof

Hi, plz give it a try (with SetOption68 1):
WiFi-2way-Dimmer-QS-WiFi-D02-Script.txt

I don't have a QS-WiFi-D02 2-way dimmer for testing.

Yes, "=Dimmer" refers to the WebUI slider and PWM1.
Could you please tell us the GPIOs for Counter1 and 2,
so we can add a template.

It's better to let the orginal firmware or switch to tasmota?