No support for thermostats with separate topics for heat/cool setpoints

[phrz]

setTargetTemperature and getTargetTemperature are mandatory keys for a MQTTThing thermostat accessory in Homebridge, but my thermostat (exposed by ZWave2MQTT) has separate setpoint temperature topics for heating and cooling. There is no single topic that I can get/set to control temperature irrespective of the thermostat's mode.

In short, I have the four following topics:

• zwave/Hallway/Thermostat/thermostat_setpoint/cooling_1
• zwave/Hallway/Thermostat/thermostat_setpoint/cooling_1/set
• zwave/Hallway/Thermostat/thermostat_setpoint/heating_1
• zwave/Hallway/Thermostat/thermostat_setpoint/heating_1/set

Is it at all possible for MQTTThing to allow for this situation? Instead of only requiring getTargetTemperature and getTargetTemperature, it could look for those keys, but if they are not found, it could allow for fallback keys getTargetHeatingTemperature, getTargetCoolingTemperature, et cetera. I really don't know how to make my thermostat work with this tool otherwise.

The only particularly major modification would be that MQTTThing would have to know which pair of topics (heating or cooling) to get and set depending on the current mode (heating or cooling).

[jonathanware]

I'm in the same boat with my thermostat.

[phrz]

Since I could not get past this issue, I ended up ditching Homebridge for my Z-Wave devices. The Zwave2mqtt folks are focusing on ZwaveJS2mqtt as its successor, which I switched to. That has support for Home Assistant autodiscovery, so I didn't have to write a big JSON file of devices, and my thermostat worked flawlessly.

That's just a suggestion to anyone who is stuck with this problem; I certainly appreciate this project, and I will keep this issue open so that the problem can be known.