Design a site like this with WordPress.com
Get started

New xdrip now supports MiBand 5

Posted bybigdigitalPosted inxdrip

Hello to all. I’m glad to announce the release of a new version of xdrip. It has a lot of changes suggested by patrons. I hope you enjoy them. Special thanks for patrons Monoid, kyungmee Yoo, mzst 123, Lukas Petro, Alberto HD,Otto75so3e, Michalis Velonakis whos supported this project. 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. (just make sure you use an updated patched MiFit v4.2.0)

New watchface legend for MiBand5

The MiBand4 have the same watchface except it has missing weather information

Xdrip miband integration apk changelog

If you like this project and want to thank an author for work done or want to support further development of features, become a sponsor on Patreon

If you have some advices regarding features that you want to see, or want to see similar feature on some specific band type, please write them in the comment of the donation form.

The latest version can be found here.

Ver 0.3.2.6(05.01.2021)

  • Synchronized with the latest official xdrip nightly build. (Support of the direct connection with libre 2 )

Ver 0.3.2.5(13.12.2020)

  • New. Added support of Amazfit Band5 device.
  • New. Collecting step data from the band. This option can be enabled in the “General settings” menu (The pool intervals defined by third-party applications like MiFit. See heart rate configuration ).
  • New. Send alarm missing notification if the alarm were missed(not dismissed or snoozed).
  • New. 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.
  • New. Update watchface after alarm if nightmode active.
  • Fix. Alarm hangs on “WAITING_USER_RESPONSE” state when night mode active.
  • Fix. Heart rate collection on new band firmware. Hear rate update interval can be configured in MiFit () or any third-party application. To see heart rate data in xdrip, the options “Use Health Data” and “Heart Rate sensor” which is located in Settings -> Smartwatch Features -> Smartwatch sensors, should be enabled.
  • Synchronized with the latest official xdrip nightly build.

Ver 0.3.2.4(23.11.2020)

  • Fix. Nigthmode feature does not work
  • Synchronized with the latest official xdrip nightly build (bluetooth connection on android 10 should be fixed. But if you still expierence a bluetooth connection issue, please try to enable “Minimize Scanning” and “Avoid Scanning” options in xdrip settings )

Ver 0.3.2.2 (18.11.2020)

  • Fix. Incorrect nigtmode timer calculation which leads to continious watchface update during nightmode (every 2-5 seconds )

Ver 0.3.2.1 (01.10.2020)

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

Ver 0.3.2 (09.09.2020)

  • Debug. 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. Before sending logs, please make sure you have added “MibandService:d” text (without quotes) in xdrip Settings->Less common settings-> Extra logging -> Extra tags for loggings . After this go to “Less common settings” -> View recent error interface. Leave enabled only “Low”, “Mid” and “High” checkboxes And click to “upload logs” button. If possible, in the feedback description text specify the approximate time when this error happens

Ver 0.3.1 (31.08.2020)

  • Fix. Use the same graph height and offset for all band screens and modes (required to correctly position “no connection” layers )
  • Fix. Graph display changes. Display prediction line even when there no treatments available.
  • Fix. Graph display changes. Display high and low lines under the bg line.
  • Fix. In rare cases, the wathface can stop updating (usually happens when Bluetooth connection lost while sending the nightmode )

Ver 0.3 (25.08.2020)

Advertisement

