Toothbrush integration

dfuerst

Now i made a reinstall.

brushtimer.js works until i rebuild electron!!!
but without rebuilding MM just shows the white screen error.

after rebuilding i get this upon sudo node brushTimer.js:

pi@raspberrypi:~/MagicMirror/modules/MMM-OralB $ sudo node brushTimer.js
module.js:597
  return process.dlopen(module, path._makeLong(filename));
                 ^

Error: Module version mismatch. Expected 48, got 50.
    at Error (native)
    at Object.Module._extensions..node (module.js:597:18)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object. (/home/pi/MagicMirror/modules/MMM-OralB/node_modules/bluetooth-hci-socket/lib/native.js:3:15)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)

so, after this rebuild i get the error of my previous post in MM

SvenSommer

@dfuerst
Module version mismatch-Error
Just to summarize and for clarification:
The Module version mismatch. Expected 48, got 50
or
NODE_MODULE_VERSION 50. This version of Node.js requires
NODE_MODULE_VERSION 51. Please try re-compiling or re-installing
is a known “bug”, which we were able to solve by the rebuilding of electron as you posted a few days ago.

So if you want to use the module in MM you have to use this statement in the MMM-OralB-folder:

sudo npm rebuild --runtime=electron --target=1.4.6 --disturl=https://atom.io/download/atom-shell --abi=50

If you want to test brushtimer.js-script standalone in the console, you need to build the packeges in the MMM-OralB-folder with

npm rebuild

Behavior of brushTimer.js script
So if I understood you correctly, you were able to start the timer, but it never stopped?
For a better understanding I added some debug information in the brushtimer.js -script. Cut you please trigger an update by

cd ~/MagicMirror/modules/MMM-OralB
git pull

and try the following scenarios and provide me with the console output text.

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.

Behavior of the module within the MM-framework
You wrote:

“noble warning: unknown handle 64 disconnected!”
“scanning was started. Everything is working fine.”
this two message’s i get upon every activation, so the MM show always SEARCHING…"

Actually this behavior is the intended action right now. As I wrote in this Bug Hunt Post I have problems in bringing noble alive within MM²-framework.
Surprisingly you aren’t suffering from this error, so could you please tell me:

Which platform (Rasperry Pi 2/3, etc.),
Node - version: node --version
npm - version: npm --version
MagicMirror: cd ~/MagicMirror/ and DISPLAY=:0 npm start

you are using?

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.