Page 1 of 1

Cookie-Data not synchronous with sen.se

PostPosted: Tue Jul 12, 2016 2:49 pm
by Nine
Hi Karl

I do have one cookie which shows "present" even sen.se knows, that the cookie is absent (the app says cookie is absent).
Reset ALL in indigo plugin does not help. Delete the cookie does not help... Is it possible, that sen.se delivers wrong data in the api? how can I check that?

Indigo debug:

Code: Select all
 updateIndigo.... Presence Caro Presence {u'lastStatusChange': '2016-07-12 13:51:03', u'used': True, u'uid': u'X4MKFXYtKpbBqnGENFBm6ShIGeW0d3dL', u'lastEventSeconds': 1468324263.0, u'url': u'https://apis.sen.se/v2/feeds/X4MKFXYtKpbBqnGENFBm6ShIGeW0d3dL/events/', u'type': u'presence', u'lastTimeTest': 1468355737.7082951, u'queryWait': {'Absent': u'4', 'Present': 60}, u'ignore': False, u'addWait': 60, u'data': {u'body': u'Present', u'code': 200}, u'payload': '2', u'subscription': u'RxsTFMVIrYGAkR90NP0LFyNPVuItFjnI'}
  updateIndigo.... Presence Caro Presence updating LastEventDate 2016-07-12 13:51:03


13:51:03 was indeed the last time, this cookie was present.

Nine

Re: Cookie-Data not synchronous with sen.se

PostPosted: Tue Jul 12, 2016 9:17 pm
by kw123
sorry just saw this.

do you use pull or push?

if push switch to pull just for 5 minutes (might need to restart) then back to push.

if you use pull do the other way around.

If you use push you can find a log file in ~documents/mother/webserver.log

you will see the push messages in clear text .

check out the address number an see if any message with number appear - if you open the log file console log viewer will open it . you can set a filter to right for that number .
I guess that number is X4MFK...



and if it states: LastEventDate 2016-07-12 13:51:03 then that is the date of the last message received .

must be a bug I guess

Karl

Re: Cookie-Data not synchronous with sen.se

PostPosted: Thu Jul 14, 2016 3:14 pm
by Nine
well... I switched from pull to push and back... changed API-key... and the next morning it went fine :-)

Will consult the specific log file next time it happens.

Simon