HVAC app address confusion

I have just started using the AMAZING Cgateweb fork by Doug Rathbone which actually supports HVAC and shutter relays etc in Home Assistant, not just lights! AND it's being actively developed, the latest update was this morning! A dream come true!

However, I'm having some issues getting HVAC control set up. I have three thermostats, only one will be used for the foreseeable future, to switch on and off a relay to turn my gas boiler on and off. His documentation references app 201 as the default, but in my setup (Toolkit 1.17.6, C-gate v3) I don't have anything on 201. The AC seems to be group 172, but the HVAC actuators are group 115 and 116.

I had assumed everything should be under a single group the same as all the lighting kit is, but it doesn't seem to be that way.

With that in mind, what group should I point Cgateweb to so I can see my thermostats and control temperature setpoints etc? The documentation isn't very clear

Thanks very much, all input appreciated.

Here's the link to the new HA plugin:
http://github.com/dougrathbone/cgateweb

 

I looked through this code and it doesn't actually support the hvac app. I think he is a bit confused. The code converts mqtt hvac commands into standard cbus ramp commands. He talks about the 5000CT2 temperature controller, but that is actually a touchscreen. My theory is that someone programmed a touchscreen to convert beteen the hvac app and lignting compatible commands (which is what do). App 201 doesn't exist but it could have been create as a lighting compatble app in the touchscreen.

Given you have a PAC, you could do the same thing then this would probably work. Just don't use app 201. Pick an app in the lighting range. How's your cbus logic programming?

Another fork of this does talk about the cbus hvac app but they say its all to hard and you have to send mqtt the actual cgate hvac commands directly which is probably harder than programming the
pac

 

Thanks mate. That's disappointing. Some HVAC actuators do actually show up in HA with this, except they are lighting. Basically I need it to look good within HA so it's easy to use for anyone that I give access to. Is there a way to have a nice dial interface in HA and then all the background stuff is done on the PAC somehow?

My coding is very weak, but learning more every day, usually asking Google Gemini to generate example code though

I will reach out to the developer and give him your feedback, he seems pretty active which is good.

 

Hey both - I maintain the CBus Home Assistant integration
https://github.com/dougrathbone/cgateweb-homeassistant

As far as I can tell i've implemented the full HVAC command set from the Cbus manual, but i don't use Cbus to control my HVAC, so i'd need more guidance and logs if something has broken?

You can try the software without home assistant just by pubsubbing to MQTT and using my base library:
https://github.com/dougrathbone/cgateweb

If you'd be open to working with me, i'd happily build out the HVAC support for you - it shouldnt be more than a few hours work.

 

Following up on this - you should be able to configure your HVAC app to run on any id, just by setting the config - read about this in the readme file here:

https://github.com/dougrathbone/cgateweb (bottom of the page)

 

Those two posts by Doug only showed up today even though they are dated 1st June.

Strange.

 

The readme actually says it doesn't suipport the Cbus HVAC native application or thermostats directly. it says that you have to program a PAC to convert the HVAC app into a lighting compatible app as I surmised above.

I've attached a PICED PAC project that does this. If your thermostat is coneected to Cbus and uses Communication Group 1 and the Unswitched zone, this project should work immediately in PICED. It has lots of comments. It allows you to create a widget on an eDLT to control the setpoint. You can also then use the above HA integration to control it. Let me know if you haver any problems with it.

 

The readme was only updated since we started on this journey I believe. Doug is working on a proper solution for all of this, I'm sending him logs etc.