@hub_hazal
Runs a house full of automations and has learned which parts must never depend on wifi.
15 credit Contributor
One thing to avoid: manually adding paths to the analyser configuration by hand.
It works, and then a library updates or you add a board and the hand-written list is wrong, silently, in a file nobody remembers editing. The generated version is regenerated; the hand-edited version rots.
If you must add something by hand, add it in the place the generator does not overwrite, and leave a comment saying why.
There are specific failures, and they are worse for a hub than for an ordinary computer for a reason that is worth understanding.
A hub is a hub. It is not one device using the network, it is the thing every other device talks to. A momentary wifi problem on a laptop means a page loads slowly. The same problem on the hub means every automation in the house is unavailable at once, and anything that was mid-conversation with it fails.
Automations are latency-sensitive in a way browsing is not. A motion sensor firing a light is expected to feel instant. Wifi introduces variable delay — usually small, occasionally hundreds of milliseconds when the channel is busy — and the perceptible result is a light that comes on late sometimes. That is the "feels slow" you are describing.
Wifi shares one channel. Somebody streaming video, a neighbour's network, a microwave, all compete. Ethernet does not share in that way.
Whatever you choose, put the reason in the configuration file rather than in your head.
A line saying that verification is off because this hop never leaves the host is the difference between a considered decision and something a future reader copies onto a link that does cross a network. Configuration outlives the reasoning unless the reasoning is written next to it.
One thing to check when it works from some devices and not others: clients that ignore your resolver.
Phones and browsers increasingly use encrypted DNS to a provider of their own choosing by default. Those queries never reach your filter, so local names fail and filtering also silently stops working on that device.
The fixes are per-platform — turning off private DNS on a phone, disabling secure DNS in a browser, or advertising your own encrypted resolver. Worth knowing before concluding your configuration is wrong, because it looks identical to a misconfiguration and it is the client deciding not to ask you.