These are chat archives for nightscout/intend-to-bolus

21st
Nov 2018
Sounds like you might have missed the step npm run global-install
jcorbett80
@jcorbett80
Nov 21 2018 00:16
Thank you @alimhassam I will give it a try now
Garrett Webb
@garetis
Nov 21 2018 00:31
@RadEnder I got mine to connect over serial. I forgot that when the connection starts you have to hit Enter once or twice to wake it up. I thought the connection was getting hung up, but just wasn't the case
Dana Lewis
@danamlewis
Nov 21 2018 00:51
@alimhassam it may be all Pi install say use dev, implying hat, whereas TI users should still install master instead. If that works, docs should be updated to clarify Pi HAT users, and note once someone successfully confirms Pi TI usage what that workflow is
jcorbett80
@jcorbett80
Nov 21 2018 01:23
@danamlewis @danamlewis doing master now but keep hanging on "adding openAPS log shortcuts" once I can get past that i will update. I redid so many installs trying to get it working the last 2 days I may need ro just do a full start over at this point. I did 2 tries so far on this one.
Sorry one of those was supposed to be @alimhassam
jcorbett80
@jcorbett80
Nov 21 2018 01:35
@danamlewis @alimhassam i just killed myopenaps, src, and go folder. I will do steps 1 2 and 3 then for step 4 do the master from what was on the master setup just sent to me and update you
jcorbett80
@jcorbett80
Nov 21 2018 01:43
@danamlewis @alimhassam I see the main issue with how I setup. Instructions say "do not hit enter" but instead hit ctrl c because pi can't run it yet. However "enter" IS the master branch from what I see. So hitting enter and trying it
Dave Gourley
@RadEnder
Nov 21 2018 07:15
@garetis Thanks for the info. I tried a few things and eventually got it to show up on a PC and my Mac. It could have been my USB cables as others have mentioned as I swapped about 10 cables out before seeming to be successful. I also left the battery plugged in instead of relying on power coming from the USB ports and it happened to work the time I did that. It could also have been what you suggested as I was trying a bunch of stuff. Good news is that I think I'm working through my first loop and am now trying to figure out when/how to stay connected through daily life... much to learn. Still trying to get used to the fact that the code will/should be helping with dosing decisions. It is a lot to adjust to.
lottainkeri
@lottainkeri
Nov 21 2018 07:21
Hi folks,
I am having issues with Nightscout. Looping works perfectly but the Nightscout reports are empty. I can see the graphs in NS.
Setup: Edison + Medtronic 522
Thanks in advance!
pm709
@pm709
Nov 21 2018 10:24
if by "Nightscout reports" you mean openaps pill empty then it could be a mlab issue (see https://openaps.readthedocs.io/en/latest/docs/Troubleshooting/Rig-NS-communications-troubleshooting.html)
I had a similar issue (pill not updated) with my setup pi3+usb ti stick on master branch. It was not related to mlab (it was nearly empty). Finally I fix it by changing my crontab : I had to replace reference to "openaps ns-loop" by oref0-ns-loop
live4sw
@live4sw
Nov 21 2018 11:48
Has anyone tested tethering with the Pixel 3 yet?
jcorbett80
@jcorbett80
Nov 21 2018 13:09
@danamlewis @alimhassam I am up and running with radio ok. now in the 20+ minute wait period to make sure all goes well. I formmatted card to clean all of the deep install components and started fresh. Did the pi bakery then chose the pi path in the docs. but instead of following it I did the bash then the curl. However where it said "Doi NOT Hit Enter" at the end of the curl I DID hit enter. Did the setup for Oref0 and answered Y Y the rebooted
jcorbett80
@jcorbett80
Nov 21 2018 13:15
@danamlewis @alimhassam I feel sure my 1st TI stick is viable. So once I have a running system I will wire it like eric said and if he confirms the firmware I will flash using the spi then do developer and let you know. Again...not to harp but I promise it is rather to help...IF a note saying TI can not follow this path I would have been on this site helping to work through it much sooner rather than the drama that happened. A paus in the final puysh out is always faster than a rush. I worked with front end for years. It is 100% of the time true. Again...only said to help. If you have been a coder in this group very long you know I have been working with pi's foir a good while. You could have droped me a message to test it and I would have gladly.And that still holds true even when I move to androidAPS.
jcorbett80
@jcorbett80
Nov 21 2018 13:45
I am up and running
@danamlewis @alimhassam I am running again...thank you
Jon Cluck
@cluckj
Nov 21 2018 13:48
:thumbsup:
jgslade
@jgslade
Nov 21 2018 14:09
When I try to login in via ssh I don't get a prompt. I get a connection, am asked for a password, it gives the login message and then a blinking cursor but no prompt. Hmmm... I plugged in a keyboard and hooked it up to a monitor and I get the same lack of prompt when logging in directly.
Last login: Wed Nov 21 07:06:49 2018

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
jgslade
@jgslade
Nov 21 2018 14:16
My rig an pump have also stopped communicating.
If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.

Unsuccessful oref0-pump-loop at Wed 21 Nov 06:19:40 MST 2018

Starting oref0-pump-loop at Wed 21 Nov 06:20:06 MST 2018 with 19 second wait_for_silence:

Waiting up to 4 minutes for new BG: glucose.json newer than pump_loop_completed

Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)

