03-30-2018, 08:18 PM
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
03-30-2018, 08:43 PM
I'm looking to give Z-wave a try again. What hardware are we using these days to interface with CQC? (I've seen references to "stick" and "Z-stick").
Happy to buy whatever is the latest and most robust.
Happy to buy whatever is the latest and most robust.
03-30-2018, 09:37 PM
Were you still planning on adding the utility to change defined path names with relative path names within the interface? I still have some floating around i would like to clean up.
03-31-2018, 08:10 AM
(03-30-2018, 08:43 PM)pinballmark Wrote: [ -> ]I'm looking to give Z-wave a try again. What hardware are we using these days to interface with CQC? (I've seen references to "stick" and "Z-stick").
Happy to buy whatever is the latest and most robust.
The new driver that folks are starting to test now uses the Aeon Z-Stick Gen 5. The driver uses that to talk to the Z-Wave network. The driver acts as a secondary controller. You still need a master controller to add/remove modules and do some other housekeeping work.
For the master the best option is probably Leviton's Vizia RF. There's a Leviton Vizia RF USB stick and a software program. You can use those on a laptop or USB enabled tablet to go around and enroll or manage Z-Wave modules. The Aeon one has to stay put on the computer where the CQC driver is running. Once you have made changes you replicate those from the master to the driver.
03-31-2018, 08:14 AM
(03-30-2018, 09:37 PM)kblagron Wrote: [ -> ]Were you still planning on adding the utility to change defined path names with relative path names within the interface?  I still have some floating around i would like to clean up.
It's still on the list. I just haven't had the time.
It is also much easier to do it manually these days as well. The file selection dialog has a check box to tell it whether to return a full or relative path. So you can just bring up the file selection dialog. It will select the current file that is already chosen. Just click the check box and hit save and it'll create the relative path for you.
03-31-2018, 11:08 AM
(03-31-2018, 08:10 AM)Dean Roddey Wrote: [ -> ](03-30-2018, 08:43 PM)pinballmark Wrote: [ -> ]I'm looking to give Z-wave a try again. What hardware are we using these days to interface with CQC? (I've seen references to "stick" and "Z-stick").
Happy to buy whatever is the latest and most robust.
The new driver that folks are starting to test now uses the Aeon Z-Stick Gen 5. The driver uses that to talk to the Z-Wave network. The driver acts as a secondary controller. You still need a master controller to add/remove modules and do some other housekeeping work.
For the master the best option is probably Leviton's Vizia RF. There's a Leviton Vizia RF USB stick and a software program. You can use those on a laptop or USB enabled tablet to go around and enroll or manage Z-Wave modules. The Aeon one has to stay put on the computer where the CQC driver is running. Once you have made changes you replicate those from the master to the driver.
Thanks Dean, got one of the Aeon sticks on the way and still have the Leviton Vizia RF. Looking forward to trying out the new version.
03-31-2018, 11:55 AM
OK, give 5.2.903 a try. Not expected to act any differently, but it has more logging around the inclusion process. It also fixes the options menu issues.
BTW, Bob, when you said you excluded the driver from STs, it just struck me that maybe you didn't run the include/exclude on the driver side? You have to run that for either an include or an exclude. If you just run something on the STs side, it may try for a while and then give up and just say, OK, I think it must be gone. But exclusion is just like inclusion in that you have to run both sides. That will then update the driver's Z-Stick info and let the driver know that it really is out of the network. The fact that the driver seems to think it is still in the network, which it would only think if the Z-Stick still thinks it is, just made me think maybe you weren't doing the exclude quite right.
Anyhoo, let's see what the trace shows this time with the extra logging.
BTW, Bob, when you said you excluded the driver from STs, it just struck me that maybe you didn't run the include/exclude on the driver side? You have to run that for either an include or an exclude. If you just run something on the STs side, it may try for a while and then give up and just say, OK, I think it must be gone. But exclusion is just like inclusion in that you have to run both sides. That will then update the driver's Z-Stick info and let the driver know that it really is out of the network. The fact that the driver seems to think it is still in the network, which it would only think if the Z-Stick still thinks it is, just made me think maybe you weren't doing the exclude quite right.
Anyhoo, let's see what the trace shows this time with the extra logging.
03-31-2018, 02:05 PM
When I was excluding in ST, I would go through removing a specific device, is is basically just a general exclusion, as well as performing a general exclusion after the specific device removal. Each time I would start it on the ST side and the run the include/exclude on CQC. As many times as I would run it, ST would say a device as been removed, or a the general exclusion of a device was successful.
It looks like the error for enabling tracing was fixed. Followed the same process as in the past, everything appears the same as you said it would. Not sure what I am doing wrong, but the trace file seems to be almost exactly the same as it was in the past. I rebooted the machine and tried again with the same result.
It looks like the error for enabling tracing was fixed. Followed the same process as in the past, everything appears the same as you said it would. Not sure what I am doing wrong, but the trace file seems to be almost exactly the same as it was in the past. I rebooted the machine and tried again with the same result.
03-31-2018, 02:24 PM
OK, it's not adding us as a secondary controller. Maybe this was the thing that was being mentioned by someone else earlier, that you had to tell STs to set it to a specific type of unit. It's adding us, but just as a regular module. The driver checks to see whether it has been added as a secondary controller, since it can't do anything useful otherwise. Since it sees it's not, it thinks it is not in the network.
Somewhere back up above, someone discussed that you had to do something on the STs side. Apparently it's not quite smart enough a thing to check the type of the Z-Stick and see if that it's a controller and add it as a secondary.
After we come back from the inclusion, we get the initial data:
17:01:41 - [ZW->DR] - RES,Msg:GetInitData/0x2,Recvd: 17:01:41) 156MSs
{
Bytes: 05 00 1D 19 E4 18 73 0F E0 78 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 05 00
}
The 2nd byte is zero. If it had been added correctly, at least the 0x4 bit would be set, indicating that we have been set to a secondary controller.
Somewhere back up above, someone discussed that you had to do something on the STs side. Apparently it's not quite smart enough a thing to check the type of the Z-Stick and see if that it's a controller and add it as a secondary.
After we come back from the inclusion, we get the initial data:
17:01:41 - [ZW->DR] - RES,Msg:GetInitData/0x2,Recvd: 17:01:41) 156MSs
{
Bytes: 05 00 1D 19 E4 18 73 0F E0 78 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 05 00
}
The 2nd byte is zero. If it had been added correctly, at least the 0x4 bit would be set, indicating that we have been set to a secondary controller.
03-31-2018, 02:40 PM
I thought what they were talking about earlier was switching devices to a special device type to associate it or tell it to add the VRC0P to group 1 for that device. I went back and looked and dont see anything directly related to adding the secondary controller. ST did give the zstick a device type of "Z-Wave Controller". The VRC0P is a 'Z-Wave Remote'. I changed the device type in ST to be a remote, reset the trace file, and with the stick already on the zwave network, tried replicating. CQC show replication succeeded. Attached is the trace file with the stick in the network already showing in ST and trying to do a replicate to the stick.