Replies: 4 comments
-
|
Please, try |
Beta Was this translation helpful? Give feedback.
-
|
Haven't touched the Tasmota integration before since automatic discovery under MQTT worked flawlessly for me but gave it a try for this specific issue. Unfortunately this doesn't solve the issue. |
Beta Was this translation helpful? Give feedback.
-
|
Are there any updates on this? Would be really for switching between especially clock scheme and so on |
Beta Was this translation helpful? Give feedback.
-
|
Sooo... It's been a while. Is there a workaround or sth we can use? |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
PROBLEM DESCRIPTION
A clear and concise description of what the problem is.
When using WS2812 addressable LED-strips in combination with the Home Assistant automatic discovery (SetOption19) the effect list (schemes) in Home Assistant is the one for non-addressable LED strips (only scheme 0 to 4, instead of scheme 0 to 12).
REQUESTED INFORMATION
Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!
Backlog Template; Module; GPIO 255:Backlog Rule1; Rule2; Rule3:Status 0:weblogto 4 and then, when you experience your issue, provide the output of the Console log:TO REPRODUCE
Steps to reproduce the behavior:
EXPECTED BEHAVIOUR
A clear and concise description of what you expected to happen.
I expect the following message to be submitted to the MQTT server under "homeassistant/light/9F74BF_LI_1/config".
{"name":"Tasmota","stat_t":"tele/tasmota_9F74BF/STATE","avty_t":"tele/tasmota_9F74BF/LWT","pl_avail":"Online","pl_not_avail":"Offline","cmd_t":"cmnd/tasmota_9F74BF/POWER","val_tpl":"{{value_json.POWER}}","pl_off":"OFF","pl_on":"ON","uniq_id":"9F74BF_LI_1","dev":{"ids":["9F74BF"]},"bri_cmd_t":"cmnd/tasmota_9F74BF/Dimmer","bri_stat_t":"tele/tasmota_9F74BF/STATE","bri_scl":100,"on_cmd_type":"brightness","bri_val_tpl":"{{value_json.Dimmer}}","rgb_cmd_t":"cmnd/tasmota_9F74BF/Color2","rgb_stat_t":"tele/tasmota_9F74BF/STATE","rgb_val_tpl":"{{value_json.Color.split(',')[0:3]|join(',')}}","fx_cmd_t":"cmnd/tasmota_9F74BF/Scheme","fx_stat_t":"tele/tasmota_9F74BF/STATE","fx_val_tpl":"{{value_json.Scheme}}","fx_list":["0","1","2","3","4","5","6","7","8","9","10","11","12"]}CURRENT BEHAVIOUR
A clear and concise description of what is currently happening.
Ehe following message is submitted to the MQTT server under "homeassistant/light/9F74BF_LI_1/config".
{"name":"Tasmota","stat_t":"tele/tasmota_9F74BF/STATE","avty_t":"tele/tasmota_9F74BF/LWT","pl_avail":"Online","pl_not_avail":"Offline","cmd_t":"cmnd/tasmota_9F74BF/POWER","val_tpl":"{{value_json.POWER}}","pl_off":"OFF","pl_on":"ON","uniq_id":"9F74BF_LI_1","dev":{"ids":["9F74BF"]},"bri_cmd_t":"cmnd/tasmota_9F74BF/Dimmer","bri_stat_t":"tele/tasmota_9F74BF/STATE","bri_scl":100,"on_cmd_type":"brightness","bri_val_tpl":"{{value_json.Dimmer}}","rgb_cmd_t":"cmnd/tasmota_9F74BF/Color2","rgb_stat_t":"tele/tasmota_9F74BF/STATE","rgb_val_tpl":"{{value_json.Color.split(',')[0:3]|join(',')}}","fx_cmd_t":"cmnd/tasmota_9F74BF/Scheme","fx_stat_t":"tele/tasmota_9F74BF/STATE","fx_val_tpl":"{{value_json.Scheme}}","fx_list":["0","1","2","3","4"]}SCREENSHOTS
If applicable, add screenshots to help explain your problem.
See EXPECTED BEHAVIOUR and CURRENT BEHAVIOUR.
ADDITIONAL CONTEXT
Add any other context about the problem here.
Beta Was this translation helpful? Give feedback.
All reactions