Preflight OK. Profile less than 60m old; Profile valid. Refreshed pumphistory and meal.json

Checking pump clock: "2018-11-21T06:30:05-07:00" is within 90s of current time: Wed 21 Nov 06:30:11 MST 2018

Error: pumphistory too old

oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning

Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)

Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)

mmtune: "916.588", 5, -47 No wait required.

If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.

Unsuccessful oref0-pump-loop at Wed 21 Nov 06:35:18 MST 2018

Starting oref0-pump-loop at Wed 21 Nov 06:36:07 MST 2018 with 1 second wait_for_silence:

Waiting up to 4 minutes for new BG: glucose.json newer than pump_loop_completed

Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)

Preflight OK. Profile less than 60m old; Profile valid. Refresh

Starting oref0-pump-loop at Wed 21 Nov 06:41:50 MST 2018 with 28 second wait_for_silence:

Waiting up to 4 minutes for new BG: ls: cannot access '/tmp/pump_loop_completed': No such file or directory

Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)

Preflight OK. Profile less than 60m old; Profile valid. Refreshed pumphistory and meal.json

Checking pump clock: "2018-11-21T06:49:30-07:00" is within 90s of current time: Wed 21 Nov 06:49:35 MST 2018

Error: pumphistory too old

oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning

Radio ok. Listening: .

Starting oref0-pump-loop at Wed 21 Nov 07:06:07 MST 2018 with 23 second wait_for_silence:

Waiting up to 4 minutes for new BG: ls: cannot access '/tmp/pump_loop_completed': No such file or directory

mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?

Radio check failed.
Jon Cluck
@cluckj
Nov 21 2018 14:24
you might have to reboot to fix that radio error, but it looks like the communications are good
have you manually set temp basals or given a bolus in the last couple hours?
jgslade
@jgslade
Nov 21 2018 14:29
I have not, the radio problems started about midnight localtime. I have rebooted several times.
Jon Cluck
@cluckj
Nov 21 2018 14:29
oh, that could be it: the "pumphistory too old" can be from the pumphistory file being too old, or the last record in the file being too old
try setting a temp basal and giving a tiny bolus to get some new records in there :)
jgslade
@jgslade
Nov 21 2018 14:35
after rebooting I can't establish a connection to get the logs, I can ssh in, but still get no prompt so I can't do anything there
ooh the log site came up
jgslade
@jgslade
Nov 21 2018 14:41
OK. Profile less than 60m old; Profile valid. Refreshed pumphistory and meal.json

Checking pump clock: "2018-11-21T07:36:27-07:00" is within 90s of current time: Wed 21 Nov 07:36:32 MST 2018

Error: pumphistory too old

oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 40s silence before mmtuning

Radio ok. Listening: .No interfering pump comms detected from other rigs (this is a good thing!)

Listening for 40s silence before mmtuning: .No interfering pump comms detected from other rigs (this is a good thing!)

mmtune: "916.588", 5, -52 No wait required.

If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.

Unsuccessful oref0-pump-loop at Wed 21 Nov 07:39:41 MST 2018

Starting oref0-pump-loop at Wed 21 Nov 07:40:04 MST 2018 with 26 second wait_for_silence:

