MMM-OralB / Bluetooth equipped toothbrush integration

timodejong95

@lavolp3 Check, I will update the docs, with more info soon.

Yeah promises could be really nice if implemented correctly, now debugging is a pain because the error logs are not as useful. I will make this better in the coming week.

When you hit the web interfase the node_helper is triggered, do you then have your brush on? Because when you start up the first time, alle the devices should be on and ready to connect.

timodejong95

I have tweaked the code a bit towards better exception handling, this might be helpful for you

djerik

Works great with my Oral B 9000!

Notes:

I had to change the git clone to https instead of git clone git@github.com:timodejong95/MMM-BluetoothDevices.git
Copying the file MMM.conf requires administrative rights
I used bluetoothctl to find the MAC of the toothbrush

timodejong95

@djerik Nice! Good to hear, and thanks for the feedback I will update the readme where needed!

lavolp3

@timodejong95 Hi Timo, it works for me now as well. Very good!
So now let’s go for the holy grail! The battery status.
It is there and I managed to get it out using noble. Don’t ask me how. Lol.
Find the code below where I meddled with Advertisements and Characteristics:

noble.on('discover', function(peripheral) {
  var ad = peripheral.advertisement || "";
  if (ad.localName == "Oral-B Toothbrush") {
    //console.log('Found device with local name: ' + ad.localName);
    //console.log('advertising the following service uuid\'s: ' + ad.serviceUuids);
    //console.log("ID: "+peripheral.id);
    //console.log("Advertisement: "+ad);
    if (ad.manufacturerData) {
        console.log('Found OralB Toothbrush with ID: ' + peripheral.id);
        console.log('ManufacturerData: '+ad.manufacturerData.toString('hex'));
        //noble.stopScanning();
        peripheral.connect(function(error) {
          if (error) {
            console.log("Error connecting to peripheral: " +error);
          } else {
            console.log('Connected to peripheral: ' + peripheral.uuid);
            peripheral.discoverServices([], function(error, services) {
              console.log("Discovering services...");
              if (error) {
                  console.log("ERROR while discovering peripherals: " + error);
              } else {
                  console.log('discovered the following services:');
                  for (var i in services) {
                      //console.log('  ' + i + ' uuid: ' + services[i].uuid);
                  }
                  discoverChars(services[3]);
                  /*setTimeout(() => {
                    noble.startScanning([], true);
                  }, 1000);*/

              }
              //peripheral.disconnect();
            });
          }
        });

        peripheral.on('disconnect', function() {
          process.exit(0);
          console.log("Peripheral disconnected. Scanning again!");
          noble.startScanning();
        });
    }
  }
});


function discoverChars(service) {
  service.discoverCharacteristics(null, function(error, characteristics) {
    //console.log("Characteristics: "+characteristics);
    for (let i in characteristics) {
      var charUUID = characteristics[i].uuid;
      console.log('  ' + i + ' uuid: ' + charUUID);
      if (characteristics[i].uuid == "a0f0ff0550474d5382084f72616c2d42") {
        let j = i;
        characteristics[j].on('data', function(data, isNotification) {
            console.log("Data: "+data);
            var valueInt = data.readInt8(0);
            console.log("Battery: "+valueInt+"%");
        });
        /*characteristics[j].read(function(error, data) {
            if (data) {
              var valueInt = data.readInt8(0);
              console.log("Battery: "+valueInt+"%");
            }
        });*/
        characteristics[j].subscribe(function(error) {
            if (error !== null) { console.log("error", error); }
        });

      }
    }
  });
}

I guess you can find the same using bluez?

If I find the time, I’ll also try out which way works better (for me).
Noble or your blues dbus way. I had several issues using noble but it had its charme (like the battery status :-) and only sending data when I activate or deactivate the brush)

dfuerst

@timodejong95 nice that there was someone realizing this project at the end.

tried your app and getting a blank WHITE SCREEN.
so maybe u can help me troubleshooting

1 cloned via https
2 did npm install
3 sudo cp MMM.conf
4 added conf including MAC (sidenote, white screen with wrong MAC address aswell)
5 paired the toothbrush via bluetooth

tried to start mirror -> white screen, and whoops message in the log

any idea what could cause this? or where to start troubleshooting?

timodejong95

@lavolp3 Thanks for the code share and great to hear it works. This weekend I will spend some to see if I can fix it, I let you know.

@dfuerst Hmm oké, thats weird normally you would see a black screen. Doest the mirror work if you disable the plugin, if so what does the logs say?

FYI: I had some issues with my git commits so I deleted and recreated the repo, no worries it’s still under the same url and won’t go away.

lavolp3

@timodejong95 Hi Timo,

since I really want to have the battery status I am currently trying to use the front end code with noble as backend in node_helper. Your backend code and all the GATT bluez stuff is much too complicated for me.

Also, I have done some tweaks on the frontend:

Hide timer after some time
convert time to m:ss
also count on beyond 2 minutes (circle is filled after 2 Minutes)
make timer bright and circle blue when the brush is running and dim it back again if it is not running.

Like it very much. Very simple tweaks in the main.js. Let me know if you want to see any of it.

Also, two brushes work perfectly! :ok_hand:

Impressive work man!

timodejong95

Thanks I really appreciate that! Yeah sure I am willing to refactor it a bit, if needed, and make it a configurable option.
Again sorry for deleting the repo, I pushed wit the wrong git user (work one). I saw that you starred/forked it.

Can you show me the changes or make a PR?

The GATT is a bit bugged I am not sure why but the services are not resolving. I am trying to fix that and I think that after that the battery status should be that hard anymore.

timodejong95

This post is deleted!