252 thoughts on “New xdrip now supports MiBand 5”

    1. Thank you!

      This is life changing.

      Miband 5 with xdrip and Dexcom G6

      One question: watchface displays weather temperature units in degrees celcius. I’d really like them in Fahrenheit. Where is this set?

      Thanks,
      Ken

      Like

      Reply
  2. Pingback: r/diabetes - PSA: XDrip now working on the Mi Band 5 | Pro Halki Diabetes Remedy

  3. Awesome, great work!
    I have 2 questions:
    1. Does the watchface of the new version differ from the upload you provided?
    2. Regarding the performance improvements, are they due to code changes or did you mange to optimizie the watchface?

    Looking forward to the approvel in xdrip branch.

    Like

    Reply

    1. I’m not planning increasing graph height because the free display space was reserved for custom watchfaces, so the user can display any information they want (heart rate, pai, etc).

      Like

      Reply

          1. Hi. This is such a great project. Thanks for all your work on it. I’ve installed v0.3.2.5, and can pair thr mi band 5 with the xDrip app, but there’s no watchface file in the xDrip folder, and no BG readings show on the band. The band just vibrates whenever a new BG reading is taken.

            Like

            Reply

  8. Hi Artem
    I am upgrading from Band 4 to Band 5.
    I deleted the key for B4 in \freemyband and after taking the steps I have auth key for B4 there. However Xdrip keeps finding auth key for B4. I tried to manually enter the Mac and the key manually, no connection with the band from xdrip.

    Like

    Reply

      1. Thanks a lot for your great work. It’s running smoothly on the MiBand 5. Can you please set the language to automatic, i’m on German language and the rest of the Band shows german letters only the Watchface is on English. Thanks in advance.. Do you have PayPal for some coffees?

        Like

        Reply

        3. Hi, the german letter defined in the wathface file. You can upload custom wathcface file with the modified watchface resources.
          Regarding paypal donations. Unfortunately there no legal way to receive payments via paypal in our country 😦 . But you can donate via Patreon service and after the first donation, you can unsubscribe. In this case, you will donate only once.

          Like

          Reply

          2. Go on the top of this blog, you will found there the latest version. You must change your xDrip App to this version. Make a backup before you delete the “normal” xDrip app. After installing you can restore your data

            Like

            Reply

      2. Please try to regenerate auth code. For this, open patched MiFit app. If you already have a paired miband here, unpair it. Then go to /sdcard/freemyband folder and delete all files here.
        After this pair your band again. Now, go to xdrip miband menu. Switch off the option “Use miband”, and then clear fields “mac address” and “auth key”. Now, switch on the option “Use miband”. You should see that your miband was found and succesfully authentificated. If not, recheck that mac address which was automatically found is the same as on your band and correct it in the “mac address” field. The mac address can be found in the mifit application.

        Like

        Reply

        1. Dear Artem
          Tried everything you told + many other things else: deleting, disconnecting, resetting the bands etc.
          Even after resetting both bands and downloading auth key for B5, xdrip search finds B4 instead of B5, even though B4 is not connected to the phone and mi fit app, whereas B5 is. I tried to be away from B4, again it does not see B5 as before.
          My B4 is of international version, B5 is of Chinese version. May it be the cause of the problem?
          Thanks in advance.

          Like

          Reply

          2. Long Story: i tried 1,5 days to connect the Chinese 5 version. When I opened the patched mi fit app to get the key, something connect it as band 4. After I installed the official mi fit app I get two updates and it was on b5. But I tried before to connect the band with xDrip and have the same fail. After reinstalling the band-xdrip version 3.0 and deleting the cache of the app it’s connecting perfectly. Maybe important: I do the restore on the xdrip app AFTER connecting to the band.

            Like

            Reply

          3. I also use the Chinese version and it works perfectly for me. First of all, make sure you use the latest xdrip version from this article (not 0.2.x) After this make sure you have enabled band visibility in the mifit settings. And then try to search miband again. If this does not help, enter mac address manually. Hope this help.

            Like

            Reply

  10. Upgraded from 4 to band 5 today. Having trouble with syncing the watchface. It is working once then nothing. If i choose another watchface in the mi fit app and then manually update bg in xdrip it works one time but then stalls again. Xdrip log says “mibandservice Could not write start command”. Any advice please?

    Like

    Reply

      1. Hi, from the error, it looks like something happen with Bluetooth connection. Please try to enable the option “Disable hight MTU” which is located under experimental section in miband menu settings. If this does not help, could you please send me a detailed error log? For this please go xdrip Settings->Less common settings-> Extra logging -> Extra tags for loggings and enter here “MibandService:d” (without quotes) . After this go to “Less common settings” -> View recent error interface. Leave enabled only “Low” checkbox . Search “Begin uploading Watchface” message and make a print screens till the error “could not write start…”. You can send screenshots to my email bigdigital.kov@gmail.com

        Like

        Reply

        1. FWIW I’m having the exact same problem on Mi Band 4. Upload is fast with MTU disabled (2 or 3 seconds), but it stops working after a while, and the watchface goes back to the default one from the mi band. When enabling MTU, the upload speed goes back to 10 seconds or so, and then the glucose stops updating, but the glucose watchface remains. I tried to get the error log, but it is too long to make a screenshot, and I can’t seem to get it out on text.

          Like

          Reply

          1. Hi Could you please try to install the following test application and let me know if it would work better for you
            https://www.dropbox.com/s/ku44dkv42o5x4ji/xdrip_miband_0.3.1.3_test.apk?dl=0

            In any case please send me the xdrip logs after you test this application.

            Here I also modified a feedback recipient address to my private server. So the log reports would be sent directly to me. To send xdrip logs, you would need to click to the “upload logs’ button which is located in the events logs interface.

            Like

            Reply

  11. Thanks for your software. It works well and with (almost) no problem. Although it says multilingual I notice that large parts of it (notably Spanish and french) are untranslated as well as the installation manual and documentation. How can I help? I have ample experience and I am willing to help as a pay back for your work.

    Like

    Reply

    1. I’ve tested the latest 0.3.1.2, and it works fine with the option “Disable hight MTU” enabled, where sync time goes back to about 10 to 12 seconds, but at least it is reliable. If I disable it, sometimes it syncs in 2 to 3 seconds at first, and other times the band just said that it could not sync, and goes back to the default watchface all the time, so it is not working at all with “Disable hight MTU” disabled..

      Like

      Reply

  14. No enlaza automaticamente xdrip 0.3.1 con mifit 4.2.0
    Tampoco sale la opción para escribir la auth key manualmente.
    Saben como solucionarlo?

    Like

    Reply

    2. Fue el mismo caso que yo tuve, pero la solución es relativamente sencilla hasta que el desarrolador resuelva el problema, Si sigues las instrucciones cuidadosamente, al instalar el Mi Fit modificado (v4.2.0) y enlazarlo con tu Banda Mi Band) crea un directorio en tu teléfono con la “llave” (llamemosla así). Se forma de dos partes: Lo que se conoce como una dirección MAC y la llave de autorización; ambas están separadas por un punto y coma . Escribe la 1era en el campo que te soliicita (inutil esperar, por el momento no la recupera) requerido y xDrip+ reconocerá la segunda (o tambien escribela

      Like

      Reply

    1. El problema que están teniendo muchas personas en España es que la pulsera no se vincula con mifit modificada. Incluso cuando han estado sincronizadas anteriormente.
      Por mucho que reseteamos las pulseras a los valores de fábrica, desinstalamos mifit modificada y la volvemos a instalar.
      La myband4 no se vincula con mifit.
      Tenéis alguna idea de cómo solucionar lo?

      Like

      Reply

      2. Francisco et all:
        Mi esposa tuvo un problema ayer:
        Después de usar sin problemas la versión 0.3.2 de xDrip+ por alrededor de 10 días, súbitamente falló. La conexión con Bubble se perdió y por más que hicimos fue inútil: no pudimos recuperarla:
        • Reiniciar Bubble y cargarlo al 100%.
        • Reiniciar alrededor de 1000 veces xDrip+ para al final desinstalarlo y retrogradarlo a la versión 0.3.1.
        • Olvidar todas las configuraciones de xDrip+ y comenzar de nuevo
        • Reiniciar MiBand 5 y reconfigurarlo nuevamente.
        En la desesperación total obviamos lo más simple reinicializar el teléfono (un Samsung J5 2017). Como magia todo volvió a la normalidad. Seguimos usando la última versión de xDrip+ sin problemas (más que por el español chungo ; trabajando en ello). Gracias BigDigital por tu programa (que no puedo compilar en Android Studio 4.0.1 64bits)
        Moraleja: no perder la calma y empezar por lo más obvio y sencillo (o perder el tiempo y la paciencia).

        Like

        Reply

  16. Hi,

    I’m on version 0.31.3 – no connectivity problems so far. I read somewhere that band should lower brightness settings during watchface synchronization. Mine didn’t – it doesn’t matter what i setup in xdrip settings. I am doing something wrong or this works same for others?

    Like

    Reply
  18. Pingback: Future of the xdrip miband project – Artem blog

  19. is this watchface also available for MiBand 4 or only MiBand 5? I’ve tried everthing to get my MiBand 4 looking like the new one from this article. I made the unpair/repair process 5-6 times now but it still looks like the MiBand 4 Graph without the weather and new IOB graph. I thought I’m enough tech geek to get it working ;D ;D

    Like

    Reply

      1. Yes I know, thats the one I’m able to use. Okay thx for the info. Are there plans to make it avaulable on MiBand 4 in the future, I bought my MiBand4 only to test your watchfaces and beeing able to support other diabetics with the setup and everything sround it, many ppl including me are interested in the MiBand5 watchface it offers weather and heart rate plus everything else we need. My MiBand4 arrived 1 week before the MiBand5 release xD so I dont really want to buy a new one only because of the watchface availability. Would be really nice to have it for MiBand4 too 🙂

        Thanks for your develompent that really helps many older diabetics which are confused when using a complex smsrtwatch with all the tech in it. The MiBand xDrip üroject and the MiBand itself is very very easy to use for each of us and thats a huge arguement to use this!! As I told, I bought it especially to dontje setup, but I’m wearing it every day becsuse I’m very impressed of its easyness 🙂

        Like

        Reply

  20. I’ve installed your version 0.3.2 and am not getting any alarm sounds any more.

    I just wanted to find out whether this is intentional or whether I have overlooked some setting.

    What might also be the case is that it is a very unusual bug because before using the Mi Band my xdrip was connected to a Pebble. For a few days I had both connected to your version, which worked okayish. The Pebble seemed to loose the BT connection more often. At that time I already got no alarm sounds any more. Should I create a bug report on Github?

    Like

    Reply

      1. Hi, thanks for the reply. I’ve been using xDrip+ for years and when I installed your version I just imported my config and database. My config has LOW alarms with sound for the whole day and a HIGH alarm with sound only over night. Also the predictive alarm is with sound.

        (In chronological order:) This night I got several HIGH alarms but I don’t remember whether I actually heard a sound. I also remember that I got an alert on the band (I think it was the predictive alarm but at that time I could only see the HIGH alarms in the logs) that I could snooze but the alarm and vibration would always come back after a few seconds. The only thing that helped was a reboot of the phone.

        The only alarm I actually heard was the LOW alarm for daytime right after I got up today. Maybe I just had to reboot the phone then? I will keep an eye on it an keep you posted, if necessary.

        Like

        Reply

    2. Hi there,
      Thanks for your great work

      Is it possible to configure a watchface that can have 2 readings on it from 2 separate collectors?
      Many thanks

      Like

      Reply

  21. Thank you so much for your hard work!
    I got it working it seems but I can’t get the heart rate displayed on the watchface even though the box is ticked.
    Also, the features like stress measure and cycle etc have disappeared from my menu on the Miband 5 – do I need to change any other settings to get that back?

    Thank you so much ^.^

    Like

    Reply

  22. I would like to support you financially but $33 per month is quite a lot to ask. As far as I know Patreon allows its users to specifiy different tiers of service. Wouldn’t it be possible to also offer a $5 tier and a $10 tier? I bet you would get more money overall because more people would pay for your Patreon.

    Like

    Reply

    1. 33$ are you sure? I haven’t set any specific charge value. You should be able to enter any donation value. I have patrons who donate 3$ and 5$ per month. In addition, if you wish, you can donate only once.

      Like

      Reply

      1. Yes, sorry, my mistake! I was looking for the different tiers, which weren’t there, and then misread the dollar amount at the top.

        Like

        Reply

        1. The iob value on the miband updates together with bg values. So i see two possibilities why this can happen. The iob was changed between readings or wathcface for some reason was not synchronized (i.e missing Bluetooth connection)

          Like

          Reply

  23. Hey, thank you so much for the active development. This bug with the night mode and loosing watchface is bugging me, but i couldnt pin it down!

    Do you already have a schedule when to send the pull request to ofical xdrip? I’m not sure if it makes sense to delet everything and install your version or i it makes sense to wait a little longer.

    Like

    Reply

    1. Hi. Nope,  i dont have any schedule for pull request. The current apk is still not ready (want to make better “other” alarm handling and make sure everything works stable). For now i suggest install and use latest xdrip from my blog.

      Like

      Reply

  24. Hi, I am using a new mi band 5 with Xiaomi Redmi 9. I followed all the steps but the watchface did not change. The mi band screen did not change and i dont receive notifications also. Have I done something wrong?

    Like

    Reply

  25. Hello! I have set up mi band on a redmi note 7. I am not getting xdrip+ readings at night. Any ideas? I haven’t noticed this so bad before. The watch face looks great. Thanks!

    Like

    Reply

  26. There is a slight bug that happens when dismissing an alert on the band. When the red button is press, there are 2 additional vibrations that weren’t there before. It was probably introduced because of the additional text that is used to tell the time that the alert will be dismissed.

    Like

    Reply

  27. Thanks for your great job… is some way to use this with AMAZFIT BIP? It´s the best xiaomi watch, as cheap as mibands, with a battery lasting 1 month, a bigger screen and ALWAYS ON (no need to turn the hand)¡¡¡¡ it would be great

    Like

    Reply

  28. Hello, today I sucessfully installed my new Mi Band 5, everything works like a charm.
    Thank you for your great work.
    Just one question: is is possible to change the wathchface that way, that instead of weather for example heartrate will be shown?

    Like

    Reply

  29. Hello,
    I have some issues with pairing my Band 5 with the phone Xiaomi Redmi Note 5. The XDrip says the band is connected, but not authenticated. In the XDrip Menu for Mi Band setting it is not possible to put auth key, I can add just MAC address. What should I do to fix it? Thank you for help.

    Like

    Reply

      1. Still the same ☹️. The file with auth key is not saved in SD card in my phone, but in internal storage (i dont have SD card in phone) Could be this the problem?

        Like

        Reply

  30. Great job. Thanks.
    This is just to report that the “Check for update version” button does not work. When you press it nothing happens. If there is a new version you just need to download it by hand and force the installation. From that point on, the update is recognized as such. Is there a bug or an error in the procedure to do updates?

    Like

    Reply

  31. Hi there, worked for half a day then locked after being out of range and had to redo but now there is no auth selection in xdrip. Have tried many times but always the same, MAC address selection there but auth selection no.
    Many thanks.

    Like

    Reply

    1. After successfully connecting the band to xDrip (means, that the patched MiFit app generated the txt-file with mac-adress and authcode) you can reinstall the original MiFit App from Playstore to get the language you’d like and any other available updates.
      The band will still work in xDrip unless you disconnect it from MiFit or perform a reset on the band.
      In this cases you have to reinstall the patched MiFit app to geenerate an new mac-adress / auth-code file.

      Like

      Reply

  35. Si vous allez sur Google Play et recherchez “My Fit App”, vous devriez trouver un bouton vert qui dit «Update» au lieu de «installer». Cliquez dessus pour que l’application soit mise à jour, le problème sera que votre montre sera peut-être dissociée et vous devrez refaire le processus d’obtention de l’adresse MAC pour xDrip

    Like

    Reply

  36. Man, you are the best!
    I had the Miband 3 and tried it with Xdrip but I didn’t like the texts every 5 minutes so much. So now I bought the Miband 5 and after about 2 days work I managed to get it going with AAPS, Xdrip+ and Mifit app.
    I can now see my BG on my phone, my watch and my receiver for my Dexcom G6.
    This is the future!

    Thank you so much!

    I started to sponsor you on Patreon and recommend to everyone else to do the same. Just 1 Euro/ month can make a difference already. I give 1.50.

    Cheers my dude, and keep up the good work!

    Like

    Reply

    1. Hi. I’m glad this project was useful to you and thank you for the donation. In the near future, i’m planning to spend collected fund to buy another one watch type. So hope the number of supported devices would be extended.

      Like

      Reply

  38. Hi, first of all: Thank you so much for the great work!

    On my phone, I’m using Gadgetbridge instead of MiFit App because of data protection reasons. Furthermore, I have installed the latest version of xDrip found on the top of this page.
    In general, everything is working perfectly fine.
    Sometimes during the night, there is a problem occuring. (Could also happen on day, but I never noticed it.)
    The miBand 5 keeps receiving new BG values but doesn’t vibrate when an alarm should go off. Instead of this, the band keeps on showing the syncronising sign every few seconds. It starts syncing, then it shows “sync completed” and waits a few seconds, then starts syncing again. It won’t stop doing this until I switch off and on again the bluetooth on my phone so the two devices unpair an pair again. Sometimes, also the watchface stops updating the BG values.
    I was wondering if the problem could be that the two apps (xDrip and Gadgetbridge) are trying to control the band, so both of them want to sync the settings.
    So I tried disconnecting the band from the Gadgetbridge app, but it still happens every now and then.
    Do you have an idea how I can solve this problem?

    Thanks again and cheers

    Like

    Reply

    1. Hi. This looks very close to the recent fix i’ve made. I’ve uploaded updated version for the xdrip. Could you please try it and let me know if problem would be fixed for you?

      Like

      Reply

      1. I used to use version 0.3.2.1 since something like three weeks ago, but the problem still occured from time to time. I’m almost sure that it has something to do with the Gadgetbridge App and some kind of conflict between the two of them.
        Anyway, I tried installing the new version 0.3.2.2 which you uploaded today, but the link only shows the dropbox page with version 0.3.2.1.

        Like

        Reply

      2. Cannot reply on your latest answer for some reason. Now I succesfully installed version 0.3.2.2. I’ll let you know if there are still problems.

        Like

        Reply

        1. Hi Artem. So now, three days after installing version 0.3.2.2, I had an issue tonight. The watchface was not updated for a few hours. The band also didn’t receive any of the several alarms that xDrip sent during this time. In the mornig, I solved the problem by deactivating and then reactivating the bluetooth on my phone.
          I had a look in the log of xDrip and noticed that after the last watchface update at 0:22, there were no signs that xDrip even tried to update the watchface. In the log note from 0:22, everything seems usual (first WatchFaceGenerator, then MiBandService). After that, there are no unusual errors listed.

          Like

          Reply

        2. Hi Artem, now, after three days of using version 0.3.2.2., I had an issue last night. Waking up at around 6, I noticed that the watchface wasn’t updated since 0:22. After deactivating and then reactivating the bluetooth on my phone, the watchface update every five minutes was working again. Having a look into the xDrip log, I noticed that after 0:22, there was not a single hint that xDrip even tried to update the watchface. After restarting the bluetooth of my phone, the usual notes in the log started to appear every five minutes again (first WatchFaceGenerator, then MiBandService).

          Like

          Reply

          1. Edit: When the usual log notes started appearing again, the watchface update every five minutes was also working again.
            Do you have an idea how to solve this problem?

            Like

            Reply

            1. Hi. Due to some missconfiguration, my previous build had missed some important latest official xdrip fixes. This can be the cause of the issue. I’ve uploaded the updated xdrip version. Could you please try it? Hope this help.

              Like

              Reply

              1. Hi Artem. I installed the newest version on 23.11. Unfortunately, I again had some problems. Tonight at some point, the miBand stopped giving alarms, until a few hours later, I woke up realizing the BG was out of range. Then, the watch started giving all the alarms that were missed in the time before. So for example, there was the “high” alarm which should have gone off 2 hours before. The I tapped the deny button on the band. After that, the band started showing the syncronising symbol. Then, it directly started to show the next missed alarm, and so on. Reconnecting the bluetooth on my phone helped. Do you have any idea why this issue occurs? It seems like it only occurs during the night.

                Like

                Reply

  39. Thank you so much for the new update 3.2.2 corresponding to the Samsung Bluetooth issue!
    It works very well so far, one slight issue when I reimported database and forgot data source was still set to dexcom follower.
    Switching miband transmission off and on again and sending Bg data manually resolved it 😀
    Is there a way to say thank you with a one-off donation somewhere without patreon?

    Like

    Reply

  40. Hi, I had one issue I found – it worked perfectly until I lost connection in the subway, since then it is asking me to pair every 5 mins again.
    I saw other threads and they had an option called ‘Avoid scanning’ that is not available in this version.

    Would you know any other way to stop the pairing request? Delete and reinstall every time it loses bluetooth connection?
    Thank you 🙂

    Like

    Reply

        1. Hiya, I used the latest version fro your blog. I did reinstall after encountering the error and it asked me once to pair – then suddenly stopped asking and it has been working fine ever since.
          I will need to use the subway again after work – the issue seems to appear when connection is lost for some time, then the pairing requests start.
          I will update you tonight if it happens again – however exporting database, deleting and reinstalling is currently a sort of fix around it.

          Another user reported a connectivity issue, couldn’t get a signal again after it working for 5 minutes and had to go back to the official build. I’m trying to help her too.
          Any settings/reports you need, please let me know.
          Thank you so much for all you do ❤

          Like

          Reply

          1. Ok, i see. Here is suggesting for similar issue from xdrip developers: “The Avoid Scanning is likely the crucial option that you need to both work-around the Android 10 issues and the November security patch. You have to also enable Minimize Scanning before it will let you enable Avoid Scanning”. So you can try to enable these options in xdrip.

            Like

            Reply

            1. Thank you – in my case, I had minimize scanning enabled but no function of ‘avoid scanning appeared – this is on the 3.2.2 version

              Like

              Reply

              1. Ah, really. My fault, seems for some reason i didn’t had the latest xdrip changes from the official repo so they were not included in my build. Thanks. I’ve updated the xdrip again. I believe this should fix the latest connection issues.

                Like

                Reply

                1. Thank you! Downloaded and connected fine, ticked ‘avoid scanning’ and am currently in the subway. Don’t seem to lose connection every time I use the subway but will let you know if there are any more issues. Miband etc all connected fine.

                  Like

                  Reply

                  1. Just wanted to confirm, using the newest version I lost connection on the subway an it reconnected afterwards without any issue- thank you so much!

                    Like

                    Reply

  41. Hi Artem, since a few weeks I got miband 4 working. I must say you have done a great job. Thx so munch. I have a question, does this work also with amazfit band 5, since amazfit und huami have worked together on their band 5 respectively.

    Like

    Reply

  42. Apologies but I suddenly seem to have issues after trying to recalibrate the sensor. Tried to delete and reinstall but even the database I exported didnt seem to contain all information, like insulin profiles are missing and were reimported incorrectly as well.
    Enabling multiple insulin profiles seemed to have fixed it and I managed to see the lines again.

    Currently I am unable to get any connection, I missed one pairing request pop up and a second one hasn’t come up yet.
    Will keep trying and update if I can get it working

    Like

    Reply

    1. I am getting a ‘got data’ in the system status but nothing appears in xdrip at all. Have tried to restart my phone too, but nothing works.

      Like

      Reply

      1. Apologies for the many messages, I got it working from scratch without importing data base but now I cannot calibrate anymore, I get a ,invalid intercept value in Xdrip classic algorithm’.
        Going after an old threat I deleted the last calibration and entered it via finger stick, but it still gave me the same error.

        Like

        Reply

  43. Hey Bigdigital! Can you share the current watch face? I don’t have my Band, so I would like to change the watch face while I’m without it

    Like

    Reply

      1. Hi. You can download the latest xdrip apk from my website, change .apk file extension to .zip and unzip archive. All watchfaces would be located in assets\miband_watchface_parts folder.

        Like

        Reply

        1. And where can I find that information from the last time it was read, because from what I saw it is not in .bin.
          Thanks in advance.

          Like

          Reply

  44. I’m writing to see if you can help me. I have everything mounted and running with xdrip, miband5 and freestyle 2. The only thing I have 2 doubts. One is if anyone knows what the button is for within the miband configuration in xdrip that says “Switch display on wrist”. And the next question is whether I should touch something to display the data of steps and keystrokes on the xdrip screen. I have already marked the 2 smartwatch sensor options but it doesn’t work out. I also have a mifit mod 4.0.7 installed Thank you !! I’m sorry for my English.

    Like

    Reply

    1. Hi! the option “Switch display on wrist” will activate band screen when you move your hand (the typical hand movement when you want to see the time on the analogue watch) . Please note, this and other watch settings can be overwritten by the mifit settings. To see the hear rate in the xdrip, the options “Use Health Data” and “Heart Rate sensor” which is located in Settings -> Smartwatch Features -> Smart watch sensors, should be enabled.
      You also need to enable hear rate monitoring in mifit settings and configure the desired detection frequency.

      Like

      Reply

      1. Hello again! I thought that the option to see the screen with the gesture is the option of “lift to wake”. The option “switch display on wrist” I think does not modify anything. Regarding the other, I already have the options marked in both xdrip and mifit, but it always shows me the heart icon with 93, and I don’t even get the steps. It’s very strange what happens to me. I have changed the measurement frequency from 1 minute to 10 minutes and I do not get changes in xdrip. Thanks for your help!!

        Like

        Reply

        1. I just installed the new update and now everything works fine! Thank you very much for fixing everything. For those who cannot install with a .jar extension, they just have to delete the .jar extension and leave the file name with .apk

          Like

          Reply

  45. Hi Artem. I installed the newest version on 23.11. Unfortunately, I again had some problems. Tonight at some point, the miBand stopped giving alarms, until a few hours later, I woke up realizing the BG was out of range. Then, the watch started giving all the alarms that were missed in the time before. So for example, there was the “high” alarm which should have gone off 2 hours before. The I tapped the deny button on the band. After that, the band started showing the syncronising symbol. Then, it directly started to show the next missed alarm, and so on. Reconnecting the bluetooth on my phone helped. Do you have any idea why this issue occurs? It seems like it only occurs during the night.

    Like

    Reply
  46. Pingback: Настройка и решение проблем с MiBand 4 и MiBand 5 - Diadim

  47. I also have some Connection problems since 2 weeks ago aproximately. Mi band 5 stops giving alarms and displays an old blood sugar value. Turning Bluetooth Off and on resolvss this, but it will happen again after some time.

    Like

    Reply

            1. OK this night it got stuck again. Seems to happen when an alarm is triggered. I can’t find the minimize scanning and avoid scanning option in my xdrip Version?

              Like

              Reply

              1. Hi, I have the same issue. To get it back working I have to either kill and restart the app or toggle Bluetooth. It happens at night, so I can’t remember what I was exactly doing to dismiss the alarm. I noticed that when this happens the MiBand State is “WAITING_USER_RESPONSE”. It stays that way until I toggle the Bluetooth connection. Maybe a timeout to get out of this state for the next watch face upload would help?

                Like

                Reply

    1. Yes. The xdrip should work fine on all andoid devices beginning from android 6. Make sure you have deleted an official xdrip apk. Also try to install xdrip by usin some file manager

      Like

      Reply

    2. Yes it works on Android 9. Go to settings and enable unknown sources for Chrome before downloading, or use an apk installer app or file manager that can do this.

      Like

      Reply

  50. Thank you for the update 😀
    How do I open a .jar file? It says .apk and that worked fine before but when I download it says apk.jar and I can’t seem to open it

    Like

    Reply

      1. When I download that .apk file it ends up as .jar file when I try to open it. I believe another commenter had the same issue. Never had that with any previous versions you uploaded

        Like

        Reply

  51. Thank you for the great work you did here. I appreciate it a lot! 🙂
    However, is it possible to deactivate the “receive CALL” feature on ALERTS? There is an option for that for other smart watches. For me it would be enough to receive just the standard notification for alerts.

    Btw. If you are in a call and an alert rises you would dismiss the call by dismissing the XDrip notification.

    Like

    Reply

  52. I cannot connect to my MiBand 5 because there is no field to enter the AUTH key when I use MAC address manually to establish connection. I have seen a screenshot here with blank MAC and an AUTH entry box but I do not have this on 23/12 nightly build or the apk from this page. Android 9 Sony G8441 Xperia XZ1 compact. Scanning for band didn’t find it. MAC establishes connection but then hits authentication issue.

    Like

    Reply

      1. Thanks. I had tried that with same result however just now I retried and it managed to scan the MiBand and give me the option to enter the Auth code. This seems “sticky” in that input optoin that was missing persists once it has appeared. On Status page I have “Status:Closed on MiBand watch screen, v2012131958 from here.

        Like

        Reply

        1. Nightly build does better and gets software version from band, says “Connected” with state: Authorization failed.

          Possible bug – Auth Key entry field in Settings is not available after installation if app has not successfully scanned a MiBand and captured a MAC.

          Like

          Reply

          1. I removed and re-did everything as you suggested. I ended up with a different Auth code and this worked. I now have the watchface etc on the band and the steps and heart rate in X-drip, so that’s a result. Thanks.

            The freemyband site has several bad links and I found that process very flaky. It generated two different codes, probably before and after a firmware change on the band which it did.

            Like

            Reply

            1. I’ve checked all links to zepp aplication on freemyband website , all of them works fine. As for auth code, f you reset or unpair your band, the new mac address and auth code would be generated. That’s why you have 2 codes. Actually you should not care about those codes because if you simply clear auth code (like it was suggested) in the xdrip, the xdrip will automatically take the correct codes from the patched zepp application. In any case glad it works for you.

              Like

              Reply

              1. I didn’t reset the band and the MAC was unchanged, I noticed in the instructions that resetting it would change the MAC so avoided that so thanks for clarifying that unpairing can also cause a change in the pairing code – wasn’t expecting that.

                Yes Xdrip picked up the auth code itself as I had removed the folders and started from scratch, that’s how I noticed it had changed as it was different to the one on the clipboard. That’s a good feature.

                My experience of the links was different, the Blue Drive links worked easily but for example the Mega link for 4.2.0 is https://shorturl.at/mwKS3 which takes me to some weird form in a foreign character set ! The zippyshare 4.2.0 link is https://shorturl.at/mqrAX which takes me to a different PDF in the same charset.

                Can you clarify how we should get back to the official app, the instructions say

                ” 1) Unpair band from existing official app
                2) Uninstall official app
                3) Reset your Mi Band (optional)
                4) Download and install the Mi Fit mod apk version
                5) Pair the band
                6) Uninstall the Mi Fit mod
                7) Finished! You can find your Auth key on /sdcard/freemyband folder of your band ”

                but this leaves me without an app and with the band paired to an uninstalled app. I have left the mod version in place for now (it’s a test phone) but these instructions are clearly incomplete – should one unpair before uninstalling, or will reinstalling the official app pick up from where it left off including the pairing ? In my case I used a test phone to recover the auth code.

                Like

                Reply

                1. I see. Indeed there some wrong links to mifit, I guess this happen because the links which were compressed with shorturl service was expired so the links were replaced by another link. As for the official app. When you deleted the patched apk, you can install and use any application you want, including official. Here you can find the missing step you were looking for https://bigdigital.home.blog/2020/01/23/future-of-the-xdrip-miband-project/#config-tutorial-general.

                  Liked by 1 person

                  Reply

                  1. Thanks, that extra documentation is helpful. I have a dilemma in that I have a Libre 2 talking directly to Xdrip using the nightly from 23/12 and I would like to use the MiBand 5 with this.

                    Is it possible to say if your 13/12 apk with MiBand5 support includes https://github.com/NightscoutFoundation/xDrip/pull/1524 which I think was about 3 days earlier ? If so I will put your apk on that phone with the L2 sensor. Otherwise I might source a MiBand 4 to be compatible with the nightly build.

                    Like

                    Reply

  53. Thanks for the miband 5 integration. I’m on the latest 0.3.2.5 app and seem to be having a minor issue where the current temperature does not show up. The rest of the weather info and the xdrip gluecose readings show up fine but there is a blank spot where the current temp should be. If I open the MiFit app on my phone, the temp will appear on the miband for a while (~30 minutes?), then disappear again. I have battery optimization disabled for both xdrip and mifit. Is there a setting I’m missing, or might this be a bug?

    Like

    Reply

  56. Hello, i would like to say THANK YOU for you work, that you do for this project. Now i have a question – i have phone OnePlus 8 (latest version Oxygen – A11), pomocí app PumpControl I’m transmitting glucose to xDrip MiBand (last ver 0.3.2.6). In xDrip i have connected my MiBand – on the screen i see the dial – but without the chart and the value of my glucose from xDrip (i see only NO DATA). I have also identifed, that the time update of the screen MiBand is not regular (i can not estimate, how regulary ist the MiBand updated).

    I dont now, if is the problem in my phone (Oxygen), or in XDrip.
    Thankx for you advise.

    Like

    Reply

      1. Thanks for the response. Yes, in xDrip I have current data that flow from PumpControl – regularly about every 5 minutes. in xDrip I see the current values ​​in the graph.

        Like

        Reply

  57. Hi, could you please rebase to the latest xdrip release(2021.01.29) or even better create a PR to merge your code into xDrip. Mine(0.3.2.5/0.3.2.6) is working quiet stable since ~6 weeks on S10e(Android 11 / 4.14.113-20607146). Thanks for your work.

    Like

    Reply

  58. Grat watchfacee, i am use mi band 5, i wish it will be poosible to add to thr screem my insulin prodective suggestion.
    It can replace the grafh which for me have no use at all.

    Like

    Reply

  59. Thanks for this nice watchface! It works very good for me. It would be very nice when you create a pull request to integrate this in the official xdrip app.

    Like

    Reply

  61. Hi. Thank you for your great work. I’d like you to ask 2 questions:
    – What does “Support of the direct connection with libre 2” mean. Currently I used Libre patched app to get glucose values from the sensor to xdrip. Is there a direct way to get the data?
    – When no data is received by the watch (mi band 4), it tends to display the old value and doesn’t strike it out (time of last update is correct, but I don’t pay attention on that every time) is there a chance to improve this?

    Like

    Reply

  62. Hi! The menu-point “Send readings as notification” is missing. (I know it should be turned off for watchface)
    I only get notification and no watchface.

    Like

    Reply

    1. Hi, yes, this, the menu was removed. Now miband4,5 and amazfit band 5 would always send readings as a watcface. If you receiving only notifications, please make sure your band charged at least 10%, otherwise, you will receive readings as a notification.

      Like

      Reply

  63. I have been trying to create my own custom watchface for the mi band 5 and xdrip. I have been tryin the whole day. I can not get it to work. I have placed various “my_watchface.bin” and “my_image.png” files in the xdrip folder. Every time i update the face through xdrip i get the “couldn’t sync” message on the mi bands display. The xdrip logs don’t show any errors, and the sync process starts, so the problem is probably that the mi band does not accept the new watchface. Everything works flawlessly with the “Allow to use custom watchface” checkbox toggled OFF, but that is not my goal 🙂 .
    I have tried:

    ¤ To use the “default” face from the xdrip folder by duplicating and renaming it to my_watchface.bin.
    ¤ To unpack the default to a folder to a folder with .json and images. This works well and everything looks good. But when I try to repack to a .bin I get the “couldn’t sync” on the band.
    ¤ With and without a “my_image.png” file.
    ¤ Decompressing the .png to 128 colors.
    ¤ Duplicating the existing “default” image in the xdrip folder and renaming it to my_image.png.
    ¤ Only having a “my_image.png” file.
    ¤ The “Disable hight MTU values” toggle increases the time taken but i still get the error.

    I always get the “couldn’t sync” message with the red circle and an X icon on the band.
    Does anyone know what is wrong?
    Can i get the following information from bigdigital (or anyone else) so i can try to get it to work:

    ¤ Exactly what program do you use to pack the folder (with .json and images) to a .bin and where did you download it?
    ¤ Your original folder (with .json and images) describing the whatchface.

    I am thankful and amazed that this project exists at all and works. Thanks bigdigital you are the real iron man!

    Like

    Reply

  64. Hi. Thank you for your kind words, I’m glad that my project was useful for you. So the “couldn’t sync” error even happens if you upload the original watchface extracted from xdrip? To extract watchface from xdrip, you can simply rename akp.jar to akp.zip and unzip it. Then go to the unzipped folder, navigate to src\main\assets\miband_watchface_parts\ . Take xdrip_miband5.bin file and rename it to my_watchface.bin , also take miband5_main_screen.png and rename to my_image.png. Upload both files to xdrip folder on your phone. Enable “custom watcface uploading” option and try to upload. If watch face was uploaded successfully, most possibly there some problem in the modified watcface. This is the tool that was used to create and pack watcface https://amazfitwatchfaces.com/forum/viewtopic.php?t=720 . The original wf json from my watcfaces can be extracted with help of this tool.

    Like

    Reply

    1. Hi, and thanks for your awesome work.
      I’m curious where the watchface gets the weather from? On my Mi Band 5, to the left of the weather, the current temp is not shown and I see a “100%” text all the time there.

      Like

      Reply

    2. Hi.
      I have the same issue as Erik. Whenever I generate a watch face using the MiBandWFTool, synching fails. Renaming a WF extracted from the apk works fine.

      Like

      Reply

      1. Also, I just noticed.. if I do nothing but unpack the watchface with the tool, and immediately repack it as-is, the file size more than doubles (115kb instead of 48.4kb).

        Like

        Reply

        1. Seems I may have found the issue.. using the MiBandWFTool version 2.1.4, I get a somewhat messed up WF (probably cause I made a mistake), but it does synch.

          Like

          Reply

  65. Hello, after my perfectly functional miband 4 with xdrip, I acquired a new amazfit band 5, unfortunately it does not work with the official application (the last of 03/31/2021) for lack of authorization, and if I ‘install miband_xdrip 0.4.1.2 then amazfit band works but the database that I saved on the official xdrip version cannot be recovered..help me to be able to use my database with my amazfit band..thanks a lot

    Like

    Reply

    1. Hi, the databse for 0.4.1.2 is the same as for the latest official xdrip. Not sure why you can’t recover it. Are you sure that you can recover you DB with the latest official xdrip nightly build?

      Like

      Reply

      1. the DB could not be recovered by the modified version: xdrip_miband_0.3.2.5.apk
        I tested twice, on the other hand on the last nightly version it is possible without problem..I will test once again and will tell you

        Like

        Reply

  67. Dear Mr. Expert:) This works perfectly on mi band 5 – thank you a lot!
    What is the situation with mi band 6? I am active in a diabetes forum and I am helping them configure this for mi band 5, now they are asking me If this would work on mi band 6? Is there any info on that please? Thank you a lot and have a nice day, Andrea:)

    Like

    Reply

    1. Hi. At the moment it wouldn’t work with miband 6. It would require a code adaptation for the new watch. On my patreon i have a pool to decide which watch integration would be the next.

      Like

      Reply

  68. Could you please rebase/sync again with the latest xdrip release which includes some bugfixes and enhancements worth to integrate i.e Always On Display and support for newer transmitter. Unfortunately the PR https://github.com/NightscoutFoundation/xDrip/pull/1659 is still in progress and I expect it will take some more time.
    I’ve been encountering problems in combination with BlueJay Watch, which gets blocked with your version(0.3.2.6).

    Like

    Reply

  69. Hi, great job. I am setting up a mi band 5 for my son. I have installed v0.3.2.4 and using Samsung s7. The graph appeared initially and displayed corrected. However then it gave a “couldn’t sync” error and the graph and number disappeared. The alarms still work. I was able to sync by using the “send BG now” and the graph appeared, but then it failed to sync again so I’ve lost the graph again. Hopefully I’ve made some simple mistake but I can’t spot it. Watch battery is almost full. Thanks.

    Like

    Reply

    1. Hi. Does the ‘couldn’t not sync’ error happens every watcface upload? Usually such error can happens if there was a weak Bluetooth connection. Normally the band connection has a stable connection distance up to 30 meters. But this distance can varying

      Like

      Reply

      1. Hi. It happens every attempt. When I first setup I was able to get a valid watch face sync by using “send bg now” but subsequent sync would all fail. I was able to get another successful sync by rebooting phone/watch, but I couldn’t find a pattern and now I can’t get a successful sync ever. I was just testing so band is right beside phone. But as you mentioned it does sound like a Bluetooth connection issue. I had it all working on an old HTC phone no problem. But it’s an s7 he carries and has connected to his miao miao xdrip setup. Thanks for your help.

        Like

        Reply

        1. It works now. I enabled the option “Disable high MTU values”. The sync is now successful. I have no idea what this option does or why it works but it does! This is great.thanks

          Like

          Reply

      2. It works now. I enabled the option “Disable high MTU values”. The sync is now successful. I have no idea what this option does or why it works but it does! This is great.thanks

        Like

        Reply

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s

%d bloggers like this: