Charmed Quark Systems, Ltd. - Support Forums and Community

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

I also figured out why it isn't picking up the names set on the units and using those as the default initial names, so now it will pick those up and save you from having to do the naming. Anyhoo, I'll bang on it a bit more tomorrow and put up another one to try. This is definitely a step forward. I also extended my times for each msg transmission state, which has helped since the driver was giving up a bit too quickly in some cases. That though is not free, it means that a bad unit can make everything slow down that much more.

(05-10-2018, 06:29 PM)Dean┬áRoddey Wrote: [ -> ]OK, I figured it out, something else stupid which was interacting with the sorting error, and which was also making for more work during startup as well, so a good fix all around.

There are some issues with some of Kevin's units but it may be because he's made changes since I last got him to do a replication for me. But definitely units 23, 21, 20, 22, 24 (decimal id) are consistently not responsive and the trace file is a mess of failures on those. Everything else pops up quite nicely now.

Are those actually battery powered ones? I don't remember. The driver is showing them as listeners, but there could be some issue there. If I'm seeing them as listeners when they aren't, that would cause the above. Otherwise they would fail the initial attempt and go to WakeWakeUp. I'm not actually showing any WaitWakeups which leads me to believe that this the case, since I'm guessing you do have some battery powered ones that aren't locks, right?

Dean,
Here is an export from my Vizia RF install tool(usb master controller)
If it helps.
Also the units you point out are the farthest away so that makes sense(will investigate). 29 must be┬ámy z-stick and 28 is a ghost┬ádevice left over from testing.

1┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Installer_1┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Vizia RF + Installer USB Stick (VRUSB)┬á┬á┬á┬á Controller
2┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Fish Tank Light┬á┬á Unknown Device┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á
4┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Fibaro_RGBW┬á┬á┬á Unknown Device┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á
5┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á SmartThingsHub┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Unknown Device┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Controller
7┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Elk M1┬á Vizia RF RS232 Interface (RZC0P/VRC0P) Controller
9┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Liv Rm Inside┬á┬á┬á┬á┬á Vizia RF 1000W MLV Dimmer (RZM10/VRM10/VRMX1)┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á
10┬á┬á┬á┬á┬á┬á┬á┬á┬á Liv Rm Outside┬á Vizia RF 1000W MLV Dimmer (RZM10/VRM10/VRMX1)┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á
11┬á┬á┬á┬á┬á┬á┬á┬á┬á Landscape Lights┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Unknown Device┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á
12┬á┬á┬á┬á┬á┬á┬á┬á┬á Fish Tank Moon light┬á┬á┬á┬á┬á Unknown Device┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á
13┬á┬á┬á┬á┬á┬á┬á┬á┬á Foyer┬á┬á┬á Vizia RF + 5A Switch (VRS05)┬á┬á┬á┬á┬á┬á
14┬á┬á┬á┬á┬á┬á┬á┬á┬á Front Porch light┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Vizia RF + 5A Switch (VRS05)┬á
16┬á┬á┬á┬á┬á┬á┬á┬á┬á Bedroom Outside┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Vizia RF 1000W MLV Dimmer (RZM10/VRM10/VRMX1)┬á
17┬á┬á┬á┬á┬á┬á┬á┬á┬á Liv Rm Wall Left┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Vizia RF + Receptacle (VRR15)┬á┬á┬á┬á┬á┬á┬á┬á
18┬á┬á┬á┬á┬á┬á┬á┬á┬á Liv Rm Wall Right┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Vizia RF + Receptacle (VRR15)┬á┬á┬á┬á┬á┬á┬á┬á
20┬á┬á┬á┬á┬á┬á┬á┬á┬á Bedroom Reading┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Vizia RF 1000W MLV Dimmer (RZM10/VRM10/VRMX1)┬á
21┬á┬á┬á┬á┬á┬á┬á┬á┬á Backyard Security┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Vizia RF 15A Switch (RZS15/VRS15)┬á┬á┬á
22┬á┬á┬á┬á┬á┬á┬á┬á┬á Back Porch light Vizia RF + 5A Switch (VRS05)
23┬á┬á┬á┬á┬á┬á┬á┬á┬á Garage Lights┬á┬á┬á┬á Vizia RF 15A Switch (RZS15/VRS15)┬á
24┬á┬á┬á┬á┬á┬á┬á┬á┬á Back Door Lock Z-Wave Lever Lock┬á┬á┬á┬á┬á┬á┬á┬á┬á
25┬á┬á┬á┬á┬á┬á┬á┬á┬á Front Door Lock┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Z-Wave Lever Lock┬á┬á┬á┬á┬á
26┬á┬á┬á┬á┬á┬á┬á┬á┬á Living Room Switch┬á┬á┬á┬á┬á┬á┬á┬á Vizia RF 4-Zone Controller (RZCZ4/VRCZ4)┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Controller
28┬á┬á┬á┬á┬á┬á┬á┬á┬á Device_28┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Unknown Device┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Controller
29┬á┬á┬á┬á┬á┬á┬á┬á┬á Device_29┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Unknown Device┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á┬á Controller
31┬á┬á┬á┬á┬á┬á┬á┬á┬á CQC┬á┬á┬á┬á┬á┬á Vizia RF RS232 Interface (RZC0P/VRC0P) Controller

