My MotionEye solution (v 0.8.1) was working perfectly with remote file storage. As soon as I migrated upto ME v 0.9.0, the video was no longer visible in ME and had to rebuild my Home Assistant (on RPi4).
A sample of the ME (0.9.0) log looks like…
WARNING: Connect error on fd 13: ECONNREFUSED
WARNING: Connect error on fd 13: ECONNREFUSED
WARNING: Connect error on fd 13: ECONNREFUSED
WARNING: Connect error on fd 13: ECONNREFUSED
WARNING: Connect error on fd 13: ECONNREFUSED
WARNING: Connect error on fd 13: ECONNREFUSED
WARNING: Connect error on fd 13: ECONNREFUSED
WARNING: Connect error on fd 13: ECONNREFUSED
WARNING: Connect error on fd 13: ECONNREFUSED
WARNING: Connect error on fd 13: ECONNREFUSED
WARNING: Connect error on fd 13: ECONNREFUSED
ERROR: Exception in callback <functools.partial object at 0xb5c99330>
Traceback (most recent call last):
File “/usr/lib/python2.7/site-packages/tornado/ioloop.py”, line 758, in _run_callback
ret = callback()
File “/usr/lib/python2.7/site-packages/tornado/stack_context.py”, line 300, in null_wrapper
return fn(*args, **kwargs)
File “/usr/lib/python2.7/site-packages/motioneye/smbctl.py”, line 283, in _check_mounts
motionctl.start()
File “/usr/lib/python2.7/site-packages/motioneye/motionctl.py”, line 129, in start
raise Exception(‘motion failed to start’)
Exception: motion failed to start
The ME config is…
motion_webcontrol: false
ssl: false
certfile: fullchain.pem
keyfile: privkey.pem
action_buttons:
The other applications in this package are…
HassOS 4.13
Home Assistant Core 0.115.1
MotionEye 0.9.0
Supervisor 245
File editor 5.1.0
Pretty confident I can get this working by rebuilding using ME v0.8.1 but prefer to find a fix for the v0.9.0.
If further data is required then please ask.
Thanks…Rob