Had to buy 10yo DOCSIS router that actually is usable
Alternatively, you don’t have to be restricted to a 10-year-old router just because of DOCSIS.
You could change the router to bridge mode , effectively making it just an external modem for any ethernet-to-ethernet router of your choosing.
Agreed.
However, I find their “Ask AI” LLM helper to actually be helpful for this. It’s linked at the bottom of the page on docs.frigate.video, and IMHO is actually one of the few LLMs that answers fairly accurately about items within its scope. It provides good source references to the actual docs that apply to the question.
I haven’t tried it yet, but I see the SMLIGHT SLZB06 get recommended a lot for Zigbee
I don’t use Memories, but yes, uploading photos with FolderSync to Nextcloud (via WebDAV) does add them to the Nextcloud database. They show up as new photos in the recent activities list.
buttons were discovered by the Conbee and worked perfectly fine, but the home assistant refuses to recognize their functionality.
That’s not the hardware stick; that’s the controller software stack. Sounds like you switched from deConz to ZHA to go with the hardware change. In which case, this is all fixed by using Zigbee2MQTT instead of HA’s built-in ZHA. Z2M supports more hardware and features than ZHA.
Also known as “the iron triangle”.
Dahua is still a top manufacturer, but does not focus on selling to individual consumers.
In the US, you will find Dahua cameras being sold most often by Amcrest and Lorex.
GlusterFS is (was) really cool, but I would not set up a new instance. It used to have significant support and development from RedHat, but they decided to halt their work on it, and focus on Ceph.
GlusterFS is getting a few slow updates from some alternate developers, but I would only count on that being fixes for current installations.
For a certain very specific usage of the word “better”
Yes, many bad ideas are possible to implement. At least temporarily. Until the next cleanup process figures out how to remove cadvisor dir regardless of file contents. Or the next OS release turns /tmp into a ram disk. Or… or… or…
Yes, it’s a fun academic exercise to think through possible mitigations. And in the end, it will still be dumb to keep this in /tmp
Why wouldn’t changing to permissions keep the file from being deleted by the internal process?
That’s like keeping your lunch laying outside on the sidewalk, getting stepped on by people and destroyed, and then wondering if your lunch would be safer if you put it in a stronger bag (but still left it on the sidewalk).
Don’t leave your lunch outside laying on the sidewalk, regardless of what you might do to “protect” it. Don’t keep important files in /tmp
Isn’t profitable? Insurance companies are definitely making profits because of their tactics of doing that to their customers,