picobrew_pico
picobrew_pico copied to clipboard
chiefwigms
Picostill found but unable to get passed Step 1/3 on Pico Z
Hi and thanks for the hard work.
Trying to setup Picostill (as it doesn't seem to work on real picobrew server). My Pi4 all setup and working as AP and connected to internet via home Wifi. It will find the Picostill and connect to it but after few seconds trying to set it up (1/3) I will get an alarm with "General Error" and then only option is "Reconnect to wifi" or "Exit".
Any idea on what I can do? Do I have to update PicoStill firmware and if so, how can I do it?
Thanks.
@marcchabot do you have or know how to get access to any of the server logs to see if there was a server error that might have created this scenario?
To verify you have both the Z and PicoStill connected to the raspberrypi server and able to communicate (the Z is the only thing that communicates to the raspberrypi during a session)?
The PicoStill during the startup sequence is the only time that it will communicate to picobrew.com (in this scenario the raspberrypi) during the actual distillation and the initial setup of the distillation process only the Z communicates to the server. The initial startup sequence we will also signal to the PicoStill to pull the latest firmware as configured on the server configuration (or default to latest available from PicoBrew proper).
I'll take a look tomorrow but if you can help me locate the log files I'll be more than happy to provide everything you need.
Picostill firmware version is 0.0.30
Marc
Le mar. 15 déc. 2020 20 h 36, Trevor Mack [email protected] a écrit :
@marcchabot https://github.com/marcchabot do you have or know how to get access to any of the server logs to see if there was a server error that might have created this scenario?
To verify you have both the Z and PicoStill connected to the raspberrypi server and able to communicate (the Z is the only thing that communicates to the raspberrypi during a session)?
The PicoStill during the startup sequence is the only time that it will communicate to picobrew.com (in this scenario the raspberrypi) during the actual distillation and the initial setup of the distillation process only the Z communicates to the server. The initial startup sequence we will also signal to the PicoStill to pull the latest firmware as configured on the server configuration (or default to latest available from PicoBrew proper).
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/chiefwigms/picobrew_pico/issues/161#issuecomment-745706570, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDGHOPUIZPZLNV45ISLUCLSVAFKVANCNFSM4U4YJ2GA .
Quick question: what is the user/password in order to ssh?
Also, could it be because of certificate problems that my connection is failed to PicoStill? I have to manually accept certificate when I go to the server from web browser. (See picture).
Thank you.
Le mar. 15 déc. 2020 21 h 56, Marc Chabot [email protected] a écrit :
I'll take a look tomorrow but if you can help me locate the log files I'll be more than happy to provide everything you need.
Picostill firmware version is 0.0.30
Marc
Le mar. 15 déc. 2020 20 h 36, Trevor Mack [email protected] a écrit :
@marcchabot https://github.com/marcchabot do you have or know how to get access to any of the server logs to see if there was a server error that might have created this scenario?
To verify you have both the Z and PicoStill connected to the raspberrypi server and able to communicate (the Z is the only thing that communicates to the raspberrypi during a session)?
The PicoStill during the startup sequence is the only time that it will communicate to picobrew.com (in this scenario the raspberrypi) during the actual distillation and the initial setup of the distillation process only the Z communicates to the server. The initial startup sequence we will also signal to the PicoStill to pull the latest firmware as configured on the server configuration (or default to latest available from PicoBrew proper).
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/chiefwigms/picobrew_pico/issues/161#issuecomment-745706570, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDGHOPUIZPZLNV45ISLUCLSVAFKVANCNFSM4U4YJ2GA .
No the pico machines don't validate certificates... and only the Z actually even uses https (though still doesn't validate certificate). This stupidity by PB allows us to take advantage of this lack of security by introducing the MITM attack (man in the middle) to even have any of this work.
ssh username and password is raspbian's default (we haven't changed it)
Here is the log from rc.local status.
�
I hope it tells you something and you can help me out. I have a 5gal wash that needs to be distilled.
�
Thanks a lot
�
Marc
�
From: Trevor Mack [email protected] Sent: Tuesday, December 15, 2020 9:47 PM To: chiefwigms/picobrew_pico [email protected] Cc: Marc Chabot [email protected]; Mention [email protected] Subject: Re: [chiefwigms/picobrew_pico] Picostill found but unable to get passed Step 1/3 on Pico Z (#161)
�
Also what is the firmware version that is reported on your Still?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/chiefwigms/picobrew_pico/issues/161#issuecomment-745727778 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDGHOL7B6DFKGRKOFKOX73SVANR5ANCNFSM4U4YJ2GA . https://github.com/notifications/beacon/ABDGHONJRM7RXVOGGNSZZDLSVANR5A5CNFSM4U4YJ2GKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFRZOOIQ.gif
● rc-local.service - /etc/rc.local Compatibility Loaded: loaded (/lib/systemd/system/rc-local.service; enabled-runtime; vendor preset: enabled) Drop-In: /usr/lib/systemd/system/rc-local.service.d └─debian.conf /etc/systemd/system/rc-local.service.d └─ttyoutput.conf Active: active (running) since Tue 2020-12-15 13:17:24 EST; 23h ago Docs: man:systemd-rc-local-generator(8) Process: 355 ExecStart=/etc/rc.local start (code=exited, status=0/SUCCESS) Tasks: 2 (limit: 2063) CGroup: /system.slice/rc-local.service └─557 python3 server.py 0.0.0.0 8080
Dec 16 10:41:56 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:41:56 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:41:56 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:41:56 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:41:56 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:41:56 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:41:56 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:41:56 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:41:56 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:41:56 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:41:56 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:41:56 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:41:56 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:41:56 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:41:56 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:41:56 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:41:56 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:41:56 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:41:56 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:41:56 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:41:56 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:41:56 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:41:56 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:41:56] "POST /import_zseries_recipe HTTP/1.0" 204 - Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:42:07 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:42:07 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:42:07 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:42:07 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:42:07 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:42:07 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:42:07 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:42:07 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:42:07 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:42:07 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings Dec 16 10:42:07 picoserver rc.local[355]: InsecureRequestWarning) Dec 16 10:42:07 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:42:07] "POST /import_zseries_recipe HTTP/1.0" 204 - Dec 16 10:42:10 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:42:10] "GET /zseries_recipes HTTP/1.0" 200 - Dec 16 10:42:10 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:42:10] "GET /static/css/bootstrap/bootstrap.min.css HTTP/1.0" 200 - Dec 16 10:42:10 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:42:10] "GET /static/css/fontawesome/fontawesome.min.css HTTP/1.0" 200 - Dec 16 10:42:10 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:42:10] "GET /static/css/tabulator/tabulator_midnight.min.css HTTP/1.0" 200 - Dec 16 10:42:10 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:42:10] "GET /static/css/fontawesome/all.min.css HTTP/1.0" 200 - Dec 16 10:42:10 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:42:10] "GET /static/css/main.css HTTP/1.0" 200 - Dec 16 10:42:10 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:42:10] "GET /static/js/convert_units.js HTTP/1.0" 200 - Dec 16 10:42:10 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:42:10] "GET /static/js/zseries_recipe.js HTTP/1.0" 200 - Dec 16 10:42:10 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:42:10] "GET /static/js/server_management.js HTTP/1.0" 200 - Dec 16 10:42:11 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:42:11] "GET /static/css/webfonts/fa-solid-900.woff2 HTTP/1.0" 200 - Dec 16 10:42:49 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:42:49] "POST /Vendors/input.cshtml?ctl=RecipeRefListController&token=30aea4c73494 HTTP/1.0" 200 - Dec 16 10:43:24 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:43:24] "GET /API/PicoStill/getFirmwareAddress?uid=30aea46b3858&version=0.0.21 HTTP/1.0" 200 - Dec 16 10:43:25 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:43:25] "GET /firmware/picostill/picostill_0_0_30.bin HTTP/1.0" 200 - Dec 16 10:43:56 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:43:56] "POST /Vendors/input.cshtml?type=StillRequest&token=30aea4c73494 HTTP/1.0" 200 - Dec 16 10:44:00 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:44:00] "POST /Vendors/input.cshtml?type=StillRequest&token=30aea4c73494 HTTP/1.0" 200 - Dec 16 10:45:47 picoserver sudo[710]: root : TTY=unknown ; PWD=/picobrew_pico ; USER=root ; COMMAND=/usr/sbin/iwlist wlan0 scanning Dec 16 10:45:47 picoserver sudo[710]: pam_unix(sudo:session): session opened for user root by (uid=0) Dec 16 10:45:48 picoserver sudo[710]: pam_unix(sudo:session): session closed for user root Dec 16 10:45:48 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:45:48] "GET /setup HTTP/1.0" 200 - Dec 16 10:46:19 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:46:19] "GET /static/css/bootstrap/bootstrap.min.css HTTP/1.0" 200 - Dec 16 10:46:19 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:46:19] "GET /static/css/fontawesome/fontawesome.min.css HTTP/1.0" 200 - Dec 16 10:46:19 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:46:19] "GET /static/css/fontawesome/all.min.css HTTP/1.0" 200 - Dec 16 10:46:20 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:46:20] "GET /static/css/tabulator/tabulator_midnight.min.css HTTP/1.0" 200 - Dec 16 10:46:20 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:46:20] "GET /static/css/main.css HTTP/1.0" 200 - Dec 16 10:46:20 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:46:20] "GET /static/js/jquery/jquery.min.js HTTP/1.0" 200 - Dec 16 10:46:21 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:46:21] "GET /static/js/tabulator/tabulator.min.js HTTP/1.0" 200 - Dec 16 10:46:21 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:46:21] "GET /static/js/bootstrap/bootstrap.min.js HTTP/1.0" 200 - Dec 16 10:46:23 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:46:23] "GET /static/js/setup.js HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET / HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/css/bootstrap/bootstrap.min.css HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/css/fontawesome/all.min.css HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/css/tabulator/tabulator_midnight.min.css HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/css/fontawesome/fontawesome.min.css HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/js/jquery/jquery.min.js HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/css/main.css HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/js/bootstrap/bootstrap.min.js HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/js/tabulator/tabulator.min.js HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/js/highcharts/highcharts.js HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/js/highcharts/export-data.js HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/js/highcharts/annotations.js HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/js/highcharts/exporting.js HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/js/highcharts/dark-unica.js HTTP/1.0" 200 - Dec 16 12:57:28 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:28] "GET /static/js/socketio/socket.io.slim.js HTTP/1.0" 200 - Dec 16 12:57:29 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:29] "GET /socket.io/?EIO=3&transport=polling&t=NPiiode HTTP/1.1" 200 - Dec 16 12:57:37 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:37] "GET /zseries_recipes HTTP/1.0" 200 - Dec 16 12:57:37 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:37] "GET /static/js/server_management.js HTTP/1.0" 200 - Dec 16 12:57:37 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:37] "GET /static/js/zseries_recipe.js HTTP/1.0" 200 - Dec 16 12:57:37 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:37] "GET /static/js/convert_units.js HTTP/1.0" 200 - Dec 16 12:57:37 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:37] "GET /static/css/webfonts/fa-solid-900.woff2 HTTP/1.0" 200 - Dec 16 12:57:37 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:57:37] "GET /static/css/webfonts/fa-regular-400.woff2 HTTP/1.0" 200 - Dec 16 12:58:29 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:58:29] "GET /socket.io/?EIO=3&transport=polling&t=NPiioe9&sid=2eae0e79224b40d390aa6c1414e20c1c HTTP/1.1" 400 - Dec 16 12:58:37 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:58:37] "GET /static/js/bootstrap/bootstrap.min.js.map HTTP/1.0" 404 - Dec 16 12:58:37 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:58:37] "GET /static/css/bootstrap/bootstrap.min.css.map HTTP/1.0" 404 - Dec 16 12:58:37 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 12:58:37] "GET /static/css/tabulator/tabulator_midnight.min.css.map HTTP/1.0" 404 -
Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
That is just a warning that we aren't validating the certificate of the picobrew.com proper domain when doing a recipe/instruction import operation. This can be completely ignored. We wouldn't be able to handle the certificate without modifications cause we are accessing via a static IP and the cert is signed with picobrew.com domain of which is redirected on the raspberrypi anyways.
These requests logs are actually the only requests from the PicoStill:
Dec 16 10:43:24 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:43:24] "GET /API/PicoStill/getFirmwareAddress?uid=30aea46b3858&version=0.0.21 HTTP/1.0" 200 -
Dec 16 10:43:25 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:43:25] "GET /firmware/picostill/picostill_0_0_30.bin HTTP/1.0" 200 -
That shows me that your PicoStill was on an older than 0.0.30 firmware release (reporting as version=0.0.21) and the offline server bumped it up to 0.0.30.
These are as I said the requests that are expected from the Z when running a "PicoStill" session and look completely normal:
Dec 16 10:43:56 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:43:56] "POST /Vendors/input.cshtml?type=StillRequest&token=30aea4c73494 HTTP/1.0" 200 -
Dec 16 10:44:00 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:44:00] "POST /Vendors/input.cshtml?type=StillRequest&token=30aea4c73494 HTTP/1.0" 200 -
Did you get prompts on the Z to acknowledge that you cleaned your PicoStill prior to use?
Yes I get passed that to the 1/3 configuration step. But then red and yellow leds on PicoStill will begin flashing and I get a General Failure.
Marc
Le mer. 16 déc. 2020 15 h 34, Trevor Mack [email protected] a écrit :
Dec 16 10:42:07 picoserver rc.local[355]: /usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
That is just a warning that we aren't validating the certificate of the picobrew.com proper domain when doing a recipe/instruction import operation. This can be completely ignored. We wouldn't be able to handle the certificate without modifications cause we are accessing via a static IP and the cert is signed with picobrew.com domain of which is redirected on the raspberrypi anyways.
These requests logs are actually the only requests from the PicoStill:
Dec 16 10:43:24 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:43:24] "GET /API/PicoStill/getFirmwareAddress?uid=30aea46b3858&version=0.0.21 HTTP/1.0" 200 - Dec 16 10:43:25 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:43:25] "GET /firmware/picostill/picostill_0_0_30.bin HTTP/1.0" 200 -
That shows me that your PicoStill was on an older than 0.0.30 firmware release (reporting as version=0.0.21) and the offline server bumped it up to 0.0.30.
These are as I said the requests that are expected from the Z when running a "PicoStill" session and look completely normal:
Dec 16 10:43:56 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:43:56] "POST /Vendors/input.cshtml?type=StillRequest&token=30aea4c73494 HTTP/1.0" 200 - Dec 16 10:44:00 picoserver rc.local[355]: 127.0.0.1 - - [16/Dec/2020 10:44:00] "POST /Vendors/input.cshtml?type=StillRequest&token=30aea4c73494 HTTP/1.0" 200 -
Did you get prompts on the Z to acknowledge that you cleaned your PicoStill prior to use?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/chiefwigms/picobrew_pico/issues/161#issuecomment-746971122, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDGHOLXHSUIDHHO6MJURYLSVEKW7ANCNFSM4U4YJ2GA .
Don't see anything in the request log that would result in that. Though will do some local testing to see if I can reproduce at all.
I'd recommend restarting the PicoStill and Z at least once and see if this experience persists. Did you try that by chance? I haven't had time to get the Still out as a snowstorm came into the area and the kids are home today.
Yes it's what I did when I had the first fail.
I had to reset the the PicoStill by holding the power while plugging to AC.
Same result.
Thanks for your help I really hope we can diagnose and fix it. But no hurry I know you do that on your spare time.
Marc
Le jeu. 17 déc. 2020 11 h 04, Trevor Mack [email protected] a écrit :
I'd recommend restarting the PicoStill and Z at least once and see if this experience persists. Did you try that by chance? I haven't had time to get the Still out as a snowstorm came into the area and the kids are home today.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/chiefwigms/picobrew_pico/issues/161#issuecomment-747534532, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDGHOKYNOQDVNYWXNEXFW3SVIT2JANCNFSM4U4YJ2GA .
I did some more tests with another PicoStill that a friend of mine borrowed me.
�
His PicoStill seems to be a newer edition (led are not the same they seem brighter) and everything worked meaning that I passed the 3 steps and got to PicoStill ready.
�
Mine seems to time out at step 1 and I get General Error.
�
Another thing I found out is that while doing step 1/3 with fault PicoStill, the yellow led (progress) will flash for a long time and then aI get the error.
�
On the PicoStill that works, ALL 3 leds will flash few times and then Z will go to step 2 & 3.
�
My question: since my PicoStill doesn’t work, could it be because of firmware version I have? Is there any way I could clash it so I can have newer version and maybe have it to work again?
�
I used it 3 times so it used to work.
�
Thanks again for your help.
�
Marc
�
From: Trevor Mack [email protected] Sent: Thursday, December 17, 2020 11:05 AM To: chiefwigms/picobrew_pico [email protected] Cc: Marc Chabot [email protected]; Mention [email protected] Subject: Re: [chiefwigms/picobrew_pico] Picostill found but unable to get passed Step 1/3 on Pico Z (#161)
�
I'd recommend restarting the PicoStill and Z at least once and see if this experience persists. Did you try that by chance? I haven't had time to get the Still out as a snowstorm came into the area and the kids are home today.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/chiefwigms/picobrew_pico/issues/161#issuecomment-747534532 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABDGHOKYNOQDVNYWXNEXFW3SVIT2JANCNFSM4U4YJ2GA . https://github.com/notifications/beacon/ABDGHOKWEM6RCGBH5MWMCSDSVIT2JA5CNFSM4U4YJ2GKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFSHHRRA.gif
Unless there are two different firmware types in the PicoStill lineup it would already be forced to the latest firmware upon booting up and connecting to the raspberrypi.