Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 06:41
    samisahla closed #5202
  • 06:41
    samisahla opened #5202
  • 03:03
    escottdexcom commented #5201
  • 02:59
    escottdexcom reopened #5201
  • 02:59
    escottdexcom closed #5201
  • 02:47
    escottdexcom opened #5201
  • 01:25
    jpcunningh commented #5189
  • Nov 12 21:15
    friedl2 synchronize #5200
  • Nov 12 20:44
    friedl2 opened #5200
  • Nov 12 15:50
    sulkaharo commented #5188
  • Nov 12 15:44
    steve8x8 commented #5188
  • Nov 12 15:39
    sulkaharo commented #5190
  • Nov 12 15:38
    sulkaharo commented #5190
  • Nov 12 15:25
    steve8x8 commented #5190
  • Nov 12 15:20
    steve8x8 commented #5189
  • Nov 12 13:59
    ondrej1024 commented #5199
  • Nov 12 13:48
    sulkaharo commented #5199
  • Nov 12 13:30
    ondrej1024 opened #5199
  • Nov 12 08:06
    jasoncalabrese commented #5113
  • Nov 12 08:05
    sulkaharo closed #5198
Paul Andrel
@stavlor
Setting up new connection to MongoDB
Successfully established a connected to MongoDB
Mongo Storage system ready
/home/crm/cgm-remote-monitor/node_modules/mongodb/lib/utils.js:132
      throw err;
      ^

Error: Cannot find module './lib/booterror'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at create (/home/crm/cgm-remote-monitor/app.js:27:22)
    at booted (/home/crm/cgm-remote-monitor/server.js:49:31)
    at Object.boot (/home/crm/cgm-remote-monitor/node_modules/bootevent/index.js:46:9)
    at saw.next (/home/crm/cgm-remote-monitor/node_modules/chainsaw/index.js:62:18)
    at finishBoot (/home/crm/cgm-remote-monitor/lib/server/bootevent.js:216:14)
    at Object.<anonymous> (/home/crm/cgm-remote-monitor/node_modules/bootevent/index.js:12:7)
crm@nightscout2:~/cgm-remote-monitor$
PieterGit
@PieterGit
@stavlor : what mongodb version are you using, if it's mongo2 it might be related to nightscout/cgm-remote-monitor#3394
Paul Andrel
@stavlor
3.4.9
PieterGit
@PieterGit
ok, i think i found some mongo issues, working on a PR at nightscout/cgm-remote-monitor#3413
perhaps that will solve your problem. there is still one unit test to fix and i need to add some code for if mongo is (temporary) down
@stavlor : feel free to test https://github.com/PieterGit/cgm-remote-monitor/tree/201803_npmupdate and report to issue 3413
Paul Andrel
@stavlor
Will do
PieterGit
@PieterGit
@sulkaharo the newest webpack is complaining about the size of our bundle. perhaps we should break down the language and only include english by default. here's a webpack analysis
image.png
WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  js/bundle.js (1.86 MiB)
Paul Andrel
@stavlor
hmm i wonder if it has something to do with my mongo url needing a replicaSet=rs-ds039163 specified
Paul Andrel
@stavlor
interesting
that is appearently the source of my problem if i point it directly at one of the servers in the cluster dev works
if i point to arbiter it apparently doesn't get the replicaset passed in my mongo uri
Paul Andrel
@stavlor
Pulling out user/pw but this is my normal MONGO_CONNECTION=mongodb://<dbuser>:<dbpassword>@ds039163-a0.mongolab.com:39163,ds039163-a1.mongolab.com:39163/nightscout?replicaSet=rs-ds039163
it's probably related to the mongodb nodejs client library
PieterGit
@PieterGit
PieterGit
@PieterGit
Paul Andrel
@stavlor
Thinking the source of the issue is something here:
var dbName = env.storageURI.split('?').pop().split('/'); dbName = dbName[dbName.length -1];
Successfully established a connected to MongoDB
dbName= nightscout
with out replicaset
Paul Andrel
@stavlor
crm@nightscout:~/cgm-remote-monitor$ ./start.sh Setting up new connection to MongoDB Successfully established a connected to MongoDB dbName= replicaSet=rs-ds039163 Mongo Storage system ready
with replicaSet Specified.
Paul Andrel
@stavlor
@PieterGit i think i've fixed it.. looks like someone had the split in the wrong order
starts right up on both my test cases so I'll put a PR in to fix the backwards split
Paul Andrel
@stavlor
@@ -43,8 +43,9 @@ function init (env, cb, forceNewConnection) {
           } else {
             console.log('Successfully established a connected to MongoDB');

-            var dbName = env.storageURI.split('?').pop().split('/');
-            dbName = dbName[dbName.length -1];
+            var dbName = env.storageURI.split('/').pop().split('?');
+            console.log("dbNameR: ", dbName);
+            dbName = dbName[0];
             mongo.db = client.db(dbName);
             console.log("dbName=", dbName)
             connection = mongo.db;
fixes it
PieterGit
@PieterGit
@stavlor : pushed a fix to my branch, still working on fixing the unit test
Paul Andrel
@stavlor
K, sounds good
Martin Haeberli
@mhaeberli
In what release would I find GVI and PGS? - how do I display it (I think I’m running Habanero Red (0.10.2) )
kaabiio
@kaabiio
Is there any way to get NS to display the decimal point of readings in mg/dL (from Spike) instead of the normal rounded reading?
Andy Rozman
@andyrozman
@kaabiio mg/dL doesn't have decimal point.
kaabiio
@kaabiio
spike ss.PNG
@andyrozman The new Spike App reads the decimal point as well in mg/dL
Paul Andrel
@stavlor
Not sure what interesting math they are doing with filtered/unfiltered to get a decimal point but highly doubt there is any real accuracy or significance in having a decimal point in sgv records for that purpose.

In most cases your database records aren't going to look like that...

{
    "_id": {
        "$oid": "5aba720e366a0ca55e7cc31e"
    },
    "sgv": 146,
    "date": 1522168321000,
    "dateString": "2018-03-27T16:32:01.000Z",
    "trend": 4,
    "direction": "Flat",
    "device": "share2",
    "type": "sgv"
}

depending on how the data is reaching NS it may look a bit different.

jamespaulley
@jamespaulley
How can I disable these alerts? https://photos.app.goo.gl/5EA33u8YSguKBuzb2
PieterGit
@PieterGit
@gooseodyssey : these look like https://github.com/nightscout/cgm-remote-monitor#pushover messages. Do you want to disable them all, or only these alerts?
jamespaulley
@jamespaulley
@PieterGit they're pushover alerts yes. I just want to disable predicted high/low warnings
katie disimone
@Kdisimone
Then turn your ALARM_TYPES to simple instead of predicted
jamespaulley
@jamespaulley
@Kdisimone I currently have no value for alarm types. I can try adding "simple". Yesterday I removed values for BG_HIGH and BG_LOW and that might have done the trick.
PieterGit
@PieterGit
@telma2006 can you rebase your patch for azure on nightscout/cgm-remote-monitor#3413 ?
Félix Sanz
@felixsanz
what is raw data? i've been reading all about it but still don't get it
PieterGit
@PieterGit
@felixsanz the sensor sent it's raw sensor value and a filtered sensor value to Nightscout (filtering out very large differences within 5 minute interval).
The raw sensors can be usefull during calibration (in which there is no filtered value available) or in some other cases as described on the page.
Félix Sanz
@felixsanz
i see
but how i do know if it worth activating raw data?
PieterGit
@PieterGit
just give it a try.
nightscout will always record the raw values if your uploader sents them, it's only an option to show them in the UI or not