Edge driver to Associate Eaton Dimmer Switch RF9642 does not show up for my device

Can you post a full screenshot of the information for the device that isn’t choosing an edge driver?

I was afraid to post the full snapshot as I thought there may be information that is sensitive and could allow others to access the device. Is that not the case? There were a number of fields that were listed. Are any of these sensitive? I included the ones that look benign to me.

  • device ID: sensitive?

  • name: “Dimmer Switch”,

  • lable: “Back Hallway Light Accessory”,

  • manufacture Name: “SmartThings”,

  • presentationID: "SmartThings-smartthings-Secure_Dimmer

  • deviceManufacturercode: “001A-4441-0502”,

  • locationID: sensitive?

  • roomID: sensitive?

  • deviceTypeID: sensitive?

  • deviceTypeName: “Secure Dimmer”,

  • deviceNetworkType: “ZWAVE”,

  • createTime: “2023-03-26T23:12:46.620Z”,

  • parentDeviceID: sensitive?

  • comletedSetup: true,

  • deviceNetworkType: "“ZWAVE”,

  • deviceTypeId: sensitive?

  • deviceTypeName: “Secure Dimmer”,

  • executingLocally: false,

  • hubId: sensitive?

  • networkSecurityLevel: “ZWAVE_S2_AUTHENTICATED”

  • type: “DTH”

  • restrictionTier: 0,

  • allowed: [ ]

BTW, I just wanted to mention that I’m sorry this is so annoyingly complicated right now

Yes this does seem very complicated given that all I want to do is make my 3-way dimmers work! LOL. That said, this community as you say seems very eager to help so I do find comfort in that. I am also stubborn and refuse to give up, which has proven to be my downfall when it comes to maintaining my sanity :sweat_smile:

1 Like

I also wanted to mention that the only reason to use zwave direct association is if you want to be sure that the accessory can still turn the light on and off even if your hub isn’t working.

If that’s not a concern, you’re OK with people just having to go over to the master to get it to work, then you can forget all about association and just use the regular automations in the smartthings app to tie the two switches together.

Someone else can tell you how to synchronize them, I don’t use that feature myself. But it doesn’t require knowing anything about edge drivers or downloading anything special.

This is the option that people use if they want to have, say, a zwave switch cause a Zigbee bulb on a different circuit to turn on and off. Or a batterypowered thread device actuate a zwave device.

As one of my engineering professors used to say “it will all work fine as long as everything is working fine.“ :wink:

So there is a very simple way to make it all work most of the time, you just have to understand that if the hub failed, the accessory wouldn’t work. your choice.

Ohh. That is very interesting. I did not see any literature about using routines to link the devices. I would be OK with that as a temporary work around so that my wife can stop bugging me that the switch does not work, and she can use it until I figure out this more robust solution. :slightly_smiling_face: I will research that in tandem with the association group solution

Tagging @jkp

None of the information output from the API Browser+ is sensitive.

I’d be curious what the deviceManufacturercode is for the Master dimmer that uses an Edge driver. I’m guessing it’s using the stock Z-Wave Switch driver.

In looking at the fingerprints for the production drivers, this is the only one that is close to the accessory dimmer but there is no specific model:

 - id: "Eaton/0000"
    deviceLabel: Eaton Dimmer Switch
    manufacturerId: 0x001A
    productType: 0x4441
    productId: 0x0000
    deviceProfileName: switch-level

Since there is still a valid DTH and there is no fingerprint match for an Edge driver, it makes sense that it installs with the DTH. Your best bet at this point is to ask @Mariano_Colmenarejo to update his Z-Wave Switch and Childs Mc driver to include your Accessory dimmer. His driver is a clone of the stock ST driver, but he has added other switch and dimmer fingerprints so that it will work with devices not included in the stock driver.

1 Like

There are multiple ways you can “link” device behavior. Since the Accessory switch is using a DTH, no Routine is going to run local to your hub. Only once both devices are using Edge drivers can the Routine(s) run local.

  • Have a Routine that says “If this device turns on then turn on this other device”. The downside is you need two Routines, one for on and one for off.
  • Use the Smartlighting app and create a rule where the “Device to control” has an Action of “Sync with switch” and choose the Master dimmer as the device to sync with.

If you expect the Accessory dimmer to mirror the dim level of the Master, then Smartlighting is really the only way to do it.

Also, you may be able to use Association Groups even with one device using an Edge driver and the other using a DTH. You would want to configure the device ID of the Accessory dimmer in Association Group 2 of the Master dimmer.

1 Like

Hi - The master dimmer that is using the Edge driver has a deviceManufacturercode: “001A-4449-0501”

That’s a great idea. I will reach out to him to see if he can add my device. Thanks!

Interesting. I only see this Eaton fingerprint that is close.

 - id: 001A/4449/0101
    deviceLabel: Eaton Dimmer Switch
    manufacturerId: 0x001A
    productType: 0x4449
    deviceProfileName: switch-level

