Cooper Aspire Scene Controller RFWC5 and RFWC5D Device Handler [beta release]

Happy Sunday, @sainsworth

I have tired process of elimination; therefore I end up removing all my 8 Cooper switches, factory reset them all. Used extension cord, means 5-7 feet away from my zooz switches, used the following steps to add the 1st Cooper.**

Added new device, follows live log to make sure its added and I waited about 3-4 minutes before I moved to next step

Under devices, I then selected my newly added Cooper device, clicked on edit, then under “Type” I selected the “Cooper Aspire Scene… DH” and hit update. Waited about 4 minutes to make sure new settings were applied. See logs for details….

fe762c6c-22db-4001-9df8-277f534e936a 12:23:08 AM: debug Parsed SceneControllerConfReport(groupId: 5, dimmingDuration: 0, sceneId: 255) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: SceneControllerConfReport(groupId: 5, dimmingDuration: 0, sceneId: 255)]

fe762c6c-22db-4001-9df8-277f534e936a 12:23:05 AM: debug Parsed AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1], groupingIdentifier: 5) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1], groupingIdentifier: 5)]

fe762c6c-22db-4001-9df8-277f534e936a 12:22:43 AM: debug Parsed SceneControllerConfReport(groupId: 4, dimmingDuration: 0, sceneId: 254) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: SceneControllerConfReport(groupId: 4, dimmingDuration: 0, sceneId: 254)]

fe762c6c-22db-4001-9df8-277f534e936a 12:22:40 AM: debug Parsed AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1], groupingIdentifier: 4) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1], groupingIdentifier: 4)]

fe762c6c-22db-4001-9df8-277f534e936a 12:22:20 AM: debug Parsed SceneControllerConfReport(groupId: 3, dimmingDuration: 0, sceneId: 253) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: SceneControllerConfReport(groupId: 3, dimmingDuration: 0, sceneId: 253)]

fe762c6c-22db-4001-9df8-277f534e936a 12:22:16 AM: debug Parsed AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1], groupingIdentifier: 3) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1], groupingIdentifier: 3)]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:54 AM: debug Parsed SceneControllerConfReport(groupId: 2, dimmingDuration: 0, sceneId: 252) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: SceneControllerConfReport(groupId: 2, dimmingDuration: 0, sceneId: 252)]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:51 AM: debug Parsed AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1], groupingIdentifier: 2) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1], groupingIdentifier: 2)]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:30 AM: debug Parsed SceneControllerConfReport(groupId: 1, dimmingDuration: 0, sceneId: 251) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: SceneControllerConfReport(groupId: 1, dimmingDuration: 0, sceneId: 251)]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:27 AM: debug Parsed AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1], groupingIdentifier: 1) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1], groupingIdentifier: 1)]

88f5393d-eb0b-41ae-bbd8-ec93e658182a 12:21:09 AM: debug Update detected: DeviceUpdated fe762c6c-22db-4001-9df8-277f534e936a

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: trace updated(): Ran within last 5 seconds so skipping.

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug associating group for button:4: 1

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug associating group for button:3: 1

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug Please Wait this can take a few minutes

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug setting configuration commands for button:2 Level:[50]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug [850401, 850101, 7004010132, 2D0101FB00, 85010101, 850201, 2D0201, 850402, 850102, 7004020132, 2D0102FC00, 85010201, 850202, 2D0202, 850403, 850103, 7004030132, 2D0103FD00, 85010301, 850203, 2D0203, 850404, 850104, 7004040132, 2D0104FE00, 85010401, 850204, 2D0204, 850405, 850105, 7004050132, 2D0105FF00, 85010501, 850205, 2D0205]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug associating group for button:2: 1

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug setting configuration commands for button:4 Level:[50]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug associating group for button:4:

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug setting scene commands for button:3 scene:253 dimmingduration:0

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug associating group for button:5:

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug associating group for button:3:

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug setting scene commands for button:4 scene:254 dimmingduration:0

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug setting scene commands for button:2 scene:252 dimmingduration:0

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug associating group for button:1: 1

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug setting configuration commands for button:1 Level:[50]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:09 AM: debug associating group for button:2:

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug setting configuration commands for button:4 Level:[50]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug associating group for button:3: 1

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug setting configuration commands for button:5 Level:[50]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug setting configuration commands for button:3 Level:[50]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug associating group for button:4: 1

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug associating group for button:2: 1

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug associating group for button:5:

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug [850401, 850101, 7004010132, 2D0101FB00, 85010101, 850201, 2D0201, 850402, 850102, 7004020132, 2D0102FC00, 85010201, 850202, 2D0202, 850403, 850103, 7004030132, 2D0103FD00, 85010301, 850203, 2D0203, 850404, 850104, 7004040132, 2D0104FE00, 85010401, 850204, 2D0204, 850405, 850105, 7004050132, 2D0105FF00, 85010501, 850205, 2D0205]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug Please Wait this can take a few minutes

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug associating group for button:5: 1

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug associating group for button:3:

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug setting scene commands for button:3 scene:253 dimmingduration:0

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug setting configuration commands for button:1 Level:[50]

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug setting scene commands for button:5 scene:255 dimmingduration:0

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug setting scene commands for button:4 scene:254 dimmingduration:0

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug setting scene commands for button:2 scene:252 dimmingduration:0

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug associating group for button:2:

fe762c6c-22db-4001-9df8-277f534e936a 12:21:08 AM: debug setting scene commands for button:1 scene:251 dimmingduration:0

12:20:36 AM: info Waiting on events…

12:20:36 AM: info For past logs for individual things go to the My Devices section, find the device and click on the Events link on the device information page.

12:20:36 AM: info This console provides live logging of your SmartThings.

Then, I used my iPhone and used my ST classic app, found my newly installed Cooper device under “things” clicked on setting icon on the top right hand side, this is where I input all my association device id’s as follow. see picture below. When done I hit save and then clicked on “Configure Scene” and waited about 4 minutes to make sure again settings were applied. See log below. I still have no luck.

fe762c6c-22db-4001-9df8-277f534e936a 12:35:33 AM: debug Parsed SceneControllerConfReport(groupId: 5, dimmingDuration: 0, sceneId: 255) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: SceneControllerConfReport(groupId: 5, dimmingDuration: 0, sceneId: 255)]

fe762c6c-22db-4001-9df8-277f534e936a 12:35:29 AM: debug Parsed AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1, 10], groupingIdentifier: 5) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1, 10], groupingIdentifier: 5)]

fe762c6c-22db-4001-9df8-277f534e936a 12:35:03 AM: debug Parsed SceneControllerConfReport(groupId: 4, dimmingDuration: 0, sceneId: 254) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: SceneControllerConfReport(groupId: 4, dimmingDuration: 0, sceneId: 254)]

fe762c6c-22db-4001-9df8-277f534e936a 12:34:57 AM: debug Parsed AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1, 6], groupingIdentifier: 4) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1, 6], groupingIdentifier: 4)]

fe762c6c-22db-4001-9df8-277f534e936a 12:34:30 AM: debug Parsed SceneControllerConfReport(groupId: 3, dimmingDuration: 0, sceneId: 253) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: SceneControllerConfReport(groupId: 3, dimmingDuration: 0, sceneId: 253)]

fe762c6c-22db-4001-9df8-277f534e936a 12:34:25 AM: debug Parsed AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1, 7], groupingIdentifier: 3) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1, 7], groupingIdentifier: 3)]

fe762c6c-22db-4001-9df8-277f534e936a 12:33:57 AM: debug Parsed SceneControllerConfReport(groupId: 2, dimmingDuration: 0, sceneId: 252) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: SceneControllerConfReport(groupId: 2, dimmingDuration: 0, sceneId: 252)]

fe762c6c-22db-4001-9df8-277f534e936a 12:33:55 AM: debug Parsed AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1, 9], groupingIdentifier: 2) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1, 9], groupingIdentifier: 2)]

fe762c6c-22db-4001-9df8-277f534e936a 12:33:25 AM: debug Parsed SceneControllerConfReport(groupId: 1, dimmingDuration: 0, sceneId: 251) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: SceneControllerConfReport(groupId: 1, dimmingDuration: 0, sceneId: 251)]

fe762c6c-22db-4001-9df8-277f534e936a 12:33:22 AM: debug Parsed AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1, 8], groupingIdentifier: 1) to [‘isStateChange’:true, ‘linkText’:‘KP_Kitchen’, ‘descriptionText’:Cooper KP_Kitchen: AssociationReport(reportsToFollow: 0, maxNodesSupported: 232, nodeId: [1, 8], groupingIdentifier: 1)]

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug associating group for button:4: 1

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug [850401, 85010108, 70040101FF, 850101, 7004010132, 2D0101FB00, 85010101, 850201, 2D0201, 850402, 85010209, 70040201FF, 850102, 7004020132, 2D0102FC00, 85010201, 850202, 2D0202, 850403, 85010307, 70040301FF, 850103, 7004030132, 2D0103FD00, 85010301, 850203, 2D0203, 850404, 85010406, 70040401FF, 850104, 7004040132, 2D0104FE00, 85010401, 850204, 2D0204, 850405, 8501050A, 7004050163, 850105, 7004050132, 2D0105FF00, 85010501, 850205, 2D0205]

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug Please Wait this can take a few minutes

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug associating group for button:5: 1

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug setting configuration commands for button:3 Level:[255]

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug associating group for button:5: [10]

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug associating group for button:2: 1

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug associating group for button:4: [6]

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug setting configuration commands for button:1 Level:[50]

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug setting configuration commands for button:4 Level:[255]

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug associating group for button:2:

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug setting scene commands for button:2 scene:252 dimmingduration:0

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug setting configuration commands for button:3 Level:[50]

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug associating group for button:1:

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug executing configure hub id is: 1

fe762c6c-22db-4001-9df8-277f534e936a 12:32:57 AM: debug associating group for button:1: [8]

fe762c6c-22db-4001-9df8-277f534e936a 12:32:45 AM: debug Executing ‘updated’

I have tried exact above steps at my friends house with his previously working Cooper keypads. i end up removing the devices and re-added… I had the same issue with his devices as well. Now I can’t get his to work anymore. :slight_smile:

At this point, I’m not sure what I’m doing wrong here…. Please advise.

Thanks a lot for hearing me and guiding me through.

@sainsworth - maybe the s2 security now enabled by the .30+ firmware might be hosing direct association of newly added devices v. devices that don’t support S2?

@jody.albritton - you guys have anyone who plays with Zwave direct association who might be able to figure out what’s going on here?

Thank you Nathan @nathancu for your reply, you might be right.
@sainsworth

After removing/resetting and adding these cooper keypad multiple times, i have manged to get 4 zooz switches out of 28 zooz to work using above steps. Upon looking into this further, i have noticed, the switches that work with cooper DH via association are the ones marked under Data filed as " networkSecurityLevel: ZWAVE_LEGACY_NON_SECURE". Other 24 zooz switches are marked as " networkSecurityLevel: ZWAVE_S2_UNAUTHENTICATED". Is there a way to change the networkSecurityLevel on the remaining 24 zooz switches? I have tired to change the device type under each switch to “Z-wave switch generic” yet the network security did not change. see attached pictures for ref.

I generally try to stay out of discussions of smartthings Z wave architecture specifically because I don’t really know anything about it. But in terms of zwave itself, there are some issues that affect interoperability of devices of different generations.

First, is the change with zwave plus to reserve association group one as the lifeline group. This means that many devices will now allow only one target in this group, the hub itself. That was not true with classic Z wave, and so sometimes you run into some issues there.

More likely is the fact that the specification was tightened up after initial release to say that association should only be allowed between devices using the same level of encryption. So S2 to S2, or S0 to S0. This is different from the initial release of S2 which implied that devices could fall back to the lower level of encryption. But now that’s not supposed to happen. The result of this inconsistency is that different devices are handling it differently, particularly if they don’t have the latest firmware versions.

Clarified Associations, IP Association and Multi Channel Association:
association should be made only if the 2 nodes are bootstrapped on the
same Security level.

That said, I have no idea what smartthings is doing when someone tries to create an association between devices on different security levels since this is not done through an official utility.

Tagging @Kianoosh_Karami @tpmanley @erocm1231 @zcapr17 @TheSmartestHouse

1 Like

I knew you were going to have some insight @JDRoberts thanks!

1 Like

@Vik The hub will automatically associate itself (Hub Controller) with Association Group 1 (Lifeline group) at join time whether the Device is Z-Wave Plus or not (due to legacy devices treating group 1 as lifeline anyway).

You have different devices here, the Zooz ones are much newer devices and support S2 security, that does not necessarily mean that S2 security has broken anything. Regardless of network security, if the DTH generates a message to be sent to the device, the hub will attempt to do so.

We generally do not get directly involved with debugging Custom DTHs, we certainly will try to provide help and guidance, but I have the following recommendation for you to try:

  1. Follow the manufacturer specific guidelines regarding associations, some devices may have different association numbers and behavior for their devices, I would certainly not assume the same number and behavior is followed uniformly across similar devices from different manufacturers.
  2. You can always request the device to send its Associated nodes for a given group back to the DTH, if something is incorrect, I would recommend to ensure that the DTH is sending the right command.
1 Like

@Kianoosh_Karami Thank you for chiming in. While some time ago I managed to get these cooper devices working with ST while using zwave scenes and association. I’m afraid I am totally unfamiliar with the security side of things. Any advice you can give me on updating and improving the DH would be greatly appreciated.

That said. I looked at my recently installed zooz switches that seem to be working fine with the cooper controller. They are all set to Z-Wave Switch Generic device type and report networkSecurityLevel: ZWAVE_LEGACY_NON_SECURE.

@Vik Can you change the DH for the switches that are not working? I’m not sure if that will change the security or not.

The hub should not be involved if the command is being sent via direct association.

Or were you referring to the initial configuration of the association? Meaning the hub is not rejecting the initial attempt to create an association between an S0 device and an S2 device, even though under the current spec it probably should?

