Skip to main content
Contents

EnergyOS brings two jobs together: managing your energy systems remotely, and managing the devices that connect everything. This guide explains what each part does, how the pieces talk to each other, and how to set them up.

Getting started

  1. Create an account and sign in. The Free plan needs no credit card.
  2. Add your energy systems under Remote energy management → Energy systems (heat pump, PV, battery, EV charger), or create demo systems to look around first.
  3. Connect a device under Remote device management → Add device. It runs the EnergyOS agent next to your systems and reports its status (see the agent).
  4. Link each system to its device. The overview then shows whether it is online.
The EnergyOS overview with the two areas: remote energy management and remote device management
The overview shows the two areas in this order: energy management, device management.

How EnergyOS fits together

EnergyOS never talks to your equipment directly. A small program at your site, the gateway or the agent, talks to the equipment and keeps one outgoing, encrypted connection to the EnergyOS message broker. Everything else happens through that connection.

How EnergyOS connects to your equipment Equipment talks to a gateway or the EnergyOS agent at your site. The gateway connects outbound over MQTT with TLS to the QLines broker, which passes the messages to EnergyOS. You use EnergyOS in a browser over HTTPS. At your site QLines Equipment Heat pumpPV inverterBatteryEV chargerEnergy meter Gateway or agent Home Assistantevcc · Node-REDEnergyOS agent(rc-agent) MQTT broker TLS, port 8883one login per deviceown topics only EnergyOS dashboards, rulesreports, alertsdata store You browseror phone MQTT over TLSoutbound only HTTPS No open port, no VPN, no fixed IP The gateway only dials out to the broker. Every device has its own login and can only use its own topics: rc/account/device/…
Everything at your site connects outwards. Nothing needs to reach into your network.
PartWhere it runsWhat it does
EquipmentAt your siteHeat pump, PV inverter, battery, EV charger, meters, sensors. Speaks its own protocol (Modbus, OCPP, KNX, Matter, a vendor API).
GatewayAt your site: a Raspberry Pi, mini PC, NAS or serverTranslates between the equipment's protocol and EnergyOS messages. Home Assistant, evcc, Node-RED, zigbee2mqtt or a small script can all be the gateway.
EnergyOS agentOn a Linux device at your siteReports the device's health (CPU, memory, disk, temperature), runs network tests and runs commands you send from the page.
MQTT brokerQLinesReceives and hands out messages. Every device has its own login and can only use its own topics.
EnergyOSQLinesShows the data, sends commands, runs rules and alerts, and shows the weather forecast and the electricity prices.

Which one do I need? To read and control energy systems you need a gateway that speaks MQTT (see Connecting equipment). To watch and manage a computer (status, charts, network quality, remote commands) you install the agent (see The agent). One device can do both: the agent and Home Assistant can run side by side on the same Raspberry Pi.

Remote energy management

An energy system is one piece of equipment: heat pump, PV system, battery, EV charger, boiler, energy meter. For each you enter a name, the type, the rated power, how it is connected, and the device (the gateway) it is linked to.

  • Overview: one tile per system with its main value and a live / no-data status. When PV, a grid meter or a battery report values, the energy flow is shown: PV, grid (import or export), battery, house consumption and the share you cover yourself.
  • System page: all latest values, a history chart (6 hours, 24 hours, 7 days, any channel), controls and the list of recent commands.
  • Demo systems: Create demo systems adds five systems with two days of simulated readings and simulated commands, to look around or to record a video.
Energy flow: PV 5.2 kW, grid export 4.7 kW, battery 0 W, house 505 W, 100 percent self-sufficient
The energy flow at the top of the page.
Add an energy system form and one tile per system: heat pump, roof PV, home battery, wallbox and grid meter
Add a system, or create demo systems. Each tile shows the main value and whether the system is live.
A heat pump system page with the latest values and a 24-hour power history chart
A system page: latest values and a history chart for any channel.

Controls

