Greg, I finally understood your problem: the server actually excludes "DMC" error notifications from all push channels, so you don't even get them by email. And that's necessary because there are so many of them, most of them with no meaning for normal usage, right? To answer your question: yes, of course that's possible. Use the CmdSeries class to fetch the records. Have a look at classes AuxBatteryData & AuxBatteryChart for an example. They fetch the "D" history, fetching the "*-Log-Notification" history is pretty much the same, just another result processing. For the display you can possibly copy the notification list or add the missing records to that. Regards, Michael Am 15.12.19 um 20:55 schrieb Greg D.:
Love the new version, Michael. Nicely done.
Merging two threads... I'm assuming that the 12v battery log is data kept on the server. Would it be possible to similarly fetch and display the DMC alert records (ref "Alert notification history") in the app, or just the overall (unfiltered) alert log? To Mark's issue with support calls, there probably should be some sort of notice / disclaimer that the records are not necessarily indicative of a vehicle failure.
Thanks,
Greg
Michael Balzer wrote:
I've just released version 3.14.0 of the Android App to the Play Store.
History: https://github.com/openvehicles/Open-Vehicle-Android/wiki/History#version-31...
* OpenChargeMap reader: raise network timeouts, add error feedback * Whiten Tesla Roadster image (issue #88) * Twizy battery chart: synchronize cells with large time offsets * Car editor: add server selection * Notifications: disable suggestions on command input * Map settings: fix spinner style * Map: o view change => disable tracking & enable 'my location' button o fetch OCM updates for view area * OpenChargeMap API: o HTTPS support o added user agent o added API key o queue area update fetches * CarsStorage: change file format to JSON to avoid further upgrade data losses * Removed obsolete previous map layout * Map settings dialog optimized & localized * Map: inhibit autotrack camera updates during user interaction * Optimize PNG files (removed exif data) * Car editor: fix crash on start with lost/corrupted car storage * Database: sanitize user input * Allow password length up to 255 characters (issue #91) * Keep foreground ApiService alive & connected on Android >= 7 * Log class cleanup * Added 12V battery history chart * Gradle update * Minify disabled due to missing classes in APK * 12V history: tolerate D records from outdated firmware versions
APK: https://github.com/openvehicles/Open-Vehicle-And...elease/OpenVehicleApp-rel...
Regards, Michael
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@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