Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums

(Advanced Search)

Forum Statistics
» Members: 17
» Latest member: TobiasCelve
» Forum threads: 13
» Forum posts: 18

Full Statistics

Online Users
There is currently 1 user online
» 0 Member(s) | 1 Guest(s)

Latest Threads
RainMachine Sprinkler Irr...
Forum: Driver Development
Last Post: kfly
05-18-2024, 02:42 PM
» Replies: 1
» Views: 72
My Z-wave migration to Ho...
Forum: CQC Community Support for CQC-based automation systems.
Last Post: Shaky
02-24-2024, 03:16 AM
» Replies: 3
» Views: 158
NightLight's CQC System ....
Forum: User Systems
Last Post: kfly
02-09-2024, 12:51 PM
» Replies: 1
» Views: 49
Archive of old CQC forum ...
Forum: CQC Community Support for CQC-based automation systems.
Last Post: admin
02-08-2024, 01:45 PM
» Replies: 0
» Views: 52
CQC Emotional Support Gro...
Forum: CQC Community Support for CQC-based automation systems.
Last Post: NightLight
02-07-2024, 09:05 PM
» Replies: 0
» Views: 43
HomeAssistant Rest API te...
Forum: Driver Development
Last Post: kfly
01-27-2024, 05:01 PM
» Replies: 0
» Views: 108
OpenWeatherMap JSON Weath...
Forum: Driver Development
Last Post: kblagron
01-18-2024, 12:01 PM
» Replies: 0
» Views: 14
OpenWeatherMap JSON Weath...
Forum: Driver Development
Last Post: kblagron
01-18-2024, 11:57 AM
» Replies: 0
» Views: 9
CQC on Github
Forum: CQC Installation files
Last Post: admin
01-15-2024, 12:26 AM
» Replies: 0
» Views: 33
Archive of CQC CQCInst fi...
Forum: CQC Installation files
Last Post: admin
01-15-2024, 12:10 AM
» Replies: 0
» Views: 55

 
  Archive of old CQC forum on the Internet Archive
Posted by: admin - 02-08-2024, 01:45 PM - Forum: CQC Community Support for CQC-based automation systems. - No Replies

Maybe helpful to dig through the Archive and find solutions or copy helpful articles to new community site.
https://web.archive.org/web/202306051548...vb_forums/

Print this item

Photo NightLight's CQC System .. still runs flawlessly
Posted by: NightLight - 02-07-2024, 09:16 PM - Forum: User Systems - Replies (1)

I'd love to find something that I could replace CQC. There simply is nothing that ticks all the boxes. Still the best damn Windows software I use today. Ill add templates and photos as soon as I figure out where to host the images. Thanks for keeping this alive guys!! Heart

CQC4ever

Print this item

  CQC Emotional Support Group!
Posted by: NightLight - 02-07-2024, 09:05 PM - Forum: CQC Community Support for CQC-based automation systems. - No Replies

I'm glad to see I found some of my CQC peeps..

Heart Heart Heart Heart

Print this item

  My Z-wave migration to Home Assistant
Posted by: kfly - 02-03-2024, 05:13 PM - Forum: CQC Community Support for CQC-based automation systems. - Replies (3)

Just finished moving from CQC/Smartthings to Home assistant with CQC as the front end.
CQC seems to work just fine including as a secondary controller on the Home Assistant Z-wave network.

My zwave setup:
Home Assistant(Yellow):
Zooz 700 Series Z-Wave Plus S2 USB Stick ZST10
 
CQC:
Aeotec Z-Stick Gen5, Z-Wave Plus USB
 
I had to migrate 40+ Z-wave devices including lights, blinds, etc.
So after migration and you will just need to in CQC:

  • Do an include/exclude for the CQC Zwave stick to join the HA new Zwave network.
  • rescan each unit on the zwave driver client interface and also update names with new unit id's
  • Obviously leave the device names in CQC the same as you will need to rename each device as the device ID’s will change on the new Z-wave network.
  • I couldn’t get my locks to work after migration on CQC so moved them to the new HA CQC rest Polling Driver in CQC(Schlage  BE469).
 
