Hey guys,

I have tracked this topic for a while and I have created an own module for bluetooth devices based on (https://github.com/Hypfer/Cybele). Currently only Oral B toothbrush is supported: https://github.com/timodejong95/MMM-BluetoothDevices

I am still testing it but it seems to work stable’ish. Although I cannot test it with an actual mirror because that is still work in progress. If you want to check it out and test be my guest. If you have any improvements or tips let me know!

Hope this helps out.

@lavolp3 Oke I have pushed some changes, see: https://github.com/timodejong95/MMM-BluetoothDevices. Don’t forget npm install.

I updated the configuration see docs. You need to add a track key to the device config with the value ‘battery’:

example:

devices: [
  { type: 'OralBToothbrush', name: 'oralb', mac: 'xxx', tracks: ['battery'], format: 'formatted' },
],

It’s still a bit buggy let me know what your experience is!

@lavolp3 No worries, check I will have a look at this when I find some time, probably this weekend. Seems that the devices couldn’t connect at the first try but failed in de second which is triggered instantly.

@djerik Thanks for sharing

I will try and fix the issues you send to be, thanks for sharing and excuses for the bugs! I might write some tests because the manual tests are stacking up and code coverage is always good.

@lavolp3 Nice, yeah thats still a thing. I thought it was the way it connects, but the devices automatically disconnects after 20-30 seconds. When disconnected its not able to get the battery status. So what I build that if the devices is disconnected at the first 5 seconds of brushing it’s going to reconnect (1 try). If that succeeds it gets the battery value. If not well, then sadly not.

I haven’t figured out a solution to keep it connected throughout the whole session or just forever. My guess is, the brush might expect data to be send to keep the connection active/alive.

In the logs I see that the reconnection has failed, do you got that every session? Else I might increase the reconnection attempts to 2.

I have just pushed some new changes which improve connecting, and a few tests cases for device connection. It requires a npm install.

@lavolp3 and @djerik if you have some time could you try it out? Also I though you already had it on but if not it might be handy to enable debugLogs.

Also I want to thank you for the time you put into this and help me by providing logs and errors so I can improve the module.

@lavolp3 Oké check, well no need to try again tonight because your up-to-date then. I will let you know when I have looked at it. For now you can prevent the errors by removing the battery in the tracks array.

@lavolp3 Check I get you. Just to be sure, you did do npm install I changed a package? If not then I will comeback to it when I have tested it myself.

@lavolp3 No worries, check I will have a look at this when I find some time, probably this weekend. Seems that the devices couldn’t connect at the first try but failed in de second which is triggered instantly.

@djerik Thanks for sharing

I will try and fix the issues you send to be, thanks for sharing and excuses for the bugs! I might write some tests because the manual tests are stacking up and code coverage is always good.

@lavolp3 Damm ashame, could you post the logs above the error? If correct there should be 2 more error logs, and just to be sure it still works when you remove the battery track, right?

@lavolp3 Oke I have pushed some changes, see: https://github.com/timodejong95/MMM-BluetoothDevices. Don’t forget npm install.

I updated the configuration see docs. You need to add a track key to the device config with the value ‘battery’:

example:

devices: [
  { type: 'OralBToothbrush', name: 'oralb', mac: 'xxx', tracks: ['battery'], format: 'formatted' },
],

It’s still a bit buggy let me know what your experience is!

I have been debugging it and it seems that the devices is ‘just’ being disconnected:

HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 64 reason 0x13
    Reason: Remote User Terminated Connection

I do not know why :/

@lavolp3

Haha thanks man.

I have made some big changes, improved connecting devices, GATT service, characteristics and some more. I have also managed to get the battery value, but I have an issue: after around 15-30 seconds after connection successfully to the device the connection drops:

{"ServicesResolved":false,"Connected":false}

I haven’t figured out why this happens, all the normal data is still received. Only the battery status not, it needs to be connected. I haven’t push anything to the repo yet. First I want to look if I can get it working (fully).

Are you experiencing the same with noble or can you get the battery status after 30 seconds or 1 minute plus?

I keep you updated.

@lavolp3 Thanks, I will have a look at that this weekend.

Also managed to connect to the services and characteristics. But how did you know the one you needed?

Because you only connecting to the 3th key in the services array and a hardcoded uuid for the characteristics. I am curious how you find the one you needed.