Controls depend on the type. Heat pump: operating mode (blocked, normal, recommended on, forced on, as in SG Ready), hot water target, power limit. EV charger: charging allowed, current limit, power limit. Battery: mode, maximum charge power. PV: feed-in limit. Boiler: flow temperature setpoint.

What happens when you change a control EnergyOS checks the value and sends the command to the gateway. The gateway answers with a confirmation, a refusal, or not at all. The result is shown as acked, failed or no confirmation, and the setting is only remembered after a confirmation. You set itmode, limit, target EnergyOS checksvalue and range Sent: …/setto the gateway Gateway confirms: …/ack okShown as acked. The setting is remembered. Gateway refuses: ack with an errorShown as failed, with the reason it gave. No answer in timeShown as no confirmation. Not assumed to work.
A setting is only remembered once the gateway confirms it. Without an answer it is shown as "no confirmation", never as done.
Controls of a demo heat pump: operating mode, hot water target and power limit, each with a Send button
Controls of a heat pump. Commands to demo systems are simulated.

Connecting equipment (MQTT)

EnergyOS talks MQTT. A gateway sits next to your equipment, talks to it in its own protocol, and exchanges flat JSON messages with EnergyOS. Any program that can speak MQTT can be the gateway: Home Assistant, Node-RED, evcc, zigbee2mqtt, a Matter server, or a small script. Use the MQTT login of the device the system is linked to: the device ID is the user name and the device token is the password, over TLS on port 8883 (server mqtt.qlines.net).

publish   rc/{account}/{device}/energy/{system_id}        {"power_w": 4200, "soc_pct": 63}
listen    rc/{account}/{device}/energy/{system_id}/set    {"cmd_id": "...", "control": "mode", "value": "eco"}
confirm   rc/{account}/{device}/energy/{system_id}/ack    {"cmd_id": "...", "ok": true, "message": ""}

The system page shows these topics with your real IDs. Readings are numbers only (up to 40 channels per message), stored at most every 10 seconds and kept for 90 days; they count towards the daily message limit of the device.

ChannelMeaning
power_wPower in W (battery: positive while charging)
grid_wGrid meter: positive = import, negative = export
soc_pctBattery state of charge in %
temp_flow_c, temp_return_c, temp_outdoor_c, temp_dhw_c, copHeat pump values
energy_kwh, energy_import_kwh, energy_export_kwhCounters in kWh
grid_limit_active1 while the grid operator limits controllable devices (§14a EnWG)

Protocols

You choose how a system is connected so the setup is documented. EnergyOS itself speaks MQTT; the gateway translates:

Equipment speaksGateway
Modbus TCP / SunSpec (inverters, batteries, meters)Home Assistant, evcc, Node-RED, or a vendor MQTT option
OCPP (EV chargers)evcc, or the charger's own MQTT interface
EEBUS, SG Ready (heat pumps)Home Assistant or the heat pump's gateway; SG Ready is two relay contacts
KNX, Matter / Thread, Zigbee / Z-Wave (sensors, switches, plugs)Home Assistant (KNX, Matter) or zigbee2mqtt, both publish to MQTT
Vendor cloud or HTTP APIA small script or Node-RED flow

EnergyOS does not talk to the equipment itself. If a gateway does not confirm a command, the page says no confirmation and the setting is not assumed.

Weather forecast

On the energy page, enter the location of your systems once (town, postcode or address). EnergyOS then loads the weather forecast for the next 48 hours: the MOSMIX forecast of the German weather service (Deutscher Wetterdienst, DWD) for the nearest forecast point, through the Bright Sky service: outdoor temperature, solar radiation and cloud cover, refreshed every hour. From it EnergyOS shows:

  • Coldest and warmest hour of the next 24 hours.
  • Expected PV yield: solar radiation × installed kWp of your PV systems × 80 % performance ratio. A simple estimate without roof tilt and orientation, good enough to tell a sunny day from a grey one.
  • Heating demand: degree hours below 15 °C outdoor temperature. More degree hours, more heat needed.
  • PV today, expected versus measured: the forecast energy since midnight next to the energy your PV systems reported. Clearly below the forecast (under 70 %) points to shading, soiling or a fault.
