Solved: RUCKUS Forums - Re: jbl 500 authentics connection problems - Page 4

jp · ‎02-11-2026

Hi pack ;-),

I ran into a problem with connecting a jbl 500 authentics speaker to Ruckus Unleashed (latest available version) on an R320: I can connect it to a WLAN set up without a password, but as soon as I set up WPA2, WPA3 or WPA2/3 combined it won't connect any more (the setup app simply stays with the message "connecting...". All attempts to reset the speaker, delete the WLAN, etc. failed.

Any ideas on this? My falback now is to have an open WLAN which just allows one client, but obviously this is far from an ideal solution. I also failed with setting up MAC access control, it won't connect either.

Cheers, Joachim.

sanjay_kumar · ‎02-18-2026

Hi,

Could you try the below steps which was having similar issue with Sonos speaker>
We have the fix applied in later version, 200.15 is the last version supported for R320.

But try this workaround from CLI and check.

https://community.ruckuswireless.com/t5/RUCKUS-Support-for-Lennar-Homes/Cannot-connect-Sonos-wireles...

View solution in original post

Imran_ruckus · ‎02-19-2026

Hi @jp

Greetings!

Thank you for your response and the update.

Execute Configuration Commands

Once the upgrade is complete, please proceed with the following steps:

Run the following commands:
(Please replace “your Wi-Fi name” with your actual Wi-Fi/SSID name, enclosed in double quotes if it contains spaces)

ruckus> en

ruckus# config

ruckus(config)# wlan "your Wi-Fi name"

ruckus(config-wlan)# no qos directed-multicast

ruckus(config-wlan)# qos directed-threshold 0

ruckus(config-wlan)# end

ruckus(config)# end

This configuration may help resolve the issue.

Here’s an example of PuTTY command line output from my lab for reference: (Bold fonts are commands to execute)

login as: admin

Please login: admin
Password:
Welcome to Ruckus Unleashed Network Command Line Interface
ruckus> en
ruckus# config
You have all rights in this mode.
ruckus(config)# wlan "Your Wi-Fi Name"
The WLAN service 'Your Wi-Fi Name' has been created. To save the WLAN service, type 'end' or 'exit'.
ruckus(config-wlan)# no qos directed-multicast
The command was executed successfully. To save the changes, type 'end' or 'exit'.
ruckus(config-wlan)# qos directed-threshold 0
The command was executed successfully. To save the changes, type 'end' or 'exit'.
ruckus(config-wlan)# end
The WLAN service 'Your Wi-Fi Name' has been updated and saved.
Your changes have been saved.
ruckus(config)# end
Your changes have been saved.
ruckus# ap-mode
You have all rights in this mode.

Once done with the commands, please reconnect and check.

Please let me know how it goes.

Thank you once again for your patience and cooperation.

Best regards,
Imran Sanadi
RUCKUS | Community Support Forums

View solution in original post

Imran_ruckus · ‎02-23-2026

Hi @jp

Thank you for your response.

Yes, that may be the issue related to the JBL connectivity/encryption.

We truly appreciate your time and patience throughout this case.
Thank you once again for reaching out to the RUCKUS Lennar Home Community.

Should you have any further questions or need assistance in the future, please don’t hesitate to contact us.

Wishing you a wonderful day ahead!

Best regards,
Imran Sanadi
RUCKUS | Lennar Home Community Support

jp · ‎02-23-2026

Thanks for help! Btw, I forgot to mention: With the recent settings the app that is supposed to connect the box to WLAN is stuck with the message "connecting"; before it came back with "connection failed". So, something is indeed different.

Imran_ruckus · ‎02-23-2026

Hi @jp

Thank you for the response and the update. That behavioral change is actually helpful information.

At this stage, the behavior points toward a compatibility limitation in the device’s WPA2 implementation rather than an issue with the Unleashed configuration.

I would recommend checking for any available firmware updates for the JBL speaker or confirming with the vendor whether WPA2-PSK (AES) with standard 802.11 settings is fully supported.

From the RUCKUS side, no additional CLI modifications are required, and the WLAN configuration currently follows standard compatibility settings for IoT devices.

Thank you again for your patience and understanding.

Best regards,
Imran Sanadi
RUCKUS | Community Support Forums