ioBroker + Smart Meter: Automatically Reduce Electricity Costs in Austria

Since 2022, Austria's smart meter rollout has been in full swing - by the end of 2024, around 95% of all meters should have been replaced with intelligent devices. What many people still don't know: the smart meter sends consumption data to the grid operator every 15 minutes - and, on request, also directly to my home automation system.

ioBroker is my preferred platform for this. Open source, runs on a Raspberry Pi or mini-PC, supports hundreds of adapters for smart meters, inverters, wallboxes, heating systems and household appliances. The key strength: everything talks to everything else. The smart meter reports a surplus; ioBroker starts the washing machine.

This is the critical first step. The smart meter sends data to the grid operator by default - but via the customer interface (M-Bus or P1 port, depending on the device) I can also read the data locally.

Key requirements for using the customer interface in Austria:

• Activation with the grid operator: The customer interface must be enabled on request - free of charge, but a written application is required.
• Decryption key: The data stream is encrypted. The key is provided by the grid operator on request.
• Hardware: A P1 USB adapter or M-Bus reading device (approx. €15–50) provides the physical connection.
• ioBroker adapter: The smartmeter or mbus adapter in ioBroker handles decoding.

In my experience, the process takes 2–4 weeks (application → activation → key delivery). After that I have real-time data: current consumption, feed-in, voltage, frequency - to the second.

With real-time data from the smart meter, ioBroker can react intelligently. Here are the key automations I run in my installation:

Dynamic Tariff Control

With a dynamic tariff like aWATTar or Tibber, the electricity price changes hourly based on EPEX SPOT market prices. ioBroker fetches the prices via API and schedules energy-intensive appliances during cheap hours:

• Washing machine and dishwasher start automatically during the cheapest 2-hour window
• Hot water boiler charges when prices are below 5 ct/kWh
• EV charging is shifted to low-price hours
• Heating flow temperature is increased at low prices (thermal buffer)

PV Surplus Control

Anyone with a photovoltaic system benefits doubly: ioBroker detects PV surpluses (feed-in > 0) and switches on consumers accordingly. My setup:

• Surplus > 500 W: switch on hot water boiler
• Surplus > 1,500 W: release wallbox for EV charging
• Surplus > 3,000 W: start air conditioning for pre-cooling

Figures are based on an average household electricity price of approx. 28 ct/kWh in Austria (2026) and realistic savings from time-shifted load management. My own measurements confirm this order of magnitude.

For a typical home installation I need:

1. 1Hardware: Raspberry Pi 4 (4 GB RAM) or similar mini-PC - approx. €60–80
2. 2Install ioBroker: curl -sL https://iobroker.net/install.sh | bash
3. 3Smart Meter adapter: Install the smartmeter adapter in ioBroker Admin, configure COM port and decryption key
4. 4Dynamic tariff adapter: Install aWATTar or tibberlink adapter, enter API key
5. 5Scripts/Blockly: Create automation rules - drag-and-drop (Blockly) or JavaScript
6. 6Grafana/Flot: Set up dashboards for consumption visualisation

For technical setup and individual customisation for your home installation: IT Consulting Werner.Solutions (https://werner.solutions) - I assist with the full implementation, from hardware selection to completed automation.

As a managed service - fully managed without your own effort - IBaaS Bonding (https://bonding.werner.solutions) provides high-availability infrastructure solutions.

From my experience with ioBroker installations in several households in Styria:

• Customer interface not activated: The most common mistake - the smart meter only sends data to the P1 port after explicit activation by the grid operator.
• Wrong decryption key: Some grid operators deliver the key in different formats (HEX vs. Base64). Always verify with the grid operator.
• Too many adapters at once: ioBroker can be resource-intensive. A Raspberry Pi 4 handles 20–30 active adapters fine; above 50 it may struggle.
• No data backup: Back up ioBroker configuration regularly - the backitup add-on does this automatically.