Charmed Quark Systems, Ltd. - Support Forums and Community

(04-26-2018, 04:13 AM)kfly Wrote: [ -> ]Some of the lights that were working lats night are not this morning.
in the Driver screen when I set to "True" I get this pop up:

"The value couldn't be written to the field. See the logs for more info..."

From the log: (Driver Verbosity is on High)
04/26 08:02:17-CQC-PC, CQCServer, CQCDrv_Z-StickThread23
{
    CQCKit, CQCDriver_DriverBase.cpp.8540, Failed/Unknown
    An unknown exception occurred while processing the command
    Z-Stick
      <CQCServer> CIDOrb_ThisFacility.cpp - 536
      <CQCAdmin> CQCKit_CQCSrvAdminClientProxy.cpp - 1945
      <CQCAdmin> CQCAdmin_DrvMonTab.cpp - 1321

}

After more test looks like the light actually does turn off but in the Driver screen I get the above pop-up and log entry.
Good news is the lights work even though the driver screen gives a pop-up. Again it is only some lights that give the pop-up when setting True/False.
thx.

I'll look at that. BTW, something I just thought about wrt to the lock not responding to secure messages is that the driver may not be securely included. This is one of the most annoying things about Z-Wave. The inclusion process is not very tight. It an fail such that the device is included, but not securely included. If so, it will work fine, but won't be able to do secure messages.

And the only way to really make sure is to exclude it, and re-include it with tracing on, and check that it got a key. But, if you do that, most likely the driver's unit id will change, which invalidates all associations to the driver, and leaves bogus associations in all the units. Some masters will allow you to assign specific ids, but most won't, they will use the next unused id.

Can you reset the trace file and flush the logs, do the field write to cause the popup, turn off tracing, then get a log dump and the trace file? That'll help figure out what might be going on. The most likely scenario is that the unit never was able to create its unit handler object, but this will help me know better.

Another option would be to set up our port server so that I can connect to your Z-Stick from here. That would let me set exactly what is going on, and probably learn a number of other things I'm not going to ever see here in my particular setup.

The above made me realize I'd not yet implemented the remote port client and chat client in the new C++ driver test harness, which would be required for this. So I put in some time today to do that. So we could get me hooked up to your Z-Stick so that I could test some things out and see what is happening.

(04-26-2018, 11:31 AM)Dean Roddey Wrote: [ -> ]Can you reset the trace file and flush the logs, do the field write to cause the popup, turn off tracing, then get a log dump and the trace file? That'll help figure out what might be going on. The most likely scenario is that the unit never was able to create its unit handler object, but this will help me know better.

Pop up error when setting True/False in some lights:
"The Value couldn't be written to the field. See logs for more info..."

System log file:
04/27 07:14:48-CQC-PC, CQCServer, CQCDrv_Z-StickThread23
{
    CQCKit, CQCDriver_DriverBase.cpp.8540, Failed/Unknown
    An unknown exception occurred while processing the command
    Z-Stick
      <CQCServer> CIDOrb_ThisFacility.cpp - 536
      <CQCAdmin> CQCKit_CQCSrvAdminClientProxy.cpp - 1945
      <CQCAdmin> CQCAdmin_DrvMonTab.cpp - 1321

}

Trace file:
Z-Wave USB3 Trace
,  Time: 7:14:39 AM
----------------------------------------------------

07:14:48 - [TRACE]- Got bool field write. Name=LGHT#Sw_Fish_Tank_Light Value=0
07:14:48 - Sending a new msg:
{
    [DR->ZW] - (REQ,Msg: SendData/0x13,AckId=24954,CBId=167) 
    {
        TarId: 2
        Class: BinSwitch
         Cmd: Set
        Bytes: 0A 00 13 02 03 25 01 00 05 A7 
    }
}
07:14:48 - [TRACE]- Sending msg, AckId=24954, Attempt #1
07:14:48 - [TRACE]- Transitioned from Idle to WaitAck state
07:14:48 - [ZW->DR] - ACK
07:14:48 - [TRACE]- Transitioned from WaitAck to WaitCallback state
07:14:48 - [ZW->DR] - RES,Msg:SendData/0x13,Recvd: 07:14:48) 7MSs
{
    Bytes: 01 
}
07:14:48 - [ZW->DR] - TRANSACK,Msg:SendData/0x13,Recvd: 07:14:48) 17MSs
{
   Callback Id: 167
        Status: Success
    Bytes: A7 00 00 02 
}
07:14:48 - [TRACE]- Transitioned from WaitCallback to Idle state

I found a few things, but everything I found was the sort of thing that would have made the field write fail, so apparently none of those were it. Can we set up the port server? I've updated my C++ driver test harness to support the remote port server and chat, so I could do that now. We'd need to wait for the next drop that includes those changes.

(04-27-2018, 12:55 PM)Dean Roddey Wrote: [ -> ]I found a few things, but everything I found was the sort of thing that would have made the field write fail, so apparently none of those were it. Can we set up the port server? I've updated my C++ driver test harness to support the remote port server and chat, so I could do that now. We'd need to wait for the next drop that includes those changes.

Sure, After next drop will setup port server so you can get a closer look.

5.2.909 is posted. This guy has a few small tweaks, but mostly is just some improvements to the remote port server, and support for that in my new C++ driver test harness, so that I can now remote debug C++ drivers. It also adds some more security stuff to the remote port server as well, in that you can now select which serial ports you want to make available. The others won't be reported and can't be opened by the test harness.

I got started on the Z-Wave driver written documentation today. I feel like I'm writing a small book. For something that is supposed to be a simple, consumer oriented system, it's got so many gotchas. Definitely for this one it will has some associated videos, since it's just too much to write it all down in a driver doc page. The written doc page will contain the details and provide links to the videos which give a tour of the driver and how to use it and all that.

I'll hold off a bit longer on the videos in case we have to change anything. The written does are a lot easier to update.