I’ve developed a camera module that works in tandem with my voicecontrol module. How do we handle these module to module dependencies when publishing a module?
Read the statement by Michael Teeuw here.
Posts
-
Handle dependencies
-
RE: Website Launched
Another one: “MagicMirror² has an extensive documentated API.”
It should probably be “MagicMirror² has an extensively documented API.” -
RE: MMM-TTS
@strawberry-3.141 I could start looking at the module for voice rec. if you don’t mind.
-
RE: Motion Detector
Huge thank you to @strawberry-3-141 for helping to troubleshoot this issue and suggesting the solution! While I know all kinds of dev languages and tools, I am pretty new RPI and Linux.
-
RE: Motion Detector
@cowboysdude this is what I had suspected. What kind of camera do you have? Web camera over usb?
-
RE: MMM-TTS
@strawberry-3.141 what’s left there, what’s working and what’s not?
-
RE: MMM-TTS
@strawberry-3.141 hey, man, what’s the state of your MMM-voice module?
-
RE: Motion Detector
@trividar before I spend some time creating a dev branch, could you please run the magic mirror from the terminal on RPI with the following command line:
npm start devThe magic mirror will be started with dev tools enabled. Switch to the 'Console" tab in the dev tools and you should be able to see the following output:
“compare result=Infinity,Infinity;0,0” when there’s no movement before your camera and something like “compare result=49,44;31,47” when there’s some movement.
Also if you could also look for errors in this console as well (red colored lines).
-
RE: Motion Detector
@strawberry-3.141 I have a feeling that the camera is not properly captured from the client side js code. I am going to create a dev branch with a lot more logging soon.
-
RE: Motion Detector
It’s logging in the terminal window that you use to start the mirror with npm start. You can also start the mirror with “npm start dev” with dev tools and there will be the output from the chromium.
-
RE: Motion Detector
@cowboysdude so just to confirm, when you run the status command on the RPI you get this output, right?
-
RE: Motion Detector
Could you also run the
/opt/vc/bin/tvservice -swhen your monitor is on? -
RE: Motion Detector
@cowboysdude could you please run the magic mirror from the terminal until it switches off and doesn’t switch back on, bring the monitor back with the command and post your screenshot of the terminal?
-
RE: Motion Detector
Was your monitor on when you were starting the magic mirror?
-
RE: Motion Detector
Ok, the next step let’s check whether the off state is detected correctly. After you switched off the monitor with the first command try to execute this in the ssh term:
/opt/vc/bin/tvservice -sand let me know which output you see.
-
RE: Motion Detector
I am sorry to hear about your issues. Trying to think of the best way to troubleshoot that. The module doesn’t do anything fancy. It just executes these in the node_helper to switch on/of the output on HDMI:
Switch off:
/opt/vc/bin/tvservice -oSwitch-on:
/opt/vc/bin/tvservice --preferred && sudo chvt 6 && sudo chvt 7As a first step, could you please try to execute these commands in the ssh terminal?
Note from admin: Please use Markdown on code snippets for easier reading!
-
RE: jquery not working on magic mirror
@Ryroro could you try run the MM with dev tools and check the console out for errors.
npm start dev