Hi Mariano - thanks for another helpful tool. I’m trying to troubleshoot a GoControl sensor; I was able to read the association groups but not the parameters. When I choose parameter scan and wake up the device, the “waiting for device response” message clears but no data appears. For the association groups, the data showed up immediately. I can try to look with CLI logging on tomorrow, but in the meantime is there anything else you can suggest?
1 Like
Hi @MarkTr
If you know the parameter numbers you want to see, set a scan range close to those values.
By default it puts a range and they may not be in that range.
If it doesn’t work, it would be necessary to see the log and check if any error occurs.
Is the sensor awake when you read the parameters?
Version of the Z-Wave Device Config Mc integrated as a child device in the Z-Wave Switch and Child Mc and Z-Wave Sensor and Child Thermostat Mc driver
Sorry, I have not been successful in setting up the group association so that my Eaton RF9642 controls my RF9640. I am following the steps above. I select Get and the SmartThings icon starts to spin
It then gives me the following error message
The fingerprint of the RF9640 that I am trying to control is:
Assuming I was to get past this step, my plan was to follow the second set of instructions below:
Per the 9640 fingerprint I see that the DNI is 0x17 so I planned to put 17 in the Node To Write Hex. The Fingerprint also shows “End Point & Command Class [1]: VERSION” so I thought this might mean that the endpoint should be 1 (see example of what I planned to enter below)
From there I planned to hit the action button
Then I planned to delete the child for both the RF9640 and the RF4642.
Then I planned for everything to work…but I cant get past “select Get”
After that I planned to repeat the entire process again, but this time put “3” in the group instead of “2” so that the dimming functionality works. Here are the specs for the RF9640 and the RF4942
manuals-backend.z-wave.info/make.php?lang=en&sku=RF9640-N&cert=ZC10-18126327
manuals-backend.z-wave.info/make.php?lang=en&sku=RF9642-Z&cert=ZC10-18126326
Also for my own understanding, what is an “endpoint” I tried to find this on the forum to no avail. I suspect the reference to endpoint that I see in the fingerprint is not the right thing.
Mind you I am an accountant my profession, with a passion for technology so please bear with me. I’m pushing 50 so too late for me to chase my passion and get my engineering degree, but I am doing my best to learn as I go…
Have you tried it with a different Device Association Type other than Multi Channel?
2 Likes
Endpoint is a term that the third-party Z wave specifications use for devices which are multi function. Some other protocols called this a multi component device.
One of the simplest examples is a multisensor. It might have one sensor for temperature, one sensor for motion, one sensor for light level. Each of those would be an endpoint.
In zwave, say that the network ID (Which in Z wave is assigned at the time that the device joins the network, and is given to it by the hub) is 17.
This particular sensor would have an endpoint 17, 1 for the motion sensor, 17, 2 for the temperature sensor, and 17, 3 for the lux sensor.
That way when the device sends the report to the hub, the hub knows which sensor is reporting.
Another example is a powerstrip. The model in this picture has five controllable outlets. Each one would count as an endpoint. So again, if the device ID is 17, 17,1 would be the first socket, 17,2 would be the second socket, and so on. It’s also possible that 17, 0 would be set up to control the power strip as a single on/off.
Some platforms use a decimal point instead of a comma, so 17.0 , 17.1, etc. either is correct under the standard, but they may vary by platform.
In the past, smartthings has referred to this concept as parent and child, so that the powerstrip would be the parent and each socket would be a child. That gets really confusing when you’re talking about Zigbee because Zigbee uses the terms parent and child in a completely different way having to do with network routing where the parent is one device and the child is a completely different physical device, but that’s smartthings for you. They made up their own terminology and then didn’t use it consistently. 
Anyway, I hope that at least clears up that issue.
Looking at the official conformance statement on the Z wave alliance site, the master dimmer, 9640, does not have multiple endpoints and supports association V2. It would not be considered a multichannel device.
https://products.z-wavealliance.org/products/3152/classes
(“multilevel” just means it’s a dimmer device. Instead of just having the binary on/off, you can set it to 20% on, 50% on, etc. So multi level.)
The 9642 is pretty much the same command structure.
In contrast, the Zooz Zen30 double switch is a single physical device with two different control buttons. One is a dimmer rocker switch for a light, and the other is an on/off button, most commonly for a bathroom exhaust fan. It has two endpoints, one for each of these controls. And it supports multi channel association.
https://products.z-wavealliance.org/products/3791/classes
1 Like
Yes, thanks I just tried that. Also moved next to the hub just in case, but received the same error message
Super informative. Thank you. You actually reminded me that I did read one of your posts which had an example about the surge protector, but I read it when I first started researching Z-wave and did not understanding anything I was reading so did not connect the dots 
1 Like
At this point it would be helpful to get logging from the driver to see what is happening when it attempts to send the command to the dimmer. To do that you will need the ST CLI which can be installed on a Windows/Mac/Linux computer. From a command line on the computer where it is installed, you’ll do the command “smartthings edge:drivers:logging” and you will be prompted for your hub’s IP address. Once you enter that, you can select the Config Mc driver. After you have a logging session start, attempt to program the association group again both single and multi channel.
Hi @Tom11
I would start by scanning all the groups of the device, to see if it responds.
Choose the Device Groups Scan option
Close the device in the app and reopen it to display the new group scan profile.
By default they are scanned from group 1 to 10, normally there are no more than 5.
Press in the action button and all the groups and the maximum nodes of each group should be displayed.
Some of the groups, normally 1, is associated with node 1, which is the Hub, if there is only one hub.
If it does not answer, it may be a problem with the security method with which the device is paired.
To set up an association:
- Choose Device Association Config. Save, close the device, and reopen it.
If it does not show the fields, you can do a refresh by sliding your finger down. - Choose Single Channel Association
- Enter the group number, 2 for example
- Enter the node, 17 in your case.
- Choose SET in group command Action
- Press action button
- The command will be sent and then it will be Get and it will show the result received from the device.
- If there is no response, it may be a device or security problem.
I have one that has broken down and does not respond to single channel associations.
2 Likes
YES !!! IT WORKED !!! You are a genius!. I followed your steps and set up 2 accessory dimmers. They work flawlessly. They turn on and off the light and they dim. The last time I was this excited was when my children were born 
Seriously cannot tell you the amount of combined hours I’ve spent studying, researching, thinking about Z-Wave and setting up associations. My family was one step away from committing me to an asylum. Hopefully I have at least demonstrated to them the attributes of perseverance. OK now on to my next obsession…
6 Likes
…Actually 1 last question. I just realized I forgot to delete the child devices for both the accessory dimmer and master dimmer prior to completing all of the steps above. If I delete them now, will I lose the association settings of the parent devices and have to start all over again?
Hi @Tom11
You can delete and recreate them whenever you want without losing anything.
They are just virtual devices that are used to configure the real device when needed
Got it. And the way I would delete them is by clicking on them and selecting Remove Device? And it does not matter what order I should remove them?
Lastly, just out of curiosity, when I go to the setting of the Parent dimmers it says NOTE: YOU MUST DELETE THE DEVICE AFTER PERFORMING THE CONFIGURATION. What would happen if I just leave them there forever? Does it affect other functionality?
This is correct.
Everything should work fine even if you don’t delete them, but there’s no point in keeping them when you can recreate them whenever you want.
It is not necessary, but when you have deleted the child devices, you can disable the preference manually as the driver cannot do it.
1 Like
12 posts were split to a new topic: Eaton Cooper RF9640 3 Way Synchronization?
Thanks again for the info. One more for you when you get I chance. I noticed one of my RF9642 Accessory dimmers has eight group 1 associated with the hub. Do you know why there are eight instead of just one?
Also when I compare to the other RF9642 that I own and the two other RF9640 that I own (see pics below) they only have five group 1 associated with the hub.
I wonder if this is because I manually factory reset my RF9642 (the one called Device Info-Back Hallway Light…" in the picture above) a few times without excluding it with the controller. I then manually removed it using the old API. Maybe I corrupted something in the registry? The device works fine, but was just wondering why it is the only one that has eight instead of five Group 1
Location List (smartthings.com)
It depends on the device, when you scan more groups than it actually has, it answers by repeating one of the groups, normally it repeats 1.
others only respond with what they really have.
The driver does not filter the device responses.
1 Like
I see. Thanks, that makes sense. Any Idea why one of my RF6942 Dimmers has 8 Group 1, but the other only has 5 Group 1?
The two have only 3 groups.
As I told you, when you scan more groups than the device has, depending on the device, it repeats the response until completing the entire requested range.
I have a fibaro that has 5 groups and only answers with 1, 2, 3, 4 and 5.
I have another one that returns 1, 2, 3, 4, 5 and then repeats group 1 until completing the range of 10
Scan with a range from 1 to 3 and you will see that no group repeats
1 Like