Configuration is performed via a single TOML file, when you start the program you must pass it the name of your configuration file eg. 

`./daikin2mqtt -config /home/ha_user/daikin2mqtt.toml`

Here is a sample configuration showing all available options...
```
# All configuration options
# All entries are required unless otherwise specified

[mqtt]
base_topic = "daikin2mqtt"          # MQTT base topic
broker = "localhost"                # MQTT broker
port = 1883                         # MQTT port
username = ""                       # MQTT broker user (use "" for none)
password = ""                       # MQTT broker password (use "" for none)

[daikin]
update_period = 60                  # Seconds pause (s) between regular updates from inverters

[[inverter]]
  ip_addr = "192.168.1.50"          # The (static) IP address of the unit  
  friendly_name = "Steve_Office"    # Must be unique. Will form part of the MQTT topic
  
[[inverter]]
  ip_addr = "192.168.1.51"          # Another unit...            
  friendly_name = "Spare_Bedroom"  
```

Replace the inverter details with your own and add an `[[inverter]]` section for every unit you want to monitor/control.

A file similar to the above named `configuration.toml` may be found in the `examples` directory.

## MQTT Configuration

| Item | Description |
| ---- | ----------- |
| base_topic | defines the root topic for all messages concerned with this instance.  For consistency, throughout this wiki, we assume that you have set it to `daikin2mqtt` |
| broker     | the hostname or IP address of your MQTT Broker |
| port       | the port for connections to the your MQTT Broker, use 1883 if you haven't changed it in the MQTT broker configuration |
| username   | either "" for no username, or the MQTT username you wish to connect as |
| password   | either "" for no password, or the MQTT password you wish to connect with |


## Daikin (General) Configuration

| Item | Suggested Range | Description |
| ---- | --------------- | ----------- |
| update_period | 30 - 600 | How many seconds to wait between actively monitoring all configured inverters.  Note that this does not influence the 'reactivity' of any MQTT front-end to commands as all `set` commands are automatically followed by an implicit `get`, rather, it controls how often a front-end is updated without user intervention. |

## Inverter Configuration

| Item | Description |
| ---- | ----------- |
| ip_addr | The (static) IP address of an inverter (actually, the adaptor connected to an inverter). |
| friendly_name | A unique identifier from the user's perspective.  It is used as the second part of the MQTT topic for all messages to identify a particular inverter, i.e. the topic will be `daikin2mqtt/<friendly_name>/...`.  Avoid special characters and spaces (or test them carefully). |

You must specify both a unique `friendly_name` for each inverter and an `ip_addr`.  

Experience has shown that there are considerable benefits to assigning static IP address to your inverters.  (Although it is possible to 'discover' units via UDP - this is not reliable.)

It is strongly suggested that, where possible, you use static IP addresses for the inverters - configured via your router or DHCP server. 

Daikin2MQTT no longer supports UDP discovery - which seems to be a weak point for many Daikin wifi adaptors.