@Wayne-TP 

lag is only between two s210 switches automations (controlled locally)

There is no lag between s200 button and s210 Switch at all.

Hub is h100, firmware is the newest: 1.5.20 build 240911 rel. 110830, signal strenght is -34 (RSSI)

Switch s210, firmware is the newest: 1.9.0 build 231106 rel. 164425, signal strength is -47 (RSSI)

Yes, my automations are locally controlled but like I said noticed lag is between two s210 switches. It's working perfectly without lag if automation is between s200 button and s210 switch.

For science I tested my s220 switch, two switches version. Left switch is turning off and on the right switch. There is a small lag, automation controlled locally.

Then I made automation between s200 button and s220 right smart switch, s200 button is turning on and off s220 right switch. There is almost no lag in that automation, controlled locally.

S220 firmware: 1.9.0 build 231106 rel. 164353, signal strength on both switches is -51 (RSSI)

S200 button firmware: 1.12.0 build 231121 rel. 092444, signal strength is -50 (RSSI)

Button and Switch are almost touching each other ;d

You can test it and you will see that automation started by s200 button are executed faster than automations started by s210 or s220 switches.

  @Wayne-TP 

oh, yes, all of these automations are labelled locally (controlled by hub)

  @Wayne-TP 

Delay between s200 and s210 is around 1 second or 1.5 second.

Delay between two s210 is around 2, 3 seconds.

I can make videos if it helps, I have few switches and few buttons, scheme is the same buttons expecting automation faster and switches slower.

For example there same delay when you control p110 socket with switch, there will be 2, 3 sec delay but if you control socket with s200 it will be executed in 1 second or less.