Most of the other switches I am controlling with coopers are using the DH Z-Wave Switch and do not report any security. These have been running for a couple of years.
@Vik Try changing up the DH on the switches to see if that gets you going. I plan to make improvements to DH for the new app. I currently do not have the time right now so lets try to figure how to get you up and running.

I’m guessing that if security is the issue the old cooper usb device will be little help to you.

1 Like

I’m not sure how the security thing works. Looking at Viks logs I believe the process of programming the associations into the cooper worked well. That could be checked by reading the association groups with tweaker.

I’m guessing the cooper is talking to the other switches but they are not listening because they are secured and the cooper is not.

1 Like

Yes, that would be my guess as well, but I don’t know for sure. Security would seem to be even more important for these messages since they are not coming from the hub. But looking at the current spec I would expect a compliant S2 hub to give an error message when the initial association was being set up through a hub utility because the trigger device is S0 and the target device is S2. But from what @Kianoosh_Karami said it sounds like the smartthings hub is not screening those “create association” requests.

I don’t know if the switch is smart enough on its own to reject the turn on request later because it’s not at the right security level.

Tagging @TheSmartestHouse

1 Like

While the hub doesn’t interfere in direct association between the devices in the network, it’s the hub that assigns a particular security device level at inclusion. Some hubs will allow the user access to the level of security they want to apply to a given device but as far as we know, SmartThings doesn’t provide this type of access to its users.

Ever since the transition to S2, SmartThings seems to apply the highest possible security level to all devices so it’s possible that if you added some of the Zooz switches a while ago before the transition to S2 had been completed or even initiated, then they were added unsecurely and can be directly associated with other devices with the same security level.

But if a given device is added as a secure device to the network, then it can only be directly associated with other Z-Wave devices in that network with the same security level. That’s partially why we suspect the Z-Wave protocol moved away from direct association as an automation tool, replacing it with hub-friendly commands like central_scene.

There’s nothing on the device side that can be changed to add it with a different security level but the device could be added in the _non_secure mode if initiated by the hub. All Zooz switches support the S2 security and the zwave_legacy_non_secure communication levels.

1 Like

All messages generated from DTHs will be using auto encapsulation, which means that the Hub will apply the highest level of security that was established at join time between the device and the Hub. So if two years ago, you added a S2 device with S0 security (We did not have S2 security enabled then), the hub will continue to use S0 going forward.

If you add a S2 device, but it fails to establish S2 security, the Hub will use the highest level of security available, and if none, the Hub will use unsecured.

1 Like

The hub is not rejecting anything to be sent to the device based on Security, see my previous comment about how Hub handles outgoing messages generated by the DTH.

There are however security related checks made on incoming messages from the device, If a device connected with S2 security sends messages without security, the specification requires the hub to drop these erroneous messages.

1 Like

@Kianoosh_Karami, as a temporary workaround is it possible to force a S2 capable device to join with S0 security (like it would have before the update) if the end user were to choose to do so?

I suspect if what we all think is happening is true, just changing the DTH in this case wont work and the Zooz (or any other device in this boat - like Jasco ZWave + devices) would have to be removed from the network and rejoined with a S0 security level somehow…

1 Like

@sainsworth Good evening, I have tired changing the DH to different types/models, yet made no difference to the security settings. I have removed and re added many different switches, tried different manufacture names before adding them, yet same issue.

@JDRoberts @nathancu @TheSmartestHouse @TheSmartestHouse @sainsworth Thank you guys for chiming in, greatly appreciate all your help here. Really hoping for a solution/temp workaround to get these keypads/switches going with this new security protocol. I came early from work, going to make few more attempts later this evening and i will keep you all posted… until then fingers and toes are crossed.

2 Likes

@Vik
I am now afraid change any of the zooz switches I have for fear they may start using S2 security and no longer work. Unfortunately Eaton does on make a z-wave plus version of this device. I think the only hope is if ST can allow users to force the security off.

You can utilize smart lighting or webcore and use the controller via hub. On off works but no dimming.

1 Like

I suspect the reason that Eaton has not come out with a Z wave plus version of this device where they have with other devices is exactly this: it relies on Association and association changed a lot with zwave plus. If they did do a zwave plus version I would expect it to use central scene commands instead of association.

Clearly the S2 security framework has broken the basic zwave principle of backwards compatibility. I understand why that happened: security features are almost always ones where you want to force people to the newest level. But it does create situations like the one under discussion here.

1 Like

@sainsworth, I added an innovelli and a GE two weeks ago which I KNOW are using S2. I also have a switch to add this weekend. Ill see if I can add it without the QR code and get it to add in S0 mode. I should be able to test all of these scenarios… But doe to my day job, it won’t happen until Saturday at the earliest.

1 Like