03-26-2025 09:25 AM - edited 03-28-2025 06:58 AM
I have 7 Leviton smart switches connected to Ruckus Unleashed, 3x DW1KD, 1x D26HD, 2x DW6HD, and 1x D215P. All of these devices have exactly the same connectivity issues with Unleashed 200.16 and later. All of these devices work perfectly with Unleashed 200.15 and earlier. The connectivity problems are worse with Unleashed 200.16.0.402 and 200.17.7.0.139 than with Unleashed 200.17.7.0.152, but the issue is still present in all Unleashed versions 200.16 and later. I'm testing with access point models R850 and R750, the behavior is the same.
Leviton Firmware
Current firmware versions of the Leviton devices (model number - firmware version):
Unleashed 200.15 and earlier
Leviton switches have no connectivity issues.
Unleashed 200.16.0.402 and 200.17.7.0.139
Leviton switches will initially connect after rebooting the Unleashed system, but will only stay connected for a few minutes to a few hours before disconnecting. Once the Leviton switches have disconnected, they will not reconnect. I've waited days to see if they could eventually recover on their own, but they could not. Rolling back to Unleashed 200.15 permanently fixes the connectivity issues for all of the switches.
Unleashed 200.17.7.0.152
Leviton switches have connectivity issues similar to what I've described for earlier Unleashed releases, but the issues are not as severe. There are two improvements with Unleashed 200.17.7.0.152. First, the switches stay connected much longer, typically hours to days before they lose connection. Second, the switches eventually reconnect on their own after a few hours to a few days. Rolling back to Unleashed 200.15 permanently fixes the connectivity issues for all of the switches.
Client Troubleshooting
I've tried a few things to get these clients to reconnect once they've lost connection with the problematic Unleashed versions:
Following is a screen cap from Unleashed client troubleshooting. It shows one of the Leviton switches after it has lost connection and is trying to reconnect, but cannot. This pattern continues forever and is exactly the same for Unleashed 200.16.0.402, 200.17.7.0.139, 200.17.7.0.152.
Following is a screen cap from Unleashed show details for the same device in the Unleashed client troubleshooting screen cap above. This shows the device during the DHCP negotiation period seen above. The device appears to be unable to acquire an IP address and eventually disassociates itself. I've made no changes to the clients, network, or Unleashed configuration while testing. The only variable has been the Unleashed firmware version that is deployed.