Synchronizing the rotary encoder and dimmer values

[ChestersGarage]

Hello,

I need the rotary encoder value to be updated when a dimmer value is adjusted through software. This would allow for the dimmer value to always be the same as the rotary encoder value. As it stands, they are almost always different because I have multiple sources changing the software value in addition to users changing the hardware value. And it makes for a usability issue because when the rotary encoder is changed, it causes the dimmer value to jump from its software value to the hardware value.

Right now, I can rotate the encoder and it changes the dimmer. But if I change the dimmer in software, it doesn't update the encoder value. Then, when I adjust the encoder again, the dimmer value jumps from what it was to what the encoder value is, which is usually very different at this point and makes for annoying bright flashes or dark "anti-flashes".

I'd like something like this, assuming this is the right way.

...
ON Channel1#state DO Var1=%value% ENDON (software change updates Var1)
ON Rotary1#Pos1 DO Var1=%value% ENDON (physical change updates Var1)
ON Var1#State DO Backlog Channel1=%value%; Rotary1=%value% (Var1 updates dimmer and encoder)
...

Keeping the dimmer value and rotary encoder in sync seems like standard basic smart dimmer functionality. Did I miss the documentation about it somewhere? Can this be done in Tasmota?

I have tried this also:

SetOption43 1
Rule1
ON Rotary1#Pos1==1 DO Channel1 + ENDON
ON Rotary1#Pos1==0 DO Channel1 - ENDON
ON Channel1#State DO IF (%value%>9 AND %value%<100) DisplayText [s4x8y20] %value%% .
ELSEIF (%value%==100) DisplayText [s4x18y20]HIGH .
ELSEIF (%value%<10 AND %value%>0) DisplayText [s4x18y20] %value%%  .
ELSE DisplayText [s4x6y20] OFF .
ENDIF ENDON

(Extra spaces and periods are how I am overwriting screen artifacts because it's slightly faster than clearing the screen on every update.)

The dimming value changes, but the DisplayText never updates. And the dimmer changes by increments of 10 instead of 1, which doesn't work for my case.

So then this:

...
ON Rotary#Pos1==1 DO Channel1 +1 ENDON
ON Rotary#Pos1==0 DO Channel1 -1 ENDON
...

Just gives me:

10:59:50.865 RUL: ROTARY1#POS1==1 performs 'Channel1 +1'
10:59:50.866 SRC: Rule
10:59:50.866 CMD: Grp 0, Cmd 'CHANNEL', Idx 1, Len 2, Pld 1, Data '+1'
10:59:50.869 MQT: stat/tasmota_218C64/RESULT = {"POWER1":"ON","Channel1":1,"Color":"03"}
10:59:50.965 RUL: ROTARY1#POS1==1 performs 'Channel1 +1'
10:59:50.966 SRC: Rule
10:59:50.966 CMD: Grp 0, Cmd 'CHANNEL', Idx 1, Len 2, Pld 1, Data '+1'
10:59:50.970 MQT: stat/tasmota_218C64/RESULT = {"POWER1":"ON","Channel1":1,"Color":"03"}
10:59:51.065 RUL: ROTARY1#POS1==1 performs 'Channel1 +1'
10:59:51.066 SRC: Rule
10:59:51.066 CMD: Grp 0, Cmd 'CHANNEL', Idx 1, Len 2, Pld 1, Data '+1'
10:59:51.069 MQT: stat/tasmota_218C64/RESULT = {"POWER1":"ON","Channel1":1,"Color":"03"}

Console configs:

SetOption15 1
Set PWM control for LED lights
0 = basic PWM control
1 = control with Color or Dimmer commands (default)

SetOption43 100
0..255 = to control Rotary step. Details #10407

MultiPWM / SetOption68 1
Multi-channel PWM instead of a single light
0 = Treat PWM as a single light (default)
1 = Treat PWM as separate channels. In this mode, use Power<x> to turn lights on and off, and Channel<x> to change the value of each channel.
Color still works to set all channels at once.
Requires restart after change

SetOption91 1
AKA: PowerOnFade 1
Enable fade at power-on

Fade 1
Speed 4 (2 sec)
Slow startup fade

SetOption98 1
Provide rotary dimmer rule triggers
0 = disable (default)
1 = enable

SetOption114 0
Detach switches from relays and send MQTT messages instead
0 = disable (default)
1 = enable

SetOption117 1
Run fade at fixed duration instead of fixed slew rate
1 = enable

Thanks!

EDIT: Immediately after posting, I realized I probably don't want SetOption68 set to ON for this project. I defaulted to ON because my last project with Tasmota was a 5-channel dimmer. That for sure needed it! But this probably doesn't.

[sfromis]

Did you look into what you get with SetOption98 0, SetOption68 0, SetOption43 100, SetOption15 1 and no rules? Tasmota is already able to control a PWM directly based on rotary operation. For the display of the number, you could then add rules to pick up the messages when the dimmer changes, including when you use the Dimmer command to set a new level directly.

[ChestersGarage]

I thought that might be the case, and I did try it, but it didn't function. But I'll check again and see if I missed something. Missing details seems to be plaguing me on this project.

[sfromis]

Typical issue would be if you used SetOption68 1 which does not provide you with a Dimmer function.

[ChestersGarage]

OK, all dimming functions and encoder work perfectly, after applying the SetOptions you posted above and disabling all rules. Even the dimmer and encoder stay in sync whether changed via encoder or software.

But ONLY if I also disable the display by removing Option A3.

As soon as the display is introduced, things get mapped/assigned/associated wrong and Tasmota fails to report dimmer values to HA. The HA dimmer dialog will dim the LED, but changing the value with the encoder does not update HA, and HA resets its dimmer slider to zero every time I open it. And in some cases, the HA dimmer won't dim the LED because somehow it is tied to a non-existent dimmer instead of the one assigned PWM dimmer. I have not identified the cause of the inconsistency.

Since my remaining issues are related to the display, I'm considering this thread solved.

Thank you!