Michael,

Server logs for PUSH notifications:

2012-11-20 14:52:21.050617 -0500 info  main: #37 C DEXZE85 rx msg P ACharging, Topping off
2012-11-20 14:56:13.216180 -0500 info  main: #37 C DEXZE85 rx msg P ACharging, Topping off
2012-11-20 15:28:37.549081 -0500 info  main: #37 C DEXZE85 rx msg P ACharging, Topping off
2012-11-20 15:40:48.776406 -0500 info  main: #80 C DEXZE85 rx msg P ACharging, Topping off Range: 46 - 66 km SOC: 83% (8194 - 8302) ODO: 3730 Km
2012-11-20 16:00:15.659214 -0500 info  main: #53 C DEXZE85 rx msg P ACharging, Topping off Range: 51 - 74 km SOC: 93% (8696 - 9304) ODO: 3730 Km

Times are EST.

Regards, Mark.

On 21 Nov, 2012, at 5:25 AM, Michael Balzer wrote:

Am 20.11.2012 20:47, schrieb Michael Balzer:
I'm currently charging my Twizy to see if the alert is functional now.

Ok, this is getting strange now... everything else works, calling cmd 6 in diag mode, SMS alerts etc., just the App wouldn't alert me. I found a "PA" entry in the Apps "TCP log" output that was cut down to the charge state line, so I thought maybe it's the "\r\n" I had put into the alert text to structure it.

I removed all of the line breaks and the first two alerts again did not come through to the App -- but the third one just did, in perfect shape!?

But for that one I now do not find any TCP log entry... is the Android App reliable concerning the TCP log function?

Mark, I'm stuck. Could you please check the server log for this? Vehicle name now is "DEXZE85".

Thanks,
Michael

-- 
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
<dexter.vcf>_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev