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

[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

[Remy_Tsuihiji]

i dont know how to do it
but, autopi is flashed with new image, (3 times to be sure) I am not sure if it is the last one: 06.03.19 v2 ??

So, what I understand is, all my data created (custom code) is on your cloud.
but he don’t want to synchronies and put in my dongle. but job is ok and synchronies well.

what is the problem ?

[Andreas_Nygren]

Hi Malte, The logfile is sent to you on support@autopi.io

Have a good weekend and keep up the good work

[plord]

@plord

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

Unfortunately I’ve not had much chance to investigate.

I noticed this morning that sleep seems to be no-longer working. I used to see events like -

but now no sleep -

Also, no workers are configured -

[plord]

I used to see in my logs line like -

2019-05-04 08:27:16,667 [cloud_cache :177 ][INFO ][858] Uploaded batch with 76 entries from queue 'pend'

but now only -

2019-05-11 05:11:28,125 [cloud_cache :177 ][INFO ][823] Uploaded batch with 2 entries from queue 'pend'

I also used to see -

2019-05-04 07:54:17,058 [messaging :615 ][INFO ][941] Starting 4 worker thread(s): _uart_keepalive, readout_30sec, readout_10sec, readout_1sec

but now -

2019-05-11 08:10:31,009 [messaging :616 ][INFO ][24571] Starting 1 worker thread(s): _uart_keepalive

Should we still have workers named readout_30sec, readout_10sec, readout_1sec ?

What do others see in advanced -> Services -> OBD Manager ? I see only _uart_keepalive -

[Steve]

I’ve got _uart_keepalive, readout_1sec and readout_30sec. Nothing for 10 seconds. And for now I’m continuing to receive data.

[plord]

I’ve got _uart_keepalive, readout_1sec and readout_30sec. Nothing for 10 seconds. And for now I’m continuing to receive data.

Ah. Many thanks.

I might try and delete my loggers and re-create them to see if that reinstates the workers.

[plord]

I might try and delete my loggers and re-create them to see if that reinstates the workers.

Didn’t re-create the workers

So looking for advice from @Malte or @Peter to see if this is the suspected cause of the issue and how I can re-create the workers.

[orcinus]

I’ve got the same issue as @plord - all workers missing except _uart_keepalive post update.

Edit: sleep works fine for me, though.

[plord]

I suppose if we can get a screen shot of a working configuration we might be able to manually re-create it.

[orcinus]

After playing with it some more, seems like mine’s working as expected, despite missing those.

It’s on a bench, but the GPS position, voltage and raspi temp are getting updated fine, and sleep works.

Odd.