January 2024 - OvmsDev - Open Vehicles

Warning in Duktape
by Michael Geddes 09 Aug '24

09 Aug '24

There's an unused variable 'dcc' warning in the below code. It seems that the 'Perform the callback' is not being 'performed! Is this deliberate? //.ichael void DukOvmsCommandRegisterRun(int verbosity, OvmsWriter* writer, OvmsCommand* cmd, int argc, const char* const* argv) { ESP_LOGD(TAG, "DukOvmsCommandRegisterRun(%s)",cmd->GetName()); auto it = MyDuktape.m_cmdmap.find(cmd); if (it == MyDuktape.m_cmdmap.end()) { ESP_LOGE(TAG, "Command '%s' cannot be found in registry",cmd->GetName ()); return; } else { DuktapeConsoleCommand* dcc = it->second; // Perform the callback } }

3 6

Firmware release 3.3.004
by Michael Balzer 17 Mar '24

17 Mar '24

Mark & everyone, there are new feature extensions in the pull request queue, i.e. poller timing control by Michael Geddes & a new MG5 model variant by Peter Grey. I'd rather close 3.3.003 now and release the current state as main 3.3.004 before merging new features that again would need testing. A new main release is overdue, and the latest fixes by Michael Geddes did improve stability significantly. I haven't had a single crash with 3.3.003-621 yet. Objections? Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

5 9

wolfssl has been converted to a git submodule
by Ludovic LANGE 19 Feb '24

19 Feb '24

Dear all, The PR https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pull/887 which converts wolfssl to a git submodule has been merged to master. For those that build / sync their trees manually, please ensure that you do `git submodule update --init --recursive` after the git pull, so that you can properly retrieve the submodule. You can confirm that everything is OK by doing: $ git submodule status 7b953e7ebb440ce9461ee469159c3759450e7c98 components/mongoose/mongoose (6.2-882-g7b953e7) c05f6c7530a8670e3d0ffdf04ee4cecb2d3b0496 components/wolfssh/wolfssh (v1.4.10-stable) 2d5a0ccae50a2ea32fc933d707b465520cc90011 components/wolfssl/wolfssl (v4.7.0-stable-5-g2d5a0ccae) 7c3878f8302c0e84578a67473e49e60bc6b3ada7 components/zip/libzip (rel-1-5-1-60-g7c3878f) d6bcf4ca4d02479f058fff44cfd171f928148179 components/zip/zlib (v1.2.11-65-gd6bcf4c) It should print (3rd line) a version of v4.7.0-stable-5-g2d5a0ccae. If instead you see: $ git submodule status 7b953e7ebb440ce9461ee469159c3759450e7c98 components/mongoose/mongoose (6.2-882-g7b953e7) c05f6c7530a8670e3d0ffdf04ee4cecb2d3b0496 components/wolfssh/wolfssh (v1.4.10-stable) -2d5a0ccae50a2ea32fc933d707b465520cc90011 components/wolfssl/wolfssl 7c3878f8302c0e84578a67473e49e60bc6b3ada7 components/zip/libzip (rel-1-5-1-60-g7c3878f) d6bcf4ca4d02479f058fff44cfd171f928148179 components/zip/zlib (v1.2.11-65-gd6bcf4c) then you need to use `git submodule update --init --recursive` Let me know if it's not working according to the plan. Regards,

3 3

Re: [Ovmsdev] Messages stopped being received on phone
by Derek Caudwell 27 Jan '24

27 Jan '24