Since you need to correlate the CQC ID to the HA ID(not sure why you cannot see the Zwave ID in HA) 
Just run this template once in Home Assistant and print out. Will give you all the device names and ID’s. Then just go in CQC and rename starting at device 2,3,4,5,etc. (see below)
I have noticed a bug/feature in CQC that if the device is already named and there is no longer a device at that ID you cannot rename:
  • Manual set the device type and then do an approve all.
  • Then change name and do a save.
 
 
HA template (in developer tools) to list device_id and names:
https://community.home-assistant.io/t/ad...ces/374502
 
{% set ns = namespace(devices=[]) %}
{%- for device_id in states | map(attribute='entity_id') | map('device_id') | unique | reject('eq', none) %}
{%- set identifiers = device_attr(device_id, 'identifiers') | list | selectattr('0', 'eq', 'zwave_js') | selectattr('1', 'search', '^([0-9]+)-([0-9]+)$') | list | first | default %}
{%- if identifiers %}
  {%- set node = identifiers[-1].split('-')[-1] | int %}
  {%- set ns.devices = ns.devices + [(node, device_entities(device_id))] %}
{%- endif %}
{%- endfor %}
{%- for node, entities in ns.devices | sort(attribute='0') %}
{{ node }}:
{%- for entity in entities %}
- {{ entity }}
{%- endfor %}
{% endfor %}


Very happy my CQC touchscreens work great with HA and any new devices or other HA devices(zigby,etc) can be access via the Rest API Home assistant driver in CQC.
Good luck
Kevin

Print this item

  HomeAssistant Rest API test Driver
Posted by: kfly - 01-27-2024, 05:01 PM - Forum: Driver Development - No Replies

Looks like Home Assistant Rest API works pretty good with CQC and should help those of use that need to add a few unsupported devices to CQC.

As everyone knows there is no other HA system out that compares to the configurability of the GUI interface you get from CQC. So why not just let HomeAssistant poll the device and CQC can lookup state/attributes from HA.

Here is a first cut of a test driver.
Driver install prompts:
1. HomeAssistant Long-lived access token (see below)
2. Polling Interval (default is 5 seconds)
3. HomeAssistant Hub IP address example: 192.168.1.1
4. List of HomeAssistant Entities to be polled (see format below)


.zip   HomeAssistant_0.2.zip (Size: 31.44 KB / Downloads: 3)

Note:

  • It polls the local HomeAssistant Hub.
  • It does one small "state" poll for each device at poll time. (so keep it to a small number of devices not supported by CQC)
  • Driver creates fields based on HomeAssistant entity names that are specified to poll  at driver configuration.
  • HA can report locks in strange states(jammed,unkown,etc) in this case the lock will be set to false(unlocked) just like the HA app does.
  • CQC has a 8 second HTTPost timer and HA seems to have a very rare 40 second timeout(when unplugging z-wave devices, HA seems to pend all post requests for up to 40 seconds until HA sets that status again). I have only seen it on sending commands to locks. guess HA pends on the lock to finish unlocking/locking,etc. In this case driver will increment the $LostConn field in the driver status screen. 
After a few weeks of testing. Seems to work well at 5 seconds poll times.

You need to Generate a Long-lived access token(Personal Access Token)
Home assistant -> "your profile" -> Long-lived access tokens
https://community.home-assistant.io/t/ho...cess-token


Devices to Poll:
Format is  Entity ID  in HomeAssistant (example below)
Home assistant -> Settings -> Devices & services -> Entities

example:
light.scene_capable_plug_in_dimmer,light.sengled_solar_light,switch.ktest_appliance_switch,lock.front_door_lock,sensor.workshop_flood_sensor_air_temperature,binary_sensor.workshop_flood_sensor_water_leak_detected


