+- Charmed Quark Systems, Ltd. - Support Forums and Community (https://www.charmedquark.com/vb_forums)
+-- Forum: General Discussion (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=3)
+--- Forum: Beta Discussions (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=12)
+--- Thread: Official 5.3 Beta Discussion Thread (/showthread.php?tid=10397)
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 07-02-2018
The trace demonstrates what I mentioned before. You apparently changed the driver moniker, so it lost the security key. It's waiting for the master to securely include it, but the master won't because it thinks it is already securely included. So you will have to either go back to the original moniker, or do the steps above.
If you are periodically getting the error about the client service, then you still have network issues of some sort presumably. The fact that it's not consistently either happening or not happening is not a good sign, and something commonly associated with the 1803 issue. You might have to add the local machine's own name to address mapping to the hosts file.
You don't do any associations, the driver does that when it ids a unit. It sends out auto-config stuff when it ids the the unit successfully. Those will be lost when you exclude and re-include the driver since the Z-Stick will get a new id. But, going with the steps above, the driver will try to id all the units again from scratch and should send out new auto-config msgs for the ones it id's.
RE: Official 5.3 Beta Discussion Thread - IVB - 07-02-2018
(07-02-2018, 11:34 AM)Dean Roddey Wrote: BTW, if you want to completely remove the Z-Wave driver under its current name, then get rid of the ISY, then re-add the Z-Wave driver under the Lighting name, that could be done. You just have to go about it correctly. You will need to do an exclude on the driver to remove it from the Z-Wave network. Then unload the driver from CQC. Then go to the same directory as the trace file above and delete the configuration file that should be there. Then re-add the driver under the new moniker. It will be starting again from scratch and should do the full secure inclusion and re-id all of the units. You will have to make sure any battery powered ones get woken up so that they can get id'd if possible and any setup for the id'd ones gets sent.
okay trying this. Need to run out of the house for 30 minutes, biab
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 07-02-2018
(07-02-2018, 11:35 AM)IVB Wrote:(07-02-2018, 11:30 AM)Dean Roddey Wrote:(07-02-2018, 11:28 AM)IVB Wrote: This is the weird thing. I'd be happy to delete it from my network if I could figure out how to do that without actually going to the unit to do an exclude, it's only used during the winter for xmas lights and is deep in the crawlspace.
https://www.amazon.com/Aeon-Labs-DSC06106-ZWUS-Z-Wave-Energy/dp/B007UZH7B8?ie=UTF8&psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00
I'm not sure what we mean here? Do you suspect this unit is an issue or something?
This is something 99% of people don't have, so if the problem is something not seen before, this could be the device. RFIT even says "unknown device"
Maybe it could be. But let's get the above issues straightened out first. Then we can get another trace and see if maybe that unit shows up in the trace in a way that makes it suspect. It could be something else altogether.
But, if you don't want to remove it, nothing to do but go push the button ultimately.
RE: Official 5.3 Beta Discussion Thread - IVB - 07-02-2018
(07-02-2018, 11:38 AM)IVB Wrote:(07-02-2018, 11:34 AM)Dean Roddey Wrote: BTW, if you want to completely remove the Z-Wave driver under its current name, then get rid of the ISY, then re-add the Z-Wave driver under the Lighting name, that could be done. You just have to go about it correctly. You will need to do an exclude on the driver to remove it from the Z-Wave network. Then unload the driver from CQC. Then go to the same directory as the trace file above and delete the configuration file that should be there. Then re-add the driver under the new moniker. It will be starting again from scratch and should do the full secure inclusion and re-id all of the units. You will have to make sure any battery powered ones get woken up so that they can get id'd if possible and any setup for the id'd ones gets sent.
okay trying this. Need to run out of the house for 30 minutes, biab
Hmm. Some progress. I
A) excluded device in RFIT with the current driver name.
B) dropped driver, recreated driver with the name I want (lighting)
C) excluded it
D) included it
It initially showed replication success, with all devices showing. It seemed to be going through to determine what each were, then within 30 seconds I can now only see 1 of the 30 devices.
I'll be back in 30 minutes, will see if the rest showed up then.
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 07-02-2018
It can take a while to complete the process. The more iffy the comms the longer it can take. And of course for battery powered units you have to go force them to talk to the driver so that it can set them up, as per the Z-Wave driver videos/written docs, which go into why that is.
RE: Official 5.3 Beta Discussion Thread - IVB - 07-02-2018
Hmm. Just back, and the driver still only shows a single field whereas immediately upon replication it showed all 30 for about a minute.
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 07-02-2018
It will only show fields for units that have been ID'd reached WaitApprove state and then you have to use the Options menu top approve them. Until that happens they won't show up. So bring up the client interface for the driver and see what the status of the units are.
RE: Official 5.3 Beta Discussion Thread - IVB - 07-02-2018
Sorry, not speaking clearly. In the client interface, where every device is shown with the various states, only one is there now.
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 07-02-2018
OK, some something must have failed in the replication. So start the trace (reset if already enabled), do another replication, then stop the trace and post the output. Let's see what happened. And, just in case, again do the regular logs with the driver in verbose during the replication as well, in case something caused an exception or some such. You've definitely got something weird going on.
RE: Official 5.3 Beta Discussion Thread - IVB - 07-02-2018
Of course, I decided to try scrubbing and redoing again, then doing trace & logs so you see the whole thing. And of course it's working now. Mostly.  Attaching trace anyway.
I'm also attaching 2 of the query info's for 4 device types not currently in the system. I couldn't get one for the VRCS2 & VRCZ4 for the following reasons:
Quote:could  not get version for CC association(VRCS2 & VRCZ4)
could not get version for CC BinSwitch (VRCS2)