Waiting up to 4 minutes for new BG: ls: cannot access '/tmp/pump_loop_completed': No such file or directory
The pump is less than a foot away from the rig
Jon Cluck
@cluckj
Nov 21 2018 14:49
mmtune: "916.588", 5, -52 No wait required. <-- that's a very good signal
did you do some manual temp basal/bolus entries?
jgslade
@jgslade
Nov 21 2018 15:06
Yeah
Martin Haeberli
@mhaeberli
Nov 21 2018 15:10
I’m getting errors in papertrail log - like …<iframe src="//www.herokucdn.com/error-pages/application-error.html"></iframe>. Only obvious thing I can see is mlab database maybe is full or near full. tried restarting dynos. no other changes to back end. any suggestions?
Nov 21 07:11:17 etghopenaps14 autosens-loop.log: Autosens refreshed: {"ratio":1.06}
Nov 21 07:11:17 etghopenaps14 autosens-loop.log: Completed oref0-autons-loop at Wed Nov 21 07:11:17 PST 2018
Nov 21 07:11:23 etghopenaps14 ns-loop.log: Refreshed carbhistory; COB: 0
Nov 21 07:11:23 etghopenaps14 ns-loop.log: {"batteryVoltage":3858,"battery":68}
Nov 21 07:11:25 etghopenaps14 ns-loop.log: <!DOCTYPE html>
Nov 21 07:11:25 etghopenaps14 ns-loop.log:     <html>
Nov 21 07:11:25 etghopenaps14 ns-loop.log:       <head>
Nov 21 07:11:25 etghopenaps14 ns-loop.log:         <meta name="viewport" content="width=device-width, initial-scale=1">
Nov 21 07:11:25 etghopenaps14 ns-loop.log:         <meta charset="utf-8">
Nov 21 07:11:25 etghopenaps14 ns-loop.log:         <title>Application Error</title>
Nov 21 07:11:25 etghopenaps14 ns-loop.log:         <style media="screen">
Nov 21 07:11:25 etghopenaps14 ns-loop.log:           html,body,iframe {
…
then the error...
Nov 21 07:12:29 etghopenaps14 ns-loop.log:         </style>
Nov 21 07:12:29 etghopenaps14 ns-loop.log:       </head>
Nov 21 07:12:29 etghopenaps14 ns-loop.log:       <body>
Nov 21 07:12:29 etghopenaps14 ns-loop.log:         <iframe src="//www.herokucdn.com/error-pages/application-error.html"></iframe>
Nov 21 07:12:29 etghopenaps14 ns-loop.log:       </body>
Nov 21 07:12:29 etghopenaps14 ns-loop.log:     </html> (NOT VALID JSON: parse error: Invalid numeric literal at line 1, column 10)
Nov 21 07:12:29 etghopenaps14 ns-loop.log: Completed oref0-ns-loop at Wed Nov 21 07:12:28 PST 2018
Jon Cluck
@cluckj
Nov 21 2018 15:27
@jgslade the other possibility is that the history is refreshing too slowly on the pi0, are you okay with switching to the dev branch?
jgslade
@jgslade
Nov 21 2018 15:30
I'd be willing to give it a go
I got a successful ssh login with the pi account, so there must be something funky going on with root.
and you'll have to re-run the interactive setup (don't use oref0-runagain.sh)
hmm, the setup may not have set PermitRootLogin yes in /etc/ssh/sshd_config
jgslade
@jgslade
Nov 21 2018 15:36
I was able to login as root but it doesn't give me a command prompt. It was working yesterday
Jon Cluck
@cluckj
Nov 21 2018 15:37
oh I see, it was hanging :\
jgslade
@jgslade
Nov 21 2018 15:39
I was able to su after logging into the pi account
This doesn't seem good...
Last login: Wed Nov 21 07:06:49 2018

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

npm ERR! fetch failed https://registry.npmjs.org/isstream/-/isstream-0.1.2.tgz
npm ERR! fetch failed https://registry.npmjs.org/jsbn/-/jsbn-0.1.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/json-schema/-/json-schema-0.2.3.tgz
npm ERR! fetch failed https://registry.npmjs.org/json-schema-traverse/-/json-schema-traverse-0.3.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/json-stringify-safe/-/json-stringify-safe-5.0.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/jsprim/-/jsprim-1.4.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/mime-db/-/mime-db-1.35.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/mime-types/-/mime-types-2.1.19.tgz
npm ERR! fetch failed https://registry.npmjs.org/oauth-sign/-/oauth-sign-0.8.2.tgz
npm ERR! fetch failed https://registry.npmjs.org/performance-now/-/performance-now-2.1.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/punycode/-/punycode-1.4.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/qs/-/qs-6.5.2.tgz
npm ERR! fetch failed https://registry.npmjs.org/request/-/request-2.87.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/safe-buffer/-/safe-buffer-5.1.2.tgz
npm ERR! fetch failed https://registry.npmjs.org/safer-buffer/-/safer-buffer-2.1.2.tgz
npm ERR! fetch failed https://registry.npmjs.org/sshpk/-/sshpk-1.14.2.tgz
npm ERR! fetch failed https://registry.npmjs.org/tough-cookie/-/tough-cookie-2.3.4.tgz
npm ERR! fetch failed https://registry.npmjs.org/tunnel-agent/-/tunnel-agent-0.6.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/tweetnacl/-/tweetnacl-0.14.5.tgz
npm ERR! fetch failed https://registry.npmjs.org/uuid/-/uuid-3.3.2.tgz
npm ERR! fetch failed https://registry.npmjs.org/verror/-/verror-1.10.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/ajv/-/ajv-5.5.2.tgz
npm ERR! fetch failed https://registry.npmjs.org/asn1/-/asn1-0.2.3.tgz
npm ERR! fetch failed https://registry.npmjs.org/assert-plus/-/assert-plus-1.0.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/asynckit/-/asynckit-0.4.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/aws-sign2/-/aws-sign2-0.7.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/aws4/-/aws4-1.7.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/bcrypt-pbkdf/-/bcrypt-pbkdf-1.0.2.tgz
npm ERR! fetch failed https://registry.npmjs.org/caseless/-/caseless-0.12.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/co/-/co-4.6.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/combined-stream/-/combined-stream-1.0.6.tgz
npm ERR! fetch failed https://registry.npmjs.org/core-util-is/-/core-util-is-1.0.2.tgz
npm ERR! fetch failed https://registry.npmjs.org/dashdash/-/dashdash-1.14.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/delayed-stream/-/delayed-stream-1.0.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/ecc-jsbn/-/ecc-jsbn-0.1.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/extend/-/extend-3.0.2.tgz
npm ERR! fetch failed https://registry.npmjs.org/extsprintf/-/extsprintf-1.3.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/fast-deep-equal/-/fast-deep-equal-1.1.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/fast-json-stable-stringify/-/fast-json-stable-stringify-2.0.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/forever-agent/-/forever-agent-0.6.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/form-data/-/form-data-2.3.2.tgz
npm ERR! fetch failed https://registry.npmjs.org/getpass/-/getpass-0.1.7.tgz
npm ERR! fetch failed https://registry.npmjs.org/har-schema/-/har-schema-2.0.0.tgz
npm ERR! fetch failed https://registry.npmjs.org/har-validator/-/har-validator-5.0.3.tgz
npm ERR! fetch failed https://registry.npmjs.org/http-signature/-/http-signature-1.2.0.tgz
That didn't quite work how I was intending...
Jon Cluck
@cluckj
Nov 21 2018 15:41
yes that's really weird
Jon Cluck
@cluckj
Nov 21 2018 15:47
you may want to systemctl stop cron before switching to dev to free up some system resources
Martin Haeberli
@mhaeberli
Nov 21 2018 15:50
ok on the nightscout error - devicestatus was full but strange failure symptom ...
Jon Cluck
@cluckj
Nov 21 2018 15:51
@mhaeberli yes it looks like ns-loop was being redirected to the application error page
(which I agree isn't the usual failure symptom)
jgslade
@jgslade
Nov 21 2018 16:39
@cluckj While it was updating my rig started working again, after it finished I was able to login as root via ssh. Though the logs is giving weird outputs again...
Wed 21 Nov 08:43:08 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:44:08 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:45:09 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:46:08 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:47:09 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:48:12 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:50:14 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:51:14 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:52:13 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:53:13 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:54:14 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:55:13 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:56:13 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:57:14 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:58:14 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 08:59:11 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 09:00:11 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 09:01:11 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 09:02:12 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 09:03:09 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 09:04:10 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 09:05:12 MST 2018

Not an openaps environment, run: openaps init

Wed 21 Nov 09:06:12 MST 2018

Not an openaps environment, run: openaps init

==> /var/log/openaps/pump-loop.log <==

Usage: grep [OPTION]... PATTERN [FILE]...

Try 'grep --help' for more information.

Usage: grep [OPTION]... PATTERN [FILE]...

Try 'grep --help' for more information.

No wait required.

If pump and rig are close enough, this error usually self-resolves. Stand by for the next loop.

Unsuccessful oref0-pump-loop at Wed 21 Nov 09:36:17 MST 2018

Updating HAT Display...

Starting oref0-pump-loop at Wed 21 Nov 09:37:06 MST 2018 with 12 second wait_for_silence:

Waiting up to 4 minutes for new BG: First loop: not waiting

Listening for 12s: .No interfering pump comms detected from other rigs (this is a good thing!)

Continuing oref0-pump-loop at Wed 21 Nov 09:37:10 MST 2018

Preflight fail. Retry 1 of preflight

Preflight fail. Listening for 5s: .No interfering pump comms detected from other rigs (this is a good thing!)

Continuing oref0-pump-loop at Wed 21 Nov 09:37:18 MST 2018

Retry 2 of preflight

Preflight fail. Listening for 12s: .No interfering pump comms detected from other rigs (this is a good thing!)

Continuing oref0-pump-loop at Wed 21 Nov 09:37:22 MST 2018

Retry 3 of preflight

Preflight fail. Couldn't preflight

oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 23 s silence before mmtuning

Updating HAT Display...

Listening for 23s: .No interfering pump comms detected from other rigs (this is a good thing!)

Continuing oref0-pump-loop at Wed 21 Nov 09:37:59 MST 2018

Listening for 23 s silence before mmtuning: Listening for 23s: .No interfering pump comms detected from other rigs (this is a good thing!)

Continuing oref0-pump-loop at Wed 21 Nov 09:38:00 MST 2018

mmtune: 2018/11/21 09:38:05 cannot connect to CC111x radio on /dev/spidev0.0

2018/11/21 09:38:05 cc111x: no response
Martin Haeberli
@mhaeberli
Nov 21 2018 16:42
@jsglade @cluckj while I am looping, I’m also still seeing frequent Not an openaps environment, run: openaps init
Jon Cluck
@cluckj
Nov 21 2018 17:09
@jgslade are those messages persisting after you've rebooted following oref0-setup.sh?
@mhaeberli debug mode? see which command is running in the wrong place?
jgslade
@jgslade
Nov 21 2018 17:17
@cluckj they started after, I rebooted again and now it's not connecting to the network.
During setup it was working
Jon Cluck
@cluckj
Nov 21 2018 17:57
hmm
Martin Haeberli
@mhaeberli
Nov 21 2018 17:57
@cluckj thx - remind me how to set debug mode … and which script causes cgm-loop to run ?
my errors look like:
Nov 21 09:44:04 etghopenaps14 cgm-loop.log:  Not an openaps environment, run: openaps init
Nov 21 09:45:03 etghopenaps14 cgm-loop.log:  Not an openaps environment, run: openaps init
Nov 21 09:46:04 etghopenaps14 cgm-loop.log:  Not an openaps environment, run: openaps init
Jon Cluck
@cluckj
Nov 21 2018 18:00
@mhaeberli cd ~/myopenaps; killall -g oref0-pump-loop; OREF0_DEBUG=1 oref0-pump-loop
Martin Haeberli
@mhaeberli
Nov 21 2018 18:00
THANKS!
on an unrelated topic - is there a query of some kind we can do against Nightscout to see how big the mongoDB is? ; also, how to get the mongoDB username/password out of heroku so command line magic can be used?
@jgslade I would power it off to make sure it's actually rebooting (unplug the pi and flip the switch on the HAT)
jgslade
@jgslade
Nov 21 2018 18:16
@cluckj Powering it off seems to have brought the network back and the pump communications.
Is there a way to disable the screen and buttons on the hat? The screen broke and no longer functions. It'sreally disappointing to me, I went with the pi because the screen seemed like it would be useful, but it cracked in the harsh environment of being in my pocket while sitting down
Jon Cluck
@cluckj
Nov 21 2018 18:17
ouch :(
is it looping now?
jgslade
@jgslade
Nov 21 2018 18:21
yeah
Jon Cluck
@cluckj
Nov 21 2018 18:22
:clap:
jgslade
@jgslade
Nov 21 2018 18:23
Thank you for helping getting it back up
Jon Cluck
@cluckj
Nov 21 2018 18:24
no problem :)
what's the state of the screen now?
jgslade
@jgslade
Nov 21 2018 18:26
it doesn't show anything any more, yesterday morning it started showing every other line, then last night the top half of the screen went completely dark, now it doesn't show anything.
Rachel Sandlain
@audiefile
Nov 21 2018 18:52
Is there a trick to accessing the offline webpage on the rig? I'm on the same network and everything but I either get connection refused or empty response errors when I try to access it.
johnnymule
@johnnymule
Nov 21 2018 21:43
How are you accessing the webpage? Hostname or IP address?
Rachel Sandlain
@audiefile
Nov 21 2018 22:55
ip address. If memory serves, hostname.local doesn't work on android.