When a device is seen but does not have a location this indicates the device has joined the Wi-Fi network but a location update was not sent or persisted for the device. One cause is the device is not using the CMX Mobile SDK or the CMX Mobile SDK for the device has not registered with the Mobile Application Server. Not until the device has registered with the Mobile Application Server will a device location be tracked. This filters out devices to those using the CMX Mobile SDK for tracking. Other devices will not be tracked to reduce load. This is one cause for the missing location updates. The unauthorized message seen could be another cause. The message could be the result of the MSE and CMX Connect and Engage not in sync with the maps being used. In CMX Connect and Engage is an option to sync and update the maps from PI. Clicking this will sync the maps again.
... View more
This has to do with the number of minutes before the Mobile Application Server will send a push notification again. By default when a user enters a zone another push notification will not be sent for that user again for 60 minutes. This can be adjusted in a properties file: /opt/cmx-mobile-app-server/apache-tomcat/webapps/cmx-cloud-server/WEB-INF/classes/config/settings.properties has an entry: # Number of minutes before sending a push notification for entering a zone again location.minutesBetweenSendingNotification=60 You can lower that number down to 1. I would suggest not lower than 1 so push notifications are handled properly in case the user bounces around a zone. After changing the setting you will need to stop and start the server: /etc/init.d/cmx-mobile-app-server stop /etc/init.d/cmx-mobile-app-server start The changes should be picked up on restart.
... View more