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
  ClickPLC driver now failing after upgrade znelbok 2 84 09-21-2020, 10:48 PM
Last Post: znelbok
  Pentair driver tom 5 657 08-02-2020, 11:29 PM
Last Post: kblagron
  Marantz receiver driver (IP) dlmorgan999 6 584 05-15-2020, 03:32 PM
Last Post: dlmorgan999
  V2 Question - OpenWeatherMap Using their New JSON Data Feed kblagron 7 741 05-07-2020, 01:40 PM
Last Post: Dean Roddey
  Variables Driver Client gReatAutomation 4 502 04-25-2020, 12:46 PM
Last Post: gReatAutomation
  Dynamic Overlay Question bryanb 4 413 04-17-2020, 03:48 AM
Last Post: bryanb
  Reconfig of Driver Causes Built In Triggers to Fire gReatAutomation 2 399 03-25-2020, 04:09 PM
Last Post: gReatAutomation
  Lutron RadioRA2 Driver and Lutron Visor Control gReatAutomation 29 5,529 03-19-2020, 01:03 PM
Last Post: gReatAutomation
  Timers Driver / Field Time Image / Seconds gReatAutomation 1 380 03-16-2020, 05:48 PM
Last Post: Dean Roddey
  Problem with Accesssing Variables Driver Client Interface kblagron 5 736 03-05-2020, 02:24 PM
Last Post: kblagron

Forum Jump:


Users browsing this thread: 1 Guest(s)