Software update on the 8th of May - Event reactors, stability and minor dashboard improvements

[Malte]

Software update on the 8th of May - Event reactors, stability and minor dashboard improvements

We have pushed a new release that contains the following changes.

Frontend - my.autopi.io

• Improved date picker for dashboard and events.
• Added ability to auto refresh the dashboard.
• Added bar charts to the dashboard widgets
• Added icons to the add widget dialog
• Performance improvements.
• Fixed an issue with too aggressive caching of the frontend.
• Minor bugfixes
• Added reactors to engines ( enables you to modify the core rules of how the device lifecycle works )
• Improved handling of default engines
• Changed rendering of API documentation (first step to a much improved API doc)

AutoPi Core

• Stability improvements
• Minor bugfixes

Note: Auto updates are currently disabled, but can be enabled in the advanced settings.

Currently the update takes quite a while to finish, and it will restart the services running on the device. So please be patient when installing the updates, it should finish by itself, or retry on errors.
Let us know if you experience any issues.

As always, feedback, comments etc are welcome!

[plord]

I currently see “Internal Server Error” when accessing the server … presumably temporary outage for the upgrade.

[Malte]

Hi Peter

Yes, we ran into a few issues that made the process take a bit longer than usual.

Best regards
/Malte

[asetyde]

My autopi with autoupdate it upgrade automatically 1 our ago

• Added reactors to engines ( enables you to modify the core rules of how the device lifecycle works )
  How it works ?

i see plord say to rename our Kona pid for rpm ? and about charge status to wake up ?

[Malte]

Hi Alexandro

The new reactors can be found in the event_reactor service under the Reactors tab.

Be aware that the reactors are responsible for creating the sleep timers that makes the device go to sleep, among other critical lifecycle events, so changing these can affect the stability of the device.

This is the first part of supporting trips for EV vehicles.

Best regards
/Malte

[Malte]

When too much time passes between releases, it can be hard to remember all the changes
We have also added

• Added bar charts to the dashboard widgets
• Added icons to the add widget dialog

Best regards
/Malte

[plord]

Nice update many thanks.

[Andreas_Nygren]

I got a error said something like “Partly Success” (or something similar) when updating. Now it seems like its not logging anymore. Nothing new in the logs since last night after update.
Can I somehow roll back the previously version?

[Malte]

Hi guys

We have just released a small update to the frontend and backend with some tweaks and bug fixes.

Frontend

• Fixed a number of issues with the new datepicker, among other things it caused it to request data with a wrong offset.
  ie. it would not show the correct data, and it would look like the car had not logged any data.
• Fixed a number of minor issues on the events page with the datepicker.
• Changed the color theme to match the autopi colors.

Backend

• Fixed some minor issues
• Changed the API Documentation to be accessable at / instead of /swagger/

Sorry about the inconvenience this has caused.

Best regards
/Malte

[Malte]

One of the fixed issues in the frontend caused the dashboard to load data with an incorrect offset. And made it look like no data was logged.

Can you check if you still see an issue?

Regarding the partial success
If the update returned partial success, it will automatically retry the update, so it has probably applied the remaining changes by now.
But you can check that on the Software Updates page on my.autopi.io.

[Andreas_Nygren]

Hi, Malte,

Yes, the dongle must have been updated by now, it says current state: updated.

It still is no data in the dashboard since last night.the Map and the RPI temperature still updates, so it looks like only OBD data is not updating. Funny thing is that i get updates via Telegram when charging from Plords script, but the Node-red code from Nejc_Koncan doesn’t report values anymore, so its not completely dead.

[Remy_Tsuihiji]

@Malte
i had make update without problem, but this night I work on python code to send via custom code.
and we can’t update the custom code to autopi.
so I had try to refrash again the dongle, put the backup of token inside, and install again python module all work fine but the problem not change. I try 2 time to flash the autopi, same result. do you have idea ?it is a bug from the serveur to push to autopi ?

only plord telegram work !

[plord]

It still is no data in the dashboard since last night.the Map and the RPI temperature still updates, so it looks like only OBD data is not updating. Funny thing is that i get updates via Telegram when charging from Plords script, but the Node-red code from Nejc_Koncan doesn’t report values anymore, so its not completely dead.

I see the same - map and RPI temperature updated only.

Unfortunately I’ve not had much chance to investigate.

[Malte]

@plord and/or @Andreas_Nygren
Thank you for reporting the issue, is it possible for you to send me the log file from the device?
At first you could check the minionutil.last_errors or .last_logs via the command line, but if that doesn’t work, then getting the entire log file will probably be very beneficial for us.

I created a small guide that describes how to upload the logfile to a dropbox app folder by sending a command via the terminal, that is much faster than using ssh to copy it.

Tip: Send device logfile to dropbox with one command

