MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    MMM-OralB / Bluetooth equipped toothbrush integration

    Scheduled Pinned Locked Moved Development
    68 Posts 13 Posters 29.2k Views 20 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • FistandantilusF Offline
      Fistandantilus
      last edited by

      Hi,

      this all requires additional equipment. I have a bluetooth enabled mirror and the toothbrush. That should be enough! I don´t want to run my phone to record data and display the recorded data later on the mirror. We just need to find a way to directly read and interpret the data using the direct bluetooth connection.
      Currently the script is just a proof of concept that we are able to read the connection status. The whole data part is still missing. I´m not that close to hardware integration and development that I could do that by my own. I can just offer support to test an maybe enhance the solution once somebody has written a library that is able to read the data send by the brush.

      1 Reply Last reply Reply Quote 0
      • FistandantilusF Offline
        Fistandantilus
        last edited by

        I have just written an additional request to PG asking for support. Lets see if I get an answer…

        1 Reply Last reply Reply Quote 1
        • SvenSommerS Offline
          SvenSommer
          last edited by

          I’m still hoping some genius starts to hack the protocol. This is the tricky part. Once this is done, building a module for the MM-framework is a walk in the park.

          Looking for some building inspiration?
          Check out my large, thin and metal framed mirror on robstechlog.com.

          Modules released:
          MMM-GoogleAnalytics
          MMM-GrafanaChart
          MMM-GrafanaGauges

          1 Reply Last reply Reply Quote 0
          • U Offline
            uhorn
            last edited by

            Hi everybody,

            i’m a developer too and also very interested in solving this use case. At the moment i consider to build up my own magic mirror, but it depends on some useful features i want to have a real benefit from it.

            Actually i want to simply get the “start” and the “stop” signal from the brush to display a timer, which is stopped on “stop” and resumed on “start”.

            Other features are more unnecessary sugar in my opinion. I’m using electric toothbrushes from Braun/Oral-B since about 20 years from now. I never changed the brush mode (if i had to, i could feel the mode. they are very various) and i’m ignoring the segmented Ring, the motivation Smiley and the star rating consequent 2 times a day.

            2 years ago my toothbrush gone broken so i’ve got a new one. At this point i noticed, that both “Smart Guides” (that’s the shipped displays with Oral-B brushes) getting “start” signal from one brush.
            This means there a no “pairings” or “syncs” between the smart guide and the brush. (maybe some days my neighbor will trigger this… :D )
            Also my new brush is the first one advertising bluetooth integration. This leads to my assumption that “Smart Guides” not using bluetooth in anyway.

            I’m not really experienced or well educated in electronic components, but maybe there is something like a proprietary radio antenna, waiting for a simple signal.
            Maybe it’s possible to build up the same radio trigger with an antenna like the “Smart Guide” is using?

            Any ideas if this would be possible?

            Greetings

            1 Reply Last reply Reply Quote 0
            • C Offline
              CedericPrivat
              last edited by

              Someone on the Home Assistant Forum seems to have the code figured out:
              https://community.home-assistant.io/t/oral-b-bluetooth-connected-toothbrush/35595/10

              Is it now possible, to display the same information like the app does?

              1 Reply Last reply Reply Quote 0
              • lavolp3L Offline
                lavolp3 Module Developer
                last edited by

                Guys, I would like to relive this topic. Using the project from the home assistant guy( who even referenced us :-) ) and our combined effort we should be able to reach something, shouldn’t we?

                @SvenSommer are you still listening? :-) I’ve looked through your repository but have not found a final implementation of a timer. There is still no server-client communication, or have I overseen something?

                The problem is still that every toothbrush version may behave a bit differently but having at least a timer on the mirror and maybe even a bit more (battery status) after that would be a big win.

                So while I’m trying to understand this code https://github.com/rfaelens/domotica/blob/master/mqtt-toothbrush.py which should present at least part of the solution, I’m happy for everyone who joins the effort to make toothbrushing great again!!

                How to troubleshoot modules
                MMM-soccer v2, MMM-AVStock

                lavolp3L 1 Reply Last reply Reply Quote 0
                • lavolp3L Offline
                  lavolp3 Module Developer @lavolp3
                  last edited by

                  Exciting times!!

                  I have been able to move a bit further on this (I think)
                  With the help of this linkedin post (which funnily enough referenced this forum) and above mentioned post in the home-assistant forum I was able to dive a bit deeper into noble and the BLE interaction.
                  The current status:

                  • I can read out battery status!! (with the help of this gitlab snippet (yeay!)
                  • I receive data when turning the brush on and off (and on again) and am able to filter this data. However I’m completely new to noble, the BLE services system and apparently need to learn a lot.
                  • I am using the npm module @abandonware/noble since the original noble has not been maintained for a few years.
                  • For some odd reason, I needed to put my js file into the noble folder and work from there. Still need to try working in the oral-b main folder

                  Here’s what I have learned:

                  According to the linkedin post (and I could validate that) the “manufacturerData” is NOT a fixed brush-specific value BUT CONTAINS ACTUALLY USEFUL INFORMATION. And it changes. Some of the brush information is written into this entry. You can get the status of the brush and the running time from this.
                  The question of course is if this is really needed.

                  From my point of view you only need a reliable signal when turning on and off the brush. I’m not sure if I have that already, @SvenSommer might have been already further than I am now, but it is still exciting.
                  It is still a problem for me to properly talk to the brush :-D . I would like to have a constant flow of information (at least receive the “manufacturedata” every second or so) when the brush is active, and currently I don’t know how to do that. Guess I need to trigger this somehow with noble.

                  TODOs:

                  • Implement a timer into the module and check if the current setup works well enough.
                  • Find more characteristics to use as data source
                  • Find out how to constantly trigger the brush to send its manufacturedata.

                  And finally here’s my code:

                  var async = require('async');
                  var noble = require('@abandonware/noble');
                  
                  //var OralB_manufacturerData = 'dc0003220c0328000001010004';
                  process.env['NOBLE_HCI_DEVICE_ID'] = 0
                  
                  noble.on('stateChange', function(state) {
                      console.log('Changed state to:' + noble.state);
                      if (state === 'poweredOn') {
                          noble.startScanning([], true);
                      } else  {
                          console.log('changed state to: ' + noble.state);
                          noble.stopScanning();
                      }
                  });
                  
                  
                  console.log('Searching for OralB Toothbrushes');
                  
                  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(ad.manufacturerData.toString('hex'));
                          //console.log('Found OralB Toothbrush with ID: ' + peripheral.id);
                          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);
                      for (var i in characteristics) {
                        var charUUID = characteristics[i].uuid;
                        //console.log("UUID: "+charUUID);
                        if (characteristics[i].uuid == "a0f0ff0550474d5382084f72616c2d42") {
                          characteristics[i].subscribe(function(error){
                              if(error !== null) console.log("error", error);
                          });
                          characteristics[i].on('data', function(data, isNotification){
                              valueInt = data.readInt8(0);
                              //console.log("Battery: "+valueInt+"%")
                          });
                          characteristics[i].read(function(error, data) {
                              if (data) {
                                valueInt = data.readInt8(0);
                                console.log("Battery: "+valueInt+"%")
                              }
                          });
                        }
                      }
                    });
                  }
                  
                  

                  How to troubleshoot modules
                  MMM-soccer v2, MMM-AVStock

                  SvenSommerS 1 Reply Last reply Reply Quote 0
                  • SvenSommerS Offline
                    SvenSommer @lavolp3
                    last edited by

                    @lavolp3 Thanks for your post. I will have a look into this, hopefully in the next week! I’m still convinced we should build this module.

                    Looking for some building inspiration?
                    Check out my large, thin and metal framed mirror on robstechlog.com.

                    Modules released:
                    MMM-GoogleAnalytics
                    MMM-GrafanaChart
                    MMM-GrafanaGauges

                    lavolp3L 1 Reply Last reply Reply Quote 0
                    • lavolp3L Offline
                      lavolp3 Module Developer @SvenSommer
                      last edited by

                      @SvenSommer Thanks Sven and good you’re back on this :-)

                      I have one question on noble I can’t figure out.
                      with noble.on('discover') I can exchange information on discovery, so as soon as the brush sends a certain signal. All good.
                      But how can I trigger the brush to send its manufacturedata, let’s say, every 2 seconds?
                      Or is that not possible at all?

                      How to troubleshoot modules
                      MMM-soccer v2, MMM-AVStock

                      lavolp3L 1 Reply Last reply Reply Quote 0
                      • lavolp3L Offline
                        lavolp3 Module Developer @lavolp3
                        last edited by

                        A small heads-up: Still not getting to terms with noble.

                        But as I had some connection problems today, I used bluetoothctl again to connect to my brush.
                        And found out that scanning with bluetoothctl gets a constant output of the manufacturerData of the brush.

                        With bluetoothctl it would be able to get information on

                        • running time
                        • mode (on/off)
                        • quadrant
                          in an interval of like 10 seconds

                        How to troubleshoot modules
                        MMM-soccer v2, MMM-AVStock

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 4
                        • 5
                        • 6
                        • 7
                        • 3 / 7
                        • First post
                          Last post
                        Enjoying MagicMirror? Please consider a donation!
                        MagicMirror created by Michael Teeuw.
                        Forum managed by Sam, technical setup by Karsten.
                        This forum is using NodeBB as its core | Contributors
                        Contact | Privacy Policy