Open joaomruas opened 4 years ago
That's strange... I don't have this problem here. Did you check your MQTT device log to see if there are any extra state reports?
(tu fala português?)
Falo, mas sou de Portugal. Estranho, precisava de saber que funcionava, pode ser do meu sistema... Vou ver. Uso SmartIR + Tasmota.
Tu podias tentar usar o evento que é acionado sempre que a entidade é atualizada pra checar se essa mudança vem da integração mesmo.
Faz uma automação com mqtt_climate_sync_state_changed
como trigger e chama algum serviço do domínio notify
pra tu conseguir “debugar”
Same here. After a few seconds, it turns back to previous state. See screenshot below: the "turned off" state don't know where it appeared from, it wasn't triggered from the remote.
It looks like SmartIR wants to keep it in previous state perhaps? But note that actual turn off command wasn't sent out neither by remote nor by SmartIR.
@nagyrobi maybe you could try to create an automation with the mqtt_climate_sync_state_changed
event and see where the changes are coming from. I'll take a look at SmartIR code to try to figure out what's happening, but, for me, it works fine.
@joaomruas @nagyrobi have you ever tried to use the Tasmota-IRHVAC component? It handles IR messages natively and is way better than SmartIR with MQTT.
didn't try yet. But I will...
I tried with Tasmota-IRHVAC. MQTT-Climate-Sync diesn't work at all with it. I am using vendor GREE commands.
Tasmota-IRHVAC is not bad actually, but lacks some flexibility I was able to receive using SmartIR.
Making a hass state set on a SmartIR Climate entity appears to be only a temporary change.
Because less than one minute later the climate entity will be externally updated with the previous state.
Does this implementation work?