You can retrieve logs from the device in different ways, but usually to retrieve the full log, you will need to SSH to the device, move some files around and then use SCP to retrieve the file. A much faster way is to push the logfile directly to your own dropbox, with a single command. To do this, you will need to do the following. Create a Dropbox app by going here and input like so: https://www.dropbox.com/developers/apps/create [01] Now click the “Generate” button under Generated ac…

[Remy_Tsuihiji]

i had try to flash my autopi with oldest version. nothing work. custom code not synchronies.

i flash again my autopi, but it is the last version ? if not, do you have the link of the last version?

[plord]

Thank you for reporting the issue, is it possible for you to send me the log file from the device?

How can we send logs ? The forum direct message doesn’t seem to allow log file attachments

[Remy_Tsuihiji]

local user@Local device $

minionutil.last_errors

>-

Binary file (standard input) matches

2019-05-10 19:16:45,393 [salt.loaded.ext.engines.spm_manager:85 ][ERROR

][712] Failed to trigger last system off event

2019-05-10 19:18:38,917 [salt.utils.schedule:927 ][ERROR ][902] Unhandled

exception running my_socdata.soc

2019-05-10 19:18:49,058 [salt.utils.schedule:927 ][ERROR ][905] Unhandled

exception running my_kwdata.kw

2019-05-10 19:18:59,863 [salt.utils.schedule:927 ][ERROR ][908] Unhandled

exception running my_sohdata.soh

2019-05-10 19:19:25,087 [salt.utils.schedule:927 ][ERROR ][922] Unhandled

exception running my_charge_status.poll

2019-05-10 19:19:50,776 [salt.utils.schedule:927 ][ERROR ][948] Unhandled

exception running my_socdata.soc

2019-05-10 19:20:02,805 [salt.utils.schedule:927 ][ERROR ][958] Unhandled

exception running my_kwdata.kw

2019-05-10 19:20:12,654 [salt.utils.schedule:927 ][ERROR ][964] Unhandled

exception running my_sohdata.soh

2019-05-10 19:20:28,709 [salt.utils.schedule:927 ][ERROR ][977] Unhandled

exception running my_charge_status.poll

2019-05-10 19:21:02,656 [salt.utils.schedule:927 ][ERROR ][991] Unhandled

exception running my_socdata.soc

2019-05-10 19:21:15,610 [salt.utils.schedule:927 ][ERROR ][994] Unhandled

exception running my_kwdata.kw

2019-05-10 19:21:25,190 [salt.utils.schedule:927 ][ERROR ][999] Unhandled

exception running my_sohdata.soh

2019-05-10 19:22:06,090 [salt.utils.schedule:927 ][ERROR ][1025] Unhandled

exception running my_socdata.soc

2019-05-10 19:22:19,856 [salt.utils.schedule:927 ][ERROR ][1032] Unhandled

exception running my_kwdata.kw

2019-05-10 19:22:27,482 [salt.utils.schedule:927 ][ERROR ][1038] Unhandled

exception running my_sohdata.soh

2019-05-10 19:22:36,641 [salt.utils.schedule:927 ][ERROR ][1050] Unhandled

exception running my_charge_status.poll

2019-05-10 19:23:45,347 [salt.utils.schedule:927 ][ERROR ][1095] Unhandled

exception running my_socdata.soc

2019-05-10 19:23:53,762 [salt.utils.schedule:927 ][ERROR ][1098] Unhandled

exception running my_kwdata.kw

2019-05-10 19:24:03,131 [salt.utils.schedule:927 ][ERROR ][1102] Unhandled

exception running my_sohdata.soh

2019-05-10 19:24:18,260 [salt.utils.schedule:927 ][ERROR ][1116] Unhandled

exception running my_charge_status.poll

2019-05-10 19:25:16,951 [salt.utils.schedule:927 ][ERROR ][1159] Unhandled

exception running my_socdata.soc

2019-05-10 19:25:25,498 [salt.utils.schedule:927 ][ERROR ][1162] Unhandled

exception running my_kwdata.kw

2019-05-10 19:25:37,676 [salt.utils.schedule:927 ][ERROR ][1165] Unhandled

exception running my_sohdata.soh

2019-05-10 19:25:58,830 [salt.utils.schedule:927 ][ERROR ][1179] Unhandled

exception running my_charge_status.poll

2019-05-10 19:26:15,317 [salt.utils.schedule:927 ][ERROR ][1189] Unhandled

exception running my_socdata.soc

2019-05-10 19:26:28,842 [salt.utils.schedule:927 ][ERROR ][1194] Unhandled

exception running my_kwdata.kw

2019-05-10 19:26:42,763 [salt.utils.schedule:927 ][ERROR ][1199] Unhandled

exception running my_sohdata.soh

2019-05-10 19:26:57,674 [salt.utils.schedule:927 ][ERROR ][1213] Unhandled

exception running my_charge_status.poll

2019-05-10 19:27:49,005 [salt.utils.schedule:927 ][ERROR ][1238] Unhandled

exception running my_socdata.soc

2019-05-10 19:27:57,478 [salt.utils.schedule:927 ][ERROR ][1241] Unhandled

