Skip to main content

Install NetDaemon runtime

There are several ways to deploy your apps. You could just run the development project and set it up yourself. NetDaemon provides a convenient ways to run your apps:

  • Using a Home Assistant add-on
  • In a docker container
  • Or using the template as base deploy your own.

So let's set it up before we can deploy the apps to it.

NetDaemon versions

This doc describes setting up the V2 version. For NetDaemon v3 please checkout installing the NetDaemon V3.

Install NetDaemon as a Home Assistant add-on

Two versions are provided, release and dev for both NetDaemon version 2 and version 3. If you feel you always want the latest and greatest changes you can choose the dev build for the version that you selected but be prepare that things break!

  1. Make a folder structure under your Home Assistant configuration directory to use for NetDaemon apps. /config/netdaemon

  2. Add the in Add new repository URL to the add-on store.

  3. Add the NetDaemon add-on.

  4. Deploy your apps in the folder /config/netdaemon/apps for V2 and /config/netdaemon3/apps for V3 .

Advanced add-on configurations

The standard way running your apps in add-on is just to copy the .cs and .yaml files to /config/netdaemon/apps or (/config/netdaemon3/apps is you are using V3) and it will dynamically compile and run them. If you want to use your own project with custom dependencies you will have to use the advanced deployment options.

Specify the AppSourcesetting in add-on config. If you set a app_source: folder, then it will dynamically compile and run apps in /config/netdaemon/folder.

If setting app_source: daemonapp.csproj it will compile and run the project in /config/netdaemon/daemonapp.csproj with all it's dependencies. To deploy apps Set the app_source: daemonapp.dll it will run the published project in /config/netdaemon/daemonapp.dll.

There is no way to include other dependencies in the standard dynamically compiled option No, for this we recommend the Advanced add-on configurations decribed above, to include for example a external nuget package.

Install as a docker container

If you are using Home Assistant Core and do not have the possibility to run add-ons, using the docker container is a convenient way to run NetDaemon apps.

Always use specific versioning tags of docker containers (not latest or dev) cause these are constantly getting new versions and things could break You can always find the latest stable version here

Example docker run configuration

docker run -d \
--name netdaemon \
--restart=always \
-e TZ=Europe/Stockholm \
-p 1337:1337 \
-v ~/netdaemon_config:/data \

-p 1337:1337 is only needed if you want the admin panel

Example using docker-compose.yaml for

version: '3.7'
image: netdaemon/netdaemon # use netdaemon/netdaemon:ver
# for specific version
container_name: netdaemon
restart: always
- HOMEASSISTANT__HOST=your_ip_or_hostname
- LOGGING__MINIMUMLEVEL=info # use trace/debug/info
- TZ='Etc/UTC' # Set your current timezone
- 1337:1337 # This is required only if
# you are running the GUI
- /config/netdaemon:/data # replace /config/netdaemon
# to your local folder

Evironment variables

The docker container needs 3 environment variables to run properly.

HOMEASSISTANT__HOSTThe host that is running Home Assistant (defaults to localhost)
HOMEASSISTANT__PORTThe port Home Assistant is running on (default to 8123)
HOMEASSISTANT__TOKENA Long Lived Acces Token(LLAT) that NetDaemon can use for the comminication with Home Assistant.
NETDAEMON__GENERATEENTITIESDefaults to False, set True if you want the autogenerated entities
LOGGING__MINIMUMLEVELDefaults to info, values are (trace, debug, info, warning, error)
TZYou will need to set container time zone to make the scheduler work properly
NETDAEMON__APPSOURCENETDAEMON__APPSOURCE is used to setup more advanced runtime options. If you set a folder, the deafult dynamically compiled apps should be set in this folder. If daemonapp.csproj the runtime will run that project with all it's dependencies.Set to daemonapp.dll for published project. For standard dynamically compiled projects you do not have to set this setting.
NETDAEMON__ADMINSet this to false to disabled the Admin UI.


/dataThe volume of the netdaemon folder should be mapped to /data See how to setup the correct folder here

Folder structure and where to map the docker volume

The ~/netdaemon_config need to point to the netdaemon folder. See image below. The red arrow in the example configuration below points to the folder that should be mapped to the /data!