11-22-2017, 05:00 PM (This post was last modified: 11-22-2017, 05:01 PM by Dean Roddey.)
Do you mean Lutron HWQS? If so, that should still be a V1 driver. Which driver did you load exactly? You may have loaded the RA2 driver, which I guess is maybe compatible with the HWQS? If so, there is also still a V1 version of that as well that you could use.
If you WANT to upgrade to the V2 version, and there are advantages to that, you can do it. All the V2 drivers are based on a set of device classes, to provide standardized access to particular types of functionality. In the HTML help you can go to:
/More Details/Drivers & Fields/V2 Drivers
That describes how V2 drivers work. It also includes a link to the reference material where the device classes are defined. The bit before the # is the device class prefix. In some cases, where a single device class supports more than one type of field (such as switches vs. dimmers) it may also add a prefix to the field name itself, such as Sw_ or Dim_ to differentiate the type.
The configuration file format is the same. You just provide the base part of the name, and the correct field name will be built up from that. If you use the old V1 version, it will be the old style names that the original driver used. If you use the V2 driver you get V2 compliant names.
This is a screenshot of my current driver. I have not changed in recently nor in years.
It is possible that I am on some odd in-between release that was not common since I was early with HWQS and I may have paid you for some custom work. I can't remember.
My actual Lutron system is HWQS. It seems that it is the RA2 driver.
I guess there is no compelling reason to upgrade to V2 for me (I won't use auto-generate). That's fine.
So, refined questions:
1. Am I on the right driver (version or dot release), or is there a need to upgrade?
2. WHY did you add v2 field prefixes to my v1 driver and mess everything up :-)    ?
It looks like you are on the V1 driver. The RA2 driver should be compatible with the HWQS system. The same driver is actually used for both V1 and V2 modes. It's just a flag in the driver manifest file that tells it which mode to run.
The model showing up in the capture above is showing RadioRA2-IP, which is the model for the V1 driver. But, it looks like you are using some non-standard version of it it, because it's showing 1.7, when the latest version if 3.0. So I'm guessing that the manifest file you have is really causing the driver to run in V2 mode.
So, do this... Look at:
[cqc]\CQCData\DataServer\Manifests\User
and see if there is a manifest file in there that indicates it is for Radio RA2 (the name should make it obvious.) If so, zip that up and e-mail it to me so that I can take a look at it.
BTW, from the info you are running the regular driver. So I'm guessing it's just the manifest file itself that's the issue. You might try:
1. Unload the driver
2. Go to the above mentioned directory and rename the manifest file (assuming it's there) or move it somewhere.
3. Restart the MS service. That should cause it to drop the previously loaded manifest info
4. Reload the driver, which should make it pick up the current manifest
See if that takes care of it. The unit configuration is in a file so that won't be affected by unloading and reloading the driver.
BTW, in #2 above, you would need to change the extension or move it out. If you just rename it but keep the .Manifest extension, it will still be loaded. The file name itself doesn't matter, just the make/model inside it.
Hmmm... I just tried it and I get V1 fields. So something strange is going on. Do you get prefixes for dimmers, thermos, etc...? All of those should have V2 prefixes if the driver is running in V2 mode.