Hi Michael, Greg Fyi, it looks like my messages also stopped on the 8 Jan GMT, I'm on Android 12 OVMS app version 4.1.2. On Fri, 26 Jan 2024 at 14:35, <ovmsdev-request(a)lists.openvehicles.com> wrote: > Send OvmsDev mailing list submissions to > ovmsdev(a)lists.openvehicles.com > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.openvehicles.com/mailman/listinfo/ovmsdev > or, via email, send a message with subject or body 'help' to > ovmsdev-request(a)lists.openvehicles.com > > You can reach the person managing the list at > ovmsdev-owner(a)lists.openvehicles.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of OvmsDev digest..." > > > Today's Topics: > > 1. Re: Messages stopped being received on phone (Michael Balzer) > 2. Re: Working on ESP-IDF5 + Have a question about ovms_module > 'Name' (Michael Geddes) > 3. Re: Working on ESP-IDF5 + Have a question about ovms_module > 'Name' (Mark Webb-Johnson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 25 Jan 2024 19:55:40 +0100 > From: Michael Balzer <dexter(a)expeedo.de> > To: ovmsdev(a)lists.openvehicles.com > Subject: Re: [Ovmsdev] Messages stopped being received on phone > Message-ID: <93610d48-1492-4ca8-b3ff-1adee6c75ee0(a)expeedo.de> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Greg, > > 8th of January matches our preparation steps for the Firebase messaging > migration. > > But that to my knowledge didn't involve any change to the server yet, > and should only have added the Firebase instance to the Google cloud > account without disabling the old GCM. > > Also? if it was an issue of the server / Google cloud, there certainly > would be other users affected. > > I assume you didn't install the beta test App build yet? That could be > worth a try. The new build works with both the old & new server API. > Google wrote the old Android APIs would continue to work until June, but > maybe that was too optimistic? > > Regards, > Michael > > > Am 25.01.24 um 00:22 schrieb Greg D.: > > Hi folks, > > > > I recently noticed that Alerts (Messages) have stopped coming to my > > phone.? The last one was on 8-January '24.? The car is still operating > > / charging normally, and has been driven since then. The Battery, Car, > > and Location screens are up to date and live. The OVMS module is > > connected to the home Wi-Fi, as normal, and I can access it through > > the internal web server (dashboard, status, etc.).? But the phone > > app's Messages page stops at 8-January. > > > > I've not messed with the module in a long time.? Last boot, in fact, > > was a crash back in July 2023, from which it recovered normally. (So > > lovely seeing an uptime in excess of 17 million seconds.) > > > > So, what happened back on 8-January?? The only thing I can think of > > was that Android is being more aggressive about shutting down > > background processing (in the name of increased battery life), but > > leaving the app running in foreground and triggering an event still > > wasn't seen on the phone.? I can see them on the Web's Dashboard, so > > the events are being generated and processed otherwise normally. > > > > The phone is a Pixel 7a, Android 14.? OVMS firmware is > > 3.3.003/ota_1/eap (build idf v3.3.4-848-g1ff5e24b1 Sep 1 2022 08:40:30). > > > > Any ideas? > > > > Thanks, > > > > Greg > > _______________________________________________ > > OvmsDev mailing list > > OvmsDev(a)lists.openvehicles.com > > http://lists.openvehicles.com/mailman/listinfo/ovmsdev > > -- > Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal > Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 > >

6 11

Working on ESP-IDF5 + Have a question about ovms_module 'Name'
by Michael Geddes 26 Jan '24

26 Jan '24

Hey, In working trying to get ESP-IDF 5+ Working, I came across the following fun thing that I'm trying to work out what is going on!! This is from main/ovms_module.cpp I'm not sure why we don't just go through all the words and compare - why the masked compare for the last entry! And why that value?? It might make sense if you masked out the final byte ... I'm just struggling to understand. Why am I looking at it?? Well there's a new warning about copy constructors.. and then I ran into a problem where 'Name' is sometimes in memory that can only be accessed 32bit int aligned (which is why the strange implementation in the first place - I get that). Can anybody shed any light on this? class Name {....... inline bool operator==(const Name& a) const { for (int i = 0; i < NAMELEN/4 - 1; ++i) if (a.words[i] != words[i]) return false; i*f (a.words[NAMELEN/4-1] != (words[NAMELEN/4-1] & 0x7FFFFFFF)) return false;* return true; }

3 4

Messages stopped being received on phone
by Greg D. 26 Jan '24

26 Jan '24

Hi folks, I recently noticed that Alerts (Messages) have stopped coming to my phone. The last one was on 8-January '24. The car is still operating / charging normally, and has been driven since then. The Battery, Car, and Location screens are up to date and live. The OVMS module is connected to the home Wi-Fi, as normal, and I can access it through the internal web server (dashboard, status, etc.). But the phone app's Messages page stops at 8-January. I've not messed with the module in a long time. Last boot, in fact, was a crash back in July 2023, from which it recovered normally. (So lovely seeing an uptime in excess of 17 million seconds.) So, what happened back on 8-January? The only thing I can think of was that Android is being more aggressive about shutting down background processing (in the name of increased battery life), but leaving the app running in foreground and triggering an event still wasn't seen on the phone. I can see them on the Web's Dashboard, so the events are being generated and processed otherwise normally. The phone is a Pixel 7a, Android 14. OVMS firmware is 3.3.003/ota_1/eap (build idf v3.3.4-848-g1ff5e24b1 Sep 1 2022 08:40:30). Any ideas? Thanks, Greg

2 1

Fwd: [Action Required] Update your apps to the latest Firebase Cloud Messaging APIs and SDKs
by Michael Balzer 09 Jan '24

09 Jan '24

Time for another Google API deprecation. It seems we'll need to update the Android App & possibly the server now to the FCM API for push notifications, the old GCM API will stop working in June 2024. Anyone volunteering to take care of this? Regards, Michael -------- Weitergeleitete Nachricht -------- Betreff: [Action Required] Update your apps to the latest Firebase Cloud Messaging APIs and SDKs Datum: Tue, 20 Jun 2023 13:26:22 -0700 Von: Firebase <firebase-noreply(a)google.com> Antwort an: Firebase <firebase-noreply(a)google.com> An: dexter(a)expeedo.de Mandatory Service Announcement from Firebase Take action before June 20, 2024 to continue receiving support. Firebase Console <https://notifications.google.com/g/p/ACUgQrEqj5I8-oiq75nsyLmVgMI_2P_O30pr9Z…> Hi Michael, We’re writing to let you know that starting *June 20, 2024* the legacy Firebase Cloud Messaging (FCM) APIs will be discontinued. What do you need to know? On *June 20, 2024,* we’re reducing the number of Firebase Cloud Messaging (FCM) legacy register APIs and legacy send APIs that provide similar functionality. This step will allow us to provide you with a more consistent experience and align with Google security standards to improve security, reliability and performance. Because of these API decommissions, some already-deprecated SDKs and features will stop working after *June 20, 2024.* Please consult the tables below to find which Firebase Cloud Messaging (FCM) APIs and corresponding services/SDKs/features will be discontinued and replaced with new alternatives. *Discontinued Send API* *Decommissioned service* *New alternative* *Legacy HTTP Protocol* Sending messages via the Legacy HTTP API. Send messages via the HTTP v1 API. *XMPP Protocol* Sending upstream and downstream messages via the XMPP API. Send downstream messages via the HTTP v1 API. Send upstream messages via HTTP/gRPC <https://notifications.google.com/g/p/ACUgQrFKp0BdXKuz3_mUi3W9wdl6DV3Ib_q0Hn…> directly from the App to your server. *Batch send API* Including multiple send requests in a single HTTP request to FCM known as Batch Send. Send messages via the HTTP v1 API, which has been optimized for fanout performance *Discontinued Register API* *Decommissioned SDK* *New alternative* *GCM register API* Google Cloud Messaging(GCM) SDKs (deprecated in 2018). Latest FCM Android SDK. *Legacy Web register API* FCM JS SDK version<7.0.0 (deprecated in 2019) Latest FCM JS SDK. *Instance ID Server API for Web* No SDK related to this API. Latest FCM JS SDK. *Discontinued Feature* *Decommissioned service* *New alternative* *Server keys* Authenticating requests with server keys. Authenticate requests with access tokens generated from authorized service accounts <https://notifications.google.com/g/p/ACUgQrE8LxWKrfZvL3R5hoSruQL4An9Vg5kFcD…> *iOS Direct Channel* Sending messages via FCM’s direct channel to iOS devices while they are running in the foreground. All iOS messages will be sent via APNS channel. What do you need to do? Take the following actions before *June 20, 2024*, to ensure that you have access to the latest supported features and to reduce the risk of future decommissions affecting your usage: * *Follow the instructions described in *Firebase FAQ <https://notifications.google.com/g/p/ACUgQrF1q42xLDBDWvEr5RHaOfbnfKhv0UdWXB…> to migrate your individual APIs. * *Update to the latest versions of Firebase SDKs*. *Platform* *Recommended FCM SDK version* Android >= 23.1.2 iOS >= 10.10.0 Web (Javascript) >= 9.22.1 Your Firebase project(s) that use Firebase Cloud Messaging APIs are listed below: * MyOvmsServer (1043773844049) <https://notifications.google.com/g/p/ACUgQrEotRQKxV6LgEoXckEV9bLkUuhj9b1dUE…> o /Your recent usage of impacted APIs/features: Server Keys/ o /Your recent usage of impacted APIs/features: Legacy HTTP protocol/ We’re here to help If you have any questions, please review the Firebase FAQs <https://notifications.google.com/g/p/ACUgQrF1q42xLDBDWvEr5RHaOfbnfKhv0UdWXB…>. Thanks, Todd on behalf of the Firebase team *Was this information helpful?* Yes <https://notifications.google.com/g/p/ACUgQrG_D9izaxqaPAZL66peR0D-yHGGWiULfq…> Neutral <https://notifications.google.com/g/p/ACUgQrFnFdXuJ_VF6ChjiUeTeV5elzVrPymaFM…> No <https://notifications.google.com/g/p/ACUgQrFb7NDlSkpL4nuGR0g71bgiRuj39SdywV…> You have received this mandatory service announcement to update you about important changes to Firebase or your account. © 2023 Google LLC 1600 Amphitheatre Parkway Mountain View, CA 94043 USA <#> -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

3 4

SSL error?
by Michael Stegen 05 Jan '24

05 Jan '24

With TLS enabled, the ovms v3 module can not connect to the openvehicles.com server anymore. When i disable TLS from the Server v2 configuration tab, the module successfully connects.. firmware is 3.3.003 Am i doing something wrong or is there a certificate issue? I (4103952) ovms-server-v2: Connection is api.openvehicles.com:6870 I (4103952) ovms-server-v2: Status: Connecting... I (4103982) webserver: HTTP GET /shell I (4104062) webserver: HTTP POST /api/execute I (4104072) webcommand: HttpCommandStream[0x3f8bfaf8]: 3484084 bytes free, executing: server v2 status E (4105182) mongoose: mg_ssl_if_mbed_err 0x3f8c3f54 SSL error: -9984 W (4105182) ovms-server-v2: Connection failed E (4105192) ovms-server-v2: Status: Error: Connection failed E (4107502) mongoose: mg_ssl_if_mbed_err 0x3f8c3f54 SSL error: -29312 W (4107502) ovms-server-v2: Connection failed E (4107502) ovms-server-v2: Status: Error: Connection failed I (4107512) ovms-server-v2: Status: Disconnected I (4151302) webserver: HTTP GET /cfg/server/v2 I (4157072) webserver: HTTP POST /cfg/server/v2 I (4162122) webserver: HTTP GET /shell I (4166952) ovms-server-v2: Connection is api.openvehicles.com:6867 I (4166952) ovms-server-v2: Status: Connecting... I (4167202) ovms-server-v2: Connection successful I (4167202) ovms-server-v2: Status: Logging in...

3 3