We are currently using CMX to track the location of product moving through our manufacturing plant. Our in-house apps rely on an older location tracking solution to get XY coordinates, map images, and zone information. We hope to replace the old solution with CMX. The difficulty we are noticing is the disappearing of tags and their information from CMX when we make calls to the API. If we make a call early in the day and then later, we may see no information at all for that tag.
What is the best way to get these location updates so our in-house apps can get the most recent coordinate for a searched tag? I have seen mention of push notifications but we have thousands of tags in our environment which could build into a pretty large db.
The issue is really due to the design; devices not in motion do not get updated location, and if not updated within certain amount of time are dropped from active table. Secondly, CMX BU say there is a tag component, where in some cases a static tag stops probing. Please see the blog post:
CMX Detect & Locate service uses the data provided by Cisco WLCs to calculate location of wireless devices that are detected by the access points that support the wireless LAN. The Cisco CMX GUI will display the physical location of Active WiFi RFID Tags, and you can setup notifications for tag location updates and stream notification for RSSI tag.
For more information about Cisco compatible tags see the Design Zone for Mobility - Design Guides - Cisco
and WLC Configuration Guides Cisco Wireless Controller Configuration Guide, Release 8.3 - Cisco
CMX BU would like to deprecate the stream notification service for RSSI tags by relying on REST API fill need/requirement.
By deprecate, they mean to just remove support for it. Information has already been removed it from the reference guides, etc., and the only support is on a case by case basis.
The partnerStreamNotification resource with listener/parser is given to CMX partners. Data depends on a java library which the BU CMX folks will provide.