Philips Dynalite

Philips Dynalite support is integrated into Home Assistant as a hub that can drive the light, switch, and cover platforms.

There is currently support for the following device types within Home Assistant:

  • Lights
  • Switches
  • Covers

A Philips Dynalite hub connects to the Dynet network, which is composed of areas, channels, and preset.

A Dynalite area typically (although not necessarily) defines some physical area, such as a room.

Each area can have one or more channels that correspond to the different devices they control. A channel can relate to a dimmable light, or other devices.

Additionally, each area can have one or more presets that determine the behavior of all the channels, and sometimes trigger additional actions. Typically, preset ‘1’ in an area means ‘on’, and preset ‘4’ means ‘off’. Additional presets could be used for scenes and dimming.


Since Philips Dynalite has virtually no auto-discover capabilities, it needs to be configured via the configuration.yaml file:

# Example configuration.yaml entry

Configuration Variables


The IP address of the bridge (e.g.,

portinteger(Optional, default: 12345)

Port number of the bridge.

namestring(Optional, default: dynalite)

Name for the bridge.

activeboolean | string(Optional, default: false)

Actively query network. When starting, it will query all devices for their current status, and also will send queries when some changes are in progress (e.g., lights dimming or covers moving). Better experience but creates more load on the Dynalite network. Value can be on, off, our init, where init will only send queries during the initial init of Home Assistant.

polltimerfloat(Optional, default: 1.0)

Polling interval for devices in transition. Value in seconds. When devices are in transition (e.g., a light fading), it will ask for a new state every X seconds until it is at the target level. Only relevant when active is set to on.

autodiscoverboolean(Optional, default: false)

Enable auto-discover. As Dynalite does not support native autodiscovery, this tracks events on your network, so if you turn on a light, it will be added to Home Assistant.


Global defaults for the system


Default fade


Definition for the various Dynalite areas.


The Dynalite area number, 1-255.


Name of the area.


Type of template to use for the area. Supported values are: room and time_cover. They are described in detail below in the template section. If the template parameters are different than defaults, they can be overridden in this section as well.

TEMPLATE_PARAMSinteger | float(Optional)

This can be any of the settings of the template. For example, for template room: room_on and room_off are possible options.


Value from template section or system defaults

fadefloat(Optional, default: 2.0)

Fade time for the area, in seconds.


Specific presets for the area.


The Dynalite preset number in the area.


Name of the preset.



fadefloat(Optional, default: 2.0)

Fade time for the preset, in seconds.

nodefaultboolean(Optional, default: false)

Do not use the default presets defined globally, but only the specific ones defined for this area.


Map of the channels in this area.


The Dynalite channel number in the area, 1-255.


Name of the channel.




Type of entity this channel should appear as. Can be either light or if this is a device that is not a light (e.g., water heater), can be switch.

fadefloat(Optional, default: 2.0)

Fade time for the channel, in seconds.


Default presets for any area without the nodefault option.


The Dynalite preset number in the area.


Name of the preset. When used in an area, it will be ‘AREA_NAME name’. For example, if a room’s name is ‘Kitchen’ and preset 4 is defined with the name Off, it will appear in HA as ‘Kitchen Off’.



fadefloat(Optional, default: 2.0)

Fade time for the preset, in seconds.


Set the default parameters for the templates.


This is used to define a room that has a preset to turn on all the channels in the area and a preset to turn off.

room_oninteger(Optional, default: 1)

Preset to turn area on.

room_offinteger(Optional, default: 4)

Preset to turn area off.


This is used to define a cover that has 3 presets: open, close, and stop. Potentially can also use a channel that some systems (e.g., Control4) use to also send commands to open and close the cover. It uses the duration it takes to open or close to determine position. In addition, many times, these covers include tilt by opening or closing for a short time, so this can be defined as well.

openinteger(Optional, default: 1)

Preset to open the cover.

closeinteger(Optional, default: 2)

Preset to close the cover.

stopinteger(Optional, default: 4)

Preset to stop the cover.

channel_coverinteger(Optional, default: No channel)

Channel that monitors the cover.

durationinteger(Optional, default: 60)

Time in seconds it takes to open or close the cover.


Time in seconds it takes to open or close the cover tilt. 0 means that the cover does not support tilt.


Type of cover for Home Assistant. Any of the possible cover classes (e.g. blind, garage, shutter) are possible.


# Example configuration.yaml entry specifying optional parameters
      port: 12345
      autodiscover: true
      polltimer: 1
          name: Office
          template: room
          name: Living Room
          template: room
          nodefault: true
          room_on: 2
          room_off: 5
              name: Entrance Spot
              fade: 10.0
              name: Dining Table
              name: Blinking Lights
              name: All Off
              fade: 3.0
          name: Curtain
          template: time_cover
          name: 'On'
          name: 'Off'
          room_on: 1
          room_off: 4

Initial configuration and discovery

Maybe the most difficult thing about a Dynalite system is finding out the areas and channel mapping. If you have them or have access to the Dynalite software and your configuration files, this could be easy, but in the likely case that your system was installed by an integrator, you will have to discover them on your own.

This is where the autodiscover option comes handy. If it is on, the component will track the Dynet network and every time a device is used, it will be added to Home Assistant. It will initially show as “Area 123 Channel 7”, but you can then add it to your configuration.yaml with the correct configuration.

For example, you would go to your kitchen light and turn it on. Now you log into Home Assistant and see what the channel was. If there was more than one discovered (e.g., someone turned off the living room lights), you can try one, turn it on and off in Home Assistant and see which light it affects.

The initial process can be a bit time consuming and tedious, but it only has to be done once. Once you are done configuring, it is better to set autodiscover to false, since there are many “fake” channels and areas that the system uses for internal communication and you do not want to have visible.