I just checked that link and YES, actually it is, thanks for pointing it out. The docs must have been updated for v0.13, they added the ffmpeg prefix to the go2rtc stance, this wasn’t there before. I found this originally in a github bug discussion with the frigate dev, where he suggested the person having issues to try this out and see what happens. There was no follow up after that suggestion though.
Note - another helpful tip for 510WA cams: in this github listing: Reolink Firmware Archive, you can find a link to version 3.1.0.1387 which I have been running for a week, this version is much newer than the latest official release (.764), it adds two useful new options in t he Stream configuration section (which is only accessible via the Web interface of the cam),
what is the point of doing that? I just checked and I have hundreds of entities, it would take a huge amount of time to see which ones to keep visible / which ones are used in automations or visualization etc. What is the harm of just leaving them exposed?
I concur with the first comment, RPi is not well suited for a media server, where you need solid storage and good performance for transcoding on the fly. However, RPis are fantastic media players
Thanks all for the tips on this. I will explore the IFTTT + todoist route that seems to be the only current option to get the Alexa/echo shopping list integrated with HA’s
I.V. Drip blend from darkcity cofee in Toronto. Roasted a few days ago. Looking forward to my morning cortado!