You can use mjpeg steram from motionEye
ok, interesting, but seems thats the only menu that doesnt expand for me? all other menus are working?Âľ
i can enable it to âONâ , but i am not able to expand it
is it because i addedd network cameras?
Camera on screenshot is also network camera, with rtsp stream
huh?
look my screenshot, it just doesnt fold open , any idea?
second question, where can you change the settings of the camera? where you can enter the url, the screen when you add the camera the first time (if IP or something should be changed), i cant find it
Turn on the advanced settingsâŚ
OMG, thats it 
thnx
ok, seems snapshot url is working / embed url also
but streaming url is not ,
also tried changing the port, maybe some conflict
progress now
192.168.0.17 sent an invalid response.
- [Try running Windows Network Diagnostics](javascript:diagnoseErrors()).
ERR_SSL_PROTOCOL_ERROR
also tried VLC to open stream, didnt work also
EDIT: if any1 can test the Videostream URL for me? like some screenshots above
for me the snapshot url and embed url is working
the streaming url is not working, tried different cams
thnx!
Hello
Iâm trying to install and run this add-on motionEye as explained but i always receive a log message with the following error:
Log
[s6-init] making user provided files available at /var/run/s6/etcâŚexited 0.
[s6-init] ensuring user provided files have correct permsâŚexited 0.
[fix-attrs.d] applying ownership & permissions fixesâŚ
[fix-attrs.d] done.
[cont-init.d] executing container initialization scriptsâŚ
[cont-init.d] 00-banner.sh: executingâŚ
Hass.io Add-on: motionEye v0.3.0
Simple, elegant and feature-rich CCTV/NVR for your cameras
From: Community Hass.io Add-ons
armhf / Raspbian GNU/Linux 9 (stretch) / HA 0.90.2 / SU 150 / stable
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executingâŚ
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] 02-updates.sh: executingâŚ
INFO: You are running the latest version of this add-on
[cont-init.d] 02-updates.sh: exited 0.
[cont-init.d] 10-requirement.sh: executingâŚ
FATAL: The configured certfile is not found
[cont-init.d] 10-requirement.sh: exited 1.
[cont-finish.d] executing container finish scriptsâŚ
[cont-finish.d] 99-message.sh: executingâŚ
Oops! Something went wrong.
We are so sorry, but something went terribly wrong when
starting or running this add-on.
Be sure to check the log above, line by line, for hints.
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
And Iâm not able to start this addon or access the web UI
Iâm using a raspberry pi 3b+ with Home Assistant
0.90.2
Can you please let know what I have to do in order to solve this issue?
Thank you in advance for your support and best regards
By default, motioneye seems to record to hassioâs âshareâ directory.
Is there a way to mount a separate drive to hassio somehow and let motioneye save to that folder so that the video files donât fill up the main drive?
EDIT: replying to myself:
I tried to add a symlink to /share/motioneye_data but motioneye was not able to write to it for some reason. Then I mounted the same folder that I symlinked to /share/motioney_data and that workedâŚ
However, changing the destination folder for every camera manually is annoying since the default cannot be set in the general preferences. I think what could work is to replace the entire /share/motioneye folder with an exernal folder mounted into the share folderâŚ
1 Like
Yep, this is a problem with the current implementation. I have had my hass.io install screwed up because there was no space left on disk. I couldnât even log in using ssh. A reboot of the system made it even worse becuase now lots of service werenât able to start.
I grabbed the console and delete a few 100 mbâs in my homedir and quickly cdâd into the docker dirs and trashed all the recordings. Rebooted the system and now everything was fine again.
Ever since that happened I removed motioneye just to be sure. If it is possible to store the recordings on a different location that would really be nice and I would most certainly try it out again.
Iâve done what I wrote in my last comment and mounted the motioneye folder into share before installing the add-on . This seems to work without any further config.
The bind mount has to be added to /etc/fstab in order to be Automatically mounted after reboots.
Its a shame that hassio does not offer a solution out of the box. For other add-ons such as influxdb this little hack is not possible because it does not keep itâs data in hassio/share.
The same thing happened to me (filled up my drive). I didnât realize I could hit advanced settings to get to the features. Can you limit the amount of recording? Say for a certain amount of days or certain amount of space?
I suppose I can just reinstall it and check it out for myself.
Edit: installed. You can choose to auto delete after 1 day, 1 week, one month, one year, forever, and custom. I am going to try 1 week in small web format.
Edit 2: Easier way for me. You can save the recordings to a network share. Perfect!
Hi. Will that addon support ingress?
Thank You. You rock man!
Thats awesome. Now I can die in peace 
when it will be released?
waiting for it
I do not work on a schedule. So cannot answer that.
1 Like
nevermind,
i will wait for your great work
thanks for providing so many addons which really helps us to keep going with home-assistant
thanks again
It is ok m8⌠somewhere SOON ⢠
2 Likes
Release v0.4.0
This release adds support for Hass.io Ingress
Besides Ingress, this release adds major upgrades to motionEye & motion itself 
Create snapshot before upgrade!
If you upgrade from a previous version of the add-on, all your current configuration files need to be converted and migrated. The add-on will do this for you, nevertheless, it is strongly advised to create an Hass.io snapshot before upgrading.
Breaking change
The addition of Ingress makes this add-on not accessible directly. If you have added motionEye via an iframe panel, this release will break that.
However, you can enable this again by going into the add-on configuration. A new section show is visible: âNetworkâ. Enter port 8765 (or anything else if you want) in the disabled field. Hit the âSAVEâ followed by the âRESTARTâ button to make your iframe work as before.
An option to add an Ingress capable add-on to the sidebar menu automatically is expected to land in Home Assistant 0.92.
Changes
-
Typo (#22) (@timmo001) -
Updates MarkupSafe to v1.1.1 (#23)
-
Updates tornado to v6.0.2 (#28)
-
Updates pillow to v6 (#29)
-
Upgrades add-on base image to 3.1.0
-
Removes custom log format override -
Makes log_level optional
-
Upgrades curl to 7.64.0-r1
-
Upgrades gcc to 8.3.0-r0
-
Upgrades musl-dev to 1.1.20-r4
-
Upgrades pip to 18.1-r0
-
Upgrades python to 2.7.15-r3
-
Upgrades mosquitto-clients to 1.5.6-r0
-
Upgrades py-setuptools to 40.6.3-r0
-
Upgrades motion to 4.2.2-r0
-
Rewrite add-on onto Bashio
-
Removes default config options
-
Adds Hassio Ingress support
-
Adds ARMv7 support
-
Workaround Docker issue by reinstating legacy tags -
Upgrades motioneye to 0.40rc5
-
Downgrades tornado to 5.1.1 -
Merged init scripts
-
Updates jinja2 to v2.10.1 (#30)
-
Updates documentation to match recent changes
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
3 Likes