Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ISY driver repeatedly losing connection
#1
I recently updated to 4.8.5 and now basically have the ISY driver useless. Any even that attempts to turn on a light seems to just get an error that the driver is disconnected.


Code:
09/06 12:18:05-, CQCServer, CIDOrbSrvWorkThread_2
{
    CQCKit, CQCDriver_DriverBase.cpp.1446, Failed/Not Ready, Error: 906/0/0
    Driver 'ISY' is not currently connected to its device
      <CQCServer> CIDOrb_ThisFacility.cpp - 536
      <CQCEventSrv> CQCKit_CQCSrvAdminClientProxy.cpp - 679
      <CQCEventSrv> CQCKit_StdCmdTargets.cpp - 179

}


Looking at other logging, I see this:
Code:
09/06 12:17:57-CQC, CQCServer, CQCDrv_ISYThread14
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Insteon.ISY_V2.DriverImpl.1632, Status/App Status
    Event read error. Error=Lost event connection
}
09/06 12:17:57-CQC, CQCServer, CQCDrv_ISYThread14
{
    CQCGenDrvS, MEng.System.CQC.Drivers.Insteon.ISY_V2.DriverImpl.239, Status/App Status
    Failed to connect. Error=Lost event connection
}
09/06 12:17:57-CQC, CQCServer, CQCDrv_ISYThread14
{
    CQCKit, CQCDriver_DriverBase.cpp.7207, Status/Lost Connection
    Driver 'ISY' has lost its communcations resource
}
09/06 12:18:02-CQC, CQCServer, CQCDrv_ISYThread14
{
    CQCKit, CQCDriver_DriverBase.cpp.3447, Status/App Status
    Driver 'ISY' is trying to get its comm resource
}
09/06 12:18:02-CQC, CQCServer, CQCDrv_ISYThread14
{
    CQCKit, CQCDriver_DriverBase.cpp.3486, Status/App Status
    Driver 'ISY' has its comm resource
}
09/06 12:18:02-CQC, CQCServer, CQCDrv_ISYThread14
{
    CQCKit, CQCDriver_DriverBase.cpp.3504, Status/App Status
    Driver 'ISY' is trying to connect to its device
}
Reply
#2
There was some change in the ISY firmware at some point, right? I seem to remember that we needed to make some changes for that and 4.8.5 would include those changes if I'm remembering rightly. Are you on the latest ISY firmware? Well, not the latest, latest as in their recent beta thingy, but the latest official release.
Dean Roddey
Explorans limites defectum
Reply
#3
Apparently I was not on latest. Updating now and will reply back later today to see if its working better...
Reply
#4
Nope, no better today. Still see a number of these errors in the logs about the driver not connected to its device.
Reply
#5
Is this with verbose logging on? If not, can you flush the logs, turn on verbose logging for the driver, give it a little time, then kill the verbose logging and get me a log dump?
Dean Roddey
Explorans limites defectum
Reply
#6
Dean Roddey Wrote:Is this with verbose logging on? If not, can you flush the logs, turn on verbose logging for the driver, give it a little time, then kill the verbose logging and get me a log dump?

Looks like it had reset back to non-verbose. I just restarted CQC completely, flushed logs and will see behavior for a bit...

I did notice that within there I saw an error about an invalid field name and an exception causing it to fail to write the value to that field. Possible that the error there would cause driver to disconnect but still show as connected in the Admin interface?
Reply
#7
The error in the example above is due to a read error on the event connection, which is how the ISY reports changes to the driver. It's like it got something it didn't understand.
Dean Roddey
Explorans limites defectum
Reply
#8
Any info? BTW, worst case, you can open it up so that I can connect to it and see what's going on, as long as it's something that will happen within some reasonable period of time.
Dean Roddey
Explorans limites defectum
Reply
#9
Sorry for delay, have a 7 month old at home so unpredectible time right now Smile

Still unreliable today. The items that are triggering it are all motion events so I can give you access and coordinate a motion trigger if it gets to that. Oddly, I don't get this when manually clicking a button in the IV to change a light. it only happens in my motion event handlers.
Reply
#10
That probably makes sense. That's an async event that will be reported from the ISY. There must be something in there that's freaking the driver out that no one else has seen. Anything unusual about the names of the motion sensors in the ISY maybe?

Anyway, let me know when you want to open it up and we can do it. Any time tomorrow is fine (after 11AM'ish eastern time, to insure I'm awake and have my caffeine pressure up to normal.)
Dean Roddey
Explorans limites defectum
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  TTS II Driver requirements znelbok 1 218 05-20-2019, 09:34 PM
Last Post: Dean Roddey
  CQC to PowerView Hub via Serial Driver Deane Johnson 18 3,501 05-14-2018, 01:11 PM
Last Post: Deane Johnson
  HAI Driver Issue avtexan 6 2,164 04-06-2018, 02:06 PM
Last Post: Dean Roddey
  Monoprice 8x8 HDMI matrix Driver NightLight 13 6,093 09-04-2017, 09:45 AM
Last Post: Dean Roddey
  ELK V2 Driver - AreaArm field & Triggers? sic0048 4 2,268 08-19-2017, 04:46 PM
Last Post: Dean Roddey
  UPB Driver Issue tcmcgec 6 3,678 01-27-2017, 07:18 PM
Last Post: Dean Roddey
  HAI OmniProII Driver problems MBurger 4 3,019 12-24-2016, 07:59 AM
Last Post: Dean Roddey
  Onkyo NR646 and Universal Integra Driver? Sendero 6 3,418 10-31-2016, 11:22 PM
Last Post: Sendero
  Train HTTP Trigger Driver jkmonroe 24 10,026 10-25-2016, 11:55 AM
Last Post: karenlee
  EventGhost alternatives to getting driver/field *TO* SmartPhone? IVB 37 9,559 08-13-2016, 07:32 PM
Last Post: IVB

Forum Jump:


Users browsing this thread: 1 Guest(s)