System & MQTT

How EOS Connect runs, how it talks to your broker, and the one address that connects it to EVCC.

What this is for

I want EOS Connect reachable on the port and timezone I expect, with logs I can read.
I want every state it holds published to MQTT and picked up by Home Assistant on its own.
I run EVCC and want the two to work together.

System

The web port, the timezone, the log level and how often everything is recomputed. Three of these — timezone, port and log level — are also the bootstrap settings, because they are needed before the settings database is open. The site coordinates here are used when your PV source is not a location-based one; see outside temperature.

MQTT

The broker connection, and whether Home Assistant should discover the entities by itself. Every topic EOS Connect publishes and every command topic it listens on is listed under MQTT.

EVCC

One address, which unlocks EVCC in four separate roles: as the inverter EOS Connect controls, as a price source, as a PV forecast source, and as the reader of your car charging load. What each role needs is under EVCC.