It might be worth getting an extended doodad and putting it somewhere halfway between.

(05-10-2018, 08:38 PM)Dean┬áRoddey Wrote: [ -> ]It might be worth getting an extended doodad and putting it somewhere halfway between.

Good excuse to get a few more switches to fill in the gap in the z-wave mesh network Smile

Plug in repeaters well if you don't have a place for a switch. Aeon Labs DSD37 Range Extender

OK, give 5.2.911 a try. This one should be doing pretty well. Delete the config file again, so that we can force it to re-scan all of them. It should pick up the right types and should pick up names from the units themselves where those have been assigned.

(05-11-2018, 12:28 PM)Dean┬áRoddey Wrote: [ -> ]OK, give 5.2.911 a try. This one should be doing pretty well. Delete the config file again, so that we can force it to re-scan all of them. It should pick up the right types and should pick up names from the units themselves where those have been assigned.

Wow, wow, wow,┬á┬á Much better. And I like it is picking up the names automatically.

Looks like it didn't pick up 21 and 23┬á both are. at "GetUnitInfo" and are┬áLeviton VRS15
How do I tell if the model wasn't found or there is a comms error to that device?
Also 22 and 24 didn't get picked up.(assume same issue).┬á When I do a rescan unit state does not change like it trying again? should state be changing?

GetUnitInfo is the first state. If it's already there, then forcing a rescan doesn't do anything. It's already trying the very first step. Are any of those secure ones that it didn't pick up?

You can tell the model wasn't found if it doesn't make it to WaitApprove basically. If it's at GetUnitInfo, then it's made no progress at all, at least in terms of talking to the unit, though it got some basic info about it that our local Z-Stick knows already. If it's anything after GetUnitInfo but before one of the 'end point' states (WaitApprove, WaitWakeup WaitDevInfo) then it's made some progress but likely comms are not good so its struggling to go further.

Have you made any changes since you last replicated the driver against the master? If so you'll need to run an include on the driver again to pick them up.

So 24/25 are secure ones. It got one but not the other. So it's not a security issue, probably just an inability to consistently communicate with one. So if 24 is the back door, is that further from the Z-Stick than the front door (25)?

Interesting Aeotec gen5 stick backup utility. Good for at least verifying the PC is working correctly with the stick.(of course need to pause the CQC z-wave driver).
You can also turn off the sticks LED lights..(not sure why you would)

https://aeotec.freshdesk.com/support/sol...p-software

Charmed Quark Systems, Ltd. - Support Forums and Community

Dean Roddey

kfly

Dean Roddey

kfly

batwater

Dean Roddey

kfly

Dean Roddey

Dean Roddey

kfly