Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
4.3 Beta Discussion Thread
I checked and it looks like DriverReady is already correctly catching the error and should only log it if the verbosity is cranked up, so it shouldn't be logging anything, and I'm not seeing anything logged when I run it with a non-existent or disconnected driver. You don't have verbose logging set in the environment or something do you?
Dean Roddey
Explorans limites defectum
I'm seeing a lot of ZWave debugging entries in the log.

I think some of them were there before the latest Beta I got, but I wondered if they should be there at all.
What are some examples?
Dean Roddey
Explorans limites defectum
Dean Roddey Wrote:What are some examples?

04/20 20:50:27-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.92, Status/App Status
ZWDebug: 8 units were reported available
}
04/20 20:50:27-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.120, Status/App Status
ZWDebug: Existing unit verification phase starting...
}
04/20 20:50:27-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.125, Status/App Status
ZWDebug: Verifying existing unit with id: 7
}
04/20 20:50:27-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.161, Status/App Status
ZWDebug: BaseType=3, GenType=10, SpecType=10
}
04/20 20:50:27-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.125, Status/App Status
ZWDebug: Verifying existing unit with id: 4
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.161, Status/App Status
ZWDebug: BaseType=3, GenType=11, SpecType=11
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.125, Status/App Status
ZWDebug: Verifying existing unit with id: 2
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.161, Status/App Status
ZWDebug: BaseType=3, GenType=10, SpecType=10
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.125, Status/App Status
ZWDebug: Verifying existing unit with id: 6
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.161, Status/App Status
ZWDebug: BaseType=3, GenType=11, SpecType=11
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.125, Status/App Status
ZWDebug: Verifying existing unit with id: 5
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.161, Status/App Status
ZWDebug: BaseType=3, GenType=10, SpecType=10
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.125, Status/App Status
ZWDebug: Verifying existing unit with id: 1
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.161, Status/App Status
ZWDebug: BaseType=3, GenType=10, SpecType=10
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.125, Status/App Status
ZWDebug: Verifying existing unit with id: 3
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.161, Status/App Status
ZWDebug: BaseType=3, GenType=10, SpecType=10
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.125, Status/App Status
ZWDebug: Verifying existing unit with id: 16
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.161, Status/App Status
ZWDebug: BaseType=3, GenType=10, SpecType=10
}
04/20 20:50:28-automation2, CQCServer, CQCDrv_ZWaveThread28
{
ZWaveUSBS, ZWaveUSBS_DriverImpl3.cpp.238, Status/App Status
ZWDebug: Existing unit verification phase completed
}
Oh, OK, during the initial phase and in the old USB driver. I'll take a look at it.
Dean Roddey
Explorans limites defectum
That issue should be dealt with for 4.3. Let me know if not. I'm doing last minute testing and updating of the web site(s) content in preparation for the 4.3 release. I'll probably post it tomorrow.
Dean Roddey
Explorans limites defectum
This guy is closed now. A new thread is opened for the post-4.3 release cycle.
Dean Roddey
Explorans limites defectum


Possibly Related Threads...
Thread Author Replies Views Last Post
  Official 5.4 Beta Discussion Thread Dean Roddey 441 41,754 06-15-2019, 02:33 AM
Last Post: Bugman
  Official 5.4 Beta Release Thread Dean Roddey 55 7,322 06-07-2019, 07:02 PM
Last Post: Dean Roddey
  Official 5.3 Beta Discussion Thread Dean Roddey 815 151,300 07-05-2018, 12:44 PM
Last Post: Dean Roddey
  Official 5.3 Release Thread Dean Roddey 27 7,910 07-05-2018, 12:44 PM
Last Post: Dean Roddey
  Official 5.2 Beta Discussion Thread Dean Roddey 244 87,644 10-14-2017, 07:57 PM
Last Post: Dean Roddey
  Official 5.2 Beta Release Thread Dean Roddey 13 8,804 10-09-2017, 06:49 PM
Last Post: Dean Roddey
  Official 5.1 Beta Discussion Thread Dean Roddey 453 197,129 05-16-2017, 03:45 PM
Last Post: Dean Roddey
  Official 5.1 Beta Release Thread Dean Roddey 28 19,502 05-12-2017, 05:44 PM
Last Post: Dean Roddey
  Official 5.0 Beta Discussions Dean Roddey 2,019 489,144 11-09-2016, 04:34 PM
Last Post: Dean Roddey
  Official 5.0 Beta Release Thread Dean Roddey 15 13,314 11-01-2016, 10:32 AM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)