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

3rd
Apr 2019
Ralsty12
@Ralsty12
Apr 03 15:36 UTC
Hey guys, I always get this error "Radio check failed. mmeowlink.exceptions.CommsException: Could not get subg_rfspy state or version. Have you got the right port/device and radio_type?"
I can manually mmtune succesfully but my loop never get past this not matter what I've tryied. (Raspberry Pi Zero W with RFM69)
Eric
@ecc1
Apr 03 15:42 UTC
The RFM69 support is only in the dev branch. That mmeowlink message means you're running master
Ralsty12
@Ralsty12
Apr 03 15:43 UTC
I did run "cd ~/src/oref0 && git checkout dev" before the install, is there more the locking in the dev branch?
Eric
@ecc1
Apr 03 15:52 UTC
@Ralsty12 I think you have to run the setup script and npm install steps, but others know more about that
Ralsty12
@Ralsty12
Apr 03 16:04 UTC
@ecc1 haven't tried rerunning the npm install, thanks
Abigail Cember
@acember
Apr 03 18:53 UTC
Ok, solved! I added one line of code: the first thing I do in fail() is call oref0-set-system-clock() to make the system time match the pump time. @scottleibrand , this is what you suggested, minus the grep: as far as I could tell that condition was not being met, so I just got rid of it. I can't think of any situations where one would not want the system time set to the pump time if NTP was not available (aka, offline looping), so I think this is the best set-up. It's definitely the most robust: people can set the time on their pump with its own interface, but if you're operating with no monitor, no internet, no battery, and no ssh-ing, now I (and any other luddites/people who need their rig to work in such rough conditions ) can just walk into any Starbucks with a rig that's unpowered and untethered, plug it into a USB port, and start looping.
Jon Cluck
@cluckj
Apr 03 22:51 UTC
:-D