Weather forecast card for München with coldest and warmest hour, expected PV yield, heating demand and a 48-hour chart of temperature and solar radiation
The forecast card with the 48-hour chart.

The forecast also drives two rules under Automation (see below). Demo systems use München as their location; their PV readings are simulated, so the expected-versus-measured line is shown for real PV systems only.

Automation and prices

Under Automation you see the German day-ahead electricity price for the next hours: now, lowest, highest, and the cheapest 3-hour window. The price is the market price without taxes, grid fees and supplier margin: good for comparing hours, not a bill. It comes from aWATTar, with Energy-Charts as a fallback.

Day-ahead electricity price bar chart with the current, lowest and highest price and the cheapest three-hour window
The day-ahead price for the next hours.

Rules switch a control when a condition starts and set it back when it ends. A rule changes at most every 5 minutes. Available rules:

  • Use PV surplus for the heat pump: when the grid meter exports more than the threshold, set the heat pump to recommended on; back to normal afterwards.
  • Charge the car with PV surplus: allow charging while the surplus lasts.
  • Heat hot water when electricity is cheap: forced on while the market price is below the threshold (ct/kWh).
  • Pre-heat before a cold spell (weather forecast): when the lowest outdoor temperature forecast for the next 12 hours is at or below the threshold (°C), set the heat pump to recommended on, so the building stores heat before the cold arrives; back to normal afterwards.
  • Leave hot water to the sun when a sunny day is forecast: when the PV yield forecast for the next 24 hours reaches the threshold (kWh), lower the hot water target to 45 °C so the sun can heat it later; 55 °C otherwise. Needs at least one PV system with its kWp.
  • Grid operator limit (§14a EnWG): while the gateway reports grid_limit_active = 1, heat pumps and EV chargers are limited to 4.2 kW; the limit is lifted when the signal ends.
The Rules card with a rule type selector, a threshold field and an Add button
Add a rule: choose the type and the threshold.

Rules need data: a rule that cannot see the values it needs does nothing (a forecast rule without a location or forecast, for example). You can pause or delete any rule.

Heat pump subsidy calculator

The federal subsidy for a heat pump in Germany (BEG EM, paid by KfW and BAFA) is not part of the EnergyOS dashboard. It is a free calculator on qlines.net that needs no account and stores nothing: Heat Pump Subsidy Calculator for Germany.

For Germany only. The calculator uses the German federal programme and applies to buildings in Germany. Subsidies in other countries follow different rules.

The heat pump subsidy calculator for Germany: a notice that it is for Germany only, and a result with an 80 percent rate, 28,000 euro eligible costs and 22,400 euro maximum subsidy
The calculator shows the rate, the cap, the maximum subsidy and your own share.

You enter the building type, the application date, the heating you replace and its age, whether you live in the building, your household income and the planned costs (or the heat pump size for a cost estimate). You get the subsidy rate, how it is built from the base subsidy and the bonuses, the maximum subsidy, your own share and, if you add your fuel use, the yearly saving and the payback.

The result is an estimate with the published rules, not a notice of grant. KfW (private owners) or BAFA decide on the application.

Remote device management

Add a device to get its status, connection quality, network tests and remote commands. The Fleet dashboard shows all devices at a glance: how many there are compared with your plan, how many are online and offline, and how many alerts are open. Each card shows the status, when the device was last seen, CPU, memory and disk use, and the latest ping. Use the filter box and the sort menu to find a device.

The Fleet dashboard with counters for total, online, offline devices and alerts, and one card per device with CPU, RAM and disk
The Fleet dashboard.

Status and last seen

Device status A device is Never connected until its agent registers. It is Online while heartbeats arrive. After no heartbeat for 2 minutes it becomes Offline and an alert opens. The next heartbeat makes it Online again. Never connected Online Offline the agent registers no heartbeat for 2 minutes next heartbeat

