You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tested 2 Tasmota lights (identical vendor and model and firmware Tasmota 9.1), 1 light with through Tasmota integration and 1 light through my own MQTT light Template.
For my own MQTT template integration transitions have always worked in all variations, it is implemented like this:
{%- if transition is defined -%}
fade 1; speed {{ transition |round |int * 2 }};
{%- endif -%}
The automation descried below does a 4s transition between two light scenes with different colors. For my own integration the transition takes 4s and is very smooth. The new Tasmota integration uses a very short transition (i think shorter than 1s).
So the Problem is that the integration does not seem to use the transition time defined by the user, but something else. (I have not checked the source code of the integration.)
It would be really nice if the user define transition duration would be used so tht I could get rid of the numerous mqtt integrations for all my lights. It is a pain to maintain...
Environment
Home Assistant Core release with the issue: 0.118.0
Last working Home Assistant Core release (if known): unknown
Operating environment (OS/Container/Supervised/Core): HASS OS
Integration causing this issue: Tasmota (beta) with Tasmota 9.1 light
Hey there @emontnemery, mind taking a look at this issue as its been labeled with an integration (tasmota) you are listed as a codeowner for? Thanks! (message by CodeOwnersMention)
Home Assistant's transition is the transition time in seconds.
On the other hand, Tasmota's speed command is the number of half-seconds scaled for a 100% fade.
This means with a speed of 10, changing from dimmer from 0..100 will need 5 seconds, but changing from 50..100 will only need 2.5 seconds.
Currently HATasmota only considers brightness when converting transition to Tasmota speed color and color temperature needs to be considered as well.
The problem
Tasmota integration:
I tested 2 Tasmota lights (identical vendor and model and firmware Tasmota 9.1), 1 light with through Tasmota integration and 1 light through my own MQTT light Template.
For my own MQTT template integration transitions have always worked in all variations, it is implemented like this:
The automation descried below does a 4s transition between two light scenes with different colors. For my own integration the transition takes 4s and is very smooth. The new Tasmota integration uses a very short transition (i think shorter than 1s).
So the Problem is that the integration does not seem to use the transition time defined by the user, but something else. (I have not checked the source code of the integration.)
It would be really nice if the user define transition duration would be used so tht I could get rid of the numerous mqtt integrations for all my lights. It is a pain to maintain...
Environment
Problem-relevant
configuration.yaml
an automation to switch between 2 light scenes with different colors
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: