rbswift

**Brightness Level** - try these 2 commands LedTable 0 DimmerRange 20,100 **Flickering** - check the Console log and make sure you actually see version 51.5, if not then upgrade again...

maybe just try `ledtable` on its own and check that it's off: ``` 03:09:33 CMD: ledtable 03:09:33 MQT: stat/kitchen/RESULT = {"LedTable":"OFF"} ```

unsure why you've got 2_7_4_9 when I've got 2_7_4_7 but I doubt that's really relevant. ``` 00:00:00 Project tasmota Dining Version 9.1.0.2(tasmota)-2_7_4_7 00:00:00 SNS: Hardware Serial 00:00:00 SHD: Shelly Dimmer...

`ShdWarmupBrightness`, `ShdWarmupTime`, and `ShdLeadingEdge` are the 3 shelly dimmer specific commands I believe. Maybe note the model number of the bulbs you are using and how many in parallel.

> … the light also switches on/off much faster now. @kratz00 Do you mean when using an external switch via the SW1 or SW2 connections? I find Tasmota sometimes takes...

> @rbswift what settings do you have in Tasmota for `SwitchDebounce` and `SetOption32`? SwitchDebounce 100. I was getting phantom switching at default 50 SetOption32 40 (default) thanks for any guidance....

I do something similar but have replaced the rocker switches with momentary, normally closed switches. PowerOnState 2 is probably what you are looking for. It's a core Tasmota feature, not...

The delay to get online typically doesn’t matter much. Toggling the light on/off is sub-second fast. A problem with a very short interruption is that it could easily be falsely...

Is it a battery powered motor? I've noticed these sometimes need a few more repeats to get them moving

Agreed. The position tracking code should ideally be seperate from the signalling code. This would need a refactor. Also as mentioned, the presumption of one channe=one motor is not always...