An alert opens: it is counted on the bell and on the Fleet dashboard.

A device is Offline after two minutes without a heartbeat. The check runs every two minutes, so it can take a little longer to show.

Last seen says how long ago the device last reported, for example 5 min ago or 3 days ago, and updates by itself while the page is open. Hover over it to see the exact time in your time zone. Under a minute reads just now; after a day the text turns amber, so a forgotten device stands out.

The device page

  • Overview: live CPU, memory, disk and temperature, and the system details: device ID, host name, operating system, architecture, agent version, registration date, last seen and uptime.
  • Telemetry: charts of CPU, memory, disk and temperature for 1 hour, 6 hours, 24 hours or 7 days.
  • Commands: run a command on the device and see the result (see Remote commands).
  • Network tests: ping, download and upload speed, DNS lookup time and HTTP checks, on a schedule or on demand with Run test now.
  • Settings: name and notes, the heartbeat interval (15, 30 or 60 seconds), the telemetry interval (30 seconds to 15 minutes), the network test schedule and the enabled features. Save and Refresh Config send the new settings to the agent.
Device page, Overview tab: live CPU, RAM, disk and temperature and the system details of the device
The Overview tab of a device.
Device page, Telemetry tab: four charts for CPU, RAM, disk and temperature
The Telemetry tab: one chart per metric.
Device page, Network Tests tab: latest ping, speed and DNS values, trend charts and the test history
Network tests: latest result, trends and history.

Alerts

EnergyOS opens an alert when a value crosses its threshold. Open alerts are counted on the bell at the top right and on the Fleet dashboard. An alert closes by itself when the value is back to normal.

AlertOpens when
Device offlineNo heartbeat for 2 minutes
High CPUCPU above 90 %
High temperatureTemperature above 80 °C
High disk useDisk above 90 %
High latencyPing average above 200 ms in the latest network test
Packet lossAny packet loss in the latest network test

Alerts show in the app. E-mail notices are off by default; contact us if you want them for your account.

The agent: install and requirements

The EnergyOS agent is a small Python program for Linux devices (Raspberry Pi, mini PCs, servers). It keeps one outgoing MQTT connection to EnergyOS, reports the device's health and runs the network tests and commands you start from the page. It is not needed for connecting energy equipment; that is the gateway's job (see How EnergyOS fits together).

Requirements

WhatNeeded
Operating systemLinux. systemd is recommended to run it as a service. Raspberry Pi OS, Debian and Ubuntu are the usual choices; ARM and x86 both work.
PythonVersion 3.9 or newer
pipInstalled by the installer if it is missing (through apt, dnf, yum, pacman, apk or the official get-pip script)
Librariespaho-mqtt, psutil, PyYAML, speedtest-cli, requests and schedule. The installer fetches them.
RightsNone to install and run as your own user. sudo only for rc-agent install-service and, if you want it, to install pip.
NetworkOutbound only: HTTPS (port 443) to www.qlines.net for the install and for the one-time init, then MQTT over TLS (port 8883) to mqtt.qlines.net. pip also reaches PyPI. The clock must be right, or the TLS check fails.
For the network testsThe ping command, and outbound access to 8.8.8.8, google.com and cloudflare.com
SizeA light background process; a Raspberry Pi is plenty

Install

  1. In EnergyOS choose Add device, give it a name and register it. Copy the token; it is shown once.
  2. On the device run the installer with your token:
    curl -sSL https://www.qlines.net/install/rc-agent | bash -s -- --token tok_xxxxxxxx
  3. Start the agent:
    rc-agent start
  4. To keep it running after you log out and after a reboot, install it as a service:
    sudo rc-agent install-service
    sudo systemctl start remotecontrol-agent
The Register a new device form with a device name and notes
Register the device first. The token appears after you register it.
Installing the EnergyOS agent: five steps and where each one puts its files Register the device in EnergyOS, run the installer on the device, initialise with the token, start the agent as a program or service, and the device turns online. Each step lists what it creates on the device or on the server. 1 Register the device

