Find your hardware before you buy anything.

The fallback for hardware no driver names: where the manufacturer publishes a register map, the device can be read over RS485 or Ethernet. Whether it can also be controlled depends on what that map exposes.

Heat pumps, wallboxes, storage and PV that carry the EEBUS mark. Pair the device and it appears — no brand entry needed.

Any charge point that can dial into a local central system. Point it at the controller and it registers itself.

Lighting, blinds, HVAC and metering actuators on an existing KNX line — the controller joins the bus rather than replacing it.

Whatever Home Assistant already integrates becomes visible to the scheduler, and the schedule becomes visible in Home Assistant.

Ecosystems the controller joins directly, with no vendor cloud in between. Plugs and switches running Tasmota are discovered over MQTT; Shelly Gen2 and newer answer over local HTTP JSON-RPC on the LAN. Devices from other open ecosystems arrive through the generic paths beside this one.

Values and states stream on MQTT topics on the device, so anything on site that speaks MQTT follows the schedule instead of polling for it.

A REST API on the device for state, forecasts, schedule and settings, with a machine-readable schema. This is the path for building automation and IT systems that integrate over HTTP.

The controller provides protocol-compatible meter emulation for selected inverter interfaces, including DTSU666-compatible and AlphaESS-compatible modes. This allows supported inverters to communicate with the controller through their standard meter interface.