I’m wondering if it matches just because the productType matches and there is no specific productID.

Zwave direct association is not bidirectional.

If the OP wants turning on the accessory switch to cause the master switch to turn on via Z wave direct association, it doesn’t make any difference if the accessory switch is in the association groups in the firmware of the master switch. That doesn’t cause the master to turn on when the accessory turns on.

The master Has to be added to the association group in the firmware of the accessory switch.

If the accessory switch cannot be added to an edge driver that exposes the association groups then there’s no way to do it with Zwave association right now, because the stock Groovy DTH doesn’t expose those settings and you can no longer add a custom Groovy DTH (like the Z wave Tweaker).

So I am afraid that in the current situation, the only solution for using zwave direct association is to get the accessory switch matched with an edge driver that exposes the association groups.

Yeah, I see what you’re saying. I think I mis-read which direction he wanted the sync to happen.

1 Like

The device can be linked by manufacturer and productType and with any productId.

- id: 001A/4449/0101
    deviceLabel: Eaton Dimmer Switch
    manufacturerId: 0x001A
    productType: 0x4449
    deviceProfileName: switch-level

In the stock driver there is a fingerprint for the Eaton dimmer and another specific fingerprint and subdriver for the Eaton accessory dimmer.

   {mfr=0x001A, prod=0x4441, model=0x0000} -- Eaton Dimmer Switch

I don’t know if this is enough to master and slave dimmers to work.

1 Like

His accessory dimmer has a fingerprint of 001A-4441-0502 so it’s not matching the model of 0x0000. I think there either needs to be an exact match or the productID needs to be removed like the fingerprint of the master.

1 Like

Thank @h0ckeysk8er
I did not see it

Added to this version of the Z-Wave Switch and Child Mc driver, which also already has the option to create child devices to configure parameters and associations of each device

I don’t know if it is a stock driver error or my mistake, but the fingerprint of the Eaton accessory dimmer with productId 0x0000 I cannot found on the Z-Wave alliance page

 Name         Z-Wave Switch and Child Mc
 Version      2023-03-27T15:26:34.151021779        
- id: "Eaton/0000"
    deviceLabel: Eaton Dimmer Switch
    manufacturerId: 0x001A
    productType: 0x4441
  # productId: 0x0000 # 0x0502 modified 27/03/2023

Here you can see how to create the configurator device if you need it

1 Like

Thank you very much! I installed the Z-Wave Switch and Child Mc, but it is not automatically adding to my RF9642 device which is using the DTH standard driver. It will only installs on my other devices that are using edge drivers

I suspect that now that you made this change on your side, when I exclude and re-add RF96402 device it will now install the Z-Wave Switch and Child Mc edge driver. But my understanding is that this is just a configuration tool and that after I am done using it I need to revert back to the standard edge driver. Since standard edge drivers are not installing on my device, how will this work?

Thanks again for this information on routines, while I try to work out the driver and Association issues I am having, I tried setting up routines as a temporary work-around, but I can’t seem to get them to work properly. In the “Smart lighting” routine could I get some help to know what to put in each section so that my accessory dimmer is controlled to my master dimmer?

  • Devices to control: Accessory Dimmer?
  • Actions - Control devices: 1. (on/off) 2. Dimmer (set/not set) 3. sync with switch (Yes/No)
  • Device status: Switch Master Dimmer? 1. (on/off) 2. Turn off when condition is reversed (Yes/No)

Also, do I need to set 1 routine for on and another for off or can I just set the Turn-off when condition is revered to “Yes”

I haven’t played with dimmers controlling each other, but my logic says:

  • Devices to control: Accessory Dimmer
  • Actions - Control devices: Sync with switch
  • Select devices: Master Dimmer

I’m not using the new version of Smartlighting, but in the older version (where sync was called mirror) this would cause actions on the selected device to be mirrored to the controlled device(s).

Thanks for the quick reply, I just tried that and it did not work. In a way I am glad it was not that simple, as I would have felt very foolish spending 8 hours on Saturday trying to set up associations for this feature to work…LOL. Oh well, I sent a note to the Aeotec Help Desk. Maybe they have a solution. I think I am calling it quits for tonight.

The OP is hoping to use the 9642 accessory to control the 9640 master, not the other way around.

The idea in this type of virtual three way is that the master controls the current to the lighting fixture.

The accessory is simply a remote to allow you to actuate the master from a different physical location.

So pressing on on the remote should then tell the master to turn on.

The accessory is the “if“ and the master is the “that”.

I don’t know what the current terminology is in the app, though, it seems to be pretty confusing. :thinking:

No, the Zwave Switch and Child Mc edge driver is not just a configuration tool. It is a full featured driver that would be used for every day functionality.

The configurator tool from the same author is called “Zwave Device Config Mc.”