December 2023 - 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

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

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

CAN2 turning off without reason
by Christos Oscar Kambiselis 11 Dec '23

11 Dec '23

Good afternoon, I've been trying to log CAN data using CAN2 in listen mode and connected to a different bus in the car ,I stopped the logging to the SD card yesterday and was going to test network streaming the data directly today, since I was having problems downloading the file, but I noticed that it goes to "Off" after an unspecified time. Yesterday I made sure it was on "Listen", after failing with the SD card file. And there is no mention of a timer, in the dev docs. Oscar

1 0

VWEUP module service interval?
by Michael Geddes 03 Dec '23

03 Dec '23

Hey All, I've been paving the way for 64 bit time_t that's apparently in the newer esp32 releases. I'm keen to know how that update to the newer sdk is going too? For persistence, I am registering the high 32bits as a second metric with "_hi" suffix (Similar to how the arrays work). One thing I've noticed is that there's a standard metric: OvmsMetricInt* ms_v_env_service_time; // Time to next scheduled maintenance/service [Seconds] cf the doc v.e.serv.time 1572590910Sec Time of next scheduled maintenance/service [Seconds] So it's a bit ambiguous but vweup (the only one who sets this metric) implementation treats this as a time_t. I think I will convert it to a 64 bit 'DateLocal' metric. Thoughts? //.ichael

3 2