Charmed Quark Systems, Ltd. - Support Forums and Community

Full Version: Insteon Driver: Name?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
In spite of the "Subject" line, I found the Insteon driver.

But I've also got something that I suspect is a template and which might get me started on setting up a screen around a few Insteon modules.

Specifically "HTPC Lighting Overlay.CQCTmplPack"

Am I on the right track?

If so, does anybody know of something more recent?

I tried CQC Admin Interface | Administer | Import Package, but it popped a "This package is not valid for this version of CQC" message.

CQC Admin Interface Version 3.0.2
EDIT - there is already an Insteon driver included in the main CQC release. This means you don't have to download the driver - it is already loaded in your system.

If you needed to download and install a driver, this is how you would do it..... Download that file somewhere and then use the CQC Admin Interface program. To top left menu item is "Administer" - then use the "Load Package" under that. Point it at the downloaded driver pack and it will load it into CQC. Then load the driver into your system by using the "Server Management" choice under the same drop down menu. Select the computer you want to load the driver on and then use the "Load Driver" option.

That is the quick down and dirty - but you probably want to watch the Tutorial Videos that Dean has created. They are located under the Support area of the main website. There is one specifically about Loading Drivers, but they are all good.
There've been a few spots over time where we've had to change the format of things such that packs created from previous versions can't be imported, unfortunately. So that one probably was created in a previous version that has crossed one of those invalidation boundaries. So you won't be able to import it into 3.x.
Dean Roddey Wrote:There've been a few spots over time where we've had to change the format of things such that packs created from previous versions can't be imported, unfortunately. So that one probably was created in a previous version that has crossed one of those invalidation boundaries. So you won't be able to import it into 3.x.

But I was on the right track with CQC Admin Interface | Administer | Import Package, right?

i.e. That menu choice is appropriate for both importing drivers and importing templates? (I'm assuming that a "Template" is a set of pre-coded controls that can be copied/modified once they are in the application's DB).
Yes - that is the correct proceedure and it works for both template and driver packs.
It works for all package types, which all includes image and macro packs.
Are there any code snip examples to be had?

I'm thinking for the Insteon PowerLinc USB controller driver - the plain vanilla one that uses (SDM?).

Also, tangentially, when I am in Interface Editor is there any way to bring up the interface I'm working on to test it? Or do I have to exit the editor and bring up Interface Viewer every time I want to test some changes?

Or is there a middle path.... something where both remain open and I hop back-and-forth?
Just save what you are working on, flip over to the viewer and do a reload (Ctrl-R) to reload it and see what you just saved.
Hop back and forth between the two. As Dean mentioned, make sure you save the changes in the Interface Editor. Then you have to reload the template in the Interface Viewer to force it to go and reload the template so it can see the changes.

If you make changes and reload the template in the interface viewer and nothing has changed, it is usually because you forgot to save the template in the interface editor. I forget to do this regularly. :-)
[QUOTE=PeteCress]Are there any code snip examples to be had?

I'm thinking for the Insteon PowerLinc USB controller driver - the plain vanilla one that uses (SDM?).
[QUOTE]

If you download some of the user templates that people are sharing, they will have the command logic programmed into their templates. This can help to see how things are done sometimes. But I cannot think of any that use the Insteon PowerLink USB Controller offhand.

But it also comes at a price. If the templates have devices that are not included in your setup (or if you have named your driver something different than the downloaded template), then all those effected commands will be commented out and it can be hard to understand what they were trying to accomplish.

If this happens, you'll get a warning that certain devices were not found and therefore commented out. I'll usually cancel out of the changes and reopen the widget. You can click on the action tab and see the command logic in the window. As long as you don't try to edit the command logic, it won't comment out those effected lines. So you can still read through the logic.

Some people are better about adding comments to their action structure to help in determining why they wrote the action as they did. Others don't add any comments, so it can be rather difficult to understand why they did certain things the way they did.
Pages: 1 2