Read the statement by Michael Teeuw here.
Toothbrush integration
-
For the Bug Hunt Post I reduced the code of the MM-scripts to a absolute minmum.
That’s the reason the module is always showing ‘SEARCHING…’ right now.If the scripts would work as exspected the console output would show
scanning was started. Everything is working fine.all the time the MM² is started.
Thats all I’m hoping to see right now. -
ok. i understand. full reply on monday
-
RPi3
NODE : v6.9.2
NPM: 3.10.9
MagicMirror@2.0.0 -
scenario 1:
scanning started…
Toothbrush connection ALIVE atMon Jan 30 2017 17:12:15 GMT+0100 (CET)
Toothbrush is running
0:1
0:2
Toothbrush connection LOST at Mon Jan 30 2017 17:12:17 GMT+0100 (CET) was alive since Mon Jan 30 2017 17:12:15 GMT+0100 (CET)
two input in less than 3 sec! (2 sec) => ignoring input!
0:3
0:4
0:5
endless countingscenario 2:
scanning started…
noble: unknown peripheral e0e5cffc4d8c connected!
noble: unknown peripheral e0e5cffc4d8c disconnected!
Toothbrush connection ALIVE atMon Jan 30 2017 17:14:25 GMT+0100 (CET)
Toothbrush is running
0:1
0:2
Toothbrush connection LOST at Mon Jan 30 2017 17:14:28 GMT+0100 (CET) was alive since Mon Jan 30 2017 17:14:25 GMT+0100 (CET)
two input in less than 3 sec! (2 sec) => ignoring input!
0:3
0:4
0:5
0:6
endless countingscenario 3:
same result as in scenario1
scenario 4:
same result as in scenario1
-
This post is deleted! -
in MM:
scanning was started. Everything is working fine.
noble warning: unknown handle 64 disconnected!
, in MagicMirror -
Behavior of brushTimer.js script
According to results of the tested scenarios your brush has a different behavior than mine.
I was expecting a reconnect when you power off your brush.
This is very bad.Maybe we can find another person to test the characteristics of this behavior?
@Shifty or @onetwankyfive: Are you able to give the testscript a run with the postet scenarios to help us out here?Behavior of the module within the MM-framework
With th help of @aschulz90 I finally solved to run noble within the MM²-framework. See here for details.
I noticed the
noble warning: unknown handle 64 disconnected!- warning. It’s nothing that should bother. -
@SvenSommer I have a brush that is compatible and can help… are the instructions posted 5 days ago the correct ones? I can give it a whirl tonight / tomorrow morning if they are.
-
@SvenSommer
Ok, as proven during the scenarios:
my brush does a connect followed by another reconnect after 3sec, which happens without user interaction.
so i land again at ‘hcitool con’, can your script be modified easiely to operate as intended at the very beginning (scanning for BLE brush macaddrr. every few seconds and stopping upon not finding it anymore, vanishing+resetting after a defined time period) of this topic?btw i use the:
Oral-B Pro 6500 Smart Series Electric Toothbrush with Bluetooth Technology Powered by Braun@onetwankyfive
i appreciate your help testing the script, please provide us with the model no/type of your brush -
@onetwankyfive
Thanks four your help! Yes, please follow these instructions of the eight steps to get the testscript running.For clarification, please provide us with the output from the four scenarios:
- Start the Brush; wait like 10 seconds and stop.
- Start and stop within 3 seconds.
- Start, wait like 10 seconds and stop. Start again within the next 10 seconds for like 5 seconds.
- Start, wait like 10 seconds and stop. Start again after 40 seconds and stop whenever you like.
And as @dfuerst mentioned the model seems to differ in their behavior. I’m using a a Braun Oral-B PRO 6000. Do you know yours?
@dfuerst
I don’t get your point in usinghcitool.
Do you get a reconnect after you have stopped your brush withhcitool?
Or is your brush connected viahcitoolas long as it’s running?To answer your question: If you want to use
hcitool, its easier to adapt to MMM-Networkscanner by @ianperrin like you did in your first attempt.
But as I already mentioned, I’m sure this is even more unreliable and unaccurate.
But if you wanna try, I’m willing to help you.
