Universal Devices ISY Insteon Driver

[wuench]

ISY Insteon Driver (V1) - Version 2.0

Description:

This driver controls the Universal Devices ISY Insteon Lighting controllers. As this driver is based on the ISY Web Services 1.0 standard, at least version 2.6.6 of the firmware is required on the ISY device.

Release Info

Version 1.0

• Original Version - tested with firmware 2.6.6 and 2.6.13

Version 1.1

• Added configurable timeout for commands

Version 1.2 - tested with firmware 2.7 (Release) and 2.7.15 (Release)

• Fixed bug with OnLevel/RampRate not showing
  
• Adjust GetNodes Timeout to support large networks
  
• Reset Subscription on Reload (to get updated status)

Version 1.3

• Reinit Event Subscription on Reload
  
• WSDL 2.0 Support
  
• Filtering of NodesUpdated Events - Less reloading

Version 1.4

• User Action/Load Events Added
  
• Get/Set ISY Variables
  
• Allow Thermostat fields for all climate devices
  
• CQC Standard Lighting Fields Support

Version 1.5

• Ignore 404 Errors when Getting Variables (No Variables Configured)
  
• AutoDebugmode On LogLev=High Upon Restart
  
• Additional Logging (BuildCmd)
  
• Fixed Device Category in Manifest

Version 1.6

• Thermostat SP/Status Fixes
  
• VariableStatus Event on Variable Changes
  
• Reload On Unknown Variable Status Event
  

Version 1.7

• Thermostat Fixes
  

Version 1.8

• Fix In/Out Issue w/CQC 4.2.906+
  

Version 1.9

• Automatic Reload on BuildCmd Errors
  

Version 2.0

• Updated to POST subscription method (support for firmware 4.x+)
  

Troubleshooting:
If possible please post a debug log of your issue if you are experiencing problems. To create a debug log, set the DebugMode field to True while the problem is occurring. This will create a log file on the machine running the driver under Program Files\CQC\CQCData\MacroFileRoot\Logs. Then zip the file and post it with your problem.

Available in CQC 4.2.922+

See the attached HTML file for additional information...

[SomeWhatLost]

couple of questions:
would this driver be a replacement for the PLM driver?
how does the isy work? does it have a better signal/whatever then the PLM?
would this solve my problem of not being able to read the status of a switch in CQC?

[wuench]

couple of questions:
would this driver be a replacement for the PLM driver?
how does the isy work? does it have a better signal/whatever then the PLM?
would this solve my problem of not being able to read the status of a switch in CQC?

The ISY uses a PLM. So I doubt you will see any better signal etc, unless maybe because you can move the ISY/PLM away from the PC. The ISY is basically a mini-controller with ENET and PLM ports. It becomes your centralized controller and it can be controlled via ENET by the ElkM1 and CQC so no need for multiple PLMs.

[sreev]

Problem 1 (probably will help resolve Problem 2): The HTML link in wuench's first posting is not working for me.
http://www.charmedquark.com/vb_forum//at...1224072605

Problem 2: I tried to add the ISY driver - it seems to be hanging at "Wait for Comm Resource". I can't see any fields for ISY to add to my screens.

I'm hoping that someone can help. I have 6 days left on my CQC trial. Being able to control Insteon with ISY will be a big factor in my decision to buy.

[SomeWhatLost]

the link works fine for me, and your link to the link works fine too...
*EDIT*: Doh!, I hate when people just say "it works fine for me"... it's of absolutely no help... and it's annoying... and I just did it to you, sorry about that...

as far as "Wait for Comm Resource" that usually means CQC could not get access to the enet port on the PC that it need to talk to the isy... do you have something running that is tying up that port?

