02-02-2020, 05:35 PM (This post was last modified: 02-02-2020, 05:52 PM by simplextech.)
Beta 912
- ISYv2 Driver looks like it's having connection issues again?
LostCommRes: 89
LostConn: 37
Just noticed this when I started looking around after a light failed to turn on like it normally had been. I installed 912 this afternoon after you posted it and restarted the system to have all counters fresh and clean so this is all new from today.
I just put the driver in Medium verbosity to see if I get anything in the logs.
[EDIT] Here's some log data. FYI I can generate this at-will by opening the ISY Admin Console. Shortly after opening the Admin Console the driver loses connection and can't reconnect until a couple minutes AFTER I close the Admin Console. This is odd. I know the Admin Console uses the SOAP connection but multiple connections are supported.
This is repeated constantly as the driver is trying to reconnect.
Code:
02/02 20:46:29-CQC-Prime, CQCServer, CQCDrv_ISY-PrimeThread10
{
CQCGenDrvS, MEng.System.CQC.Drivers.Insteon.ISY_V2.DriverImpl.759, Status/App Status
Error sending SOAP command GetNodeProps. Error=Got HTTP error 404 while POSTing URL http://192.168.1.106/services/
}
02/02 20:46:29-CQC-Prime, CQCServer, CQCDrv_ISY-PrimeThread10
{
CQCGenDrvS, MEng.System.CQC.Drivers.Insteon.ISY_V2.DriverImpl.240, Status/App Status
Failed to connect. Error=Lost event connection
}
02/02 20:46:29-CQC-Prime, CQCServer, CQCDrv_ISY-PrimeThread10
{
CQCKit, CQCDriver_DriverBase.cpp.7650, Status/Lost Connection
Driver 'ISY-Prime' has lost its communcations resource
}
(02-02-2020, 05:54 PM)Dean Roddey Wrote: I'm guessing that the admin console is eating up a lot of the time of the device which is making it not respond in time.
I have no idea what all the Admin Console would be doing. I know on first load it reads the same data of all of the devices and info and caches that. It uses a SOAP subscription to watch all of the changes. After the initial loading of the Admin Console it should just sit and consume very little if not actively sending any commands or adding devices etc.
I just load the Admin Console and let it sit there and the driver just can't connect while the Admin Console is open. I close the Console and a couple minutes later the driver reconnects.
02-02-2020, 07:09 PM (This post was last modified: 02-02-2020, 08:05 PM by simplextech.)
The ISYv2 driver is continually disconnecting. It seems like on each event that comes from the ISY it drops the connection and reconnects...which means it's nearly constant.
[EDIT] things seem to have stabilized... nevermind... as I was typing this it's now gone into another reconnect cycle.....
02-03-2020, 01:29 AM (This post was last modified: 02-03-2020, 01:31 AM by kblagron.)
I am on 5.4.911 and I noticed in the Irrigation Scheduler where it displays previous run times, that the time / date formatting from previous versions were okay, this is showing the raw formatting - not the actual times. I attached a screenshot of what I am talking about. Not a big deal since I am moving away from this driver, but may affect others if it is a bug.
(02-02-2020, 07:09 PM)simplextech Wrote: The ISYv2 driver is continually disconnecting. It seems like on each event that comes from the ISY it drops the connection and reconnects...which means it's nearly constant.
[EDIT] things seem to have stabilized... nevermind... as I was typing this it's now gone into another reconnect cycle.....
Clear the logs, put it into verbose mode, let ir run for a minute, then take it back out and post the log output. Let's see what's going on. It may be that you have too much stuff running at once and it's just not able to keep up. I've seen this on Hues and Elks and Omnis, where there's a lot of stuff configured on the device plus multiple things talking to it, and it just can't keep up and stops responding in a timely manner. But let's see what the logs say.
(02-02-2020, 07:09 PM)simplextech Wrote: The ISYv2 driver is continually disconnecting. It seems like on each event that comes from the ISY it drops the connection and reconnects...which means it's nearly constant.
[EDIT] things seem to have stabilized... nevermind... as I was typing this it's now gone into another reconnect cycle.....
Clear the logs, put it into verbose mode, let ir run for a minute, then take it back out and post the log output. Let's see what's going on. It may be that you have too much stuff running at once and it's just not able to keep up. I've seen this on Hues and Elks and Omnis, where there's a lot of stuff configured on the device plus multiple things talking to it, and it just can't keep up and stops responding in a timely manner. But let's see what the logs say.
I've put it into verbose mode this morning and watching. So far everything is clean with no problems. I suspect you are correct in there was too much load going to the ISY and it was having trouble servicing multiple requests. I've reduced load to only the v2 driver and disabled the v1 driver, disabled the nodeservers I was running and I disabled the Home Assistant component as well.
- RadioRa 2 Driver
- Occupancy sensor field is created but status never updates. Separate post about this
- Pico remotes are added to the client driver but no fields are created for them. In the Event Triggers Monitor I can see the triggers for the button presses but there's no fields created so I can't create events for the button presses.
I don't think the driver creates any fields. It just sends out triggers when you press one so that you can react to it. The events are User Action type events, which is common for these types of scenarios (buttons on wall panels and such that exist just to invoke events.)
(02-04-2020, 02:05 PM)Dean Roddey Wrote: I don't think the driver creates any fields. It just sends out triggers when you press one so that you can react to it. The events are User Action type events, which is common for these types of scenarios (buttons on wall panels and such that exist just to invoke events.)
Ok so no fields just manual entry of the user action in the trigger?
