Announcement: SPoT 2.4 & vSPoT 1.4 are Available!

[michael_brado]

We are pleased to announce that SPoT 2.4 (cloud based SCG) and vSPoT 1.4 are now Available!
Release Notes, User Guides, SPoT FAQ and vSPoT Installation Guides are posted on Support.

 

1.      
Supported Firmware

This
release is compatible with the following Controller firmware:

·        
ZoneDirector release
9.8 (minimum version 9.8.0.0.369) and above.

·        
RuckOS 3.0 and above
(SZ100, SCG200, vSCG)

2.      
Supported
Pre-Engine API Versions

·        
1.0

·        
2.0

·        
2.1

3.      
Supported
Mobile Devices

The
Calibration app (iOS) has been tested on the following devices:

o   iPhone 5c, 5 and 5s

Supported
OS:

o   iOS 7+

The
Calibration app (Andriod) has been tested on the following devices:

o   Nexus 4 and 5, Samsung S2.

Supported
OS version:

o   Android 4.0+

4.      
SPoT Login
and App Download URLs

a.       Web App URL

The web-based version of the Calibrator App can be
accessed at:

·        
https://us-sys.ruckuslbs.com/calibrator for USA customers.

·        
https://eu-sys.ruckuslbs.com/calibrator for EU customers.

·        
https://sg-sys.ruckuslbs.com/calibrator for Asia customers.

b.      Locator App URL

The URL for the SPoT Locator App is:

·        
https://us-sys.ruckuslbs.com/locator

 

c.       SPoT Login URL

URLs for different regions:

·        
America and rest of world: https://us-sys.ruckuslbs.com.

·        
Asia: https://sg-sys.ruckuslbs.com

·        
Europe: https://eu-sys.ruckuslbs.com

d.      Calibrator App

·        
Calibrator App Quick Start Guide:

§  SPoT
Calibrator App QSG

·        
Calibrator App for iOS:

§  Apple
App Store

·        
Calibrator App for Android:

§  Google
Play Store

 

e.      Software Image Download for
vSPoT 1.4:

The software will
shortly be available for download from the support website.

https://support.ruckuswireless.com/products/76-vspot#firmwares

 

5.      
Enhancements and Resolved Issues in this Release

a.      
System

•       
Added
“Delete” button to SPoT Admin portal, enabling admins to delete a venue.

·        
New
status light to represent time drift for access points page (see Limitations
below for more details). Status light will turn amber if AP time drifts by more
than +/- 5 seconds.

·        
New
Post-Engine API endpoint to retrieve reporting status of access points

·        
Radio
map processing to accept partially opaque children in background.

·        
Allow
creation of multiple zones with same prefix and numbers that correspond to its
floor number e.g. zone1, zone11, zone111.

 

b.     
Venue

·        
Rate
limit by first N number of calculated locations of MUs for a venue (off by
default; can be enabled on a per-venue basis).

·        
Heartbeat
log lines for pas_worker/s.

·        
Resolved
an issue with Voronoi Locator crashes due to corrupted Voronoi cells for some
tessellations in MongoDB.

·        
Collator
will survive intermittent MQTT broker disconnections and maintain persistent
registered topics subscriptions of MGRs and PARs across restarts.

 

c.      
vSPoT

·        
Added
amber status light to assist in troubleshooting NTP time sync issues.

·        
Bug
fixes to enhance stability

·        
The
vSPoT release are mapped to Cloud SPoT releases as shown below –

vSPoT
Release

Cloud
SPoT Release

1.0.0

2.0.0

1.0.1

2.0.0

1.1.0

2.1.0

1.2.0

2.2.0

1.3.1

2.3.1

1.4.0

2.4.0

 

 

6.      
Limitations and Caveats

a.      
System

·        
AP
status lights - The AP status updater process samples reports every minute, or
at the AP reporting interval setting, whichever is higher. This means that the
status lights will only be updated at the same rate reports are being sampled.

When time drift (amber light) is
shown for an access point, this means that the difference in time between a
report being sent out from the access point and the time the venue server
received the report is outside of the acceptable range. While this usually
means that the access point's time is not synchronized with a valid NTP server,
there are various other reasons why this might happen:

·   Network latency is high.

·   An AP is heavily loaded and its system time
drifts. This is because APs prioritize WiFi traffic over other functions.

·   The AP status updater process is running on
a system that is heavily loaded. This is because the system is not able to
process reports in a timely manner. There is a higher chance of this occurring
on an AIO or vSPoT deployment.

b.     
vSPoT

·        
None

 

c.      
Venue

·        
None

[worker_yipst]

question, what is the difference between SPot and vSPoT? 
SPot -> on cloud server? 
vSPot -> on VM? 

is it the only difference?

[michael_brado]

Correct.