A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
Read the statement by Michael Teeuw here.
MMM-OralB / Bluetooth equipped toothbrush integration
-
@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?
-
@timodejong95
I have removed the module, installed again and added the extra piece of configuration. The updated UI is working fine, but there is no battery indicator. Is this the log you are looking for?[2020-04-22 19:40:43.278] [LOG] MMM-BluetoothDevices received device update for OralB
[2020-04-22 19:40:43.389] [LOG] MMM-BluetoothDevices trying to connect to: OralB 1/2
[2020-04-22 19:40:53.451] [LOG] MMM-BluetoothDevices received device update for OralB
[2020-04-22 19:40:53.673] [LOG] MMM-BluetoothDevices trying to connect to: OralB 2/2
[2020-04-22 19:40:59.444] [LOG] MMM-BluetoothDevices received device update for OralB
[2020-04-22 19:41:10.482] [LOG] MMM-BluetoothDevices received device update for OralB
[2020-04-22 19:41:13.767] [ERROR] MMM-BluetoothDevices unhandled exception:
[2020-04-22 19:41:13.771] [ERROR] MMM-BluetoothDevices Error: Error: waitForServicesResolved: timeout exceeded
[2020-04-22 19:41:13.774] [ERROR] MMM-BluetoothDevices {“troubleshooting”:“devices#resolve-services”,“extra”:{}}
[2020-04-22 19:41:21.451] [LOG] MMM-BluetoothDevices received device update for OralB
[2020-04-22 19:41:32.477] [LOG] MMM-BluetoothDevices received device update for OralB
[2020-04-22 19:41:43.546] [LOG] MMM-BluetoothDevices received device update for OralB
[2020-04-22 19:41:54.482] [LOG] MMM-BluetoothDevices received device update for OralB -
@timodejong95 there are no logs above that.
I get this error before I started the brush[2020-04-23 00:19:17.258] [ERROR] 00:19:17 <error> MMM-BluetoothDevices unhandled exception: (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:47 Logger.error) [2020-04-23 00:19:17.263] [ERROR] 00:19:17 <error> MMM-BluetoothDevices Error: Error: Couldn't connect to BABSIS OralB after 2 tries. (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:47 Logger.error) [2020-04-23 00:19:17.277] [ERROR] 00:19:17 <error> (node:2929) UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON --> starting at object with constructor 'DBusObject' | property 'proxy' -> object with constructor 'Object' | property 'org.freedesktop.DBus.Introspectable' -> object with constructor 'DBusInterface' --- property '$parent' closes the circle at JSON.stringify (<anonymous>) at /home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/index.js:24:25 at processTicksAndRejections (internal/process/task_queues.js:89:5) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut) [2020-04-23 00:19:17.284] [ERROR] 00:19:17 <error> (node:2929) UnhandledPromiseRejectionWarning: TypeError: Converting circular structure to JSON --> starting at object with constructor 'DBusObject' | property 'proxy' -> object with constructor 'Object' | property 'org.freedesktop.DBus.Introspectable' -> object with constructor 'DBusInterface' --- property '$parent' closes the circle at JSON.stringify (<anonymous>) at /home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/index.js:24:25 at processTicksAndRejections (internal/process/task_queues.js:89:5) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut) [2020-04-23 00:19:17.289] [ERROR] 00:19:17 <error> (node:2929) 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:27 writeOut) [2020-04-23 00:19:17.293] [ERROR] 00:19:17 <error> (node:2929) 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:27 writeOut) [2020-04-23 00:19:17.296] [ERROR] 00:19:17 <error> (node:2929) [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:27 writeOut) [2020-04-23 00:19:17.299] [ERROR] 00:19:17 <error> (node:2929) [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:27 writeOut) [2020-04-23 00:23:44.731] [LOG] 00:23:44 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:23:47.096] [LOG] 00:23:47 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:23:57.944] [LOG] 00:23:57 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:24:08.935] [LOG] 00:24:08 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:24:19.917] [LOG] 00:24:19 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:24:30.925] [LOG] 00:24:30 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:24:41.961] [LOG] 00:24:41 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:24:52.927] [LOG] 00:24:52 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:25:03.965] [LOG] 00:25:03 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:25:14.860] [LOG] 00:25:14 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:25:25.926] [LOG] 00:25:25 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:25:36.875] [LOG] 00:25:36 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:25:47.877] [LOG] 00:25:47 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:25:58.907] [LOG] 00:25:58 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log)This error vanishes when I deactivate the JSON.stringify function.
I have the feeling that everything is working, but the battery is not showing up at all.Also, when closing the mirror (ctrl+c when I started it with
npm start dev) I get these errors:[2020-04-23 00:38:03.482] [ERROR] 00:38:03 <error> (node:4615) UnhandledPromiseRejectionWarning: TypeError: device.destroy is not a function at Dongle.disconnectDevices (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Dongle.js:223:28) at Dongle.destroy (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Dongle.js:58:17) at Class.stop (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_helper.js:46:23) at App.stop (/home/pi/MagicMirror/js/app.js:252:16) at App.<anonymous> (/home/pi/MagicMirror/js/electron.js:108:7) at App.emit (events.js:200:13) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut) [2020-04-23 00:38:03.486] [ERROR] 00:38:03 <error> (node:4615) UnhandledPromiseRejectionWarning: TypeError: device.destroy is not a function at Dongle.disconnectDevices (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Dongle.js:223:28) at Dongle.destroy (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Dongle.js:58:17) at Class.stop (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_helper.js:46:23) at App.stop (/home/pi/MagicMirror/js/app.js:252:16) at App.<anonymous> (/home/pi/MagicMirror/js/electron.js:108:7) at App.emit (events.js:200:13) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut) [2020-04-23 00:38:03.489] [ERROR] 00:38:03 <error> (node:4615) 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:27 writeOut) [2020-04-23 00:38:03.495] [ERROR] 00:38:03 <error> (node:4615) 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:27 writeOut) [2020-04-23 00:38:03.503] [ERROR] 00:38:03 <error> (node:4615) [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:27 writeOut) [2020-04-23 00:38:03.509] [ERROR] 00:38:03 <error> (node:4615) [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:27 writeOut) -
-
and more debugging messages, sorry for the spamming:
[2020-04-23 00:51:53.902] [LOG] 00:51:53 <log> MMM-BluetoothDevices starting hub (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/node_helper.js:23 Class.startHub) [2020-04-23 00:51:58.845] [LOG] 00:51:58 <log> MMM-BluetoothDevices unhandled adapter msg: {"serial":1536,"path":"/org/bluez/hci0","interface":"org.freedesktop.DBus.Properties","member":"PropertiesChanged","signature":"sa{sv}as","sender":":1.8","type":4,"flags":1,"body":["org.bluez.Adapter1",[["UUIDs",[[{"type":"a","child":[{"type":"s","child":[]}]}],[["00001112-0000-1000-8000-00805f9b34fb","00001801-0000-1000-8000-00805f9b34fb","0000110e-0000-1000-8000-00805f9b34fb","00001800-0000-1000-8000-00805f9b34fb","00001200-0000-1000-8000-00805f9b34fb","0000110c-0000-1000-8000-00805f9b34fb","0000110a-0000-1000-8000-00805f9b34fb","0000111f-0000-1000-8000-00805f9b34fb","00001805-0000-1000-8000-00805f9b34fb"]]]]],[]]} (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:32 Logger.debug) [2020-04-23 00:52:01.474] [LOG] 00:52:01 <log> MMM-BluetoothDevices unhandled adapter msg: {"serial":1542,"path":"/org/bluez/hci0","interface":"org.freedesktop.DBus.Properties","member":"PropertiesChanged","signature":"sa{sv}as","sender":":1.8","type":4,"flags":1,"body":["org.bluez.Adapter1",[["Discovering",[[{"type":"b","child":[]}],[true]]]],[]]} (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:32 Logger.debug) [2020-04-23 00:52:01.993] [LOG] 00:52:01 <log> MMM-BluetoothDevices trying to connect to: DIRKS OralB 1/2 (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:52:13.667] [LOG] 00:52:13 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:52:13.834] [LOG] 00:52:13 <log> MMM-BluetoothDevices awaiting services for device: DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:32 Logger.debug) [2020-04-23 00:52:17.445] [LOG] 00:52:17 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:52:23.028] [LOG] 00:52:23 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:52:33.871] [ERROR] 00:52:33 <error> MMM-BluetoothDevices unhandled exception: (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:47 Logger.error) [2020-04-23 00:52:33.875] [ERROR] 00:52:33 <error> MMM-BluetoothDevices Error: Error: waitForServicesResolved: timeout exceeded (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:47 Logger.error) [2020-04-23 00:52:33.905] [LOG] 00:52:33 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:52:44.875] [LOG] 00:52:44 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:52:55.859] [LOG] 00:52:55 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:53:06.911] [LOG] 00:53:06 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:53:17.884] [LOG] 00:53:17 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) [2020-04-23 00:53:28.849] [LOG] 00:53:28 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) -
@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.
-
@timodejong95 said in MMM-OralB / Bluetooth equipped toothbrush integration:
@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.
I don’t have a problem with that. Devices are connecting well as soon as I activate them. Everything works really well except no battery status shown.
Apparently the waitForService process ends unresolved, hence is not able to get the information from the battery service[2020-04-23 00:52:33.875] [ERROR] 00:52:33 MMM-BluetoothDevices Error: Error: waitForServicesResolved: timeout exceeded (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:47 Logger.error) -
@lavolp3 Check I get you. Just to be sure, you did do
npm installI changed a package? If not then I will comeback to it when I have tested it myself. -
@timodejong95 said in MMM-OralB / Bluetooth equipped toothbrush integration:
@lavolp3 Check I get you. Just to be sure, you did do
npm installI changed a package? If not then I will comeback to it when I have tested it myself.Yes I did.
Did it now again (but no new installations) and trying again tonight -
@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.
-
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.
-
@timodejong95 IT WORKED! At least partially, that is.
0|mm | 00:13:17 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:17.988] [LOG] 0|mm | 00:13:17 <info> MMM-BluetoothDevices reconnecting to: DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:24 Logger.info) 0|mm | [2020-04-26 00:13:17.995] [LOG] 0|mm | 00:13:17 <log> MMM-BluetoothDevices trying to connect to: DIRKS OralB 1/1 (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:21.469] [LOG] 0|mm | 00:13:21 <log> MMM-BluetoothDevices connected to device: DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:21.534] [LOG] 0|mm | 00:13:21 <log> MMM-BluetoothDevices awaiting services for device: DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:32 Logger.debug) 0|mm | [2020-04-26 00:13:21.552] [LOG] 00:13:21 <log> MMM-BluetoothDevices waiting for services to be resolved for: DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:32 Logger.debug) 0|mm | [2020-04-26 00:13:29.503] [LOG] 0|mm | 00:13:29 <log> MMM-BluetoothDevices connected to: DIRKS OralB after 1 try (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:29.961] [LOG] 0|mm | 00:13:29 <log> MMM-BluetoothDevices battery updated to: 100% for: DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:32 Logger.debug) 0|mm | [2020-04-26 00:13:29.966] [LOG] 00:13:29 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:29.979] [LOG] 00:13:29 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:30.255] [LOG] 0|mm | 00:13:30 <log> MMM-BluetoothDevices battery updated to: 100% for: DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:32 Logger.debug) 0|mm | [2020-04-26 00:13:30.259] [LOG] 00:13:30 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:31.229] [LOG] 0|mm | 00:13:31 <log> MMM-BluetoothDevices battery updated to: 99% for: DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:32 Logger.debug) 0|mm | [2020-04-26 00:13:31.234] [LOG] 00:13:31 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:31.466] [LOG] 0|mm | 00:13:31 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:31.520] [LOG] 0|mm | 00:13:31 <log> MMM-BluetoothDevices connection lost with device: DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:33.303] [LOG] 0|mm | 00:13:33 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:33.315] [LOG] 0|mm | 00:13:33 <info> MMM-BluetoothDevices reconnecting to: DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:24 Logger.info) 0|mm | [2020-04-26 00:13:33.318] [LOG] 00:13:33 <log> MMM-BluetoothDevices trying to connect to: DIRKS OralB 1/1 (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:43.919] [LOG] 0|mm | 00:13:43 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:13:54.916] [LOG] 0|mm | 00:13:54 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:14:05.881] [LOG] 0|mm | 00:14:05 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:14:13.884] [LOG] 0|mm | 00:14:13 <info> MMM-BluetoothDevices failed to reconnect to: DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:24 Logger.info) 0|mm | [2020-04-26 00:14:13.886] [LOG] 00:14:13 <log> MMM-BluetoothDevices Error: Error: Couldn't connect to DIRKS OralB after 1 try. (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:32 Logger.debug) 0|mm | [2020-04-26 00:14:16.957] [LOG] 0|mm | 00:14:16 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:14:28.049] [LOG] 0|mm | 00:14:28 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:14:38.869] [LOG] 0|mm | 00:14:38 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:14:49.968] [LOG] 0|mm | 00:14:49 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:15:00.855] [LOG] 0|mm | 00:15:00 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:15:12.156] [LOG] 0|mm | 00:15:12 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:15:22.928] [LOG] 0|mm | 00:15:22 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log) 0|mm | [2020-04-26 00:15:33.865] [LOG] 0|mm | 00:15:33 <log> MMM-BluetoothDevices received device update for DIRKS OralB (/home/pi/MagicMirror/modules/MMM-BluetoothDevices/src/Logger.js:17 Logger.log)Battery updates are there but only in the beginning.
I would assume my battery drains more than this one percent in 2 minutes but may be wrong.
Nothing displayed on the mirror.
Might still be missing? -
@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.
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