mddub / nightscout-osx-menubar Goto Github PK

Hi! Can you add bridge battery information? in drop-down menu somewhere after history.

Nightscout Menubar has encountered a fatal error, and will now terminate.
A Python runtime not could be located. You may need to install a framework build of Python, or edit the PyRuntimeLocations array in this application's Info.plist file.

It seems that Python 2.7 and even Python 3 is not shipped / installed with macOS Monterey.

My solution attempt:

1. Installed Python 2.7 from https://www.python.org/downloads/release/python-2718/ (macOS 64bit)
2. Added to /Applications/Nightscout Menubar.app/Contents/Info.plist in section PyRuntimeLocations:
   /Library/Frameworks/Python.framework/Versions/2.7/bin/python

Then, in terminal:
3. rm /Applications/Nightscout Menubar.app/Contents/MacOS/python (which was symlinking to a wrong location of python: It's not installed in /usr/bin/python anymore, but in /usr/local/bin/python)
4. ln -s /usr/local/bin/python /Applications/Nightscout Menubar.app/Contents/MacOS/python

When I try to launch Nightscount Mebubar, it seems to go a little further, but still, I get a little dialog saing "Nightscount Menubar Error" with the buttons "Open Console" and "Terminate".

In Console (system log) I just see
Apr 24 01:01:25 MBP5 Nightscout Menubar[6316]: Nightscout Menubar Error

Now, I don't know what I could do anymore.

is there any way i can modify the python to accept two Nightscout URL? I got two kids with T1. I love this app btw!!

This would be really handy to have in the dropdown menu :)

Right now the app requests the 6 most recent SGVs every 20 seconds. It should instead cache them, and request only SGVs with a timestamp newer than the most recent one cached. Then it could also continue to display when there's a brief network problem.

Menubar correctly pulls in data on configuration, but doesn't automatically refresh. (Going to configure and hitting "ok" pulls in new data, though.)

I think it's a good idea. Just red color at menubar

I don't like using AM and PM, my Macbook is displaying 24hrs and its faster to see if it matches.

It regularly falls behind so i need to check it fast.

I apologize for not attaching any leak analysis, but in Activity Monitor, Nightscout is using 2 GiB of real memory after running for several weeks.

How do you set an API key here? I have all my data protected with a key so only those with it can access the logs.

Thanks.

Would be great if we could configure the app to use mmol as unit instead of mgdl.

Hey,
I Love Nightscout Menubar.

I work at a place that has the vast interwebs behind a proxy, so I was wondering how hard it would be to add a setting for the user to enter a proxy address, and to push HTTP requests through that proxy.

Thanks!

If I double click on the app, nothing seems to happen. If I run it from the command line I get the following:
LSOpenURLsWithRole() failed for the application /Applications/Nightscout Menubar.app with error -10810.

Error code 10810 is pretty useless.

Console message is also useless.
Nov 14 12:16:45 Johns-MacProTwelve com.apple.xpc.launchd[1] (com.warkmilson.nightscout.menubar.39984[37191]): Service exited with abnormal code: 1

Somehow I got it running once (not sure what I did) but I thought it was a good app and would like to get it running regularly.

Thanks.

Great little app! Thanks!
I modified nightscout_osx_menubar.py to have the token, since ours is a locked down site. Might be nice to add as an option in the program.

/api/v1/entries/sgv.json?count={count}&token=XXXXXXXXXXXXXXXX

This is strange, I got my workaround: the NS website IS working!
The Tomato app seems to upload it to Nightscout.

But only the NS menubar can't get it from the Heroku server anymore? link hasn't changed and it supposed to get data through Nightscout anyway.. please explain why it cant get the data?

Many Thanks,
Jules

After the latest upgrades to my Nightscout instance, the menubar doesn't work anymore, complaining about TLSV1_ALERT_PROTOCOL_VERSION. Is this something I can fix myself?

Delta value is correct for ~1 minute after a new reading, but then it becomes "+0.0".