Toothbrush integration

dfuerst

of course, i used the electron downgrade. obviously i didn’t know that i have to enter " npm rebuild" to test the .js, sorry for that.

you understood me correct. the timer never stopped, i will check that again after git pull

as i 'm abroad till monday i will provide this infos to you on monday.
you wrote the error is the xpected behaviour? as i mentioned MM showed just SEARCHING…

many thanks for your effort

SvenSommer

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.

dfuerst

ok. i understand. full reply on monday

dfuerst

RPi3
NODE : v6.9.2
NPM: 3.10.9
MagicMirror@2.0.0

dfuerst

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 counting

scenario 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 counting

scenario 3:

same result as in scenario1

scenario 4:

same result as in scenario1

dfuerst

This post is deleted!

dfuerst

in MM:
scanning was started. Everything is working fine.
noble warning: unknown handle 64 disconnected!
, in MagicMirror

SvenSommer

@dfuerst

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.

onetwankyfive

@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.

dfuerst

@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