Plume makes regular updates to the cloud in order to add new features and fix issues. Most updates do not have a visible impact on the behavior of your network and new features often require updates to the Plume app for you to access them.
The updates listed below are changes that you may see affect the behavior of your network.
_______________
The following updates have been made to the Plume cloud as of May 5th, 2020 (version 1.56):
- New: Updated device type display name logic to use Host names for Windows and Android systems when available.
- New: Optimizer now uses the reported channel gain/SNR to select topology without factoring the power/noise level per device model
- New: Ability for support to initiate at any time a speed test with a specific OOKLA server ID
- New: Multicast to Unicast conversion on Wifi Interface for wireless IPTV use cases
- New: Data for tracking connectivity stats per client per band
- New: If there is an established network uplink via DHCP, IGMP Proxy Configuration will forward join and other IGMP frames from the LAN into the uplink WAN and forward the returned multicast stream into the customers LAN, (PPPoE for uplink not covered)
- New: Allow wifi stack to continue operation on main channel and at the same time run background CAC (Channel Availability Check
- New: Motion & People at Home Push Notifications loc-keys enhancement
- New: Network overview related metrics and Data is being sent to regional Plume servers in production for improved health monitoring.
- New: Allow Interference improvements thresholds (at least for GW only locations) to be runtime configurable
- New: Enhance the Interference improvement thresholds for low interference single Gateway pod locations
- Fixed: Customer API was allowing blank ipv4 and ipv6 DNS addresses and was passing through to controller which was causing the locations to not initialize correctly and was preventing them from coming online.
- Fixed: proxy was configured on the wrong interface.
- Note: Additional new features and improvements of this build are targeted for our ISP partners and support.
The following updates have been made to the Plume cloud as of March 25th, 2020 (version 1.54):
- New: Allow users to override IPv6 DNS servers with custom ones.
- New: When a location with multiple hardware types are configured as gateways, Plume will prefer designating SuperPods as the master gateway to enforce proper feature capabilities.
- New: Allow controller to enable/disable backhaul based on the location’s configuration.
- Fixed: Increase HTTP client buffer size to avoid timeouts during surge of outgoing queries to controller (usually in nightly optimizations).
- Fixed: Model name and version persistence when a node connects.
- Fixed: Issue with People at Home push notifications not being sent to the app and Plume Motion alerts arming/disarming occurring when there is a People at Home change.
- Fixed: Reduced load on database due to IP Threat queries.
- Fixed: Resolved regression in 1.53 where optimizations would not always select the strongest links between nodes, which led to failed optimizations.
- New: Added API health check for Plume Motion services.
- Note: Additional new features and improvements of this build are targeted for our ISP partners and support.
The following updates have been made to the Plume cloud as of February 25th, 2020 (version 1.53):
- New: Added support for Plume Motion capabilities.
- New: Added support for Home Away capabilities.
- New: If a firmware upgrade fails, GW nodes wouldn’t upgrade until rebooted. The cloud will now schedule a “no pods left behind” check during the maintenance window to re-upgrade the GW node. Checks will be randomized across the whole maintenance window to avoid peaking.
- New: All steering events data will now be written to Plume’s database in raw format and the stats will be calculated offline instead of inline in data pipeline. This resolves occasional incorrect stat calculations.
- New: Plume Cloud API now supports Japanese translations for email verification, password reset, and API validation messages.
- New: Optimizer improvement to penalty logic for link deployment failures in order to prevent multiple failed optimizations when the node is too far from the target node connection. Minimum signal to noise ratio will be more conservative and failure counts will apply to the whole band in order to increase optimization robustness in this case.
- New: Fix to ensure correct device icon shows on Plume app when device category is unavailable.
- Fixed: Cache last access zone for disconnected clients to prevent Guest and Internet Only devices from appearing in the wrong category.
- Fixed: Change IPv6 Prefix table flag for autonomous from ‘false’ to ‘true’ when mode is ‘ALL’.
- Fixed: Remove duplicate rows from a partner’s proprietary device freeze functionality in controller.
- Fixed: After factory reset, DHCP reservation used old network settings (Specific for an ISP Partner).
- Fixed: Adds capability to dynamically change log levels at the location/node level. This allows debugging a location without having logs be too verbose.
The following updates have been made to the Plume cloud as of January 30th, 2020 (version 1.52):
- New: Always fallback to default client steering profile if a custom device type profile is not found
New: Introduce integration plug in to Advanced IoT Protection for increased accuracy - New: Internal feature flag added and use DeviceType API
- New: (OpenSync) Change CODA-4582 init condition from wan-ip to radios.
- New: (OpenSync) Change UBC1322 init condition from wan-ip to radios
- New: (OpenSync) Optimization of device type syntax
- Fixed: (OpenSync) ICMPv6 packets are dropped when traversing CT. This causes Neighbor Discovery protocol (ICMPv6) to not work on occasion.
- Fixed: DeviceType Healthcheck reports incorrect failure counts
- Fixed: DeviceType fails to reload DeviceDetector models
- New: APIs for support personnel to better support GDPR requests
- Note: Additional new features and improvements of this build are targeted for our ISP partners.
The following updates have been made to the Plume cloud as of December 17th, 2019 (version 1.50.1):
- New: Set IPv6 prefix on_link state to true by default.
- New: Remove DHCP option 26 from DHCPv6_Server.
- New: Optimizer to skip the 2.4 GHz channel assignment for clients -5 GHz-only locations when the 2.4 GHz band is missing in the original topology.
- New: Remove DHCP option 26 from DHCPv6_Server.
- Fixed: Missing preferred and valid lifetime in IPv6_Prefix table.
- Fixed: Devices classified incorrectly as Home devices when they are Guest zone.
- Fixed: Can not buy pods from app.
- Fixed: Support activating DFS mode backhaul only disables DFS completely.
- Fixed: Device typing issue for IPv6 only clients
- Fixed: Controller does not properly resend the Openflow Rules if it fails
- Fixed: Inbound IP Threat detection doesn't work reliably due to Openflow Rule issues.
- Note: Additional new features and improvements of this build are targeted for our ISP partners.
The following updates have been made to the Plume cloud as of October 16th, 2019 (version 1.47.0):
- New: Allow user to override Ipv6 DNS servers with custom ones
- New: Mobile Alerts are aggregated into a single notification when multiple intrusion attempts are detected.
- Improved: Improved statistics and graphs for support personnel.
- Fixed: 802.11k -Speculative kick takes 5-6 minutes to get the result, which causes the following directed kick to be ignored.
- Fixed: Issue with device typing API not returning proper device category.
- Note: Additional new feature and improvements of this build are targeted for our ISP partners
The following updates have been made to the Plume cloud as of September 11th, 2019 (version 1.46.0):
- Fixed: Speed test metrics not being available for support personnel
- Fixed: QoE stats displayed incorrect number of hops for support personnel
- Fixed: Back off period for Client Steering not expiring for client devices with a high Frequency of trouble events.
- Fixed: Speculative kick being issued even if the client is already probing.
- Fixed: Icons not always updated after being typed.
- Fixed: IOT devices attempting to open too many connections when Frozen.
- Fixed: Speculative kick being issued even if the client is already probing.
- Fixed: Restarting controller disables Iot Device IP FlowStats.
- Note: Additional new feature and improvements of this build are targeted for our ISP partners
The following updates have been made to the Plume cloud as of September 5th, 2019 (version 1.45.1):
- New: API for Subscription Changes
- Improved: Improved QoE device typing and capability reporting for support personnel.
- Fixed: Redirector lookups get into retry loop.
- Fixed: Empty Band and Client steering events table not populating for support personnel
- Fixed: IP-Threat detection is not getting enabled on the pod in some instances.
- Note: Additional new feature and improvements of this build are targeted for our ISP partners
The following updates have been made to the Plume cloud as of August 22nd, 2019 (version 1.44.1):
- New: Ipv6 LAN DHCP added support to disable configuration
- New: Added enforcement to custom DNS settings that prevents users from specifying two of the same DNS servers.
- Improved: Updated QoE metrics and improved calculations for Support personnel.
- Improved: Changed interference calculation per location based on the busiest time frame to improve optimizations.
- Fixed: Device Freeze fixes including: using timezone based on GeoIP, instead of defaulting to Pacific and scheduler for SCHOOLNIGHTS at client level does not actually freeze client.
- Fixed: Scheduled upgrades not starting on time because Customer API for Controller initialization did not include timezone.
- Fixed: Node connections unstable as Optimization keeps failing on firmware 2.4.1-23
- Fixed: Remove category 50 or whitelist youtube.com for Adultandsensitive filter
- Fixed: Frozen devices reporting DNS Queries to Anomaly Detector even though not under Advanced IoT Protection
- Fixed: Bandwidth Usage on pod shows different values than Bandwidth Usage for device
- Fixed: High Client Steering Trouble events per client, no expiry of backoff period.
- Note: Additional new feature and improvements of this build are targeted for our ISP partners
The following updates have been made to the Plume cloud as of July 31st, 2019 (version 1.43.1):
- Improved: Improved failed optimization reporting sent to support.
- Improved: Improved QoE device typing and capability reporting for support.
- Fixed: Device Freeze fixes including using timezone based on GeoIP, instead of defaulting to Pacific.
- Fixed: Pod and device Health now being displayed correctly in the app.
- Note: Additional new feature and improvements of this build are targeted for our ISP partners
The following updates have been made to the Plume cloud as of May 20th, 2019 (version 1.41.1):
- New: Limited the number of pods that can be associated to a single packID.
- New: Client device rapid reconnect events are reported.
- New: 15 minute storage policy implemented for Realtime Insights.
- Improved: Improved onboarding analalytics being sent to support.
- Fixed: Adblocking is no longer deleted is the Adolescent Content Access policy is implemented by support.
- Note: Additional new feature and improvements of this build are targeted for our ISP partners
The following updates have been made to the Plume cloud as of May 11th, 2019 (version 1.39.5):
- Note: This build is primarily targeted for our ISP partners
- Improved: Improved user experience for Advanced IoT Protection
- Fixed: Devices are now removed from quarantine if Advanced IoT Protection is disabled at the location level
The following updates have been made to the Plume cloud as of April 10th, 2019 (version 1.38.3):
- Note: This build is primarily targeted for our ISP partners
- Improved: Improved accuracy of metrics available to support personnel to assist with troubleshooting.
- Improved: Use IP instead of DNS name for controller manager address.
The following updates have been made to the Plume cloud as of March 19th, 2019 (version 1.37.4):
- New: Support for advanced IoT Protection features added.
- Fixed: Device Typing issue caused by devices missing certain features
- Fixed: Improved accuracy of reasons for blocked websites in Secure and Protect
- Fixed: Swipe action for unblocking websites in app
The following updates have been made to the Plume cloud as of February 19th, 2019 (version 1.36.3):
- New: Off channel scan toggle based on hardware model
- Fixed: Bug that causes anomaly detection to fail to initialise
- Fixed: Bug that causes Amazon device OS detection issue
- Fixed: Device Typing issue causing inconsistent naming of Roku 4 4400X
- Fixed: Improved device typing of LiFX Color 1000 light bulb
The following updates have been made to the Plume cloud as of January 21st, 2019 (version 1.35):
- New: Sticky 11v kick contains the recommended neighbor list
- New: Include loop parameter into Ethernet dry run check
- Fixed: Home AP active on both 5GU and 5GL
- Fixed: Optimizations potentially getting stuck after link expiry
The following updates have been made to the Plume cloud as of December 18th, 2018 (version 1.34):
- New: Support for IGMP Snooping auto mode
- New: Add controller support for UPNP sniffing and IGMP
- Improved: Change to location-level approved/blocked website logic applies to people/devices
- Improved: Enable DNS based Device Typing
- Fixed: DeviceType failing to startup due to missing private IP
The following updates have been made to the Plume cloud as of October 29th, 2018 (version 1.32):
- New: Implemented minimum firmware version for onboarding (2.2.0-30 / 1.0.0-30)
- Fixed: Bug that causes Speed Test to occasionally fail to complete
- Fixed: Bug that prevented setup of custom Device Freeze schedules
The following updates have been made to the Plume cloud as of September, 2018 (version 1.31):
- New: Ethernet backhaul support when Network is in Router Mode
- Improved: Removed client traffic from interference calculations to reduce unnecessary optimizations and improve effectiveness of overnight optimizations
- Improved: Added the ability to blacklist a website, without the need for content filtering to be enabled.
The following updates have been made to the Plume cloud as of September, 2018 (version 1.30):
- New: Support for content filtering and parental control
- Improved: 802.11kv steering sends neighbor lists required by Android devices for proper steering
- Improved: New device typing improvements
- Improved: Gain threshold settings adjusted to improve weak links
The following updates have been made to the Plume cloud as of Jul 31st, 2018 (version 1.28):
- Improved: Device typing accuracy has been improved
- Fixed: Device freeze issues with School Night, Bedtime, and custom end times
The following updates have been made to the Plume cloud as of June 30th, 2018 (version 1.27.2):
- New: Networks that are constantly using more than 10 Mbps will now be treated as being idle (less than 10 Mbps being used) after 4 days, so that optimizations and ISP speed tests can be run.
- Fixed: Speed test scheduling will no longer get stuck.
The following updates have been made to the Plume cloud as of April 9th, 2018 (version 1.23.2):
- Fixed: Bug causing optimization notifications to continue to report as in progress when the optimization has been completed.
- Fixed: Bug that causes Pod health status not to display correctly
The following updates have been made to the Plume cloud as of March 13th, 2018 (version 1.22):
- New: The LED on the Pods will only start to blink when topology changes start during an optimization. This stops the LED from blinking while the Pods wait for the cloud to finish calculating the new topology
- Improved: Optimizations will not change channels for small improvements in topology. This is to avoid disturbing connected devices
- Improved: Enhancements in the optimization process that will now retry failed links
- Improved: Enhancements in Client Steering that will improve user experience on Static Devices
- Fixed: Correctly report network status when it is in bridge mode
The following updates have been made to the Plume cloud as of Jan 29th, 2018 (version 1.19):
- Available now: Additional information provided when sending a network password via text, email, etc.
- Available with future app update: Freeze each device based on a template that applies only to that device.
- Fixed: Devices will now correctly report as ‘Online since…’ when viewing the device grid.