Please feel free to fix, enhance or change driver as needed.
    maybe:
  • enhance Lights to do color light fields
  • Add more device types as I only added light, lock, switch, and sensors.(or a more elegant lookup table of some kind)
  • Sensor should work for any sensors and binary_sensors as they are just text fields.

Obviously the Rest API Driver is not intended for a bunch of devices/entities/sensors. The "http://{{hass_url}}/api/states/{entity ID}" poll  is pretty small and efficient. unlike the smartthings hub where you hand to pull a ton of capabilities and parse out.

One major change from smartthings api is all commands to HomeAssistant are done by calling a Service "http://{{hass_url}}/api/services/light/" instead of just calling the device(smartthings) or EntityID(HomeAssistant) and setting the attributes.


I see no reason someone couldn't write a cool websockets driver so we can migrate all our CQC devices to HomeAssistant and still use CQC as the GUI frontend.

https://developers.home-assistant.io/docs/api/websocket

Print this item

  OpenWeatherMap JSON Weather Driver (V2 Compatible)
Posted by: kblagron - 01-18-2024, 12:01 PM - Forum: Driver Development - No Replies

OpenWeatherMap.org released an API (named OneCall) that provides current weather information based on your lat/long along with 8 days of forecast data in JSON format.  It allows 1000 calls per day to the free account that you will have to set up on their website (which is the same API key that the shipped OWM driver used).

This version is V2 Compatible, but there is another version available that uses the fields from the old Weather / Weather Underground / DarkSky drivers.  This version does not have as many additional fields and nor any weather alerts, so unless you are just stuck on the V2 functionality, the other driver would be the recommended one to use.

.cqcdrvpack   OpenWeatherMapJSON V0.92.CQCDrvPack (Size: 14.02 KB / Downloads: 0)
.docx   OWM-JSON V0.92 Documentation.docx (Size: 22.12 KB / Downloads: 0)

Print this item

  OpenWeatherMap JSON Weather Driver (Old Fields)
Posted by: kblagron - 01-18-2024, 11:57 AM - Forum: Driver Development - No Replies

OpenWeatherMap.org released an API (named OneCall) that provides current weather information based on your lat/long along with 8 days of forecast data in JSON format.  It allows 1000 calls per day to the free account that you will have to set up on their website (which is the same API key that the shipped OWM driver used).

This version is backward compatible with the old Weather, Weather Underground, and DarkSky driver fields, but their is another version is available that is V2 compatible.  This version has many additional fields and weather alerts, so unless you are just stuck on the V2 functionality, this driver would be the one to use.

.cqcdrvpack   OpenWeatherMapJSON1.0 V0.51.CQCDrvPack (Size: 15.62 KB / Downloads: 0)
.html   OWM-JSON1.0 V0.51 Documentation.html (Size: 26.76 KB / Downloads: 0)

Print this item

  CQC on Github
Posted by: admin - 01-15-2024, 12:26 AM - Forum: CQC Installation files - No Replies

https://github.com/DeanRoddey/CQC?

License

Both CQC and CIDLib are available under the MIT open source license.

https://opensource.org/licenses/MIT

Print this item

  Archive of CQC CQCInst files
Posted by: admin - 01-15-2024, 12:10 AM - Forum: CQC Installation files - No Replies

Click on below link to download:


.zip   CQCInstSE_6_0_7.zip (Size: 39.45 MB / Downloads: 5)

.zip   CQCInstSE_6_0_1.zip (Size: 39.26 MB / Downloads: 1)

.zip   CQCInstSE_6_0_0.zip (Size: 39.31 MB / Downloads: 2)

Print this item

  Solar Assistant - MQTT
Posted by: kfly - 01-13-2024, 05:19 PM - Forum: Driver Development - No Replies

