Can a NAS be the brain of whole-house intelligence? I installed Home Assistant into Feiniu, and even with external automation, it still ran

the year our smart devices reached forty-nine, my wife said something heartbreaking: "Turn on the light and swipe three apps, check the temperature and then swipe another one—what kind of smart is that?" I've counted the devices once, and I wrote it in of forty-nine devices, where WiFi, Bluetooth, and Zigbee are all packed together. What truly made me decide to undergo surgery were three things that the Mijia app was increasingly unable to handle.

three family matters, the Mi Home App can't handle them

the first item, once the conditions are nested, the system crashes. I want the entrance light to "automatically turn on after sunset, but if no one is home," you have to check if your phone is connected to home WiFi. This condition doesn't work when you tap the second layer of nesting in the Mi Home app. Its "simultaneous satisfaction" can't fit the combination of "after sunset" plus "any phone online." Second, the historical curve cannot be traced. The Bluetooth thermo-hygrometer in the living room only had real-time readings and a coarse, unreadable weekly report. I wanted to confirm whether the living room temperature dropped to 16 degrees in the early morning over the past week to decide whether to set the radiator's timer, but after a long time, I couldn't find the original data.

the third thing is the most infuriating. My sister was away on a business trip for about half a year, and the Graffiti Solution waterer on the balcony was managed for me. Since then, I've had both Mi Home and Tuya apps on my phone, switching between them every day. When the humidifier needs to be refilled, Mi Jia only pushes it to the Mi Home app and its own home. I want to push it to my wife's phone lock screen, but it can't do it.

three things point to the same answer: the family needs its own brain, gathering forty-nine devices together, and I'll write the logic myself. The perfect spot for this brain is the Feiniu NAS in the corner, which is running 24×/7 in the corner—it's already spinning, just adding a container.

Loaded into Feiniu: One container has four parameters

The official image of

Home Assistant is called homeassistant/home-assistant on Docker Hub. It can be installed in Feiniu's app center or Docker graphical interface. the relationship between an image and a container I explained this before when writing about Docker, so I won't repeat it here. Remember four parameters:

After

the container, wait two minutes, then enter 8123 in your browser. The wizard completes: name your family, create an account, and fill in your location—don't skip this step. Later, when you 'turn on the sunset lights,' use it to calculate the time the sun sets in your home. The whole trip takes five minutes, faster than when I tried to pretend to be Jellyfin. If you want to learn Docker systematically, you can refer to the beginner's from hardware selection to application deployment. Here, it's just one container among them.

bring Mijia in: the official team has stepped in, no need to catch token

before, connecting Mi Home devices to Home Assistant was a dirty job: you had to use third-party integration, log into your Xiaomi account to collect tokens, and tokens would expire, and once they expired, the devices would all turn gray. In February 2025, Xiaomi officially released an open-source integration, called Xiaomi Home on GitHub, and that page was completely overturned.

operation path: Set → device and service → integration in the lower left corner of the 8123 backend. Search for Xiaomi Home, the Xiaomi account login page will pop up, then scan the code in the Mi Home app on your phone to authorize, and the device list will swipe in from a full page. My forty-nine units were delivered at once, even with Chinese names like "living room light" and "entryway light" as they were, no need to reconfigure them. One thing to note: this official integration updates are quite frequent. After major version upgrades, the physical IDs of certain devices may change, and the entity names referenced in automation will become invalid. Just go to its configuration page, click "Update Device List," and check the automation again. Don't rush to suspect your device is broken.

there is a technical boundary to keep in mind: WiFi devices supporting LAN control (such as lights and sockets), while HA communicates directly to devices within the LAN; Bluetooth sub-devices (thermo-hygrometer, the batch of hanging under the speaker Pro gateway) still go through the gateway, go to the cloud, and loop back. This dividing line determines who survives and who is paralyzed in offline testing.

Xiaoai speakers, don't retire. It continues to serve as a voice entry and Bluetooth gateway, the Mi Home app continues as a remote control, and HA is an extra brain, not a replacement—each of the three systems does its own thing, and none of them delays the other.

three automation lines running, first look at the logic, then check the network disconnection

HA's automated editor is three-part: trigger, condition, action. "And" and "Or" are nested randomly. The rule I've been stuck by Mijia for two years finishes in ten minutes: the trigger should be set to sunset (calculated by local astronomical algorithms, no need to check online), the condition is "any phone connected to home WiFi," and the action is to turn on the front door light. On evenings when no one was home, the lamp was quietly left dark.

second rule: all lights automatically turn off at 23:30 at night, triggering the time to save you worry. The third is a backup for the humidifier: when the living room humidity drops below 40%, turn on the outlet, and send a notification to my phone's lock screen—the notification goes the Bark channel I used to set alerts for the NAS last time. This whole curl is so good that any phone in the family can get a push for free.

Santiao ran for a week, and the most satisfying part was the sunset route: the sun's setting point changed daily, so the light time adjusted accordingly, so I didn't have to manually change the schedule every month like I did at Mi's place.

external network test and three accounts from the NAS side

Saturday morning, I spent half an hour unplugging the fiber cable from the optical modem, specifically checking the quality of these three automated wires. The conclusion is divided into two levels, honestly jot it down:

this result is consistent with the about the robot vacuum disconnected: logic is local, execution is on the local network, and any device that needs to go to the cloud and circle around stops working. The vacuum cleaner's map has a local chip, so it disconnects from the network and scans; HA's sun angle is calculated by itself, so the light is turned on—it's the same thing.

NAS still have three accounts to settle. Memory: HA steady-state uses over 400MB, plus Jellyfin and qBittorrent. My 8GB Feiniu is solid, but for a 4G memory machine, you need to consider it first. Electricity costs are the most worry-free: NAS is always running 24×7, and year's electricity bill has already been calculated . HA relies on memory, not electricity, so the marginal cost is about zero.

writing plate is the most shady of all. HA has a component called recorder, which records every state change of each entity into an SQLite database by default—forty-nine devices. High-frequency entities like signal strength and battery percentage can write the database to dozens of MB overnight. On the third day after installation, I used the old method of checking who woke me up from sleep saw that the mechanical disk was woken up right after sleeping and returned to how it was before treatment. Three tricks to fix it: exclude high-frequency entities like signal strength in the configuration, increase commit_interval to make the drive less frequent, and move database files to that old SSD download drive— download drive never sleeps, so just write it. With three moves, the mechanical disk stayed steady all night.

Who

Avoid Messing With: Take It Personally

you really want to install it, follow this order: first confirm NAS memory and Docker environment, set up a container and select the network as the host, enter 8123 to complete the wizard, then scan the code to connect to Mijia, use the first automated test triggered by time (the simplest and least scamming method), run smoothly before playing Sunset and Conditional Nesting. For recorder drive issues, I recommend fixing them on the day you build the PC, rather than waiting until the hard drive is constantly disturbed to remember—there's an extra resident container on your NAS, and every drive must be worthy of it.