are you sure your running the isy driver and not the PLM driver? (I know, it's a stupid question, but I am running out of insightful ones)

here are the relevant bits from the instruction HTML:
Driver Configuration

* Username - Enter a valid username for your ISY device.
* Password - Enter a valid password for your ISY device.
* MyURL - The driver has the capability to discover the address and configuration locations of the ISY device using Universal Plug and Play. To use UPnP leave this blank. If you do not wish to use UPnP to discover the ISY controller, you can alternatively enter the ISY's URL here. This can be found on the Admin console's Help/About menu.

Connection Details

The ISY uses UPnP broadcasts to announce it's location to the network (UDP port 1900). Commands are sent using Web Services to a Control URL using HTTP POST commands and an Event Subscription connection to a second URL is used to communicate events to clients asynchronously. The Event Subscription uses keepalives to keep the connection open, if no event traffic is seen on the subscription socket after 40 seconds the driver is reloaded.

[wuench]

Yeah, the links work for me too. Not sure what's up there. Maybe your browser is blocking it somehow.

What version of firmware are you on? Version 1.0 of the ISY driver was tested on 2.6.6 firmware which was the latest at the time, it will not work with 2.6.5 and below. BTW, 2.6.6 does have a bug where access via CQC and the web interface will lock up every few weeks and require a poweron/off of the ISY to get it back up. I have run into this myself.

They are up to firmware 2.6.12 and version 1.0 of the driver hasn't been tested with these, they are recommending to wait for 2.6.13 as 2.6.12 also has a bug with web services which the driver uses. YMMV with later versions. I need to upgrade my ISY and test it, but it looks like there aren't any good candidate versions at this time. They all have a lot of bugs. They are working their way up to a 2.7 production release, hopefully beta 2.6.13 will be a good candidate for that.

If anyone has used a different version of firmware and has any feedback please let me know.

[sreev]

Thank you both very much for your prompt replies. I tried the link in IE and it works (still doesn't work from Google Chrome - strange)! Sorry about that.

I bought the ISY-99i IR/PRO just a week ago from SmartHome and it still has v.2.6.5. I am surprised at this because I just saw that your first post from July refers to 2.6.6. I will try to upgrade the firmware and see if it helps. I will report back.

Thanks again!

[sreev]

That was it. I upgraded the ISY firmware to 2.6.11 (12 is in beta) and it immediately connected. Thank you so much.

Smarthome sold me old stock then. I hope firmware is the only difference.

[wuench]

All 2.6.x releases are beta. The only production versions are 1.0 and the upcoming 2.7. If they ever release it.

[daddyd]

I give up, I need some help, I have been pulling my hair out trying to get my isy99ir connected to CQC. The following is an excerpt from the log:


01/18 12:49:55-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, CQCKit_DriverBase.cpp.2582, Status/App Status
Driver 'isy' is trying to get its comm resource
}
01/18 12:49:55-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
GetCommRes: Bound to TCP Port 2343
}
01/18 12:49:55-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
GetCommRes: Location URL(Manually Set):http://192.168.0.194/desc
}
01/18 12:49:55-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
SetupFields: Getting URLs.
}
01/18 12:49:55-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
GetURLs: ISY Address: 192.168.0.194:80
}
01/18 12:49:55-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
GetURLs: Base URL: http://192.168.0.194
}
01/18 12:49:55-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
GetURLs: Control URL: http://192.168.0.194/services
}
01/18 12:49:55-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
GetURLs: Event URL: /eventing
}
01/18 12:49:55-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
SetupFields: Authenticating
}
01/18 12:49:55-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
Send: Auth Response:200 - SOAP OK
}
01/18 12:49:55-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
SetupFields: Getting ISY Configuration
}
01/18 12:49:55-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
Send: GetConf Response:200 - SOAP OK
}
01/18 12:49:56-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
ParseResp: ISY Model:ISY 99i 1024 IR Firmware:2.6.13
}
01/18 12:49:56-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.114, Status/App Status
SetupFields: Getting ISY Nodes
}
01/18 12:49:57-DOWNLOADS, CQCServer, CQCDrv_isy_Thread3
{
CQCKit, MEng.System.CQC.Runtime.CQCLogger.108, Status/App Status
Send Exception: No reply to HTTP GET/POST request
}

It just keeps repeating this over and over. Any thoughts?