I know its not really a driver since it uses MQTT. But hay this really isn't supported by me either Smile.

[Image: eqcX5P0.png]

https://solar-assistant.io/



Overview
This is a very special driver in that it actually allows you to create 'pseudo fields' whose values are

1. Import the attached template into CQC admin screen(File/Tools/Import packages)
2. Start the MQTT Broker in the Solar Assistant device config screen.
3. Install CQC MQTT Driver and name the Moniker:  “SolarAssistant”
4. Edit the Config file as per your inverter setup:
5. Install CQC  LogicSrv driver and add the 3 fields and source fields(to calculate percentages for the real time gauges)
6. Create/Edit MQTT config file for data to be accessed by CQC
“C:\Program Files (x86)\CQC\CQCData\Server\Data\MQTT\SolarAssistant”


.zip   SolarAssistantV1.zip (Size: 816.8 KB / Downloads: 0)


To add 3 fields to the LogicSrv Configuration screen (to hold calculation for gauges)
Of course my Inverter is a 3K invert you should change 3000 to match your inverter so gauges are  correct.(note Since there is no gauge widget had to make images – 10% 20% 30%,etc)

Defined Fields Source Fields Formula
BatteryPowerPercent SolarAssistant.BatteryPower 10 *  %(1) / 3000
GridPowerPercent SolarAssistant.GridPower 10 *  %(1) / 3000
LoadPowerPercent SolarAssistant.LoadPower 10 *  %(1) / 3000

My MQTT  Config file:
(highly recommend downloading and running MQTT Explorer software  to get your fields for config file)
C:\Program Files (x86)\CQC\CQCData\Server\Data\MQTT\SolarAssistant
<?xml version="1.0" encoding="US-ASCII"?>
        <!DOCTYPE MQTTCfg PUBLIC "urn:charmedquark.com:CQC-MQTTCfg.DTD" "CQCMQTTCfg.DTD">
        <MQTTCfg Version="1" MQTTPort="1883" MQTTAddr="192.168.2.191">

            <Fields>

                <Generic Topic="solar_assistant/inverter_1/load_power/state" BaseName="LoadPower" Access="R" FldType="Card" >
                      <PLFmt Type="BinText"/>
                </Generic>

                <Generic Topic="solar_assistant/inverter_1/grid_power/state" BaseName="GridPower" Access="R" FldType="Card" >
                      <PLFmt Type="BinText"/>
                </Generic>

                <Generic Topic="solar_assistant/inverter_1/grid_voltage/state" BaseName="GridVoltage" Access="R" FldType="Float" >
                      <PLFmt Type="BinText"/>
                </Generic>

                <Generic Topic="solar_assistant/inverter_1/pv_power/state" BaseName="PvPower" Access="R" FldType="Card" >
                      <PLFmt Type="BinText"/>
                </Generic>

                <Generic Topic="solar_assistant/total/battery_state_of_charge/state" BaseName="BatteryStateOfCharge" Access="R" FldType="Card" >
                      <PLFmt Type="BinText"/>
                </Generic>

                <Generic Topic="solar_assistant/total/battery_power/state" BaseName="BatteryPower" Access="R" FldType="Int" >
                      <PLFmt Type="BinText"/>
                </Generic>

                <Generic Topic="solar_assistant/inverter_1/battery_current/state" BaseName="BatteryCurrent" Access="R" FldType="Float" >
                      <PLFmt Type="BinText"/>
                </Generic>

                <Generic Topic="solar_assistant/inverter_1/battery_voltage/state" BaseName="BatteryVoltage" Access="R" FldType="Float" >
                      <PLFmt Type="BinText"/>
                </Generic>

                <Generic Topic="solar_assistant/inverter_1/device_mode/state" BaseName="DeviceMode" Access="R" FldType="String" >
                      <PLFmt Type="BinText"/>
                </Generic>
               
            </Fields>

        </MQTTCfg>

Print this item