Your IT expert
in Frankfurt

First I measure instead of guessing: signal strength in every room and which channels the neighbours use. In Frankfurt apartment blocks, many networks often share the same channels in the 2.4 GHz band. Only then do I decide whether a setting is enough, the router just needs a better spot, or a second access point is really needed. I rarely recommend a repeater, because connected over Wi-Fi it halves the speed.

First I check whether wallbox, inverter and meter can talk to each other at all, usually over Modbus or the manufacturer's interface on the local network. Then I set up evcc to use your system's surplus and, when the sun is not enough, keep charging on one phase instead of stopping, provided your wallbox supports it. With dynamic tariffs, the price curve comes in. It all runs on a small computer at your home, not in a cloud that can be switched off.

First we look at which process is worth it at all: often enough the honest answer is that an automation costs more upkeep than it saves. If it is worth it, I usually build it with n8n on your own server, so no customer data sits with a provider and there is no monthly fee per run. A language model goes in only where it is really needed, not for its own sake.

I plan from the function, not the device: what should happen in the morning, what when you leave the house. That determines which technology is needed at all. I prefer components that work locally and do not fail when the internet is down or a manufacturer ends its service. The light must still switch on at the wall.

I build static sites delivered as finished HTML instead of computing in the background on every visit. That is faster, cheaper to run, and there is no login page that can be hacked. This site is built the same way. I check accessibility and loading time before launch, not after.