exception running my_kwdata.kw

2019-05-10 19:28:06,370 [salt.utils.schedule:927 ][ERROR ][1245] Unhandled

exception running my_sohdata.soh

2019-05-10 19:28:20,445 [salt.utils.schedule:927 ][ERROR ][1258] Unhandled

exception running my_charge_status.poll

2019-05-10 19:28:55,820 [salt.utils.schedule:927 ][ERROR ][1288] Unhandled

exception running my_kwdata.kw

2019-05-10 19:29:04,317 [salt.utils.schedule:927 ][ERROR ][1291] Unhandled

exception running my_sohdata.soh

2019-05-10 19:29:19,302 [salt.utils.schedule:927 ][ERROR ][1304] Unhandled

exception running my_charge_status.poll

2019-05-10 19:29:33,702 [salt.utils.schedule:927 ][ERROR ][1309] Unhandled

exception running my_socdata.soc

2019-05-10 19:29:58,611 [salt.utils.schedule:927 ][ERROR ][1316] Unhandled

exception running my_kwdata.kw

2019-05-10 19:30:06,890 [salt.utils.schedule:927 ][ERROR ][1320] Unhandled

exception running my_sohdata.soh

2019-05-10 19:30:23,272 [salt.utils.schedule:927 ][ERROR ][1333] Unhandled

exception running my_charge_status.poll

2019-05-10 19:30:53,295 [salt.utils.schedule:927 ][ERROR ][1346] Unhandled

exception running my_kwdata.kw

2019-05-10 19:31:04,949 [salt.utils.schedule:927 ][ERROR ][1349] Unhandled

exception running my_sohdata.soh

2019-05-10 19:31:20,452 [salt.utils.schedule:927 ][ERROR ][1362] Unhandled

exception running my_charge_status.poll

2019-05-10 19:31:34,640 [salt.utils.schedule:927 ][ERROR ][1373] Unhandled

exception running my_socdata.soc

2019-05-10 19:32:01,800 [salt.utils.schedule:927 ][ERROR ][1380] Unhandled

exception running my_kwdata.kw

2019-05-10 19:32:15,792 [salt.utils.schedule:927 ][ERROR ][1384] Unhandled

exception running my_sohdata.soh

2019-05-10 19:32:29,718 [salt.utils.schedule:927 ][ERROR ][1397] Unhandled

exception running my_charge_status.poll

2019-05-10 19:32:41,008 [salt.utils.schedule:927 ][ERROR ][1425] Unhandled

exception running my_socdata.soc

2019-05-10 19:34:00,506 [salt.utils.schedule:927 ][ERROR ][1491] Unhandled

exception running my_socdata.soc

2019-05-10 19:34:08,575 [salt.utils.schedule:927 ][ERROR ][1500] Unhandled

exception running my_kwdata.kw

2019-05-10 19:34:17,187 [salt.utils.schedule:927 ][ERROR ][1519] Unhandled

exception running my_sohdata.soh

2019-05-10 19:34:23,209 [salt.utils.schedule:927 ][ERROR ][1526] Unhandled

exception running my_charge_status.poll

2019-05-10 19:35:26,991 [salt.utils.schedule:927 ][ERROR ][1583] Unhandled

exception running my_socdata.soc

2019-05-10 19:35:34,565 [salt.utils.schedule:927 ][ERROR ][1586] Unhandled

exception running my_kwdata.kw

2019-05-10 19:35:44,277 [salt.utils.schedule:927 ][ERROR ][1589] Unhandled

exception running my_sohdata.soh

2019-05-10 19:35:55,383 [salt.utils.schedule:927 ][ERROR ][1595] Unhandled

exception running my_charge_status.poll

2019-05-10 19:36:30,028 [salt.utils.schedule:927 ][ERROR ][1610] Unhandled

exception running my_socdata.soc

2019-05-10 19:36:40,308 [salt.utils.schedule:927 ][ERROR ][1614] Unhandled

exception running my_kwdata.kw

2019-05-10 19:36:48,309 [salt.utils.schedule:927 ][ERROR ][1619] Unhandled

exception running my_sohdata.soh

2019-05-10 19:36:53,852 [salt.utils.schedule:927 ][ERROR ][1623] Unhandled

exception running my_charge_status.poll

2019-05-10 19:37:47,611 [salt.utils.schedule:927 ][ERROR ][1656] Unhandled

exception running my_sohdata.soh

2019-05-10 19:37:55,790 [salt.utils.schedule:927 ][ERROR ][1659] Unhandled

exception running my_charge_status.poll

2019-05-10 19:38:09,136 [salt.utils.schedule:927 ][ERROR ][1671] Unhandled

exception running my_socdata.soc

2019-05-10 19:38:17,720 [salt.utils.schedule:927 ][ERROR ][1675] Unhandled

exception running my_kwdata.kw

local user@Local device $

[Malte]

Hi Remy

What happens if you run the module yourself in the console?

Best regards
/Malte