Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: An Idea - CQC as Front End for Home Assistant
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Because of the decline in CQC and I have a of of devices that are now not connected to CQC and I need to integrate somehow, I was unfortunately forced to look at Home Assistant.

Things like Tuya, Modbus, and many other mainstream integrations exist in HA that we really should have had in CQC.

People talk about how great it is, but honestly, CQC is far better with only the lack of drivers being its biggest issue right now.

So this got me thinking, HA has an API, so if we could build a driver for CQC to talk to HA, we could then use CQC as a graphical front end to HA, and this could breath some new life into CQC.

Keep all the drivers there, so something not in HA can be covered in CQC, and just add the HA drivers and auto import all fields from HA.

Any thoughts on this as an idea - I am still learning HA (2 days into it), and I still prefer my CQC by a long way so far.

(04-26-2022, 01:49 PM)znelbok Wrote: [ -> ]So this got me thinking, HA has an API, so if we could build a driver for CQC to talk to HA, we could then use CQC as a graphical front end to HA, and this could breath some new life into CQC.


Was in same position. CQC still best and most flexible front end GUI. I kludged together a CQC driver to access the SmartThings Hub API and let it control all the devices that are no longer controllable by CQC.
CQC has a really good IDE and lots of driver examples. 
If you  can get a couple commands from the API  to work in postman "" creating a driver in CQC is not that hard(just poll every x seconds).   Creating a more elegant driver with the features you suggested would probably be in the paid work category (Dean?)

Best of luck on your Home Automation journey.
While I'm not currently unable to automate any new devices without CQC, I can see this coming up soon and was also looking at what else is out there.  Coming to the same conclusions as you guys.  I can't see myself setting CQC aside. It's still great and what I want to use but I'll need to address the lack of new drivers likely ever being available sometime.  CQC has been a huge part of my hobby life and I'm having a hard time coming to grips with it going away.

I've only ever edited a driver in CQC but don't have the skill/desire/time to write a driver (or multiple drivers) from scratch currently. HA seems to be quite active and can talk to a lot of different things from what I could see, but the UI/way you interact with it doesn't interest me as much for what I am used to. (Haven't actually installed it though).

Your idea is interesting for sure.  Actually the SmartThings driver idea is very similar.  Both could be great to breath some more longevity to CQC.  Count me as  interested in your thoughts as you explore HA a bit further and feasibility of a driver.  At some point I'd be willing to install it too, or maybe buy a SmartThings (or both).  

As a simple hack, I've been using IFTTT for a couple newer devices to get status into CQC and have a google home and speaker tied to CQC in a closet that gets text to speech commands to do things via CQC for now... not how I want to continue to pseudo automate things.
I agree on doing what we can to make sure this continues to work down the road as much as we can as we use it everyday in our house. I don't know anything about HA, so can't really comment.

I was very hesitant writing drivers for CQC even though I had coded in Fortran and C back in the 80's and 90's for technical applications for my company. Since there are so many drivers that have been written, it was much easier than I thought to grab one as a template, and then work through the coding for a driver. The ones I did were simple JSON retrieval, but I wouldn't be scared now to attempt a serial or ethernet driver.