Closed SeeeeebDe closed 1 year ago
Hey there @emontnemery, @jbouwh, mind taking a look at this issue as it has been labeled with an integration (mqtt
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
mqtt documentation mqtt source (message by IssueLinks)
@SeeeeebDe Not sure what your problem is, I tried your config, and from that it seems possible to turn on and off the climate using mode_command_topic
. Also if the state is received correctly via mode_state_topic. So I do not quite see what your problem is. At least this does not seems an issue with MQTT.
Hello Jan,
Thank you for helping.
I manage to operate some state changes using the widget buttons, but the issue is that the two buttons « flame » and « power » used to be reversible and to work independently one from each other, but it seems now to be linked : one turns off and the other turns on. Each button is no more reversible. And this is not compliant with HomeKit.
The state is set by the mode_state_stopic, what payload indicate an off or heat state? Are these sent after the mode command heat or off are sent?
If the state is correctly set, it also should work with HomeKit
Let me know if MQTT is working okay for you. I cannot discover an issue. Is this only an issue with HomeKit?
Sorry I’ve not been really available. Yes mqtt works fine. I still manage turning heating on and off with the « chauffage jacuzzi » switch (both ok in HA and HomeKit)
This is the Climate entity that doesn’t work properly (both in the card in my HA dashboard and in HomeKit).
Okay, i am going to close this one as it seems I cannot do much here. At least it does not seem that there is an issue with MQTT.
But Climate entity is part of mosquito mqtt integration, right ? When I said mqtt works fine, I was talking about mqtt communication (every other commands still works). only the climate entity has been affected
Not sure what you mean. There is nothing wrong with the climate entity. I suggest you have a look at the power_command_topic option. I assume Homekit will call service climate.turn_on or climate.turn_offf. Awake your MQTT climate using the power command topic, after that the climate should report back it's current mode. See also the MQTT release notes on the breaking changes. https://www.home-assistant.io/blog/2023/07/05/release-20237/#breaking-changes
The problem
Hello all,
I just started having troubles after the last core update 2023.7 with the climate object.
I searched a while about what could have changed and just discovered this change : if I understand well the power_command_topic is no more used and the mode_command_topic must be used instead.
I try different configurations with no satisfying results.
In HA, now the flame button of the climate widget turns the heater on and the power buttons turns it off. With some change on the mode_command_template, it could also behave inversely (flame turns off and power turn on).
But in both case none of these two buttons could turns on and then off by it self.
The main issue is that this breaks the HomeKit integration that works with one button only, that is now frozen.
Anyone you knows of a fix could be brought ? Any update to connect it again correctly with HomeKit ?
What version of Home Assistant Core has the issue?
2023.7.1
What was the last working version of Home Assistant Core?
2023.6
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Mosquito Mqtt
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
No response