Fleet dashboard, Add device. You get a token (shown once).

On the server

A device record, the token (stored hashed) and a broker login for this one device.

2 Run the installer

One command on the device: it checks for Python 3.9+, adds pip if missing and installs the agent.

On the device

The rc-agent command (in ~/.local/bin or /usr/local/bin), the Python package and 6 libraries.

3 Initialise

rc-agent init sends the token over HTTPS (443) and gets the device identity back.

On the device

config.yaml with the IDs, the token and the server address, in ~/.config/remotecontrol/ or /etc/remotecontrol/.

4 Start

rc-agent start runs it in the foreground; sudo rc-agent install-service makes it a service.

On the device

A systemd service, remotecontrol-agent, running as the user remotecontrol.

5 Online

The agent logs in to the broker, sends its details and then reports every 30 s.

On the server

Status Online, live telemetry, commands and network tests for this device.

Network needs

Outbound HTTPS (443) for the install and step 3, outbound MQTT over TLS (8883) from then on. Nothing inbound.

The installer works in five steps. The boxes show what each step creates and where.

On Debian 12 and Raspberry Pi OS the system Python is "externally managed". The installer then adds pip's --break-system-packages flag. If you prefer to keep the agent separate, create a virtual environment first (python3 -m venv ~/rc-agent-env), install the package into it with that environment's pip (https://www.qlines.net/install/remotecontrol-agent.tar.gz) and start ~/rc-agent-env/bin/rc-agent.

What is installed where

WhatWhere
rc-agent command~/.local/bin (user install) or /usr/local/bin (installed as root)
Python package and librariesThe site-packages folder of the Python the installer used
Settings (ID, token, server)~/.config/remotecontrol/config.yaml; as a service /etc/remotecontrol/config.yaml (readable by the service user only)
Service/etc/systemd/system/remotecontrol-agent.service, running as the system user remotecontrol (no login, no home folder)
Running-process marker/tmp/remotecontrol-agent.pid
LogThe terminal; as a service journalctl -u remotecontrol-agent

The settings file holds the device token in plain text. Protect it: chmod 600 ~/.config/remotecontrol/config.yaml. If a token leaks, use Regenerate Token in the device settings: the old one stops working.

What the agent and EnergyOS say to each other

All messages are small JSON documents on topics under rc/{account}/{device}/. The agent starts every conversation: it connects, subscribes to three topics (config, cmd/request, nettest/trigger) and publishes what it has. EnergyOS answers on the topics the agent listens to.

Messages between the agent, the broker, EnergyOS and you The agent connects to the broker, subscribes to its topics, registers and receives its configuration. It then sends a heartbeat every 30 seconds, telemetry every 60 seconds and network tests on a schedule. When you run a command, EnergyOS sends it to the agent, which runs it and sends the result back. Agent MQTT broker EnergyOS You Start connect: TLS + the device's own login subscribe: config, cmd/request, nettest/trigger register: agent version, host name, system config: intervals, features, network test schedule Then, all the time heartbeat every 30 s: "still here" telemetry every 60 s: CPU, memory, disk, temperature, uptime network test on schedule (default hourly), or when you ask When you run a command Run: the command text cmd/request (only if the device is online)

runs the program, as the agent's user

cmd/response: output, error text, exit code, duration result in the history
One connection, started by the agent. A command takes the same way back: EnergyOS asks, the agent runs it and answers.
Topic (under rc/{account}/{device}/)DirectionContent
registeragent → EnergyOSAgent version, host name, system, architecture, Python version
configEnergyOS → agentHeartbeat and telemetry interval, enabled features, network test schedule
heartbeatagent → EnergyOS"Still here", every 30 seconds by default
telemetry/systemagent → EnergyOSCPU, memory, disk, temperature, uptime, load; every 60 seconds by default
nettest/trigger and nettest/resultbothStart a network test now; its result (ping, DNS, HTTP checks, speed)
cmd/request and cmd/responsebothThe command to run; its output, error text, exit code and duration

Commands of the agent

CommandWhat it does
rc-agent init --token … --server mqtt.qlines.netChecks the token with EnergyOS and writes the settings file
rc-agent startRuns the agent in the foreground
rc-agent statusShows whether it runs and a summary of the settings
rc-agent test-nettestRuns one network test and prints the result
sudo rc-agent install-serviceCreates the service user, copies the settings to /etc/remotecontrol and installs and enables the systemd service

Remove the agent

  1. Stop and remove the service, if you installed it: sudo systemctl disable --now remotecontrol-agent and delete /etc/systemd/system/remotecontrol-agent.service.
  2. python3 -m pip uninstall remotecontrol-agent, and delete the settings folder.
  3. Delete the device in EnergyOS. This also removes its login at the broker.

Remote commands

On the Commands tab of a device you can run a command on the device and read the answer. Commands go through the agent, only while the device is online, and every command is logged with who sent it, when, the exit code and the duration.

Device page, Commands tab: quick command buttons, an input field and the history of commands with exit code, duration and status
The Commands tab: quick commands, the input field and the history.

How a command runs

The agent does not start a shell. It splits your text into words the way a shell would (quotes work) and starts the program directly, as the user the agent runs as. That is safer, and it explains why only some things work as typed.

How the agent runs a remote command The command text is split into words and the program is started directly, without a shell, as the user the agent runs as. The agent waits up to the timeout, collects the output and sends back the exit code, output and error text. Pipes and redirects need an explicit shell such as bash -c. Your commanddf -h /

typed on the device page

Split into words

like a shell would, so quotes work: ls "my dir"

Start the program

directly, no shell, as the user of the agent; no input (stdin closed)

Wait and collect

Up to 30 seconds; then the program and anything it started are stopped.

Result back

Exit code, output and error text (each up to 64,000 characters).

Works as it is uname -adf -h /systemctl status evcc/usr/bin/python3 /opt/x.py Needs a shell

Pipes, redirects, &&, wildcards, $VARIABLES, cd, export:

/bin/bash -c 'df -h | head -2'

One command, run by bash.

Environment

Same user, PATH and variables as the agent process. As a service that is a small, clean environment, not your login shell.

Use full paths when in doubt.

The agent runs the program itself. There is no shell in between, unless you ask for one.
You typeResult
df -h /, uname -a, uptimeWorks: a program and its arguments
df -h | head -2, a && b, ls > file, ls *.logDoes not work as written: pipes, &&, redirects and wildcards belong to a shell
cd /tmp, export X=1, echo $HOMEDoes not work: these are shell built-ins and variable expansions
/bin/bash -c 'df -h | head -2'Works: you ask for a shell yourself, and it runs the whole line
sudo rebootWorks only if the agent's user may run it without a password (see below)
A program that waits for input, or runs longer than 30 secondsStopped after 30 seconds, together with anything it started. The input is closed, so nothing can ask a question.
A very long outputCut at 64,000 characters per stream, with a note

In short: a command uses the agent's own user and environment. As a service that is the remotecontrol user with a minimal PATH and no login profile.

To use your own environment, run /bin/bash -lc '…' for a login shell, call programs by their full path (for example the venv/bin/python path), or add Environment= lines to the service.

Which environment a command sees

A command runs as the user that runs the agent, with the environment of the agent process: its PATH, its HOME, its working folder and its variables. It does not read .bashrc or .profile, because no login shell is involved.

  • Started by hand (rc-agent start): the environment of that terminal, including an activated virtual environment.
  • Started as a service (install-service): the system user remotecontrol with the minimal environment systemd gives a service (a short PATH such as /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin). It is not your login user, has no home folder and is not in the sudo group.

Using your own environment

You wantDo this
To see what the agent seesRun env and whoami as commands
Your login environment (.profile, PATH additions)/bin/bash -lc 'your command' (a login shell of the agent's user)
A program from a virtual environmentGive the full path: /home/pi/venv/bin/python /home/pi/check.py
Permanent variables for every commandAs a service: sudo systemctl edit remotecontrol-agent, add [Service] and Environment="NAME=value" (or EnvironmentFile=/etc/remotecontrol/env), then restart the service. By hand: set them before rc-agent start.
Commands as another userRun the agent as that user (edit User= in the service), or allow exactly the commands you need with a sudoers rule for the remotecontrol user
A restart of the deviceThe Reboot Agent button sends sudo reboot. Allow it with a sudoers file such as remotecontrol ALL=(root) NOPASSWD: /usr/sbin/reboot, /usr/bin/systemctl reboot

Everyone who can sign in to your EnergyOS account can run commands on every device in it. Give the agent's user only the rights it needs, never make it root for convenience, and protect the account with a strong password.

Security and privacy

  • Encrypted: all MQTT traffic uses TLS (port 8883), and the agent checks the server's certificate. The website and the agent's one-time token check use HTTPS.
  • One login per device: the device ID is the user name and the token the password. A device can only publish and listen on its own topics, so one device cannot read or control another.
  • No inbound connections: equipment stays behind your router. The gateway and the agent connect outwards.
  • Tokens: stored hashed at EnergyOS. A lost or leaked token is replaced with Regenerate Token in the device settings (the agent disconnects until it is set up again); deleting a device removes its login at once.
  • Private by account: energy systems, readings, devices and commands belong to your account only.
  • Weather and place search: only the location text you type, and the coordinates found from it, are sent to the weather and place services; no account data.
  • Backups: data is backed up every night. Deleted data leaves the backups as they roll over, within six months.

Account, plans and limits

Under Settings you see your plan and how much of it you use (devices and today's messages), change your password and e-mail address, compare plans and, if you wish, delete your account.

The Settings page with the account overview, change password, change e-mail address, plans and delete account
Settings: plan usage, password, e-mail address, plans and account deletion.
WhatLimit
Devices, messages per device per day, data retentionDepend on your plan; see Pricing and the plan cards in Settings
Energy systems per account30
Automation rules per account20
Energy readings1 per system per 10 s, kept 90 days; commands kept 180 days

Data is backed up every night.

Questions and troubleshooting

I forgot my password. What now?

On the sign-in page choose Forgot password? and enter your e-mail address. The link in the e-mail is valid for one hour and works once. Signed in, you change the password under Settings → Change password. A new password signs you out on all other devices.

How do I change my e-mail address?

Under Settings → Change e-mail address, with your current password. We send a link to the new address; once you click it (within 24 hours), you sign in with the new address and all mail goes there. The old address gets a notice. Devices, systems and data stay as they are, installed agents need no change.

How do I delete my account?

Under Settings → Delete account, with your current password. Everything is deleted right away: devices are disconnected and removed, together with energy systems, readings, rules, settings and the activity log. Copies in our backups are deleted as the backups roll over, within six months. Your UtilityControl account, if you have one, is separate.

The installer says "Python 3.9+ not found".

Install a current Python 3 (sudo apt install python3 python3-pip on Debian-based systems) and run the installer again.

The agent starts but the device stays "Never connected" or "Offline".

  • Check the log (journalctl -u remotecontrol-agent -f or the terminal). "MQTT connect refused" means the token does not match this device: use Regenerate Token in the device settings and run rc-agent init again with the new token.
  • Check that the device can reach mqtt.qlines.net on port 8883 (outbound), and that its clock is correct.
  • Some company networks block port 8883; ask the network owner to allow it outbound.

A command says "Executable not found".

The program is not in the agent's PATH. Use its full path, or see Using your own environment.

A control says "no confirmation".

The gateway did not answer in time. Check that it runs and listens on the …/set topic of that system, and that it publishes on …/ack. EnergyOS does not assume the setting worked.

Is the subsidy calculator result binding?

No. It is a calculation with the published rules. The grant decision is made by KfW or BAFA.

The subsidy rules changed. What now?

The rules are stored as data and updated by us; the result page shows the date they were last checked.

Need a feature or a plan upgrade?

Contact us.