Hi, I have been trying to install OpenAPS on Pi Hat, Medtronic 722 (which serves as CGM and Pump) and got stuck in error messages for several weeks, Profile invalid, Couldn't refresh_old_profile, etc. The signal between Pi Hat and Pump seems to be strong, and the setup retrieves the data OK and updates Nightscout with BG, but it does not generate any treatment files (no files within enact). I followed Dave Cole's note (http://www.dc9.com/openapsonrpizero/InstallingOpenAPSMasteronRPIZeroW.html). I also tried to install the Raspberry Pi Desktop version, but nothing seems to work. Any suggestions would be appreciated.
Starting oref0-pump-loop at Sun 1 Aug 03:54:07 CDT 2021 with 2 second wait_for_silence:
MDT CGM configured; not waiting
Listening for 2s: .No interfering pump comms detected from other rigs (this is a good thing!)
Continuing oref0-pump-loop at Sun 1 Aug 03:54:11 CDT 2021
Attempting to retrieve MDT CGM data from pump
MDT CGM data retrieved
Old settings: pump profile refresh unsuccessful; trying again on next loop
Profile invalid: -rw-r--r-- 1 root root 596 Aug 1 02:55 settings/profile.json
No more radio errors; canceling reboot
pump profile refresh unsuccessful; trying again on next loop
oref0-pump-loop failed. pump_loop_completed more than 15m old; waiting for 23 s silence before mmtuning
@Foxy7 Thank you! I ran the script as soon as I came home got the following result - it looks okay to me, but I don't know if I expect something else
~/myopenaps# cd ~/myopenaps && sudo service cron stop && killall -g openaps ; killall-g oref0-pump-loop; oref0-mmtune && sudo service cron start
openaps: no process found
├─sed -n s/."response":\([^}]\)}/\1/p
└─socat -,ignoreeof /root/src/openaps-menu/socket-server.sock
killing bash /usr/local/bin/oref0-pump-loop pid 913 pgid 614 running for 430 seconds
mmtune: "916.700", 3, -20 -- "916.750", 3, -22
@tzachi-dar Oh, interesting. So is this 1% closure thing is primarily due to the PiHAT not being powered from a battery and from a wall charger instead? Why is the battery measuring less than 1% if a RPi+HAT is connected to a wall charger? Seems like a noteworthy limitation of that combination, I don't recall seeing that in the docs anywhere?
Although I have interest in diving into the code at some point I don't think I really have the wherewithal to do it now, and am apt to buy a bonnet and use that instead for this planned home-based RPi4 rig. That being said, it is possible the issues I was having with the RPi0+HAT were stemming from this wall charging issue and not the limitations of the Pi0? I don't remember my issues specifically but do remember it working sporatically, so maybe it was related to when it was charged via battery/wall and I didn't make that connection?