Read the statement by Michael Teeuw here.
MMM-OralB / Bluetooth equipped toothbrush integration
-
@timodejong95 OK I have identified the source of the error.
It originated from the connectDevice function on Dongle.js
I had a wrong mac address for the brush which leads to an unresolved promise.
Good luck finding the promise :smiling_face_with_open_mouth_smiling_eyes:
(I love/hate promises…)Correcting the mac address I get new unresolved rejection errors.
[11:54:35.940] [LOG] 11:54:35 <log> Retrying Dirks OralB 2/3 (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Device.js:42 Promise) [11:54:35.964] [ERROR] 11:54:35 <error> (node:23373) UnhandledPromiseRejectionWarning: Software caused connection abort (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:54:35.970] [ERROR] 11:54:35 <error> (node:23373) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:54:35.975] [ERROR] 11:54:35 <error> (node:23373) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:55:16.260] [LOG] 11:55:16 <log> Retrying Dirks OralB 3/3 (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Device.js:42 Promise) [11:55:16.275] [ERROR] 11:55:16 <error> (node:23373) UnhandledPromiseRejectionWarning: Software caused connection abort (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:55:16.279] [ERROR] 11:55:16 <error> (node:23373) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2) (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:55:56.582] [ERROR] 11:55:56 <error> (node:23373) UnhandledPromiseRejectionWarning: Error: Couldn't connect to Dirks OralB after 4 tries. at Promise (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Device.js:46:16) at new Promise (<anonymous>) at tryConnect (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Device.js:40:14) at Object.iFace.Connect (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Device.js:56:13) at EventEmitter.<anonymous> (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/dbus-native/lib/bus.js:140:19) at EventEmitter.emit (events.js:187:15) at /home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/dbus-native/index.js:106:14 at Socket.<anonymous> (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_modules/dbus-native/lib/message.js:55:9) at Socket.emit (events.js:182:13) at emitReadable_ (_stream_readable.js:540:12) (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:55:56.588] [ERROR] 11:55:56 <error> (node:23373) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3) (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:55:56.593] [ERROR] 11:55:56 <error> (node:23373) UnhandledPromiseRejectionWarning: Software caused connection abort (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut) [11:55:56.599] [ERROR] 11:55:56 <error> (node:23373) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4) (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)So… Software caused connection abort. Don’t know what that means unfortunately. Guess I need to learn a bit more about the connection process. But I get the feeling that this module is a bit too complex for just using with my toothbrush.
Let me know if you know my problem. -
@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.
-
I have tweaked the code a bit towards better exception handling, this might be helpful for you
-
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
-
@djerik Nice! Good to hear, and thanks for the feedback I will update the readme where needed!
-
@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) -
@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 troubleshooting1 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 bluetoothtried to start mirror -> white screen, and whoops message in the log
any idea what could cause this? or where to start troubleshooting?
-
@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.
-
@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!
-
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.
-
This post is deleted! -
I can’t PR to your new repo, so here’s the code from MMM-BluetoothDevices.js:
/*jshint esversion: 6 */ //'use strict'; Module.register('MMM-BluetoothDevices', { // Default module config. defaults: { name: 'raspberrypi', mode: 'le', hci: 'hci0', interfaceName: 'org.bluez.Adapter1', services: [ { type: 'CurrentTimeService' }, ], devices: [], layout: { title: { position: 'bottom', key: 'name', }, data: { position: 'bottom', fields: [ { key: 'mode', text: 'mode' }, ], }, }, hideAfter: 10 * 60, }, getStyles() { return ['MMM-BluetoothDevices.css']; }, // Override dom generator. getDom() { const wrapper = document.createElement('div'); wrapper.classList.add('toothbrushes'); if (this.loading) { wrapper.innerHTML = 'Loading...'; wrapper.className = 'light small'; return wrapper; } const table = document.createElement('table'); const row = document.createElement('tr'); for (const deviceKey in this.devices) { const deviceType = this.devices[deviceKey].device.type; if (deviceType === 'OralBToothbrush') { row.appendChild(this.renderToothbrush(deviceKey)); } else { throw new Error(`Unknown device type: ${deviceType}`); } } table.appendChild(row); wrapper.appendChild(table); return wrapper; }, renderToothbrush(deviceKey) { const device = this.devices[deviceKey]; const deviceTd = document.createElement('td'); deviceTd.classList.add('toothbrush'); deviceTd.style.textAlign = "center"; const deviceCircle = document.createElement('div'); deviceCircle.classList.add('toothbrush-circle-container'); deviceCircle.classList.add(`toothbrush-circle-${device.data.state}`); const deviceCircleText = document.createElement('div'); deviceCircleText.classList.add('toothbrush-circle-text'); const deviceCircleSvg = document.createElementNS('http://www.w3.org/2000/svg', 'svg'); deviceCircleSvg.classList.add('toothbrush-circle-ring'); const deviceCircleSvgCircle = document.createElementNS('http://www.w3.org/2000/svg', 'circle'); deviceCircleSvgCircle.classList.add('toothbrush-circle'); deviceCircleSvgCircle.setAttribute('stroke-width', 15); deviceCircleSvgCircle.setAttribute('fill', 'transparent'); deviceCircleSvgCircle.setAttribute('r', 52); deviceCircleSvgCircle.setAttribute('cx', 60); deviceCircleSvgCircle.setAttribute('cy', 60); deviceCircleSvg.append(deviceCircleSvgCircle); deviceCircle.append(deviceCircleSvg); deviceCircle.append(deviceCircleText); //const time = device.data.time > 120 ? 120 : device.data.time; const time = device.data.time; // initial start this.updateCircle(deviceCircleSvgCircle, deviceCircleText, time); if (device.data.state === 'running') { deviceTd.style.display = 'block'; deviceCircleText.classList.add('bright'); deviceCircleSvgCircle.setAttribute('stroke', '#0080fe'); this.counters[deviceKey] = { time, interval: setInterval(() => { this.counters[deviceKey].time += 1; this.updateCircle( deviceCircleSvgCircle, deviceCircleText, this.counters[deviceKey].time ); }, 1000), }; } else { deviceCircleText.classList.remove("bright"); deviceCircleSvgCircle.setAttribute('stroke', '#aaa'); setInterval(() => { deviceTd.style.display = "none"; }, this.config.hideAfter * 1000); } const deviceLabel = document.createElement('div'); deviceLabel.classList.add('title'); deviceLabel.classList.add('small'); deviceLabel.innerText = device.device[this.config.layout.title.key]; const dataContainer = document.createElement('div'); dataContainer.classList.add('small'); dataContainer.classList.add('light'); for (const key in this.config.layout.data.fields) { const data = this.config.layout.data.fields[key]; const field = document.createElement('div'); field.innerText = `${data.key}: ${device.data[data.key]}`; dataContainer.appendChild(field); } if (this.config.layout.title.position === 'top') { deviceTd.appendChild(deviceLabel); } if (this.config.layout.data.position === 'top') { deviceTd.appendChild(dataContainer); } deviceTd.appendChild(deviceCircle); if (this.config.layout.title.position === 'bottom') { deviceTd.appendChild(deviceLabel); } if (this.config.layout.data.position === 'bottom') { deviceTd.appendChild(dataContainer); } return deviceTd; }, updateCircle(deviceCircleSvgCircle, deviceCircleText, time) { var secs = time % 60; deviceCircleText.innerText = Math.floor(time / 60) + ":" + (secs < 10 ? "0" + secs : secs); const radius = parseInt(deviceCircleSvgCircle.getAttribute('r')); const circumference = radius * 2 * Math.PI; if (time > 120) { time = 120; } const percent = (100 / 120) * time; const offset = circumference - percent / 100 * circumference; deviceCircleSvgCircle.style.strokeDasharray = `${circumference} ${circumference}`; deviceCircleSvgCircle.style.strokeDashoffset = offset; }, start() { Log.info(`Starting module: ${this.name}`); this.devices = {}; this.counters = {}; this.loading = true; this.sendSocketNotification('FETCH_TOOTHBRUSHES', this.config); }, socketNotificationReceived(notification, payload) { if (notification === 'FETCH_TOOTHBRUSHES_RESULTS') { Log.info('MMM-Toothbrush: Got toothbrush results'); this.devices = payload; for (const counterKey in this.counters) { const counter = this.counters[counterKey]; clearInterval(counter.interval); } if (this.loading) { this.loading = false; this.updateDom(1000); } else { this.updateDom(0); } } }, });it’s also in the develop branch of my module
-
@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.
-
@timodejong95 I used this gitlab snippet. Don’t remember how I got there. I guess from the homeassistant forum which is also working on that.
For more follow-up see my post in this threadWhen I use bluetoothctl on my RasPi I am getting lots of output form the brush recently. I’m not sure why exactly, maybe because my Pi is coupled with the brush.
Primary Service /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050 a0f0ff20-5047-4d53-8208-4f72616c2d42 Vendor specific Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0070 a0f0ff2b-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0070/desc0072 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char006d a0f0ff2a-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char006d/desc006f 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char006a a0f0ff29-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char006a/desc006c 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0067 a0f0ff28-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0067/desc0069 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0064 a0f0ff27-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0064/desc0066 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0061 a0f0ff26-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0061/desc0063 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char005e a0f0ff25-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char005e/desc0060 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char005b a0f0ff24-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char005b/desc005d 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0058 a0f0ff23-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0058/desc005a 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0055 a0f0ff22-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0055/desc0057 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0051 a0f0ff21-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0051/desc0054 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0050/char0051/desc0053 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration Primary Service /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e a0f0ff00-5047-4d53-8208-4f72616c2d42 Vendor specific Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char004c a0f0ff0d-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char004c/desc004f 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char004c/desc004e 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0048 a0f0ff0c-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0048/desc004b 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0048/desc004a 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0044 a0f0ff0b-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0044/desc0047 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0044/desc0046 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0040 a0f0ff0a-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0040/desc0043 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0040/desc0042 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char003c a0f0ff09-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char003c/desc003f 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char003c/desc003e 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0038 a0f0ff08-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0038/desc003b 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0038/desc003a 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0034 a0f0ff07-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0034/desc0037 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0034/desc0036 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0030 a0f0ff06-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0030/desc0033 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0030/desc0032 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char002c a0f0ff05-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char002c/desc002f 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char002c/desc002e 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0028 a0f0ff04-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0028/desc002b 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0028/desc002a 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0025 a0f0ff03-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0025/desc0027 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0022 a0f0ff02-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char0022/desc0024 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char001f a0f0ff01-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char001f/desc0021 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Primary Service /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0010 a0f0fff0-5047-4d53-8208-4f72616c2d42 Vendor specific Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0010/char001b a0f0fff4-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0010/char001b/desc001d 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0010/char0018 a0f0fff3-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0010/char0018/desc001a 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0010/char0015 a0f0fff2-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0010/char0015/desc0017 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0010/char0011 a0f0fff1-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0010/char0011/desc0014 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service0010/char0011/desc0013 00002902-0000-1000-8000-00805f9b34fb Client Characteristic Configuration Primary Service /org/bluez/hci0/dev_58_7A_62_3F_63_80/service000c 00001801-0000-1000-8000-00805f9b34fb Generic Attribute Profile Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service000c/char000d 00002a05-0000-1000-8000-00805f9b34fb Service Changed Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service000c/char000d/desc000f 00002902-0000-1000-8000-00805f9b34fb Client Characteristic ConfigurationDo we have to look into one of these characteristics/desricptors for the value?
-
@lavolp3 Well according to the gitlab code we’re looking for this:
Characteristic /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char002c a0f0ff05-5047-4d53-8208-4f72616c2d42 Vendor specific Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char002c/desc002f 00002901-0000-1000-8000-00805f9b34fb Characteristic User Description Descriptor /org/bluez/hci0/dev_58_7A_62_3F_63_80/service001e/char002c/desc002e 00002902-0000-1000-8000-00805f9b34fb Client Characteristic ConfigurationThe characteristic is the one the referenced noble code is filtering for.
Now GO Timo!
Make brushing great again! -
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.
-
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 ConnectionI do not know why :/
-
@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!
-
@timodejong95 No luck yet.
No Battery status to be seen and this error in the logs0|mm | [2020-04-20 01:21:08.432] [ERROR] 01:21:08 <error> (node:23220) UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON 0|mm | --> starting at object with constructor 'DBusObject' 0|mm | | property 'proxy' -> object with constructor 'Object' 0|mm | | property 'org.freedesktop.DBus.Introspectable' -> object with constructor 'DBusInterface' 0|mm | --- property '$parent' closes the circle 0|mm | at JSON.stringify (<anonymous>) 0|mm | at /home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/index.js:24:25 0|mm | at processTicksAndRejections (internal/process/task_queues.js:89:5) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut) 0|mm | [2020-04-20 01:21:08.435] [ERROR] 01:21:08 <error> (node:23220) UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON 0|mm | --> starting at object with constructor 'DBusObject' 0|mm | | property 'proxy' -> object with constructor 'Object' 0|mm | | property 'org.freedesktop.DBus.Introspectable' -> object with constructor 'DBusInterface' 0|mm | --- property '$parent' closes the circle 0|mm | at JSON.stringify (<anonymous>) 0|mm | at /home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/index.js:24:25 0|mm | at processTicksAndRejections (internal/process/task_queues.js:89:5) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut) -
@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?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login