This is a issue with new app version. I think
Do not change the driver, the bulb you change will stop working until you pair again.
Tomorrow I will see the logs, but what I saw yesterday does not seem to have to do with the driver and with the fact that the device does not execute the received command.
Have you tried a different bulb?
Try to start at a higher % level 5%, 10% for progressive on.
test with > 7 sec transition time.
For this to work well the device has to have a variable frequency electronics driver to be able to adjust the transition times to different ranges of level increase.
If you put a short time 3 sec, for a high level range, 1% to 100%, your device hardware may not be able to adapt the frequency of the dimmer’s PCM modulator.
In this the quality of the hardware of the bulbs matters.
The tests I do with an OSRAM work very well, however TUYA bulbs are not able to work with transition times, the price is something!
The Zigbee specification for the transition time says that it will comply with the time sent in the command as tightly as the device can.
In this most up-to-date documentation I have seen that the units to be sent are tenths of a sec.
The documentation that I used when I made this part of the driver did not say this so clearly and it was the result of trial and error. The driver is sending times that are almost half the correct ones.
I will modify it by multiplying the value in preferences by 10, instead of multiplying by 6 now
device:send(zcl_clusters.Level.commands.MoveToLevelWithOnOff(device, math.floor(on_Level/100.0 * 254), math.floor((device.preferences.levelTransTime * 10))))
I will also set a higher limit of 10 sec, it can be set up to 6553 sec. as long as the device supports it.
I leave it for today