Another Update:
I got my CT30 to a point where I’m happy with how it’s working. I ended up using the http binding rather that the specific binding. I borrowed heavily from Scot’s post #5. This solved both of my problems of the setpoint in the sitemap not updating correctly and saving the setpoint when switching between heating and cooling.
This is not at all a criticism of Eric’s work on the Radio Thermostat binding… it’s just a limitation of how the API works. You have to post updates to the a_heat/a_cool values in order for the setpoint to be retained, but the API returns the value for the setpoint as h_heat/h_cool… at least as far as I’ve been able to determine.
ETA:
Further looking through the API, there is a value for “t_type_post” Integer value that indicates whether a POST on t_heat/t_cool will result in temporary or absolute temperature change.
It is indicated a depreciated, however, and although I get a success response when attempting to set it to 1 it does not actually change.