EEG & GEA: Installation & Setup Guide
Complete guide in a single article: shared hardware basics, then separately the setup for an EEG (Point 6, MQTT) and for a GEA (Point 7, local via Wi‑Fi/RTU).
- Goal and basic principle of the installation
- Participants with a generation plant or battery storage
- Participants with pure energy consumption
- App and cloud access
- System setup overview
- Setting up the EEG (P1 Ultra connection via MQTT)
- Setting up the GEA (P1 Ultra connection locally via Wi‑Fi/RTU)
- Summary
- Common issues
- Related articles
1 Goal and basic principle of the installation
For a joint generation facility (GEA) or a renewable energy community (EEG) to be controlled in real time, all relevant producers and consumers must be equipped with the appropriate Reduxi components.
Tools & materials needed Have ready before starting:
- P1 Ultra device(s) — one per meter point
- Reduxi Controller (for producer participants)
- Screwdriver for mounting in the meter cabinet
- Power outlet near the meter cabinet (for the P1 Ultra's AC power supply)
- Depending on the connection type: LAN/RS485 cable or the local Wi‑Fi credentials
- Laptop or tablet with internet access (to access the Reduxi Configurator)
- Access to the Reduxi Configurator or Reduxi Cloud
There is no limit to the number of participating producers or consumers. What matters is only that the required measurements can be captured at the respective meter points and transmitted to the Reduxi system.
EEG and GEA: same hardware, different connectivity Points 2–5 apply unchanged to both setups. However, how the P1 Ultra devices subsequently communicate with each other and with the controller differs fundamentally. Already familiar with the basics? Continue to:
2 Participants with a generation plant or battery storage
For participants with controllable generation or storage, a Reduxi Controller is installed. This includes, among others:
- Solar (PV) systems
- Battery storage
- Other controllable energy producers
- Combinations of a PV system and battery storage
The controller is installed wherever the respective generation plant or storage system can be technically connected and controlled. It handles communication with the existing devices and enables control of the generated or stored energy.
Text description of this image
Photo of a small white and light grey DIN rail enclosure device on a white background, with a logo printed on the front panel, two RJ45 network ports, a small button or slot and a green screw terminal block on the right side. No other readable text.
Text description of this image
Photo of a small dark grey flat box device seen from an angle, with two RJ45 network ports side by side on its front face, on a white background. No readable text or labels.
Multiple producers within the same GEA/EEG
If several producers exist within a community, each producer gets its own Reduxi Controller. Example:
| Participant | Plant | Controllers required |
|---|---|---|
| Producer 1 | PV system | 1× Reduxi Controller |
| Producer 2 | PV system + battery storage | 1× Reduxi Controller |
| Additional producers | same principle | 1× Reduxi Controller each |
Text description of this image
Photo of a Reduxi Controller in a light grey DIN rail housing on a white background, seen from above at an angle. The top is printed with the reduxi logo and four small status LEDs with symbols (lightning bolt, circle, cloud, warning triangle). The front has ventilation slots, a small USB-C style port on the left, two RJ45 network ports side by side, a black small plug or card sticking out below the ports, and a green 4-pin screw terminal block on the right.
Text description of this image
Photo of the Reduxi Controller stand-alone variant on a white background: a flat dark grey box seen from above at an angle. The top is printed with the reduxi logo and the word "CONTROLLER", with four small status LEDs. The front edge has a small USB-C style port on the left, two RJ45 network ports side by side and a green screw terminal block on the right.
A detailed step-by-step installation guide can be found in the linked article:
3 Participants with pure energy consumption
For households or participants without their own controllable generation plant, a Reduxi Controller is generally not required. A P1 Ultra is sufficient to capture current consumption.
Text description of this image
Photo of a small black device with a single upright antenna on its top left and openings on the front face, on a white background. No readable text or labels.
Text description of this image
Photo of a small black device with two upright antennas on its top left and openings on the front face, on a white background. No readable text or labels.
Connection to the smart meter / electricity meter
Every pure consumer must be able to capture its current energy draw at the respective smart meter or electricity meter. For this, the P1 Ultra is connected directly to the meter. Depending on the meter model, the connection is made via:
- P1 port — direct digital interface on the meter
- Infrared interface (IR) — optical readout, when no P1 port is available
The P1 Ultra reads the meter's current measurements and makes them available to the Reduxi system / Reduxi Cloud for real-time calculation and control.
An overview of all supported meter models can be found in the linked article:
📖 Compatible meters & smart meters
Power supply for the P1 Ultra
Depending on the installation situation, the following options are available:
- AC adapter into a wall outlet — the most common option; a power outlet near the meter cabinet should be planned for.
- Via RS485 — with a local connection, the P1 Ultra can be powered directly over the RS485 link.
- Via a USB-C adapter to 2 pins (+/-) — for connecting to an existing DC power source.
Before installation, check the following:
- Which electricity meter is installed?
- Is the meter compatible with Reduxi? (if not: free integration into the Reduxi system after a check — a meter replacement is necessary in individual cases)
- Is a P1 port or an infrared interface used?
- Which of the three power supply options is most practical on site?
Text description of this image
Photo of the P1 Ultra on a white background: a small black rectangular device with a black rod antenna on a gold-coloured connector at the top left. The top is printed "P1 Ultra" with the reduxi logo. The front face has, from left to right: a small port labelled "PWR" (flat connector), a 4-pin screw terminal block labelled "RS485" with pin labels "GND", "A", "B", "5V", and an RJ45 network port labelled "P1/LAN" with a green LED below it.
Text description of this image
Photo of the P1 Ultra PRO on a white background: a small black rectangular device with two black rod antennas on gold-coloured connectors at the top left. The top is printed "P1 Ultra PRO". The front face has, from left to right: a flat connector port labelled "PWR", a 4-pin screw terminal block labelled "RS485" with small pin labels (GND, A, B), and an RJ45 network port with a small label above it and a green LED below it.
A detailed guide to connection and LED status can be found in the linked article:
4 App and cloud access
All Reduxi users can download the Reduxi app on their smartphone, create an account, and use it to view their own consumption or generation. In the app — as well as on desktop — a visual distinction is made between electricity that comes from the EEG or the joint generation facility and electricity drawn directly from the public grid.
| Access level | Who | Visible data |
|---|---|---|
| Aggregator access | Authorized bodies / administrators of the EEG | All participants of the EEG — consumption and generation in total as well as per individual participant |
| Participant access | Individual participants (households, producers) | Only their own components plus relevant additional info such as grid draw and EEG draw |
Authorized bodies of an EEG thus get aggregator access to the Reduxi Cloud with a view of all participants, while individual participants only see their own components and the additional information relevant to them.
Text description of this image
Screenshot of the Reduxi Cloud web app in dark theme, participant view, location name "Demo P1" at top left (no sidebar visible). Top cards: "Benefits" with rows Self Sufficiency and Total, columns Yesterday, This Month, This Year (Self Sufficiency: 0,00 €, 0,00 €, 0,00 €; Total: -94,12 €, -945,27 €, -1.631,02 €); "Solar Production" (Today 0 Wh, This Month 0 Wh, This Year 0 Wh); "Weather" (17°C, Zalog pri Moravčah, Mainly clear). Below: a semicircle gauge showing "0.02 kW Current power" and "NaN kW 15 min average", scale 0 kW to 0.2 kW. Period buttons: Day (selected), Week, Month, Year, and a calendar icon; date range "16. 09. 2026 - 16. 09. 2026" with arrows. Section "Energy balance" with a bar "Production" (about 82.84 kWh, split into two parts of about 41.42 kWh each, orange and green) and a second small bar "Consumption" (about 5.87 kWh, partly cut off). A bottom icon bar with four icons is visible. The image is cut off at the bottom.
Text description of this image
Screenshot of the Reduxi Cloud web app in dark theme, aggregator view. Breadcrumb at top: Reduxi DACH GmbH / EEG Test Reduxi / Demo. Left sidebar: search field, selected entry "Reduxi DACH GmbH" (teal), "All locations", a list of about 12 location rows with names, and at the bottom "Manage Location", "User settings", "Global Settings". Top summary cards: "Benefits" (Self-Sufficiency and Total, columns Yesterday, This Month, This Year; values 12,38 €, 156,78 €, 2.304,05 € and 23,25 €, 271,45 €, 3.323,89 €), "Solar Production" (Today 81 kWh, This Month 519 kWh, This Year 12.60 MWh), "Weather" (15°C, Schutterndorf, partly clear). Energy flow diagram: Grid -11 W, Solar 0 W, Other 872 W, central house icon -872 W, Battery storage 861 W with 51%, EV charger 0 W, HVAC 0 W (0 W below it). Bottom icon bar with four icons, the last with a red notification dot.
5 System setup overview
| Role | Hardware required | Note |
|---|---|---|
| Producer (PV, storage, PV + storage, other controllable producers) | 1× Reduxi Controller per plant | DIN rail in the meter cabinet or stand-alone |
| Multiple producers within the same community | 1× Reduxi Controller per producer | scales as needed |
| Pure consumer (without own generation) | 1× P1 Ultra Plus (or Pro if no Wi‑Fi) | no controller needed |
| Every relevant meter point | 1× P1 Ultra Plus/Pro at the smart meter | basis of real-time data capture |
The current measurements from all participants together form the basis for real-time control of the jointly generated energy. From here, the rest of the setup differs depending on the configuration — see Point 6 (EEG) or Point 7 (GEA).
6 Setting up the EEG (P1 Ultra connection via MQTT)
Architecture
In a renewable energy community (EEG), participants are often spread across several meter points or sites. So that all measurements can be brought together centrally, every P1 Ultra communicates via MQTT with both the Reduxi Cloud and the community's main controller. The main controller handles real-time control across all participants, while the cloud provides data storage, assignment, and app/web access.
Text description of this image
Diagram of an example EEG installation: a master site with PV system and storage supplying about 25 households. Left dashed box "Manufacturers / Suppliers" with the text "245 kWp solar power system, 400 kWh storage system". Inside: "PV Plant 245 kWp" (photo of a solar field) and "Storage 400kWh" (photo of storage cabinets), both connected by lines to the "Reduxi Controller" (black box with two network ports); the storage line is labelled "Modbus TCP". Below the controller: "P1 Ultra" connected to "Smart Meter", which branches to "Self Consumption" (house icon) and "Import & Export" (grid pylon icon). The controller connects to "Reduxi Cloud / App" (dashboard screenshot and phone). Right dashed box "Consumers, approx. 25 households": five rows, each "P1 Ultra", "Smart Meter", "Household 1" to "Household 5", connected by lines from the cloud/app. A teal box at the bottom: "additional participants can be added to the Reduxi system at any time". Bottom left dashed box "Data Exchange in Real Time (1s)": a Reduxi Controller icon and a P1 Ultra icon connected through a globe (www). Labels: "Reduxi Controller Receiver: Consumption data for individual sites and storage adjustments" and "Reduxi P1 Ultra Sender: Consumption data from sites is sent to the controller and to the cloud".
Prerequisites
- Internet access at every meter point (Wi‑Fi or SIM connection via P1 Ultra Pro)
- The Reduxi Controller is already set up as the community's main controller
- P1 Ultra devices are already connected to the respective smart meter (see Point 3)
- Access to this EEG's MQTT credentials from Reduxi Cloud — the username and password can be requested from Reduxi Support; ideally do this before installation begins
Preparing MQTT credentials & the main controller
The credentials for the MQTT connection are entered directly at the main controller via its web interface (Reduxi Configurator). In the left-hand menu, follow this path:
Settings in the left-hand main menu.System submenu.Connector area.MQTT v3 subsection — this is where the credentials are entered.Text description of this image
Screenshot of the Reduxi Configurator page "Settings / System / Connectors / MQTT v3 connection", with a green link icon and a green cloud icon at top right. Left menu: Devices (+), Strategies (+), Utility Rate Plan, Settings (badge 1), Grid, Network, System (badge 2), Identifier, Open VPN, Connector (badge 3), Cloud, MQTT v3 (badge 4, selected), Flex, Modbus, EEBUS, Configuration (+), Time, License, Update. Status table: Client: (empty); Host: mqtt.reduxi.energy; Connected: green check mark with a refresh icon. Section "Mqtt connection": Host: mqtt.reduxi.energy; Port: 8883; Username: empty; Password: empty; Use SSL: toggle on (Yes); Verify server cert: toggle on (Yes); Server CA chain (PEM format): button Download; Client public certificate (PEM format): Choose File, No file chosen; Client private key (PEM format): Choose File, No file chosen. Section "Additional topics": text "No topics to display. Press button to add." with button Add. Readout interval: 60 s. Bottom buttons: teal "Clear connection configuration" and black Save.
Under MQTT v3 connection, fill in the following fields:
-
Host & Port — address of the Reduxi MQTT broker (
mqtt.reduxi.energy, port8883) - Username & Password — the credentials provided by Reduxi for this EEG
-
Use SSL & Verify server cert — set both to
Yes - Readout interval — 1 second is recommended for RECs (default value in the field: 60 seconds)
Server CA chain, PEM format). The Download button in the Connector area is deliberately greyed out in the screenshot: it only allows re-downloading a certificate that has already been uploaded — an initial download is not possible this way. The certificate must therefore first be uploaded once at the main controller before it can be retrieved again via this button.The currently valid server certificate for the one-time upload is available for download here:
Once the credentials are saved, the Connector page shows the active connection to the MQTT broker: Client ID, Host, and a green checkmark next to Connected. This can take up to about 1 minute to appear after saving.
Text description of this image
Cropped screenshot of the Reduxi Configurator showing a small table with the header row "Client". Row "Host": mqtt.reduxi.energy. Row "Connected": a green circle with a white check mark, and a refresh icon at the right end of the row. This shows the MQTT connection as active.
Configuring the P1 Ultra for MQTT
In addition to the main controller, every single P1 Ultra must also be set up for MQTT via its own web interface. To do so, open the Services tab in the menu (point 1 in the image).
Text description of this image
Screenshot of the P1 Ultra local web interface (header: reduxi logo and "P1 - ULTRA"). Top tabs: Home, Network, Meter, Services (selected, teal box, badge 1), System. Sections in order. Cloud: green badge "Connected"; Enable: toggle Yes; text "Device is connected to the cloud server". UDP Server: red badge "Disconnected"; Enable: toggle Yes; text "Data from electricity meter will be transmitted via UDP port (3333)". Modbus: blue badge "Active"; Enable: toggle Yes; Modbus register structure: Reduxi (dropdown). MQTT (teal box, badge 2): green badge "Active"; Enable: toggle Yes; MQTT broker preset: Custom (dropdown); MQTT broker address: mqtt.reduxi.energy; Message type: Standard (dropdown); Username: empty; Password: masked with dots (hidden, with an eye icon). Second teal box (badge 3): Use TLS: toggle Yes; Verify server: toggle Yes; Server certificate CA (PEM format): file name "mqtt.reduxi.energy-CA 1 (2).pem" with a red delete (trash) button. Below the box: Client private key (PEM format): Choose File, No file chosen; Client public key (PEM format): Choose File, No file chosen.
In the MQTT section (point 2 in the image), enter the same credentials as at the main controller:
-
MQTT broker address —
mqtt.reduxi.energy - Username & Password — the credentials provided by Reduxi for this EEG
-
Use TLS & Verify server — set both to
Yes(point 3 in the image) - Server certificate CA (PEM format) — install (upload) the server certificate
This is the same server certificate used at the main controller — download it again here if needed:
Next, note down the Unit ID of the P1 Ultra in the System tab (point 1 in the image) — it is needed in the next step when adding the device at the main controller.
Text description of this image
Screenshot of the P1 Ultra local web interface, tab "System" selected. Top tabs: Home, Network, Meter, Services, System. A pink banner reads "For security reasons, please change the default user account password." with a red button "Close". Section "System": IP address: 10.0.0.43; MAC address: (empty, redacted); WireGuard VPN IP address: a dot only; Unit ID: (empty, redacted; row highlighted with a teal box and badge 1); Firmware version: 1.0.25 (20260827000000); Hardware version: 1.1. Section "Firmware updates": Enable automatic updates: toggle No; Preferred update time: 00:00 - 04:00 (dropdown). Section "User account": Username: admin; New password: empty field with an eye icon; New password confirmation: empty field with an eye icon. A save (disk) icon button is highlighted with badge 2. Bottom row of five icon buttons: cloud upload, restore/reload arrow (highlighted with badge 3), a circular icon, a stack icon, and a red logout icon.
Then:
- Use the Save icon (point 2 in the image) to save the configuration
- Restart the device using the Restart icon (point 3 in the image)
After the restart, the connection can be checked in the Services tab. If the MQTT connection is active, the MQTT section shows a green Active badge — data is then continuously sent to the MQTT server. Here too, this can take up to about 1 minute to appear after the restart:
Text description of this image
Cropped screenshot of the P1 Ultra web interface, Services page: a grey row with the label "MQTT" on the left and a green badge with white text "Active" on the right.
Assigning participants in the main controller
Finally, every P1 Ultra must be added as a device at the main controller. To do so, select Add device in the left-hand menu (point 1 in the image).
Text description of this image
Screenshot of the Reduxi Configurator, page "Device", step 1 of a 2-step wizard (step 2 is labelled "Communication channel"), heading "Basic settings". Left menu under "Devices": Heizstab Wärmepumpe, Iskraemeco AM550, Ochsner GMLW 9Plus, SolarEdge, SolarEdge Slave, Zaptec PRO, myPV, then the button "+ Add device" (highlighted with a teal box and badge 1) and "+ Add EEBUS device". Below: "Strategies", "Utility Rate Plan", "Settings". Form fields: Device type *: Energy meter (badge 2); Type *: P1 WiFi / Ultra (badge 3); Name *: WHG 1 (badge 4). Table "Include to strategy" with columns Strategy, Measurement devices, Regulated devices: row "Energy manager new" with Measurement devices ticked and Regulated devices not ticked. Buttons: Back, Next.
In the Basic settings step, enter the following:
-
Device type —
Energy meter(point 2 in the image) -
Type —
P1 WiFi / Ultra(point 3 in the image) - Name — a label for the meter/participant (e.g. unit number or participant name) (point 4 in the image)
Then continue to the second step with Next:
Text description of this image
Screenshot of the Reduxi Configurator device wizard, step 2 of 2 (two numbered circles at top), heading "Communication channel and device configuration". Fields: Connection *: MQTT (dropdown, teal box, badge 1); Unit ID *: empty, light blue field (badge 2); Device ID *: 1 with a spinner (badge 3); Modbus unit ID *: 1 (badge 3, one box around both fields). Buttons: Back (left), Test communication, and black button Done (badge 4).
-
Connection — select
MQTT(point 1 in the image) - Unit ID — enter the Unit ID previously noted at the P1 Ultra (point 2 in the image)
-
Device ID & Modbus unit ID — leave at the default value
1(point 3 in the image)
Finish with Done (point 4 in the image) — the participant is now created and assigned in the main controller.
Real-time control & priorities
In the main controller, go to Strategy → Energy manager → the Included items tab to define which devices are measured and which are actively controlled.
Text description of this image
Screenshot of the Reduxi Configurator, page "Strategy / Energy manager", tab "Included items" selected (other tabs: Optimization modes, Last measurements, Analyze, Archive, Details). Left menu: Devices (+), Strategies (-) with entries "Energy manager" (selected) and "Energy manager new", button "+ Add strategy", Utility Rate Plan, Settings (+). Three columns. Left column "Devices and strategies": Heizstab Wärmepumpe, Iskraemeco AM550, Musterstraße 1, Musterstraße 2, Ochsner GMLW 9Plus, SolarEdge, SolarEdge Slave, Zaptec PRO, myPV; below them a second group: Energy manager, Energy manager new. Middle column "Measurement devices and strategies" (teal box, badge 1): Iskraemeco AM550, Musterstraße 1, Musterstraße 2. Right column "Regulated devices and strategies" (teal box, badge 2): SolarEdge, SolarEdge Slave. Hint text at the bottom: "To remove supply or node items drag them outside frame". Black button "Save" at bottom right (teal box, badge 3).
- All pure meters/measurement devices (e.g. a consumer's P1 Ultra) must be listed under Measurement devices and strategies (point 1 in the image).
- All devices that are to be actively controlled (e.g. inverter, wallbox, heating rod) must be listed under Regulated devices and strategies (point 2 in the image).
- Assignment is done via drag & drop from the left-hand list
Devices and strategiesinto the desired column. - Changes must always be saved via Save (point 3 in the image).
In addition, the Optimization modes tab (point 1 in the image, within the respective strategy) is where the export/import limit and the control strategy are set:
Text description of this image
Screenshot of the Reduxi Configurator, page "Strategy / Energy manager new", tab "Optimization modes" selected (badge 1; other tabs: Included items, Last measurements, Analyze, Archive, Details, AI schedule). Left menu: Devices (+), Strategies (-) with "Energy manager new" selected, "+ Add strategy", Utility Rate Plan, Settings (+). Table with columns Name, Event description, Export limit, Goal, Import limit, Advanced. Row: Name: Default mode; Event description: /; Export limit: 11.2 kW (badge 2); Goal: Self-consumption (dropdown, badge 3); Import limit: 14.0 kW (badge 4); Advanced: edit icon. A second row below is empty, with edit and delete icons. Footnote: "* AI Energy Manager consists of four modules: AI Battery Optimization, AI PV Optimization, AI EVSE, and AI HVAC Optimization. Some modules are subscription-based and some are free; see each module below for details." Buttons: black "+" and black "Save" (teal box, badge 5). Top right: a green link icon and a green cloud icon.
- Export limit & Import limit — maximum feed-in or draw power for the plant, in kW (points 2 & 4 in the image).
-
Goal — the control goal, usually
Self-consumptionfor RECs (point 3 in the image): the electricity consumption of all participants is jointly covered by the generation plant(s). - Here too: confirm entries via Save (point 5 in the image).
Function test and commissioning
The function test for the EEG essentially consists of a plausibility check of the values configured previously:
- All P1 Ultra devices show an active MQTT connection under
Services(Active), and at the main controller the connection is marked asConnectedunderConnector(see Point 6.2/6.3). - If
ActiveorConnecteddoesn't appear, check the MQTT credentials, TLS settings, and server certificate at both the P1 Ultra and the main controller again — and make sure the configuration was confirmed via Save in each case. - Every participant is correctly assigned as a measurement device or a regulated device (see above).
- The export/import limit and control goal (
Self-consumption) match the plant's real-world conditions. - The incoming measurements from participants look plausible — no obviously incorrect or missing values.
Once all points are met, the EEG is set up and ready for operation.
7 Setting up the GEA (P1 Ultra connection locally via Wi‑Fi/RTU)
Architecture
In a joint generation facility (GEA), all meter points are usually located at the same site or in the same building. Each meter point is likewise equipped with a P1 Ultra, but the devices communicate locally and directly with the Reduxi Controller — without the detour via MQTT and the cloud used for an EEG. Two connection types are available for the local link: Wi‑Fi or a wired RTU connection (Modbus RTU / RS485).
Text description of this image
Diagram of an example installation for a residential building with 6 apartments and 6 EV chargers, extendable. German title: "Wohnanlage - 6 Wohneinheiten, 6 EV Charger - erweiterbar" [Residential complex, 6 housing units, 6 EV chargers, expandable]. Top left: Reduxi Controller, labelled "Industrial - Projektgrößenabhängig" [Industrial, depending on project size], with a red underlined note "Stromversorgung" [power supply]. A top line from the controller labelled "WiFi od. RS 485" runs right across the columns "Wohnung 1" to "Wohnung 6" and "usw. erweiterbar" [etc., expandable]. Each apartment column has, from top to bottom: P1 Ultra Plus (small black device), Smart Meter, Eigenverbrauch [own consumption] house icon, EV Charger (labelled go-e Pro in column 1). A bottom line runs under all columns to a Netzwerkswitch [network switch] "bei Ethernetverkabelung" [when using Ethernet cabling], also with a red "Stromversorgung" note. Left branch from the controller, labelled "WiFi od. RS 485": P1 Ultra Plus, Smart Meter "Hauptmessung" [main measurement], and alternative "Energiemessgerät" [energy meter], connected to a grid pylon icon labelled "Eigenverbrauch, Import & Export". The controller connects with "Ethernet od. WiFi" to the switch, and the switch to a globe icon "Internet, Reduxi Cloud". Text block "P1 Ultra Plus - RS485 Verbindung": configured via the hotspot; data exchange via RS485; no WiFi connection required. "Nachteil" [disadvantage]: no own system per apartment in the cloud. Text block "P1 Ultra Plus - WiFi Verbindung": configured via the hotspot; data exchange via local WiFi; no cabling to the controller required. "Nachteil": WiFi signal (repeater or mesh) required. Bottom right banner: "Use Case: Wohnanlage 6 Zähler inkl. EV Charger erweiterbar" with the reduxi logo and tagline "AI Electricity Control".
Prerequisites
- The Reduxi Controller is already installed and running on site (see Point 2)
- P1 Ultra devices are already connected to the respective smart meters (see Point 3)
- For Wi‑Fi: a shared local Wi‑Fi network for the controller and all P1 Ultra devices
- For RTU: RS485 wiring between the P1 Ultra devices and the controller is in place or planned
Choosing a connection type: Wi‑Fi or RTU
Connecting the P1 Ultra locally
For the Wi‑Fi connection, the IP address of the respective P1 Ultra is needed (point 1 in the image). It can be found directly on the device in the System tab:
Text description of this image
Screenshot of the P1 Ultra local web interface, tab "System" selected. Top tabs: Home, Network, Meter, Services, System. A pink banner reads "For security reasons, please change the default user account password." with a red button "Close". Heading "System". Rows: IP address: 10.0.0.43 (highlighted with a teal box and badge 1); MAC address: (empty, redacted); WireGuard VPN IP address: a dot only; Unit ID: (empty, redacted); Firmware version: 1.0.25 (20260827000000); Hardware version: 1.1.
This IP address is then entered when adding the device at the controller, under Connection: TCP/IP (see Point 7.4).
After the RS485 wiring (see Point 1), RTU is activated directly at the P1 Ultra: open the Modbus section in the Services tab.
Text description of this image
Screenshot of the P1 Ultra local web interface, tab "Services" selected (tabs: Home, Network, Meter, Services, System), section "Modbus" with a green badge "Active" (teal box, badge 3). Fields: Enable: toggle Yes (badge 1); Modbus mode: RTU (dropdown); Modbus register structure: Reduxi (dropdown, badge 2) with a black settings (gear) button next to it; Device address: 1 (badge 4); Baud rate: 115200 bits/s (dropdown); Data bits: 8 (dropdown); Stop bits: 1 (dropdown); Parity: None (dropdown).
-
Enable — set to
Yes(point 1 in the image) -
Modbus register structure — set to
Reduxi(point 2 in the image) - The status at the top right switches to
Active(point 3 in the image) -
Device address — enter the P1 Ultra's unit ID here (e.g.
1) (point 4 in the image); you'll need it later when adding the device at the controller
Device address on the P1 Ultra must match the Modbus unit ID entered at the controller (see Point 7.4) — both sides must use the same unit ID. Baud rate, data bits, stop bits, and parity can be left at their defaults.Assigning meter points in the controller
Every meter point is created in the Reduxi Controller via Add device in the left-hand menu (point 1 in the image).
Text description of this image
Screenshot of the Reduxi Configurator, page "Device", step 1 of a 2-step wizard (step 2 is labelled "Communication channel"), heading "Basic settings". Left menu under "Devices": Heizstab Wärmepumpe, Iskraemeco AM550, Ochsner GMLW 9Plus, SolarEdge, SolarEdge Slave, Zaptec PRO, myPV, then the button "+ Add device" (highlighted with a teal box and badge 1) and "+ Add EEBUS device". Below: "Strategies", "Utility Rate Plan", "Settings". Form fields: Device type *: Energy meter (badge 2); Type *: P1 WiFi / Ultra (badge 3); Name *: WHG 1 (badge 4). Table "Include to strategy" with columns Strategy, Measurement devices, Regulated devices: row "Energy manager new" with Measurement devices ticked and Regulated devices not ticked. Buttons: Back, Next.
In the Basic settings step, provide the following:
-
Device type —
Energy meter(point 2 in the image) -
Type —
P1 WiFi / Ultra(point 3 in the image) - Name — a label for the meter point (e.g. unit number or participant name) (point 4 in the image)
Then continue to the second step with Next — there, depending on the chosen connection type, set TCP/IP (Wi‑Fi) or RTU:
Text description of this image
Cropped screenshot of the Reduxi Configurator device form with two panels. Left panel "Communication channel": Connection *: TCP/IP (dropdown, badge 1); IP *: 10.0.0.43 with black button "Scan for IP" (badge 2); Port *: 502 with black button "Test port" (badge 3). Right panel "Device configuration": Modbus unit ID *: 1 (badge 4). The fields are marked with teal boxes and numbered badges.
-
Connection — select
TCP/IP(point 1 in the image) -
IP — enter the IP address noted at the P1 Ultra (optionally, search automatically via
Scan for IP) (point 2 in the image) -
Port — default value
502, can be checked withTest port(point 3 in the image) -
Modbus unit ID — default value
1(point 4 in the image)
Text description of this image
Cropped screenshot of the Reduxi Configurator device form with two panels. Left panel "Communication channel": Connection *: Local serial port (dropdown, badge 1); Port *: RS-485 port 1 (dropdown, badge 2). Right panel "Device configuration": Modbus unit ID *: 1 (badge 3). The fields are marked with teal boxes and numbered badges.
-
Connection — select
Local serial port(point 1 in the image) -
Port — select the RS-485 port used (e.g.
RS-485 port 1) (point 2 in the image) -
Modbus unit ID — must match the unit ID stored on the P1 Ultra under
Services → Modbus(see Point 7.3) (point 3 in the image)
Finish with Done — the meter point is now created in the controller.
Real-time control & priorities
In the Reduxi Controller, go to Strategy → Energy manager → the Included items tab to define which meter points are measured and which devices are actively controlled.
Text description of this image
Screenshot of the Reduxi Configurator, page "Strategy / Energy manager", tab "Included items" selected (other tabs: Optimization modes, Last measurements, Analyze, Archive, Details). Left menu: Devices (+), Strategies (-) with entries "Energy manager" (selected) and "Energy manager new", button "+ Add strategy", Utility Rate Plan, Settings (+). Three columns. Left column "Devices and strategies": Heizstab Wärmepumpe, Iskraemeco AM550, Musterstraße 1, Musterstraße 2, Ochsner GMLW 9Plus, SolarEdge, SolarEdge Slave, Zaptec PRO, myPV; below them: Energy manager, Energy manager new. Middle column "Measurement devices and strategies" (teal box, badge 1): Iskraemeco AM550, Musterstraße 1, Musterstraße 2. Right column "Regulated devices and strategies" (teal box, badge 2): SolarEdge, SolarEdge Slave. Hint at the bottom: "To remove supply or node items drag them outside frame". Black button "Save" at bottom right (teal box, badge 3).
- All pure meter points (e.g. a unit's P1 Ultra without its own generation) must be listed under Measurement devices and strategies (point 1 in the image).
- All devices that are to be actively controlled (e.g. inverter, wallbox, heating rod) must be listed under Regulated devices and strategies (point 2 in the image).
- Assignment is done via drag & drop from the left-hand list
Devices and strategiesinto the desired column. - Changes must always be saved via Save (point 3 in the image).
In addition, the Optimization modes tab (point 1 in the image) is where the GEA's export/import limit and control strategy are set:
Text description of this image
Screenshot of the Reduxi Configurator, page "Strategy / Energy manager new", tab "Optimization modes" selected (badge 1; other tabs: Included items, Last measurements, Analyze, Archive, Details, AI schedule). Left menu: Devices (+), Strategies (-) with "Energy manager new" selected, "+ Add strategy", Utility Rate Plan, Settings (+). Table with columns Name, Event description, Export limit, Goal, Import limit, Advanced. Row: Name: Default mode; Event description: /; Export limit: 11.2 kW (badge 2); Goal: Self-consumption (dropdown, badge 3); Import limit: 14.0 kW (badge 4); Advanced: edit icon. Footnote about the AI Energy Manager modules. Buttons: black "+" and black "Save" (teal box, badge 5). Top right: a green link icon and a green cloud icon.
- Export limit & Import limit — maximum feed-in or draw power for the plant, in kW (points 2 & 4 in the image).
-
Goal — the control goal, usually
Self-consumptionfor GEAs (point 3 in the image): the electricity consumption of all participants is jointly covered by the generation plant(s). - Here too: confirm entries via Save (point 5 in the image).
Function test and commissioning
Finally, the values configured earlier are checked for plausibility: correct assignment of meter points to measurement devices or regulated devices, and a plausible export/import limit and control goal for the plant. Since the P1 Ultra devices of a GEA communicate locally (Wi‑Fi/RTU) directly with the controller, a direct communication test is also available per meter point.
At the created device, test the connection via the Test communication button (next to Save) (point 1 in the image):
Text description of this image
Screenshot of the Reduxi Configurator device page with a modal dialog "Test communication" (close icon X at top right) laid over a greyed-out background. Dialog text: "Successful readout from device"; Active power: 23.0 W; Country: AUSTRIA null; Export active energy: 2.5651456E7 Wh; Export active power - 1 minute average: 12.3415 W; Export active power - 15 minute average: 6.9219 W; Export active power: 0.0 W; Export reactive energy: 1.9703036E7 VArh; Import active energy: 3.8028548E7 Wh; Import active power - 1 minute average: 2.3415 W; Import active power - 15 minute average: 177.5033 W; Import active power: 23.0 W; Import reactive energy: 8603357.0 VArh; Message structure: AUSTRIA KARNTEN NETZ null; Meter comm. error: false null; Model name: ISKRA AM550 null; Off-grid: false null. Button "Close" (black). Background, partly visible: "Do you want to invert direction for energy import and export" with Default: No; fields L2 is connected to main feed: L2 and L3 is connected to main feed: L3; section "Communication channel" with Connection *: TCP/IP, IP *: 10.0.0.43, Port *: 502, Extended IP recovery: toggle on (Yes). Bottom buttons: Delete device, "Test communication" (teal box with badge 1) and Save.
- A successful response (
Successful readout from device) shows the values just read (including active power, meter reading, meter model) — this confirms correct communication for the respective meter point. - If no response appears or an error occurs, check the IP address/port or wiring, and the Modbus unit ID, again.
Once all meter points have been tested successfully and the values are plausible, the GEA is set up and ready for operation.
✓ Summary
Shared foundation (Points 1–5): Electrical work carried out by a licensed electrician, one P1 Ultra per meter point with a secured power supply, and the appropriate app/cloud access for participants or the aggregator.
EEG (Point 6): The P1 Ultra devices communicate via MQTT through the Reduxi Cloud with the main controller. Credentials and the server certificate are stored at the controller and each P1, and every meter point is assigned via its Unit ID.
GEA (Point 7): The P1 Ultra devices communicate locally and directly with the controller — recommended via RTU (Modbus RTU/RS485), or alternatively via Wi‑Fi. Assignment is done via IP address or Modbus Unit ID.
Both paths together: Set up the strategy in the Energy Manager (measurement devices/regulated devices, export/import limit, control goal), then finally check the connection and the measurements for plausibility. Once all connections are active and the values are plausible, the plant is ready for operation.
→ Common issues
| Issue | Solution |
|---|---|
| MQTT connection doesn't show as Connected (main controller) or Active (P1 Ultra) | Re-check the credentials (Host, Username, Password), confirm Use SSL & Verify server cert / Use TLS & Verify server are both set to Yes, and that the server certificate has been uploaded at both the main controller and the P1 Ultra. Confirm the configuration was saved at each device – status can take up to about a minute to appear (see Setting up the EEG). |
| Server certificate can't be downloaded from the Connector page | The Download button in the Connector area only re-downloads a certificate that has already been uploaded once – it can't be used for the initial download. Get the current server certificate from the download link in this article and upload it manually first, at both the main controller and each P1 Ultra. |
| Test communication to a GEA meter point fails (Wi‑Fi or RTU) | For Wi‑Fi, re-check the P1 Ultra's IP address (or use Scan for IP) and the port (default 502). For RTU, verify the RS485 wiring and that the Modbus unit ID entered at the controller matches the one stored on the P1 Ultra under Services → Modbus. Make sure the device is reachable on the same network (Wi‑Fi) or bus (RTU) as the Controller (see Setting up the GEA). |
| A participant or meter point is missing from the totals, or isn't being controlled | Confirm it's correctly listed under Measurement devices or Regulated devices in Strategy → Energy manager → Included items, and that the assignment was confirmed with Save. |
| Export/import limit or control goal doesn't match the plant | Re-check the values under Strategy → Energy manager → Optimization modes – Export limit, Import limit, and Goal (usually Self-consumption) – and confirm they were saved. |
| P1 Ultra isn't reading the meter, or the meter looks incompatible | Check that the P1 Ultra has its own dedicated power supply (AC adapter, RS485, or USB‑C – it doesn't take power from the meter itself), and that the connection type (P1 port vs. infrared) matches the meter model. See Compatible meters & smart meters if the meter itself might not be supported yet. |