AnsweredAssumed Answered

I don't understand, what the MSE is doing here....

Question asked by spongebobsquarepants on Jan 29, 2014
Latest reply on Feb 13, 2014 by spongebobsquarepants


finally I made it this morning to schedule Presence and Absence for just ONE device (my own) by applying entityFilter. So far so good. Presences was rather accurate, whereas Absence is ****... Scheduled for AbsenceDuration of 2 minutes, AbsenceNotifications just come in after the phone's wifi is off for > 30 minutes or so...


Now I wanted to give ContainmentEvent a try.. What a mess...


What is wrong with this? (private things anonymized)


1) Check for scheduled notifications:


curl -i -k -u <user:pass> -H "Accept: application/json" https:<ip_of_mse>/api/contextaware/v1/notifications -X GET


































Hey, is this just one containment trigger or not?? IMHO, it is...


But what I get is still the same old Presence/Absence notification as scheduled (and deleted) 2 hours ago... Gees, that is so stupid...



"PresenceEvent": {

   "subscriptionName": "all-event-trigger",

   "entity": "WIRELESS_CLIENTS",

   "deviceId": "xx:xx:xx:xx:xx:xx",

   "locationMapHierarchy": "xx",

   "locationCoordinate": {

     "x": 122.52,

     "y": 168.58,

     "unit": "FEET"


   "mseUdi": "xx",

   "geoCoordinate": {

     "lattitude": xx,

     "longitude": xx,

     "unit": "DEGREES"


   "floorRefId": -6048156075595661243,

   "timestamp": "2014-01-29T10:38:34.809+01:00"




Not a trace of a single Containment Notification, as I would expect.


I would suggest to go back to the labs with all that stuff...