-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: getUserMedia is not implemented in this browser #56
Comments
Could you try enabling the legy camera support in the raspi-config tool? 3 Interface Options -> I1 Legacy Camera |
The Legacy Camera is on. |
I'm having the same issue too, runs fine in Chromium once authorised. |
FYI: I switched back to the legacy raspios (https://www.raspberrypi.com/news/new-old-functionality-with-raspberry-pi-os-legacy/) and there the bug doesnt seem to appear. |
Correct. On the legacy raspios it works. |
So we can close thi sissue for now? |
I have the same issue. I'm using MM more than 4 years and now I just updated MM to version 2.0.19. After the update MotionDetector stop to work with message "Requested device not found". I tried workaround (start MM with 'npm run server' and open chromium thru remote XDisplay (MobTerm). First time it asked me to allow camera and next time it didn't. Is it possible to make this chromium setting permanent for all browser session, or something similar? My mirror is in my living room and I don't /can't have mouse and keyboard always connected to start it manually every time. |
It looks like this won't work again with the latest version of MagicMirror.
|
Has anyone had any luck with this? |
I reinstalled raspbian and now keep getting following message:
Error: getUserMedia is not implemented in this browser
Tested older and new versions of raspbian on Pi4, also Stretch version on Pi3.
Config > address: “0.0.0.0”,
When changing to “localhost” or “127.0.0.1” you get the “NotFoundError: Requested device not found”
https://forum.magicmirror.builders/topic/16315/mmm-motiondetector-error-getusermedia
The text was updated successfully, but these errors were encountered: