The Android PUSH notification issue is caused by Google turning off the C2DM push notification system we use. They have obsoleted the service for all users of c2dm. We are trying to migrate to the replacement GCM (Google Cloud Messaging), but it is not a simple replacement. The server side support needs to be re-written. While the changes in the App should be simple, GCM seems to require newer google frameworks, which break some of the libraries we are using. We are working on it, but Android PUSH notification not working at the moment. Regards, Mark.

On 26 Oct, 2015, at 10:34 pm, Fran Terry <fterry@tesco.net> wrote:

Hi Micheal,

Seems to be an issue with this new version, not geting any notifications from OVMS via IP, not tried this via SMS yet. If I send a command via Andoird App, system sends back reply OK.

Also noticed a possible issue with CFG profile not applying before each trip.

Currently have feature #14 set to 0, however also tried with 64.

Any ideas?

Thanks

Fran

On 03/10/2015 17:49, Michael Balzer wrote:

...

Package: http://dexters-web.de/f/tw/OVMS-Twizy-3.6.1.zip <http://dexters-web.de/f/tw/OVMS-Twizy-3.6.1.zip>

Changes: see tag "V3.6" in the user guide

Framework V2.7.4: - New compiler switches to disable framework functions: OVMS_NO_CHARGECONTROL OVMS_NO_CTP OVMS_NO_SMSTIME OVMS_NO_VEHICLE_ALERTS (all need to be set for Twizy build) - Potential buffer overflow fix in net_msg_forward_sms() - Fix stp_l2f() for negative values - Fix SMS MSG wrapper for long commands

Framework V2.8.1: - Make COPS more lenient - Support GPRS DNS

Twizy V3.6.0: - New: All power values now based on real battery power (current * voltage) - Battery current sums + min/max moved to separate fields - STAT command extended by grid energy drain estimation - RT-GPS-Log extended by BMS limits, auto power levels and battery current min/max - RT-PWR-Log extended by battery coulomb counts (Ah) - "RT-PWR-UsageStats" is now "RT-PWR-Stats", fields reordered and units converted (to save space), coulomb count discharge/charge sums added (Ah) - Rework & bug fixes in auto power adjustment - Auto RECUP power adjustment extended by 100% reference power (ATT: CFG RECUP parameters changed!) - New: auto DRIVE power adjustment (ATT: CFG DRIVE parameters changed!) - New: CFG CLEAR = clear SEVCON diagnostic logs - Now using GSM time (NET_FN_CARTIME) for more accurate parking times - New: feature #14 & 64 = send notification on charge starts - Fixed charge time estimation for SOC > 94% - ISR performance optimization - car_SOC no longer rounded to avoid 99.5% == 100% - Trip end odometer saved & used for RT-PWR-Log charge entries - Fixed auto power minprc calculation with default (-1) - Fixed auto power calculations for default minprc values - Changed auto recup level to scale levels configured - car_SOC no longer rounded to avoid 99.5% == 100% - Trip end odometer saved & used for RT-PWR-Log charg

Twizy V3.6.1: - Fix: battery alert state also remembered for IP notification - Fix: compiling without OVMS_TWIZY_CFG - ideal range calculated with temperature influence approximation - Battery capacity estimation - Charge start restarts SOC window (to get most recent BMS SOC) - Charge interruption no longer restarts power sums & SOC window

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk <mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Thanks, I should of been reading the C2DM thread! Thanks Fran ----- Original Message ----- From: "Michael Balzer" <dexter@expeedo.de> To: ovmsdev@lists.teslaclub.hk Sent: Tuesday, 27 October, 2015 8:59:50 AM Subject: Re: [Ovmsdev] Twizy release 3.6.1 SMS notifications are not affected. If you don't want the trip reports to be sent, add 16 to feature #14. Regards, Michael Am 27.10.2015 um 01:47 schrieb Mark Webb-Johnson: The Android PUSH notification issue is caused by Google turning off the C2DM push notification system we use. They have obsoleted the service for all users of c2dm. We are trying to migrate to the replacement GCM (Google Cloud Messaging), but it is not a simple replacement. The server side support needs to be re-written. While the changes in the App should be simple, GCM seems to require newer google frameworks, which break some of the libraries we are using. We are working on it, but Android PUSH notification not working at the moment. Regards, Mark. <blockquote> On 26 Oct, 2015, at 10:34 pm, Fran Terry < fterry@tesco.net > wrote: Hi Micheal, Seems to be an issue with this new version, not geting any notifications from OVMS via IP, not tried this via SMS yet. If I send a command via Andoird App, system sends back reply OK. Also noticed a possible issue with CFG profile not applying before each trip. Currently have feature #14 set to 0, however also tried with 64. Any ideas? Thanks Fran </blockquote> -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev