These are chat archives for nightscout/intend-to-bolus
light it on fire and switch to network-manager ?
Eric, do you have any good suggestion on using network-manager for switching wifi and BT connections and working with openaps?
I have some issues that I am unable to pinpoint . e.g. I've managed to migrate wpa configurations to network-manager (I hope) as the rig successfully connects to wifi. when out of range it will go to BT. The weird thing is that I am not sure if oref0-online has some influence in this, weather if it should have any influence. In network logs I see that oref0-online tries to cycle wlan0 interface, but isn't the point in using NM that it should do this instead of oref0-online? before disabling it (and I am unsure yet how or should I disable this) how do I make sure that I have set up NM correctly?
So after the above uncertainty : when migrating to NM, what did you do for it to work? I've removed wlan and bnep from
/etc/network/interfaces and created SSID configurations for all wifi APs that the rig connects to in relevant NM folder. other than that, is there something else that needs to be done? like, add BT connection profile, or special configuration in openaps to disable oref0-online?
Sorry for the long text. Hope I am making myself coherent.
btw. we are now running pi-zero as a permanent home rig + edison as a mobile rig. They work great in tandem. The pi is working on
ce1e867 dev commit and edison is working on
@Ricco555 with network-manager the oref0-online script should be unnecessary. I completely removed /etc/network/interfaces and interfaces.d/, also the ifupdown package. You still have to connect once "manually" (using nmcli) to each WiFi network and once to your BT hotspot, but after that network-manager will remember all the required info.
The one thing I haven't tried to do is add a WiFi ESSID and password "ahead of time" without just connecting to it. I find myself just using a couple of known WiFi networks and using BT tethering everywhere else
i build my first rig.
I am stuck at "Installing OpenAPS on your rig" : at the end of Step 4 : setup script
I use that command : cd && ~/src/oref0/bin/oref0-setup.sh
I put my parameter.
I try the script 3 times and the script never ask to schedule a cron.
I got that message:
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
/root/src/mraa/ already exists; Updating mraa source to stable release v1.7.0
HEAD is now at 8ddbcde... mraa: Update to v.1.7.0
You are not currently on a branch. Please specify which
branch you want to merge with. See git-pull(1) for details.
git pull <remote> <branch>
Couldn't pull latest mraa v1.7.0 release
Thx for your help,
rm -rf /root/src/mraa/) and re-run setup
journalctl /usr/sbin/NetworkManagerto see what it's been up to
grep serial ~/myopenaps/pump.ini | tr -cd 0-9' with 'mdt settings', he try to connect on 916 Mhz. After every reboot. An 'export MEDTRONIC_FREQUENCY=868.450' set it up to the correct frequency. Then, mdt settings and so on are correct. What is the problem ?
git pullin your ~/src/oref0` directory? there was a bug which made that happen that we fixed
apt-get -y -t jessie-backports install jq
x12-fixwill be considerably easier than running it from
@ecc1 is there some clear schematics about those wires to solder? I would not make another mess
@mrboletmrpot I have the same breakout board and have used only 8 connections. Vin, Gnd, G0, Sck, MISO, MOSI, CS and RST. Mine is using old walrus connection, but the new one as @ecc1 suggested is preferable because installation of openaps is more straightforward. I can confirm, only change G0 to physical pin 15, CS to pin 26, and RST to 22.