4.3 Beta Discussion Thread

[Dean Roddey]

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?

[jkish]

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.

[Dean Roddey]

What are some examples?

[jkish]

Originally Posted by Dean Roddey

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
}

[Dean Roddey]

Oh, OK, during the initial phase and in the old USB driver. I'll take a look at it.

[Dean Roddey]

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]

This guy is closed now. A new thread is opened for the post-4.3 release cycle.