Hi Andrea, thanks for sharing!
However, I can’t get this to work. I’m trying this remotely, since I don’t have access to local HA for few months. Have you tried this remotely, does it work for you?
And yes, the switch remains as “off”, whatever I do.
I do have multiple cameras, hence the numbering “4” and “5”.
I will continue searching for a solution to have a switch that toggles motion detection (or video device, or even the whole add-on) on/off.
because right now I’ve created 2 automations: the first one to turn on the motion detection when I leave home and the second one to turn off it when I’m come back.
The automation works locally, so you can add a switch to activate both the automations (it is not a good solution but only to understand if it works) probably ther is a way to configure a toggle to do this avoiding 2 switch (but i don’t know how).
I suggest to configure also the e-mail notification when a motion is detected (it helped me to undestand when the motion detection is active and when not even if the toggle in motioneye add-on remain always OFF).
the only things that comes in my mind that you can do is: call the address as http://ipaddressHASSIO:7999/1/detection/start from a browser by a device connected on the same lan of hassio and then try to trigger the motion detection on motioneye on the wished ipcam (by moving one hand in front of the camera ) whait to receive the e-mail notification and in case nothing happens changing the number in the address till you find the camera wished that is activated corretely.
I don’t know how the motion detection “maps” the number of the ipcam… for example my ipcam has camera id =2 but in the link i need to specify …:7990/1/detection/start it is a little bit strange
I know that probaly ther is a better and structured way to do it, but I don’t know it
I also have the switch working in lovelace UI showing the actual state. Using the switch I can simply turn off the motion detection to stop receiving email alerts.
The key issue was (as Andrea also pointed out) to use different camera id than in motioneye web UI. I have no idea why the camera id is different, but now it works for all of my cameras.
I have no plan to implement any “smart logic” by sensing whether I’m at home or not. Simple switch in UI is quite enough for now. (Cameras are located in a remote location, at our summer house).
For some reason my raspberry pi3 cpu runs 10 degrees cooler after updating to v.0.7.0.
There was also some strange behavior earlier between cpu temperatures in camera daylight/night-mode, where in night-mode cpu usually running around 55°C and in daylight around 65°C. Now the cpu temp stays constantly around 45°C.
I am not sure if it was because of the new version or just “restarting” the addon.
Well ‘Add-ons’ are a part of Home Assistant (old HassIO) where you would have the ‘supervisor’ tab. I take it that you are just running Home Assistant Core? In this case you won’t be able to use this…unless you upgrade to Home Assistant (old name ‘HassIO’)
Many thanks.
I’m running it via docker image on a raspberry pi2 B.
Do you know any image usable on a rpi?
Actually I’m using homeassistant/raspberrypi2-homeassistant
Checking in docker hub I see some images like netdaemon/homeassistant-addon-armhf
Does addon work as separate image?
I have two cameras, one I could successfully authorize with Google Drive - but with the other camera, when I press “Test service” it just idle forever. Any tips?
Not that I found. I couldn’t get HassOS to give me access to the external drive / USB stick. I switched to running Ubuntu / HA to get around this but haven’t actually tried with external storage just yet.