Official 5.3 Beta Discussion Thread

Official 5.3 Beta Discussion Thread - Printable Version

+- 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)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82

RE: Official 5.3 Beta Discussion Thread - kfly - 06-05-2018

Dean,
Any chance you could add to┬áthe CQC Admin Interface app, under the File menu┬á"Open┬áRecent"?. Even if you keep only 5 or 10┬árecent pages it would be helpful.

Adobe Photoshop has a good layout:

[Image: JBFXyEr.jpg]

RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 06-06-2018

OK, I've updated the Schlage lock device info for the next drop to reflect that info. Be sure to force a rescan after you upgrade to make it pick up the new device info.

RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 06-06-2018

(06-05-2018, 04:50 AM)kfly Wrote: Dean,
Any chance you could add to┬áthe CQC Admin Interface app, under the File menu┬á"Open┬áRecent"?. Even if you keep only 5 or 10┬árecent pages it would be helpful.

Adobe Photoshop has a good layout:

I'll put it on the list as something to look at for the next round.

RE: Official 5.3 Beta Discussion Thread - batwater - 06-07-2018

Dean, I had the Admin Interface "blow up" on me this morning. Here's how to recreate, open Zwave Client Interface, pause the driver, after driver is paused (or maybe while it was pausing, don't remember) close the Client Interface...

I'm investigating whether because the driver is in a constant discovery state whether that is draining my lock batteries. I came home after a business trip and my garage lock was at 0, dead, no juice. Batteries were only a week old and I know they were good, fresh out of a package. Front door lock that I replaced is exhibiting the same behavior but it is a newer generation of the lock, it was down to 40%, batteries were replaced at the same time. I've paused the driver and replaced the batteries. It's either the driver or something else, so process of elimination since this is the newest thing that has been added to my zwave network equation.

RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 06-07-2018

The driver will periodically continue to attempt to talk to the device if it's not responding. The alternative is that it can take a really long time to connect to it if anything goes wrong, since it has to wait a lot longer between retries. It's on the order of 30 seconds or so, so it shouldn't be going crazy anything. It could possibly be graduated where the interval gets longer and longer until it gets up to some fairly long period. Of course that would mean that if you then fixed it, it could be a long time before the driver would try to talk to it again. Though if you forced it to send out something like a wake-up or node info frame the driver could reset the interval back.

You can see what it's doing of course, just on the trace and leave it on for an hour or so. We can see what amount of activity is going on and how often it's talking to the locks. Once something gets to one of the final states, then it either stops being talked to at all, or if its ready it does a very slow poll on the order of ten minutes, only if it hasn't heard anything from the unit in that long for some other reason.

The ten minute ping could also be cranked up, at the cost of taking a long time to realize it's not responding.

RE: Official 5.3 Beta Discussion Thread - batwater - 06-07-2018

Understood, did you catch my info on the Admin Interface crashing?

RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 06-07-2018

Yeh, I'll check that.

RE: Official 5.3 Beta Discussion Thread - kfly - 06-08-2018

Dean,
How do I get the new z-stick controller to recognize my Leviton┬á VRCZ4-M0Z 4-Button Zone Controller (wall switch)
https://www.amazon.com/gp/product/B004KN87OE/
it doesn't respond to a query unit but I do see some packets from it in the trace(see below).
When the driver comes up it goes "Disabled" imediatly

Unit 1A is the┬áVRCZ4-M0Z

Z-Wave USB3 Trace
,┬á Time: 9:02:02 PM
----------------------------------------------------

21:02:15 - [ZW->DR] - REQ,Msg:AppUpdate/0x49,Recvd: 21:02:15)┬á
{
┬á ┬á Type: Node Info
┬á ┬á SrcId: 1A
┬á ┬á GenType: GenCtrl
┬á ┬á SpecType: 0
┬á ┬á Classes: Association 2D 7C Naming 82 PowerLev Version ManSpec 91 EF SceneAct SceneActConf
┬á ┬á Bytes: 84 1A 0F 02 01 00 85 2D 7C 77 82 73 86 72 91 EF 2B 2C┬á
}
21:02:17 - [ZW->DR] - REQ,Msg:AppUpdate/0x49,Recvd: 21:02:17) 2705MSs
{
┬á ┬á Type: Node Info
┬á ┬á SrcId: 1A
┬á ┬á GenType: GenCtrl
┬á ┬á SpecType: 0
┬á ┬á Classes: Association 2D 7C Naming 82 PowerLev Version ManSpec 91 EF SceneAct SceneActConf
┬á ┬á Bytes: 84 1A 0F 02 01 00 85 2D 7C 77 82 73 86 72 91 EF 2B 2C┬á
}

Looking here. does this help?
https://github.com/OpenZWave/open-zwave/blob/master/config/manufacturer_specific.xml
</Manufacturer>
<Manufacturer id="001d" name="Leviton">
<Product type="0702" id="0261" name="VRCZ4-M0Z 4-Button Zone Controller"/>
</Manufacturer>

RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 06-08-2018

We need to add a device info file for it. It's wall powered so just use the drop down menu on that unit to do a query unit info and save the info to a file with the make/model as the name and send it to me.

Also, in the meantime, use the drop down to bring up the manual association dialog. Associate it with the driver (group one is almost certainly what you want for something like this.) Reset the trace, then press each button once, then stop it and post the output. That will show me for sure what it sends for each button.

Presumably it sends a scene activation msg for each button, but let's make sure.

RE: Official 5.3 Beta Discussion Thread - kfly - 06-08-2018

(06-08-2018, 05:34 PM)Dean┬áRoddey Wrote: We need to add a device info file for it. It's wall powered so just use the drop down menu on that unit to do a query unit info and save the info to a file with the make/model as the name and send it to me.

Also, in the meantime, use the drop down to bring up the manual association dialog. Associate it with the driver (group one is almost certainly what you want for something like this.) Reset the trace, then press each button once, then stop it and post the output. That will show me for sure what it sends for each button.

Presumably it sends a scene activation msg for each button, but let's make sure.

"query unit" does not work. keeps saying "Could not get the version for CC Association"
Also cannot do association because unit state is always "Disabled" automatically.

Here is the trace. I pushed all four on buttons one at a time then all four off buttons.(didn't see any differences between the messges).

Z-Wave USB3 Trace
,┬á Time: 10:21:53 PM
----------------------------------------------------

22:22:05 - [ZW->DR] - REQ,Msg:AppUpdate/0x49,Recvd: 22:22:05)┬á
{
┬á ┬á Type: Node Info
┬á ┬á SrcId: 1A
┬á ┬á GenType: GenCtrl
┬á ┬á SpecType: 0
┬á ┬á Classes: Association 2D 7C Naming 82 PowerLev Version ManSpec 91 EF SceneAct SceneActConf
┬á ┬á Bytes: 84 1A 0F 02 01 00 85 2D 7C 77 82 73 86 72 91 EF 2B 2C┬á
}
22:22:13 - [ZW->DR] - REQ,Msg:AppUpdate/0x49,Recvd: 22:22:13) 7786MSs
{
┬á ┬á Type: Node Info
┬á ┬á SrcId: 1A
┬á ┬á GenType: GenCtrl
┬á ┬á SpecType: 0
┬á ┬á Classes: Association 2D 7C Naming 82 PowerLev Version ManSpec 91 EF SceneAct SceneActConf
┬á ┬á Bytes: 84 1A 0F 02 01 00 85 2D 7C 77 82 73 86 72 91 EF 2B 2C┬á
}
22:22:13 - [ZW->DR] - REQ,Msg:AppUpdate/0x49,Recvd: 22:22:13) 308MSs
{
┬á ┬á Type: Node Info
┬á ┬á SrcId: 1A
┬á ┬á GenType: GenCtrl
┬á ┬á SpecType: 0
┬á ┬á Classes: Association 2D 7C Naming 82 PowerLev Version ManSpec 91 EF SceneAct SceneActConf
┬á ┬á Bytes: 84 1A 0F 02 01 00 85 2D 7C 77 82 73 86 72 91 EF 2B 2C┬á
}
22:22:14 - [ZW->DR] - REQ,Msg:AppUpdate/0x49,Recvd: 22:22:14) 1157MSs
{
┬á ┬á Type: Node Info
┬á ┬á SrcId: 1A
┬á ┬á GenType: GenCtrl
┬á ┬á SpecType: 0
┬á ┬á Classes: Association 2D 7C Naming 82 PowerLev Version ManSpec 91 EF SceneAct SceneActConf
┬á ┬á Bytes: 84 1A 0F 02 01 00 85 2D 7C 77 82 73 86 72 91 EF 2B 2C┬á
}
22:22:14 - [ZW->DR] - REQ,Msg:AppUpdate/0x49,Recvd: 22:22:14) 224MSs
{
┬á ┬á Type: Node Info
┬á ┬á SrcId: 1A
┬á ┬á GenType: GenCtrl
┬á ┬á SpecType: 0
┬á ┬á Classes: Association 2D 7C Naming 82 PowerLev Version ManSpec 91 EF SceneAct SceneActConf
┬á ┬á Bytes: 84 1A 0F 02 01 00 85 2D 7C 77 82 73 86 72 91 EF 2B 2C┬á
}
22:22:16 - [ZW->DR] - REQ,Msg:AppUpdate/0x49,Recvd: 22:22:16) 1290MSs
{
┬á ┬á Type: Node Info
┬á ┬á SrcId: 1A
┬á ┬á GenType: GenCtrl
┬á ┬á SpecType: 0
┬á ┬á Classes: Association 2D 7C Naming 82 PowerLev Version ManSpec 91 EF SceneAct SceneActConf
┬á ┬á Bytes: 84 1A 0F 02 01 00 85 2D 7C 77 82 73 86 72 91 EF 2B 2C┬á
}