Type 1 Miao Miao not connecting with Bluetooth

Thanks for the tag @Knikki

Yeah I get that a lot. The Bluetooth on your phone doesnt connect to the MM. As @Knikki has already said if you go to the Burger menu (top left of screen) and go to Bluetooth scan, the MM will appear on that, jsy press the MM and, fingers crossed, it should spring into life

Forgot to say best app is Xdrip plus...... https://github.com/StephenBlackWasAlreadyTaken/xDrip/wiki/Download-Current-Version

https://github.com/jamorham/xDrip-p...ector-runs-on-the-watch-with-wear-integration
Pretty useful link as well

@Joesdad , if the other suggestions don't work, I'd maybe try unpairing the bluetooth earpiece devices which seem to be listed on the screenshot.

I recall seeing a few posts on the xdrip+ issues page where Samsung phones just don't play nice when there's more than one bluetooth gadget involved.

I think one involved it all working well until he got in his car and the bluetooth music system or something like that messed it up.

There's some connection issues discussed here, maybe a few ponters in there:

https://github.com/NightscoutFoundation/xDrip/issues/440

Oops, @Joesdad , we just cross-posted - glad to see you got it working!

Joesdad said:

My next question is, Is there a way to share the results? The setup for DS at the moment is that we have a smartphone in his classroom. A teachers assistant (TA) uses LibreLink to send his readings to the school nurse. If she thinks he needs treating, she will come to the classroom or send a message to the TA. So, how can we get Xdrip+ to send his readings automatically to the school nurse?

Click to expand...

Need a little more info on how you're planning to do this. You can set up a follower phone with the xDrip+ sync options, though that would require 2 Android phones, both with Internet connectivity or connected to the same WiFi network.

A more involved option (as far as setting up goes) is to sync to a Nightscout instance over the Internet which can be viewed from any web browser.

It should do because each phone with the app will have a Bluetooth pairing with each individual Miaomiao. Each device will have an individual 48-bit Bluetooth address (BD_ADDR) not dissimilar to a MAC address used to identify networking equipment at a low level.

I don't use the Miaomiao myself but use the similar Blucon and I have seen it stay connected in extremely noisy environments for Bluetooth and other wireless devices on the 2.4GHz range (think hundreds if not thousands of devices) with little need for maintenance for the pairing.

you can follow the steps below to turn off the "Trust Auto-Connect":


Setting——> Less common settings ——>Bluetooth Settings——>Trust Auto-Connect(Turn it off!)


if needed, you should restart your phone!


for the app, you can use Xdrip , glimp and tomato app

Joesdad said:

Thanks. What i'm worried about is, that with Samsung you don't pair with the MM using the phone's own bluetooth settings. You just do it through XDrip+'s settings>bluetooth scan. So I'm imagining a scenario where two devices show up. I suppose we'll just have to remember which one to press.

Click to expand...

Yep, I do it the same way with mine, although the Blucon seems to have a unique name (like BLU00000 [0s are random numbers]).

You could make a note of the Bluetooth address (BD_ADDR) that appears underneath the name as this will be unique for each Miaomiao - the last 2-3 pairs of hexadecimal bytes makes up the Lower Address Part (LAP) which uniquely identifies each device so they should all be different. That way you know you're picking the right one inside Bluetooth Scan - I've highlighted the bit I mean in the screenshot below.

db89 said:

Yep, I do it the same way with mine, although the Blucon seems to have a unique name (like BLU00000 [0s are random numbers]).

You could make a note of the Bluetooth address (BD_ADDR) that appears underneath the name as this will be unique for each Miaomiao - the last 2-3 pairs of hexadecimal bytes makes up the Lower Address Part (LAP) which uniquely identifies each device so they should all be different. That way you know you're picking the right one inside Bluetooth Scan - I've highlighted the bit I mean in the screenshot below.

Click to expand...

I've been wondering about this too. I recall when I set blucon up for the first time I was prompted to type the number on the edge of the blucon into xdrip+ and assumed that that paired the two so it knew to "talk" to that device.

When I later got the miaomiao, I was surprised that I didn't have to do that procedure, although I vaguely recall having to click the mm entry on the bt scan screen, so maybe that's enough to pair them, excluding other devices on the area without having to type any numbers in like blucon.

Conicidentally, I was at the T1DRoM looping seminar on Saturday with lots of people wearing cgm, pumps and loops, posted a bit about on T1S,r,U and Mel posted back about a loop facebook post from some folks at the event saying their devices seemed to be getting communications with other pumps - yikes! One boy went running past me saying, "f, my loop's down!"

https://www.diabetes.co.uk/forum/threads/type-1stars-r-us.150597/page-814#post-2054240

As I don't have a miaomiao I can't say for sure but it sounds like they have no pairing code programmed into them (or it will be some default which most devices will automatically try like 000000 or 123456). The Blucons have a random 6 digit pairing code before they will accept a connection which is what you had printed on the side. Not ultimately secure, but enough to stop random pairing requests.

Also, once paired from the Scan screen I no longer see my Blucon in the list unless I reset it with a PIN so I presume it takes itself out of pairing mode and the phone knows it's already paired with it so maintains the connection.

I guess if some of these devices are in pairing mode all the time ready to accept any connection request you will inevitably end up with odd things occurring. I would hope in future generations of these devices lessons will be learned on this front and they could add simple things like NFC for easier pairing - my earphones and speakers do this and they're a breeze to connect to: tap, pair, ????, you were done 2 steps ago..

The seminar sounds very interesting Scott, it's exciting where we're going bit by bit. Although there's always going to be someone spoil the party by involving regulatory bodies (who move like glaciers) when they end up doing things with the power we're giving to ourselves in FGM addons and looping. With great power.. etc. etc. yada yada. Link

db89 said:

Also, once paired from the Scan screen I no longer see my Blucon in the list unless I reset it with a PIN so I presume it takes itself out of pairing mode and the phone knows it's already paired with it so maintains the connection.

Click to expand...

That makes sense - the same thing happened with miaomiao too at set-up, disappears from the bt scan screen, so I guess any others detected on a further bt scan would need to be clicked before talking to the app.

db89 said:

The seminar sounds very interesting Scott, it's exciting where we're going bit by bit.

Click to expand...

Yeah, it was pretty motivational. I got a copy of Dana Lewis' new book Automated Insulin Delivery on my kindle after it and have started reading that.

I've always been a bit meh about pumps as I like the simplicity of MDI assisted by cgm, but hearing those stories at the seminar about bg more or less looking after itself in the background courtesy of an algorithm is very attractive.

Some DSNs and docs from where I'm treated were there, so I was saying to a couple of them - ooh, go on, prescribe me a patch-pump, I wanna patch-pump!