Xdrip smartwatch patch

Xdrip smartwatch patch


  • Welcome to Nightscout
  • New xdrip now supports MiBand 5
  • Patching LibreLink for Libre2 – clearing the FUD
  • Welcome to Nightscout

    Posted in xdrip Hello to all. It has a lot of changes suggested by patrons. I hope you enjoy them. Their contributions were spent to buy a new MiBand5 and implement miband 5 integration and to improve xdrip features. Please note, this is a beta xdrip version. If there are no issues, the pull request will be sent to the official xdrip application. The configuration for MiBand5 was left unchanged. And has the same procedure as for MiBand4.

    The latest version can be found here. Ver 0. Support of the direct connection with libre 2 Ver 0. Added support of Amazfit Band5 device. Collecting step data from the band. See heart rate configuration. Send alarm missing notification if the alarm were missed not dismissed or snoozed. The band setting was reorganized. Removed device-specific settings from the miband settings features and screens menu because they potentially can conflict with mifit and other applications that can communicate with the band.

    All those settings can be configured in third-party applications. Update watchface after alarm if nightmode active. Heart rate collection on new band firmware.

    Hear rate update interval can be configured in MiFit or any third-party application. Synchronized with the latest official xdrip nightly build.

    Nigthmode feature does not work Synchronized with the latest official xdrip nightly build bluetooth connection on android 10 should be fixed. Incorrect nigtmode timer calculation which leads to continious watchface update during nightmode every seconds Ver 0. The watchface can stop updating if there were connection issue during wathcface update. Replace graph BG value representation from lines to dots like in xdrip apk.

    MiBand5 Watchface uploading issue on some phones New. Send readings as a notification option. Now For MiBand 2 and 3 the readings would be sent as notification. For MiBand 4 and 5 would be used watchface uploading. Call notifications. For call notifications use MiFit or any thirdparty apk. I order to simplify debugging, this version has a modified feedback recipient address. The xdrip log reports would be sent directly to my private server.

    If you have some issues please send me the logs so i can analyze them and suggest some solution. The logs can be sent via xdrip events logs interface. If possible, in the feedback description text specify the approximate time when this error happens Ver 0. Graph display changes. Display prediction line even when there no treatments available. Display high and low lines under the bg line. In rare cases, the wathface can stop updating usually happens when Bluetooth connection lost while sending the nightmode Ver 0.

    Display IoB on graph if available Improvement. Watchface uploading speed now should be 3 times faster. For me the watchface uploading for MiBand 4 takes seconds Improvement. Bluetooth status indication. Crossed bg value when there no bluetooth connection between band and xdrip.

    Increased steps and battery font size on all watchfaces Improvement. Data loss indication. The wathcface would be updated faster when there no new data available.

    Following that announcement. Okay then, what does it do? The github repository contains code and instructions for an Android LibreLink user to extend the LibreLink app to pass the glucose values that it interprets from the data it receives over bluetooth from Libre2 out to another listener app.

    It effectively creates an external interface for the LibreLink app. How does this work then? Essentially, what you are doing when you are adding the patch to the code is adding a small, precise incision to the app at the point where the values are generated to create an interface to distribute them out to a receiver app instead of just providing them to the alarm functions within the application. The authorisation of the rightholder shall not be required where reproduction of the code and translation of its form within the meaning of points a and b of Article 1 are indispensable to obtain the information necessary to achieve the interoperability of an independently created computer program with other programs, provided that the following conditions are met: a those acts are performed by the licensee or by another person having a right to use a copy of a program, or on their behalf by a person authorised to do so; b the information necessary to achieve interoperability has not previously been readily available to the persons referred to in point a ; and c those acts are confined to the parts of the original program which are necessary in order to achieve interoperability.

    The provisions of paragraph 1 shall not permit the information obtained through its application: a to be used for goals other than to achieve the interoperability of the independently created computer program; b to be given to others, except when necessary for the interoperability of the independently created computer program; or c to be used for the development, production or marketing of a computer program substantially similar in its expression, or for any other act which infringes copyright.

    Or in other words, if you were to decompile and modify LibreLink yourself in order to provide an interface for the data that it creates which is not readily available from the app already at a programmatic level, then you appear to be covered by this clause of the directive. You as the user of LibreLink for Libre2 have signed up to the license, and that license is not allowed to stop you doing the following under this directive, as stated in paragraph 16 emphasis mine.

    Protection of computer programs under copyright laws should be without prejudice to the application, in appropriate cases, of other forms of protection. However, any contractual provisions contrary to the provisions of this Directive laid down in respect of decompilation or to the exceptions provided for by this Directive with regard to the making of a back-up copy or to observation, study or testing of the functioning of a program should be null and void.

    So what about things like MiaoMiao, Droplet, Bluecon, etc? The original Libre provided data in an unprotected form that could be read and transferred to an app to interpret the data. Effectively the hardware that was being produced was simply using standard NFC protocols to pass data between two devices.

    With the advent of Libre2, the data is now encrypted, which changes things slightly, as in order to create an interface, you need to break the encryption.

    Where does this leave potential users? Share this:.

    The sole purpose of your specific website is to display the data.

    New xdrip now supports MiBand 5

    Due to the caveats mentioned and for many other reasons, it is important to not rely on this for therapy. Reading through the step by step instructions for your particular setup before you start will help prepare you for putting everything together and learning how to use the system.

    Please note: Many of the resources and documents on this site describe the original Nightscout setup which involves a cable and an Android. There are wireless solutions now available. Documentation is being added and revised on an ongoing basis. All we ask is that you pay it forward because wearenotwaiting. Are you looking for technical support for your existing Nightscout installation or do you have questions about your existing Nightscout installation?

    Note: There is no support or any warranty of any kind. The quality and performance of the project is with you if you choose to use it. This is a project that was created and is supported completely by volunteers.

    Patching LibreLink for Libre2 – clearing the FUD

    See heart rate configuration. Send alarm missing notification if the alarm were missed not dismissed or snoozed. The band setting was reorganized. Removed device-specific settings from the miband settings features and screens menu because they potentially can conflict with mifit and other applications that can communicate with the band.

    All those settings can be configured in third-party applications. Update watchface after alarm if nightmode active. Heart rate collection on new band firmware. Hear rate update interval can be configured in MiFit or any third-party application. Synchronized with the latest official xdrip nightly build.

    Nigthmode feature does not work Synchronized with the latest official xdrip nightly build bluetooth connection on android 10 should be fixed. Incorrect nigtmode timer calculation which leads to continious watchface update during nightmode every seconds Ver 0.

    The watchface can stop updating if there were connection issue during wathcface update. Replace graph BG value representation from lines to dots like in xdrip apk.

    MiBand5 Watchface uploading issue on some phones New. Send readings as a notification option. Now For MiBand 2 and 3 the readings would be sent as notification. However, any contractual provisions contrary to the provisions of this Directive laid down in respect of decompilation or to the exceptions provided for by this Directive with regard to the making of a back-up copy or to observation, study or testing of the functioning of a program should be null and void.

    So what about things like MiaoMiao, Droplet, Bluecon, etc? The original Libre provided data in an unprotected form that could be read and transferred to an app to interpret the data. Effectively the hardware that was being produced was simply using standard NFC protocols to pass data between two devices. With the advent of Libre2, the data is now encrypted, which changes things slightly, as in order to create an interface, you need to break the encryption.

    Where does this leave potential users?


    thoughts on “Xdrip smartwatch patch

    1. Willingly I accept. In my opinion, it is an interesting question, I will take part in discussion. Together we can come to a right answer. I am assured.

    Leave a Reply

    Your email address will not be published. Required fields are marked *