Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Question on CQC Driver Pack Install
#1
I had originally built a driver, which I then updated to a new version, along with updated manifest showing the new version number.  When I build the new driver pack, and then installed, the AI still shows the original version number, even with a CQC App Shell recycle or Server reboot.  If you go to "Add New Driver", the only option is the new version.  

I can reconfig the driver and it will change the version number, and from what I can tell, that is the only way to update the information.  

The new driver pack overwrites the original version's manifest and command file , and the new version's enhancements are included, but the info shows it to be a previous version (unless you reconfig).   Bug possibly?
Reply
#2
That's to be expected, though it is a bit inconsistent. The manifest info (and the user input it generated) is stored as the driver configuration. It doesn't get reset just because you install a newer version. But the CML has to be seen since it's replaced what was there before. So it sees the code but not the manifest (if you pause/resume or restart both of which cause the driver to load the code again.) It's only when you do a reconfigure that the new manifest and old stored away info are merged and you are allowed to provide info for any new prompts and such (and possibly new fixed prompts behind the scenes.)

During upgrade that same process is done, since it kind of has to be, but any new prompts are just defaulted until such time as you reconfigure since that's the only way to enter that info.

So it's a bit messy, but that's the way it currently works. Normally, the only time drivers get upgraded is during a system upgrade. Any time I give someone a driver pack I tell them to install and reconfigure, which gets everything caught up. Most of the time the driver is running and would have to be reconfigured also just to see the new CML. But if you restart the driver or system, without a reconfig then the CML is seen but not the new manifest info.
Dean Roddey
Explorans limites defectum
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  New V2 Nest driver Dean Roddey 92 14,476 01-06-2020, 05:09 PM
Last Post: keepersg
  Lutron RadioRA2 Driver and Lutron Visor Control gReatAutomation 28 1,550 12-10-2019, 03:45 PM
Last Post: Dean Roddey
  Triggered Event on Timer Question znelbok 7 300 12-09-2019, 02:10 PM
Last Post: znelbok
  Possible Bug - Lutron RadioRA2 Driver and Thermostat gReatAutomation 39 2,296 11-13-2019, 03:57 PM
Last Post: Dean Roddey
  "Stay Awake" in Denon driver? George M 7 499 10-25-2019, 07:58 AM
Last Post: Bugman
  Serialization of CQC SMS Serial Interface Driver gReatAutomation 52 2,745 09-21-2019, 12:59 PM
Last Post: gReatAutomation
  Atlona Driver? cavalier240 5 521 09-16-2019, 01:29 PM
Last Post: Dean Roddey
  HTTP Trigger Driver - see trained URL's? Shaky 1 216 09-15-2019, 12:25 PM
Last Post: Dean Roddey
  Spotify driver for CQC? znelbok 1 276 09-03-2019, 04:08 PM
Last Post: Dean Roddey
  SONOS Driver Question gReatAutomation 13 986 08-23-2019, 12:37 PM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)