FHEM Setup on Windows: Port, Perl, and First Start

The FHEM setup on Windows takes two downloads and one command: the fhem-6.4 zip package, released March 29, 2025, and a Strawberry Perl portable build. Extract both into the same folder, run perl\bin\perl fhem.pl fhem.cfg, and the web frontend answers on port 8083, per the FHEMWiki Windows guide edited December 28, 2025. Nothing touches the Windows registry unless you go on to install the service.

What does the FHEM setup on Windows install?

The FHEM setup on Windows puts two files in one folder, fhem.pl and fhem.cfg, and the fhem.de Windows HOWTO asks for at least 350MB of free space before you unpack anything.

Step	What you do	Where the step comes from
1	Download fhem-6.4.zip, the release of March 29, 2025	fhem.de, download section, accessed October 9, 2026
2	Extract fhem-6.4\fhem-6.4 into a new folder, for example f:\my-fhem	FHEMWiki, FHEM Installation Windows/en, edited December 28, 2025
3	Extract a Strawberry Perl Portable Edition into that same folder; the wiki uses 5.42.0.1 64-bit	FHEMWiki, edited December 28, 2025
4	Run portableshell.bat, then perl\bin\perl fhem.pl fhem.cfg	FHEMWiki, edited December 28, 2025
5	Set up the firewall exception for the Perl interpreter	FHEMWiki, edited December 28, 2025
6	Open http://localhost:8083/fhem in the browser	FHEMWiki, edited December 28, 2025

The same folder works on a USB stick or on an internal drive, so the install itself stays reversible. Once it runs, the hardware question arrives separately: the fhem.de description asks for a 24/7 machine plus a CUL, EnOcean or Z-Wave USB stick for real sensors and actors. The walk-throughs under Tutorials start from the same unpack-and-launch point.

How does FHEM setup on Windows update itself?

FHEM on Windows started from a command line prints nothing and never hands the prompt back, so a busy console window is the healthy state, not a hang.

“There is no visible output and the command won’t terminate.” That is how the fhem.de FHEM on Windows HOWTO describes the start command, in the section on starting FHEM, accessed October 9, 2026.

Updates run from inside the frontend. Type update in the FHEMWEB command line, wait, then type shutdown when the process asks for shutdown restart, and relaunch perl\bin\perl fhem.pl fhem.cfg from the console. The fhem.de HOWTO puts the runtime of that last command at around a minute and recommends running save first so the config is not lost.

Which commands should run first after FHEM setup on Windows finishes?

The First steps in FHEM guide, English version edited January 1, 2025, walks through five commands with no radio hardware attached at all.

1. define mySwitch1 dummy creates a switch that has no physical lamp behind it.
2. attr mySwitch1 room Training puts it in a room; devices with no room attribute land in Unsorted.
3. attr mySwitch1 webCmd on:off adds the two buttons to the room view.
4. define n_mySwitch1 notify mySwitch1 set myLamp1 $EVENT copies any event to a second device.
5. define a_myLamp1 at +00:01:00 set myLamp1 off turns that lamp off after one minute.

Then type save. Until you do, FHEM marks the unsaved state with a red question mark next to Save config and the changes vanish at the next restart. Once real sensors arrive, the readings land in FileLog files or, if you prefer a database, in dblog; the mechanics of getting FHT updates into a database are covered in logging FHT updates to a database.

Can FHEM setup on Windows start as a service and stay off the network?

FHEM installed as a service starts invisibly during Windows boot, but that install writes an entry into the Windows registry, which the portable install deliberately avoids.

From a command prompt opened as administrator, extend the machine PATH to cover the fhem, perl\bin and c\bin folders, run perl fhem.pl fhem.cfg -i, then net start fhem. Windows lists the result as “fhem server” in Administrative Tools. The older fhem.de HOWTO installs the extra Perl modules Win32::Daemon and Win32::Console before that step. Service mode also behaves better: shutdown restart completes, while the console start ignores it.

Out of the box the frontend answers on port 8083 with no password and no encryption, and the FHEM Quick-Start, edited November 9, 2023, calls that a security warning. Hardening means allowed devices plus the HTTPS attribute for FHEMWEB and SSL for telnet. Once you start shipping sensor events somewhere else, a message pipeline earns its keep; that is the subject of enterprise logging and alerting.

USB dropouts are the failure people blame on FHEM and it is not always FHEM’s fault. “This is not an issue of fhem but a problem of hardware and/or USB drivers,” the FHEM FAQ on fhem.de, accessed October 9, 2026, says about a dongle that disconnects and reconnects on its own.

FHEM Setup on Windows FAQ

Does the FHEM setup on Windows change the Windows registry?

No. The portable install documented by FHEMWiki leaves the registration database untouched, which is why the zip and the Perl build can live on a USB stick. Registering FHEM as a service is the one step that does write a registry entry, and it needs an administrator prompt.

Which Perl build does FHEM setup on Windows need?

A Strawberry Perl Portable Edition, extracted into the same folder as fhem.pl. The FHEMWiki walkthrough uses the 64-bit 5.42.0.1 portable package and runs portableshell.bat before starting FHEM. The FHEM FAQ lists Perl 5.6 or newer as the floor, and Win32::SerialPort on Windows for serial sticks.

Why does FHEM print nothing after I start it on Windows?

FHEM runs as a server, so the command that starts it stays attached and quiet. The fhem.de HOWTO says it plainly: no visible output, and the command does not terminate. If the window never returns a prompt, that is normal, and the web frontend on port 8083 is where you check whether it came up.

Can FHEM setup on Windows start automatically at boot?

Yes, as a Windows service. From an administrator command prompt you run perl fhem.pl fhem.cfg -i, then net start fhem, and Windows lists the service as “fhem server” in Administrative Tools. It starts invisibly during Windows startup, and the service mode handles shutdown restart cleanly, which the console start does not.