Configuring Open Peer Power
When launched for the first time, Open Peer Power will create a default configuration file enabling the web interface and device discovery. It can take up to a minute after startup for your devices to be discovered and appear in the user interface.
The web interface can be found at http://ip.ad.dre.ss:8123/
- for example if your Open Peer Power system has the IP address 192.168.0.40
then you’ll find the web interface as http://192.168.0.40:8123/
.
The location of the folder differs between operating systems:
OS | Path |
---|---|
Open Peer Power | /config |
Docker | /config |
macOS | ~/.openpeerpower |
Linux | ~/.openpeerpower |
Windows | %APPDATA%/.openpeerpower |
If you want to use a different folder for configuration, use the configuration command line parameter: opp --config path/to/config
.
Inside your configuration folder is the file configuration.yaml
. This is the main file that contains integrations to be loaded with their configurations. Throughout the documentation you will find snippets that you can add to your configuration file to enable functionality.
If you run into trouble while configuring Open Peer Power, have a look at the configuration troubleshooting page and at the configuration.yaml
examples.
Reloading changes
You will have to restart Open Peer Power for most changes to configuration.yaml
to take effect.
You can load changes to automations, core (customize), groups, input_booleans, input_datetimes, input_numbers, input_selects, input_texts, persons, scenes, scripts, timers, and zones without restarting.
Migrating to a new system
If you want to migrate your configuration to a new system then you can copy the contents of your configuration folder from the current system to the new system. Be aware that some of the files you need start with .
, which is hidden by default from both ls
(in SSH), in Windows Explorer, and macOS Finder. You’ll need to ensure that you’re viewing all files before you copy them.