I just figured out that recent version of motionEye addon with Ingress support prevents using Snapshot URL of a camera unless you are authorized against Home Assistant UI. If you open the URL in an incognito window, you’ll get “unauthorized” error. This makes impossible, e.g., to use it as the still_image_url parameter for an HA camera.
There is a workaround: one should change addon configuration so that container port in the Network Section has a meaningful value (e.g. 8675 like Frenck suggested in the release notes). Save, restart addon, then open motionEye with URL like: <your_ha_address>:8675, then copy Snapshot URL again. This new URL will be accessible outside of HA.
Hope this helps.
scr,
Do you find it better to use the still image directly from the camera or from motion eye?
Thanks for this tip. The same thing can be used to allow authorization with Google Drive service. For anyone else that’s having the same issue.
- Set the motioeye port (ie. 8675).
- Open motionEye with URL like: <your_ha_address>:8675
- The authorize service for Google Drive will now work as you’re no longer using the Ingress URL.
My camera doesn’t offer still image URL so I cannot compare. I wanted motioneye to provide one to test new stream HA feature which is only supported by the generic camera component for now. Generic camera, in turn, requires two parameters: still_image_url and stream_source. Nevermind, I failed to get it working both using rtsp stream from my camera and mjpeg stream provided by motioneye.
Did anybody manage to use camera.stream service with a motioneye stream?
Additional thoughts: if you have only one client for your camera, probably you’ll notice no difference or even motionEye may add a small delay. But for several clients motionEye should handle it better than a tiny camera microcontroller.
I’m using motioneye with a Dafang Hack cameras, all of which have their own built-in motion detection. And create an MQTT binary switch for motion detection, which HA can auto-discover.
Which would be best in terms of lower CPU / RAM resource use? Let the DaFang Cameras do the motion detection or let MotionEye handle it?
The main reason for wanting to use MotionEye is that it has a very handy feature of auto-uploading stills and video to my Google Drive. So I have an off-site backup.
Thanks, currently only have one cam, and will add an additional one this summer. They are LTS cams, so probably more than I need, but they work great. Plus I get a great deal on them. I figured if I didn’t have MotionEye handle streaming it would work better (since the camera is already doing it, and supports still, ONVIF, etc).
Lately I noticed every time I go to the MotionEye add-on, I have to login over and over again. This while the remember me button is turned on. Something to do with cache or…?
I use Safari the latest version on my macOS.
my stream still only shows a couple seconds of video then freezes with the a picture card… its fine in the actual MotionEye window
someone is kind enough to explain to me how to configure the recordings on “google drive” I have not found any documentation on the steps. Thank you
I have an issue that has persisted since I first started using the addon. Every time the addon is restarted I get a critical error which makes it unusable:
CRITICAL: media directory "/var/lib/motioneye" does not exist or is not writable
The only workaround is for me to unistall and re-install the add-on. Fortunately I have a backup config for the addon so that I can reconfigure it quickly. The above error is always for the same directory.
sorry in the post 146 I don’t see “The steps are detailed” I see this …
These are the steps to follow.
Hello,
I am trying to run PS3Eye camera (USB) connected to RPI3B running HassIO 0.92.2.
I tried looking for some guidance here.
However aint got much traction.
Can someone please guide how to use PS3Eye camera to be able to use MotionEye for Motion detection. For motioneye itself I guess pretty much a lot of documentation would be availabe to make it work.
Thanks.
I’m still unable to get the add-on to start up. As far as I can tell everything is setup correctly.
I have /share/google_assistant.json
installed and the content looks right…
{
"installed":{
"client_id":"XXXXXXXX.apps.googleusercontent.com",
"project_id":"XXXXXXXX",
"auth_uri":"https://accounts.google.com/o/oauth2/auth",
"token_uri":"https://oauth2.googleapis.com/token",
"auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs",
"client_secret":"XXXXXXXX",
"redirect_uris":[
"XXXXXXXX",
"http://localhost"
]
}
}
Those who have it work, are you able to shed some light or share your config?
I’m using Hass.io inside Docker/Proxmox and currently running HomeAssistant 0.93.0
Is there someone who has been able to get a ESPHome ESP32 camera to work with motioneye?
I added the ESP32 camera with ESPHome. Then I added the integration, so that I have a new entity within Hassio, containing the videostream.
Now I’m struggling to find the correct settings to access this stream in motioneye. Any help would be appreciated!
Providing the ESP32 camera is broadcasting an RTSP stream, you should be able to access it in MotionEye as a Network Camera.
A quick Google search seems to imply that the following address is what you need. rtsp://yourdevipaddr:8554/mjpeg/1
the trailing address after the port number maybe different in your case.
I tried your suggestion, but I’m still struggling. Which camera type do I choose?
Also it’s unable to connect: