Improvements

[Electrik-rich546456]

Hello Ive been using xdrip to receive the data from my FSL2 sensor for a long time now and always thought it was silly to have the need of OOP2 to decode the data from the sensor. Considering this app can do it, why can't xdrip?
Am i mistaken by the looks of your comment #1524 (comment) .

Does anyone know if there is a branch that has the ability so send the data gathered to libreview for my health provider to see my levels and cards and insulin administered

[Teute0815]

• You can use juggluco to receive your sensor data (glucose values) and forward it to xDrip via different means (libre broadcast, local Nightscout, Eversense)
• In juggluco you can also add your LibreView account, so all data will be uploaded there, if you want.
• Regarding insulin, you would obviously have to put that it into juggluco in order to receive it in LibreView, because xDrip doesn't connect to any sensor vendor for good reasons #2742

If it doesn't have to be an original/official "LibreView" Documentation, you can retrieve glucose values from juggluco, add treatments in xDrip and send all this data to nightscout and have a report tool (like Nightscout Reporter) generate your reports - that's how I do it.

Libre 3 -> juggluco (glucose values) -> Libre patched/Local webserver/Eversense -> xDrip (retrieved glucose values + added treatments) -> Nightscout -> Nightscout Reporter -> generate various in depth reports

Some people are also asking for a fully filled OEM LibreLink app. At least for the glucose values you can achieve that by force stopping juggluco half an hour before sensor expiry and scan the sensor with the OEM app. That way you get all the sensor data into your app (no insulin, though). Force stop OEM and rescan with juggluco to get back to your original setting.
In order to be able to do that, you have to retrieve your account ID from LibreView into juggluco (Settings/LibreView) otherwise the sensor won't be recognized. Retrivieng your AccountID is a "one time" thing, you won't have to be connected/sending to LibreView all the time in order to get that working.

[PhilTU]

I was referring to Juggluco's use of Abbott code. That is a vulnerability in terms of DMCS action by Abbott. By keeping sensor specific vendor code or algorithms out of xDrip the project is insulated from this.

Accessing Libreview contrary to the terms & conditions adds to the exposure, Diabox had to remove its Libreview upload.

So while you might find a helper app like OOP2 "silly" it provides a degree of protection and can also be chsnged quickly in response to new sensor types.

Juggluco web site could be shut down tomorrow morning.

[Electrik-rich546456]

Ok so how does oop2 get away with it then ?

[PhilTU]

Either it doesn't breach any IP or it hasn't been noticed. Glimp would be another example.

[Electrik-rich546456]

Glimp doesn't work with fsl2...
as regards oop2 not getting DMCS how and why can't the good apps just have it built in ?

[PhilTU]

Did you try Glimp on a Libre 2 ;-)

some apps contain things that can be interpreted as breaking the law by infringing someone's rights. OOP2 apparently does not. So it's more a case of what's not in OOP2 than what is.

Can you install J..lo without having Libre...k present ? Why is Dia..x apk 50 MB ?