@joaocosme eu não estou muito por dentro dos covers mas segundo o que me enviaste por MP
cover:
- platform: mqtt
name: "insidegarage"
#POWER2 cooresponde ao switchX no ip do sonoff(neste caso, switch2 = POWER2)
state_topic: "cmnd/2/POWER2"
command_topic: "cmnd/sonoff8/POWER"
availability_topic: "tele/sonoff8/LWT"
payload_available: "Online"
payload_not_available: "Offline"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "OFF"
state_closed: "ON"
optimistic: false
retain: false
- platform: mqtt
name: "outsidegarage"
#POWER2 cooresponde ao switchX no ip do sonoff(neste caso, switch1 = POWER1)
state_topic: "cmnd/2/POWER1"
command_topic: "cmnd/sonoff11/OFF"
availability_topic: "tele/sonoff11/LWT"
payload_available: "Online"
payload_not_available: "Offline"
payload_open: "ON"
payload_close: "ON"
payload_stop: "ON"
state_open: "OFF"
state_closed: "ON"
optimistic: false
retain: false
e segundo o que eles dizem aqui:
Considerations
If you are using the state of a platform that takes extra time to load, the Template Cover may get an unknown state during startup. This results in error messages in your log file until that platform has completed loading. If you use is_state() function in your template, you can avoid this situation. For example, you would replace {{ states.switch.source.state == 'on' }} with this equivalent that returns true/false and never gives an unknown result: {{ is_state('switch.source', 'on') }}
Talvez depois o @j_assuncao quando estiver em um pc te consiga ajudar, ele tá mais dentro do assunto de configuração que eu.