Charmed Quark Systems, Ltd. - Support Forums and Community

We still definitely need to figure out the locks.

My Yale locks appear to be working fine with the latest driver. I can lock / unlock and have correct battery status. To load the new driver, I followed posted instructions to unload the old driver, delete the config file and then reload with the new driver.

Should I expect any of the battery powered devices to fill in correctly (they haven't, driver has been loaded for almost 24 hours) or do I need to wake them up and do something? What is the procedure?

Battery power feedback is based on the device waking up and sending that info out once in a while. There may be some configuration parameter we don't know about so far that needs to be set to make it do that. What specific models are involved? I'm assuming here that you mean you see a battery field, but it is just set to 0? Or do you mean it doesn't have a battery field? Lots of devices don't support the battery CC, so there's no way to get that info. It's not required for battery powered devices or anything.

My Yale lock doesn't seem to so far have ever sent out a battery report either. I'm guessing we have to enable it with some config parameter, but there's none listed for it that seems to be for such a thing.

I guess maybe for locks it doesn't send it out and we have to read it periodically. I'll try that. There's no information for any of this stuff so it's all guess work.

I found info on the Yale locks and you are supposed to poll the battery level, it doesn't send it out periodically. I updated those guys to indicate that is required, but mine sure doesn't seem to be responding to the queries. It's responding to the door lock state, so the communication is good.

BTW, I had to remove my Z-Stick from the network and re-add it in order to get the lock to start responding. Not sure what's up with that. And, after re-adding of course the id changed and that invalidates all of the associations already set. There's no way to get that right again without deleting the config file. I guess I need to an 'auto-config all' type option or something.

Well, it did eventually respond to a battery query. I think it has something to do with sending a query to the lock before it has sent out the response to the last one. That shouldn't be a problem. As long as the msg has been transmitted, that's all that counts. It doesn't respond initially because the battery life query goes out along with the door lock state. Later, when it does the slow ping, it responds to that since they are more spread out by that point.

I got a bunch more fixes in today. I'll get another drop up tomorrow. We may be getting pretty close here.

(05-13-2018, 09:08 AM)Dean Roddey Wrote: [ -> ]Battery power feedback is based on the device waking up and sending that info out once in a while. There may be some configuration parameter we don't know about so far that needs to be set to make it do that. What specific models are involved? I'm assuming here that you mean you see a battery field, but it is just set to 0? Or do you mean it doesn't have a battery field? Lots of devices don't support the battery CC, so there's no way to get that info. It's not required for battery powered devices or anything.

My Yale lock doesn't seem to so far have ever sent out a battery report either. I'm guessing we have to enable it with some config parameter, but there's none listed for it that seems to be for such a thing.

I guess maybe for locks it doesn't send it out and we have to read it periodically. I'll try that. There's no information for any of this stuff so it's all guess work.

My Yale locks are reporting battery status.  I wonder if that is a function of the master hub which in my case is SmartThings?

If you were responding to my original question about the battery powered devices then I am confused. None of the door, motion or multi-function sensors that I sent you MFG info on are filling in.  For example the garage door tilt sensor which was filling in before you re-swizzled everything is no longer doing so.

I did not have to remove and rejoin the zwave stick in order to have the line powered devices or the battery powered Yale locks show up, they came right up when the driver loaded and went through it's initial startup process.

The only reason they wouldn't report is because of configuration not being set or associations not being set. When I put up today's drop, though I know it's a bit of a pain to keep doing it, delete the config file and let it go from scratch. A lot of things have been fixed and let's see how it does now. It should also be faster.

OK, 5.2.912 is posted. A lot of fixes and improvements to the Z-Wave driver. Though I know it's annoying to keep doing, please delete the config file so that we can be sure we are not getting any old issues. And some device info stuff has been tweaked and we want to insure that those changes get picked up.

This one should be a bit faster on the whole. It also now will recover from you pulling out the Z-Stick and re-inserting it, which it wouldn't before. And just a number of fixes and improvements that should make it work better.

Can't seem to get the Z-Stick to come online with 5.2.912. Stuck in connecting/disconnecting.
rebooted,removed/added driver/deleted file....

Could this be related to my 2 locks I had disabled before? 
Would it help to remote into my system?

05/14 18:21:24-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CQCKit, CQCDriver_DriverBase.cpp.3689, Status/App Status
    Driver 'Z-Stick' is trying to get its comm resource
}
05/14 18:21:24-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CIDComm, CIDComm_Port.cpp.205, Failed/Lost Connection, Error: 5013/0/0
    Write failed on /Local/COM8. Port Err: {None}
      <CQCServer> ZWaveUSB3S_ZStick.cpp - 157

}
05/14 18:21:29-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CQCKit, CQCDriver_DriverBase.cpp.3689, Status/App Status
    Driver 'Z-Stick' is trying to get its comm resource
}
05/14 18:21:29-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CIDComm, CIDComm_Port.cpp.205, Failed/Lost Connection, Error: 5013/0/0
    Write failed on /Local/COM8. Port Err: {None}
      <CQCServer> ZWaveUSB3S_ZStick.cpp - 157

}
05/14 18:21:34-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CQCKit, CQCDriver_DriverBase.cpp.3689, Status/App Status
    Driver 'Z-Stick' is trying to get its comm resource
}
05/14 18:21:34-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CIDComm, CIDComm_Port.cpp.205, Failed/Lost Connection, Error: 5013/0/0
    Write failed on /Local/COM8. Port Err: {None}
      <CQCServer> ZWaveUSB3S_ZStick.cpp - 157

}
05/14 18:21:39-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CQCKit, CQCDriver_DriverBase.cpp.3689, Status/App Status
    Driver 'Z-Stick' is trying to get its comm resource
}
05/14 18:21:39-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CIDComm, CIDComm_Port.cpp.205, Failed/Lost Connection, Error: 5013/0/0
    Write failed on /Local/COM8. Port Err: {None}
      <CQCServer> ZWaveUSB3S_ZStick.cpp - 157

}
05/14 18:21:44-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CQCKit, CQCDriver_DriverBase.cpp.3689, Status/App Status
    Driver 'Z-Stick' is trying to get its comm resource
}
05/14 18:21:44-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CIDComm, CIDComm_Port.cpp.205, Failed/Lost Connection, Error: 5013/0/0
    Write failed on /Local/COM8. Port Err: {None}
      <CQCServer> ZWaveUSB3S_ZStick.cpp - 157

}
05/14 18:21:49-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CQCKit, CQCDriver_DriverBase.cpp.3689, Status/App Status
    Driver 'Z-Stick' is trying to get its comm resource
}
05/14 18:21:49-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CQCKit, CQCDriver_DriverBase.cpp.3728, Status/App Status
    Driver 'Z-Stick' has its comm resource
}
05/14 18:21:49-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CQCKit, CQCDriver_DriverBase.cpp.3746, Status/App Status
    Driver 'Z-Stick' is trying to connect to its device
}
05/14 18:21:51-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CQCKit, CQCDriver_DriverBase.cpp.3788, Status/App Status
    Driver 'Z-Stick' has connected to its device
}
05/14 18:21:52-CQC-PC, CQCServer, ZWIOThreadZ-Stick
{
    CIDComm, CIDComm_Port.cpp.205, Failed/Lost Connection, Error: 5013/0/0
    Write failed on /Local/COM8. Port Err: {None}
      <CQCServer> ZWaveUSB3S_ZStick.cpp - 1662

}
05/14 18:21:52-CQC-PC, CQCServer, ZWIOThreadZ-Stick
{
    ZWaveUSB3S, ZWaveUSB3S_ZStick.cpp.1668, Failed/App Status
    An exception occurred in the I/O thread, restarting it
}
05/14 18:21:52-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CQCKit, CQCDriver_DriverBase.cpp.7511, Status/Lost Connection
    Driver 'Z-Stick' has lost connection to it's device
}
05/14 18:21:52-CQC-PC, CQCServer, CQCDrv_Z-StickThread27
{
    CQCKit, CQCDriver_DriverBase.cpp.7545, Status/Lost Connection
    Driver 'Z-Stick' has lost its communcations resource
}