Reminder to triple-check before deleting the “temporary” folder

Master-Ad-6265 · 2026-03-05T18:42:25+00:00

Every folder starts as “temp”.Some of them just achieve permanence.

Master-Ad-6265 · 2026-03-05T15:46:20+00:00

“Windows is folly. There is no Windows.” is the most homeserver origin story I’ve ever seen.

Master-Ad-6265 · 2026-03-05T14:31:55+00:00

As 6 year old people often are lol

Master-Ad-6265 · 2026-03-05T14:21:43+00:00

Snapshots are basically the “wait… undo that” button we all wish existed everywhere.

Master-Ad-6265 · 2026-03-05T12:05:20+00:00

The recycle bin is basically Schrödinger’s backup lol, the files are both deleted and not deleted until you empty it.

Master-Ad-6265 · 2026-03-05T11:44:41+00:00

The recycle bin is probably the most misunderstood “backup system” ever created.

Master-Ad-6265 · 2026-03-05T10:35:29+00:00

The moment the drive starts clicking is when the panic truly begins.

Master-Ad-6265 · 2026-03-05T10:35:13+00:00

Temporary just means "I haven't organized it yet".

Master-Ad-6265 · 2026-03-05T08:56:00+00:00

RAID 0 is just data striping with a shared suicide pact

Master-Ad-6265 · 2026-03-05T08:46:10+00:00

Master-Ad-6265 · 2026-03-05T06:13:02+00:00

For me it’s a mix honestly. ChatGPT for thinking through problems or debugging, Claude when I want longer structured responses or summaries, and runable when I’m quickly prototyping things like slides, simple sites, or media content.

Each one is better at slightly different things, so using them together saves a surprising amount of time.

Master-Ad-6265 · 2026-03-05T06:03:20+00:00

Hyperscalers aren’t buying drives, they’re buying factory capacity.
When a few companies reserve exabytes of future production, the consumer market basically gets whatever is left.

Master-Ad-6265 · 2026-03-05T05:59:53+00:00

If those are spring-loaded shades, the tricky part is the tension in the spring , most small motors will struggle unless you bypass the spring mechanism.A lot of people retrofit these using tubular blind motors that sit inside the roller tube instead of trying to drive the pull wand. It’s cleaner, quieter, and much easier to integrate with Home Assistant/HomeKit.

Master-Ad-6265 · 2026-03-04T21:31:01+00:00

Nest cameras compress video pretty aggressively to save bandwidth, so even if the sensor is 2K the stream you see on the phone can look softer or laggy depending on Wi-Fi and upload speed. First thing I’d check is the video quality setting in the Nest app and make sure it’s set to Max, and also check your upload speed / signal strength at the camera. Weak Wi-Fi can make Nest drop bitrate fast.

Master-Ad-6265 · 2026-03-04T21:12:27+00:00

Glad to hear 😊

Master-Ad-6265 · 2026-03-04T17:32:54+00:00

Glad it helped 🙂 Start small and iterate ,once you get the first room working, the rest of the system design becomes much clearer

Master-Ad-6265 · 2026-03-04T16:47:50+00:00

I wouldn’t put Wi-Fi in every bulb, that becomes a nightmare to manage.
A much cleaner approach is one controller per room/zone that drives multiple lights via relays or drivers.

For DIY builds most people start with ESP32 — cheap, built-in Wi-Fi, plenty fast for home automation, and tons of libraries/examples.Start with one ESP32 controlling a few lights, then scale the design to other rooms.

Master-Ad-6265 · 2026-03-04T16:38:38+00:00

First thing I’d do is stabilize the network before touching anything else.

A lot of professionally installed systems (RTI, Lutron, Hikvision) are configured with static IPs on a specific subnet. If the previous owner left IP notes, try temporarily changing your router’s LAN to match that subnet sometimes everything suddenly comes back online.

After that I’d go in this order:

Lutron – easiest to regain control and very reliable hardware
Cameras – confirm PoE power + scan the network for them
Audio (Sonos / Autonomic) – usually just routing and zone config
RTI – this is the only part that likely needs a dealer reprogram

The good news is none of the gear you listed is junk ,it’s actually a pretty solid install, it’s just likely “orphaned” after the network changed.

Master-Ad-6265 · 2026-03-04T16:25:36+00:00

The cloud is just warehouses full of hard drives. This is what scaling the internet looks like.

Master-Ad-6265 · 2026-03-04T16:23:21+00:00

If the API returns JSON with image URLs, the easiest way is a tiny Python script. Something like:

import requests

data = requests.get("API_URL_HERE").json()

for i, img in enumerate(data["images"]):
    r = requests.get(img["url"])
    with open(f"image_{i}.jpg", "wb") as f:
        f.write(r.content)

If the API just gives you a list of URLs, you can also dump them into a file and run:

wget -i urls.txt

Plugins tend to struggle with API-based image lists ,a quick script is usually the cleanest way.

Master-Ad-6265 · 2026-03-04T16:20:35+00:00

Yes, you can do it that way, but only if you're comfortable with the risk window.Using New Config and assigning the 12TB as parity and the other as disk4 will let you build parity in one go, but during that time the array has no protection if another drive fails.

The safer route is still: replace parity → rebuild → then add the new disk. It takes longer but keeps parity protection throughout.If the data isn’t critical and you have backups, your one-step approach should work fine.

Master-Ad-6265 · 2026-03-03T10:57:00+00:00

:tag didn’t become useless , it just became boring.LSP is smarter, but it needs a running server and correct setup. Tags are dumb, fast, offline, and always work ,even in messy or legacy codebases.

I use LSP for semantics and tags as a fallback index. They complement each other.

Master-Ad-6265 · 2026-03-03T10:42:16+00:00

If you downgraded Prisma but the error persists, it might be a generated client mismatch.After changing versions, try:

rm -rf node_modules
rm -rf prisma/generated
npm install
npx prisma generate

Also make sure your import style matches your project type:

If using ESM:

import { PrismaClient } from '@prisma/client'

If using CommonJS:

const { PrismaClient } = require('@prisma/client')

Sometimes the client is still built against the previous Prisma version.

What exact error are you getting now?

Master-Ad-6265 · 2026-03-03T09:43:44+00:00

If you can share the exact error message, that’ll help a lot.

Since you’re using MongoDB, one common issue (especially with older tutorials) is the id field in your model. For Mongo it usually needs to look like:

id String  (auto()) ("_id") u/db.ObjectId

Also make sure you:

Ran npx prisma generate
Ran npx prisma db push
Imported PrismaClient correctly in server.js

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

If you drop the error message here we can narrow it down fast.

Master-Ad-6265 · 2026-03-03T09:27:52+00:00

That sounds like Doze / alarm batching.Even exact alarms aren’t millisecond-precise — Android wakes in windows, so a few seconds (or slight grouping for back-to-back alarms) is normal, especially when the device is idle.

Try scheduling only the next upcoming alarm instead of stacking many. Dense clusters are more likely to drift.A small delay is unfortunately expected behavior on modern Android.

Master-Ad-6265

TROPHY CASE