I notice that when Stringify tells my TP-Link LB100 WiFi dimmer bulb to turn on at 1% brightness, it actually flashes briefly to 100% brightness and then drops to 1% (ouch! that hurts when I'm waking up!). The bulb is set to turn on at 100% brightness by default, so clearly Stringify is sending two commands, i.e., "turn on" and then "set brightness to 1%".
I tested and verified that this only happens with Stringify. IFTTT does not do this, nor does Google Home nor TP-Link's Kasa app.
Since the TP-Link support is still labeled "beta", I hope this is a bug that could be fixed?
The workaround is to set the bulb to turn on at 1% by default in the Kasa settings, but it means that every time I tell Google Home to turn it on, I have to add "at 100%".