@MichMich that‘s excellent! Thanks so much!

@devmil I have the same mirror, but 4mm thick, and it works really well. Thickness shouldn’t be an issue, because the sensor is easily able to detect motions in adjacent rooms separated by stone walls. I‘d suggest to increase slightly the sensitivity by increasing the trimmer value.

Further check the soldering joints between trimmer and sensor. Maybe they need to be reworked so that the solder provides a proper connection.

You made my day, guys! 🤣

@LeonMentor You’ll have to script the CCU for that. @falke69 has recently posted, how he solved that.
See this post.

@lavolp3 great!

Hmmm…that’s strange.
Here is my config for MMM-Pir-Sensor I use:

//----------------------------------------------------------------------------------------
{
        module: 'MMM-PIR-Sensor',
        config: {
        sensorPin: 4,
        powerSavingDelay: 150, // (seconds) how long the monitor will be turned on
        
        }
},
//----------------------------------------------------------------------------------------

And this is the wiring of the sensor with the GPIO, which corresponds to the above config. ‘sensorPin: 4’ corresponds to GPIO_4 (brown cable)

@bachoo786 there exist alternative libs like piGPIO or GPIOzero, but I have no experience with them. Why not try MMM-PIR-Sensor? It is easy to install and to configure and works out of the box with the RCWL-0516.

@bachoo786 First re-check if the sensor is cabled correctly to the GPIO as described in my tutorial. Further check if the resistor is soldered correctly to the sensor. Maybe there is a “cold soldering joint”. Sounds trivial, but the devil is a squirrel (old german saying )
Then, extend the detection range to the max, to check if the sensor is generally OK (200 Ohms) and re-run @cowboysdude script. If this works, then reduce the resistor step by step until you reach the desired detection range. Theoretically 80 Ohms should provide a range of 40-50 cm, but from my experience this may vary strongly as the resistor value does not correspond linearly to the detection range.

@bachoo786 yes, you can also use pin 1 and 2.

An example:
The max value of the resistor (Rmax) is between pin 1 and 3.
Between pin 1 and 2 is the restitor value R1, and
between pin 2 and 3 is the resistor value R2.

Rmax = R1 + R2. (or R1=Rmax - R2, resp, R2=Rmax - R1)

Thus, you can use both options (R1 pin 1/2 or R2 pin 2/3).

@dvbit congrats to that MM (Monster Mirror 😉) and a happy new year! Happy to see that you use the RCWL😁

@BreakBeatJunkie Congrats to your MM! I like the simple frame design.
The thermal problems with the Pi4 are well known. As far as I know the foundation is incrementally improving the firmware. The latest beta has reduced the temperature nearly down to the level of a Pi 3B+.

@Oxyd said in My first Magic mirror, 3D Printed frame - fr - en:

Volumic STREAM 30 DUAL

Oookaayy…I won‘t show that frame to my Ender 3🤣

@Lordy I’d like to return the wishes to you and the whole community, too!🍀🍀🍀

@Oxyd that‘s absolutely impressive! Great job! Which 3D printer have you used?

@anno1972 you can still register for a API key
https://creativecommons.tankerkoenig.de/ —> API-key

For facial recognition, what hurts the Pi ? The PiCam itself (so an USB camera should be better ?) or the multiple call to photo / recognition / photo / recognition…?

It iS not the cam that demands so much resources. It‘s the software and the algorithms that allocate RAM and CPU to accomplish recognition. It is of course amazing that technically a small RPi is able to do that and demonstrate the potential on HW and SW. But still, I sometimes ask myself, is it really beneficial and adds it so much value to the „customer“ to justify the effort and expense? I admit that this question shouldn’t be asked under us mirror builders ☺️ I‘d be happy to see how you accomplished that and what your experiences are, as I‘m eager to learn.

@oli1204 glad that it works now!

@wibimaster said in Microphone, camera integration, and noob questions ;):

MVA display

Well, to answer your question specifically, it might be good to know what you want to achieve with the mic. If you want to control the mirror ang e.g. switch pages, turn display on/off, then it is sufficient to put an Echo Dot behind the mirror, connect it to the RPi as power supply and use the MMM-AlexaControl module. This is the way I went and I am totally happy with it.
That is less expensive and totally hasselfree compared to installing a dedicated mic and installing and configureing a module that emulates an Echo device on the RPi. If you intend not to use Alexa services, e.g. Lucy, ten it is of course a different game.

The PiCam should work behind the glass. But maybe you do some research regarding red blured images and IR-filtering or automatic IR-cutoff provided by the cam. I made some experiments with a PiCam (15 € knock-off from AliExpress with automatic IR-cutoff, great cam that no is going to be used with OctoPi) and facial recognition but did’t succeed. The resources needed are pushing the RPi to the limits and reliability was zero. Further I found no real user story to implement that into my MM at the end.

The MVA panel combined with the Mirropane Chrome Spy is a good choice (also my combo), as it provides a pretty good contrast compared to TN panels.

@Mykle1 THAT looks cool!👍🏻

@alyyyaaannnaaa I‘m using MMM-AlexaControl instead and it works great. The module you mentioned is not in active development.