Advanced configuration
A freshly installed ioBroker system is running, but it's configured for convenience, not continuous operation: no login, no encryption, no backups, all data stored in the built-in file databases. This is fine for a start. However, as soon as the system is used seriously, it's worth taking a look at the points in this chapter.
| Page | What it's about |
|---|---|
| Access management | Users, groups, and the rights to the individual object. |
| authentication | Enable login to Admin, web and the other interfaces. |
| Encryption | HTTPS and certificates for web access. |
| CLI | Commands on the command line. The escape route when the user interface is no longer accessible. |
| Multihost | Distribute the load across multiple computers. |
| Redis | Maintain the states in a faster database. |
| Data recording | Record values: history, influxdb or sql, and how to switch between them. |
| interfaces | Access points for everything that is not an adapter: simple-api, rest-api, WebSocket. |
| Data backup | What is being backed up, where it goes, how often, and how it is returned. |
If you only read one of these pages, make it the data backup page . Everything else can be done later, but a missing backup cannot.
A sensible order for a system that is intended to remain:
- Set up the security system and trigger it manually once.
- User password
adminAssign and activate registration . - If the system is to be accessible beyond the home network: encryption is required, or better yet, the route via the IoT adapter .
- Create separate user accounts with restricted rights for other people in the household.
- Only when the system grows large: Redis and possibly multihost .