RUCKUS One IoT Integration: Transitioning to Profile-Based Configuration

The integration introduces profile-based RUCKUS IoT controller configurations, allowing you to select a predefined RUCKUS IoT Controller profile from RUCKUS One.

Feature Overview

Prior to the availability of profile-based RUCKUS IoT controller configurations, the RUCKUS One IoT integration required manual configuration of the IoT environment at both the venue and access point (AP) levels. You had to manually enter the IP address or Fully Qualified Domain Name (FQDN) of the MQTT broker that the IoT devices would communicate with, meaning that for every venue and each associated AP, the MQTT broker details had to be individually configured.

The RUCKUS One IoT integration introduces two functional enhancements:
  • The IoT Controller can be added as a gateway device within your RUCKUS One account, supporting centralized management and venue/AP association.
  • IoT Controller configuration at the AP level is streamlined by your associating an IoT Controller configuration profile at the venue level.

With this enhancement, you can define an IoT profile that includes key settings such as the MQTT broker IP/FQDN and other related parameters. Once the profile is created and assigned to a venue, RUCKUS One automatically applies the corresponding configuration to all associated access points without requiring manual input at each location. The shift from manual configuration to automated, profile-driven deployment represents a significant advancement in simplifying and scaling IoT management within the RUCKUS One ecosystem.

Requirements

This feature is supported on the following:
  • For RUCKUS One APs, ensure the AP firmware version is 7.1.0.510.1005 or later.
  • The virtual RUCKUS IoT (vRIoT) Controller running firmware version 2.4.0.0 or later.
  • RUCKUS APs with the RUCKUS IoT Module installed.
  • For T670 APs, ensure the AP firmware version is 7.1.1.520.675 or later.
  • RUCKUS One managed venues having IoT-enabled APs.

Considerations

Consider the following when configuring and using this feature:
  • The RUCKUS One Gateway menu option includes an IoT Controller sub-option, supporting adding, viewing, editing, and deletion of IoT Controllers.
  • The RUCKUS One Dashboard includes IoT Controllers in the Devices tile, displaying the number of IoT Controllers added to the tenant account.
  • The venue-specific Devices tab contains an IoT Controller sub-tab, displaying the status and configured FQDNs / IP addresses for the associated IoT Controller(s).
  • The RUCKUS One Venues includes IoT Controller column, which indicates the number of IoT Controllers associated with the venue or its access points (APs).
  • The AP-specific configuration-mode Network Control tab contains an IoT Controller section, displaying the associated IoT Controller and supporting your customizing the settings.

Best Practices

This feature has no special recommendations for feature enablement or usage.

Prerequisites

Before implementing this feature, ensure the following prerequisites are met:
  • The virtual RUCKUS IoT (vRIoT) Controller has been installed on a hypervisor.
  • You have the required credentials to log in to the RUCKUS IoT Controller.
  • You have the FQDN or IP address of the RUCKUS IoT Controller.
  • You have obtained the valid API key for the RUCKUS IoT Controller.
  • The RUCKUS IoT Module is installed on the required RUCKUS APs.
  • Your RUCKUS One account has enough device networking licenses available; each IoT Controller added to RUCKUS One consumes 1 license.