An hour or so ago, I noticed NS stopped working…I thought maybe it was just a server side issue but when I started digging, I didn’t see any messages online about any disruption in service. @Liam-M’s NS / Heroku account was set up using his email address…well, apparently his NS has been DELETED due to unpaid invoices that I didn’t know anything about…the last I knew, I was on a monthly payment plan for his Heroku site…Liam may have received those emails, but he wouldn’t have known to tell me about them and I didn’t know.
Long story short, we currently have NO NS site. I’m going to have to set it all up brand new and I remember it being a PITA all those years ago when I did it originally.
Just posting here to remind folks to keep better track of your Heroku account than I did! I just assumed it was on auto-pay, smooth sailing.
I was NOT going to go through the hassle of recreating the Mongo DB, Heroku settings and all that, so I went with a hosted plan…pay $60/year and it’ll be done for me from now on. I remember that being the MOST PAINFUL part of getting his Loop / NS configured way back when and I wasn’t gonna do it again.
I signed up with NightscoutPro and in under 10 minutes my site was back up and running.
I did NOT look forward to spending the entire weekend rebuilding the entire thing.
Child accounts tend to be very well protected by the providers. It’s quite likely that sending a demand for money (i.e. an invoice) to a child will be summarily deleted by the provider.
I certainly think your idea of going with a paid NightScout provider, rather than a paid Cloud provider like Heroku is a very good idea. Originally there were no NightScout (or TidePool, etc) providers; it was very DIY.
Anyone who still is with Heroku or any paid cloud provider really should consider swapping to a (paid) NightScout provider or, possibly, TidePool (which is currently free). The extra cost of going to a NightScout provider really is made up for by the support.
Those who think this stuff should be free can do what I do; I have my own MongoDB which runs on two replicated servers in my garage, running two instances of NightScout, and I use Cloudflare to connect xDrip+ and AAPS to one or the other (it doesn’t matter which). My wife reads my BG through the Cloudflare link. It’s “free”, but it was a lot of work to set up and it has to be maintained. Based on what I was paid in the past it’s costing at the very least $600/year (not counting the time to set it up.)
The only thing I’m trying to figure out again is how to get the remote bolus set up…I have all the API Key / Team, etc., info but can’t get that to appear. I have a support message in on it. Care Portal is on / active plugin. Not sure, but not worried about it right now..just glad NS is back up.
For those who are wondering if NightScoutPro is the only choice, originally I used SugarMate. It was very good; at one time I was able to communicate directly with the developers/owners and they were very good. I stopped when they got bought by Tandem, I think they moved to a subscription model at that point but don’t quote me. They’re not providing NightScout but they should certainly work for anyone who realizes this can become a big issue very fast.
That’s the app, there’s lots of info and opinions out there.
I used to use SugarMate also and have several posts about it from the past. I moved away from it because the alarms/alerts (especially for High BGs) weren’t helpful. I did like the phonecalls, though. But since moving to SugarPixel, there is nothing else comparable for alerting, imo.
That’s probably required. Being able to inject insulin into someone through the Cloud is a big deal and, therefore, a big liability for any provider. I’ve only used NightScout as a recording medium; unless I’ve made a really bad mistake my AAPS will not accept bolus instructions from NS or, for that matter, xDrip+ or anything else.
It’s always required an authenticator token only available on my phone. It’s a great piece of functionality to have available as I can turn on/off overrides, administer remote boluses to him and enter carbs, etc., It was a very useful functionality so I’m hoping I can figure out how to get it set up again with this hosted plan.
Here is how I log in to my current implementation:
Notice that there is no “?token” thingy in the second; instead the log-in is via a user-name and pass-word. The user name is “admin” and I’m not revealing the password
IRC this can be done using the “token” form, however that is insanely unsecure; the “password” goes in to the command sent to the web server and therefore logged by the ISP etc.
So if you are using the “token” form they will probably ask you to change to admin/password and all will work fine. If they don’t and there is some other problem I suggest you change to admin/password anyway; I only worked this out today because I checked xDrip+ and it certainly requires that form. I’m using the twice-nightly release.
API Secret <> Token authenticator for Remote boluses. If you’ve never had it turned on, you should go read the info from Looped on it.
This is a very secure practice and is widely used among Loopers requiring Key creation through Apple Developer Account and that key info linked to your (paid) account being what makes remote activities possible at all. Then anytime you want to issue a command, it requires a 6 digit code through an authenticator app (changes ever 30 seconds).
Go to my website ns.1707hcr.net tell me if I’ve ****'ed up. That bit should be obvious. The issue is that if you use a “token” you’ve given away all your security. Depending on how you set it up this may or may not be an issue. I’m still guessing that this is why NSPro want to check, I’ve never been unimpressed by them and I can’t say that for many commercial operations.
I use an authenticator app (Okta) which produces random 6-digit numbers that change every 30 seconds. Standard part of 2FA which is the most secure method currently for ensuring your security.
You’re thinking I mean “token” == “API Secret”…and I’m not. So maybe incorrect term used. See 1st paragraph above…that is required with remote bolusing…whatever term you like for that random 6-digit number.
API Secret is what allows me to enter Admin mode within NS, OR have SOME level of access…for instance, I have the nurses set up as Read Only through their API Secret (token).
But to remote bolus you have to create a “Key” (APNS_Key) within your PAID (only available in paid accounts) Apple Developer account. Then put the key pieces of info where they need to be and that should make the functionality / plugin work within NS. When it works, I see a “+” in the upper right that I can click to see a list of remote bolus options…I just don’t see the “+” right now. NS Pro offers the right fields that I should be putting the info within to see it, and I put those key pieces of info there, but it’s not working…so I’m probably missing some step that hopefully the CS will help me figure out.
I don’t think that; it’s just a different UI. Talk to the NightScoutPro customer support; this is the very support they are paid to provide and I’m pretty sure that you are not the first parent to call.
All of these guys have always struck me as very professional. They have reasonable requirements for everyone’s safety and, yep, they are incomprehensible. (Not their fault, I blame the WC3
My hope was that the built-in section for that info inside of NS Pro would magically make the plugin visible again (as it did in my old instance of NS), but that didn’t happen. So, hopefully they’ll be able to point me in the right direction.
I had all the info for the below windows and have Care Portal on, so it should have just worked (like magic.)
@ClaudnDaye like @Liam-M my NS/Heroku plan went haywire when they did all the changes some time ago. I’m not good enough with server stuff to figure it out so I just plopped down a small fee/month over at T1Pal with is a hosted NS site started by people who were originally involved in NS.
The fee isn’t huge, the site never crashes and I can write the fee off my taxes just like a medicalert membership.
My endo has a private login, my spouse has a private login and my GPS has a private login that are all specific to them so they can see my data real-time and run any NS reports they want (personally that’s fine with me, and I’m sure you could limit this).
@ClaudnDaye glad you found an easy solution that works for your family.
I’m going to have to set it all up brand new and I remember it being a PITA all those years ago when I did it originally.
