Instructions for some wall boxes, meters and inverters

You need to set a unique Slave ID for each controller: cFos Charging Manager -> System Configuration -> Modbus

Slave ID1
Type16 bit word
Value to writeNew Slave ID
Write func16


From then on, the controller only listens to the new Slave ID. Then write a register >= 2000 (e.g. the register 2001 again with the new slave ID). Then the value remains active after a restart.

Set all DIP switches and rotary switches to default. Set the rotary switch for the maximum current on the main board to 5 (16A / 11kW). Set the desired Modbus Slave ID with DIP S4 according to the table in the manual. In the Charging Manager, enter COMx,19200,8,e,1 as the address

In cFos Charging Manager -> Configuration

addressCharge Point ID, as configured in the EVSE
IDConnector ID, as configured in the EVSE

In cFos Charging Manager -> cFos Power Brain controller Configuration: Enable "EVSE as OCPP client"

IDAs configured in the Charging Manager (the connector ID is always 1)
ServerURL of your OCPP backend, including port number, e.g. The "/" at the end can be important depending on the backend - for cFos Charging Manager, the port number is always 19520

The rotary switch of the TWC must be set to "F"
Caution: You may need to swap the two connection wires to the EVSE if you don't get a response.
In cFos Charging Manager -> System Configuration -> Tesla TWC

Find ID

An attempt is made to find the ID of the Tesla TWC. Meanwhile, only one TWC may be connected. The ID is 4 digits (in hex).
In cFos Charging Manager -> Configuration

Address / IDEnter the found values (COM address / ID) here

Modbus port is always 502. The slave ID is normally 255. For Phoenix Contact it could also be 180.
The cFos Charging Manager should also run with the "Pro" models from Wallbe (i.e. those with built-in counters). We are still looking for someone to test this with. Please feel free to contact us!

OCPP: setup via the innogy eConfig app

Once a connection to the wallbox has been established via the innogy eConfig app, click on "Business / Commercial" to set up the configuration. When selecting the backend, select "3rd party backend". Depending on the connection, WLAN or LAN must be selected for the network, and for WLAN the SSID and the WLAN password must also be entered. After the Wallbox has connected to the network, the backend can finally be configured. Enter ws://xxxx:p/ as the backend URL, where xxxx stands for the IP of the cFos Charging Manager in the network, e.g., and "p" stands for the port to be used (e.g. 19500). So in the example the address was ws:// If the connection to the backend is to be SSL-encrypted, the "ws" at the beginning of the URL must be replaced by "wss". The name under which the wallbox reports to the backend is entered under "ChargeBox ID", e.g. LP000123 or CP456. If the Wallbox is also to be authenticated with a password, this can be specified as an option. In this case, the username must contain the same value as the ChargeBox ID field.

OCPP: setup via the wallbox's web interface (from firmware version 1.3.26)

The current firmware version is displayed in the innogy eConfig app after it has connected to the wallbox. The web interface can be reached via HTTPS (port 443) under the IP address of the wallbox. First, a connection to the network must be established as described above. The IP address of the Wallbox is then to be determined using the router used (e.g. The web interface can then be accessed via a browser. Please ignore certificate warnings. Login with "admin" and enter the PUK of the eBox as the password.
The OCPP configuration is done in the "ECU" menu, "OCPP" submenu. A name is selected under ChargeBox Identity, under which the eBox reports to the OCPP backend, for example LP000123 or CP456. The URI of the OCPP backend is entered for the end-point URI, e.g. ws:// for unencrypted or wss:// for encrypted connections. If the eBox is also to be authenticated with a password, this can be entered under "Password". In this case, the username must be the same as the ChargeBox Identity. All other parameters can be left at the default values. The "Use of relative meter readings" parameter should not be activated. The "Validate server certificate" parameter must not be activated. The settings are accepted with "OK". If necessary, restart the eBox via the "System -> Reset -> Router restart" menu.

Operate the innogy eBox on the cFos Charging Manager via Modbus TCP

From firmware 1.3.26, the innogy eBox can also be operated via Modbus TCP. The firmware version can be queried using the innogy eConfig app. The web interface of the eBox is set up and called up as described above. The Modbus settings are made in the LDP1 -> Load management menu. Select modbus_tcp as the load management type. Select the network to be used as the interface, i.e. net1 for LAN1, net2 for LAN2 and wlan1 for the WLAN network. The TCP port to be used can be selected under Port. For Modbus this is 502 by default. The settings are accepted with "OK". If necessary, restart the eBox via the "System -> Reset -> Router restart" menu.

Unfortunately, we are currently not aware of any Modbus register for reading the charged kWh. We are grateful for any information on this!

Here you need a two-wire connection with a twisted cable (bell wire, network cable). In the housing of the eMH1 you will find an RJ12 socket which is connected to the RS485 on the circuit board. The (middle two) pins 3 and 4 are Modbus A and B. So you need an adapter from RJ12 to two-wire. Since A and B are not specified for Modbus, you may have to swap the wires if the EVSE cannot be reached. Address is COM1,38400,8, E, 1 (under Windows and Raspberry possibly another COM port, e.g. COM3).

Enter the following parameters in the cFos Charging Manager: Address: serial number of the wall box (e.g. EH123ABC), ID: irrelevant, user: user name in the Easee cloud, i.e. e-mail address or mobile phone number including international area code (e.g. +49) , Password: Password for the above username in the Easee cloud.

Enter the IP address at which the go-e can be reached in your home network as the address.

Enter the IP address at which the wallbox can be reached in your home network as the address. To activate the KEBA UDP protocol, you must set DIP switch 1.3 in the wallbox to "on". You can also integrate the x-series via OCPP.

Enter the IP address at which the wallbox can be reached in your home network as the address. Alternatively, you can also integrate them via OCPP.

Integration via Modbus: possibly deactivate OCPP, deactivate free charging, activate Modbus, select Modbus Register Set TQ-DM100. Then address the Wallbox under port 502, eg enter as the address. Alternatively, you can also integrate them via OCPP: Enter Websockets JSON OCPP backend URL (including port) of the cFos Charging Manager, e.g. ws://, then start charging with an RFID.

Please note that the Autoaid only runs with a specific firmware with the cFos Charging Manager (currently 1.1.258). It might work with a newer version. But this is not confirmed. To set up the box, download the EVSE Mesh app from the App Store. Instead of the EN+ backend, the IP address and port of the cFos Charging Manager must be specified. If the IP address of the cFos Charging Manager was and the port was 19520, you would have to enter the following in the Autoaid Wallbox: (unencrypted) and (encrypted). Port: 19520. "ws://" or "wss://" may also work instead of "http://" or "https://". Encrypted connections are currently untested. In the cFos Charging Manager, "EVSE with OCPP" must be selected as the device type and the OCPP Charging Point ID of the Autoaid Intelligent must be specified as the address. The Charge Point Id is the serial number of the Wallbox starting with SN. It will be displayed in the app.

S0 meters trigger a certain number of pulses per kWh with a switching output. The number of pulses per kWh must be set correctly. The wiring is done with twisted pairs (bell wire, telephone line, network cable). Since the switching outputs are usually semiconductor outputs, it may be necessary to swap the S0 lines on the meter. When connecting to the cFos Power Brain Controller, avoid 12V short circuits that can destroy the controller. Here detailed information on S0 counters.

Select the appropriate meter type and wire the contacts A with A and B with B using a two-wire line (telephone line / For cable lengths exceeding 10m, we recommend terminating resistors of 120 ohms, 1/4 watts at both ends of the bus. Since A and B are not standardized, you may have to swap the wires. Each device on the bus has a unique ID that you must enter in addition to the address. Enter COMx, baud, bits, parity, stops as the address, e.g. COM1,9600,8, N, 1 where x is the COM port to which your two-wire line is connected: Always COM1 with the cFos Power Brain Controller. With Windows and Raspberry you have to find out the COM port of your RS485 adapter. Baud, bits, parity, stops can be found in the manual for the counter. At ABB mostly 19200.8, N, 1, at Eastron 9600.8, N, 1, at Orno and ZZ4 D513020 9600.8, E, 1. Each device on Modbus RTU (two-wire) must have a unique ID. If you operate several devices on one bus, you may have to change the ID in the devices. This can be done either using the control buttons on the meter or with the Modbus UI in the Charging Manager under "Configuration".

The Powerfox meter sends its data to the manufacturer's cloud. You can then call this up again with the cFos Charging Manager. Enter the address: Here, 'user' is your username and 'pwd' is your password. If your username contains an @ you have to %40 , e.g. becomes

The Shelly 3EM is booked into the house network and can then be addressed via HTTP API. The address is then//user: pwd@ 'User' is your username and 'pwd' is your password (%40 , eg becomes

Select "Elgris Smartmeter" as the device type. The counter can be integrated using Modbus TCP. Enter the address with which the meter is logged into the house network and port 502, e.g. Id is mostly 1.

With PV equipment, we always recommend trying the device type 'SunSpec Solar Inverter' first. Enter the IP address under which the device is registered in your home network as the address. Port is often 502 (or 1502), e.g. You may have to enter the ID correctly, as some manufacturers show different devices under certain IDs. If necessary, see the manufacturer's documentation. For some devices, Modbus TCP must also be enabled. SunSpec is a standardization for different device models. There can be several models shown in one device, which you can select (if necessary). Here information about SunSpec parameters. You can additionally configure the SunSpec start register if the IP address of the device is correct but no SunSpec device is found. If you need a specific SunSpec model (and want to exclude others), you can use the "SunSpec Model Index" to make the Charging Manager skip the registers of the previous models. You can find more about the respective SunSpec start register and the order of the SunSpec models in your device in the manufacturer's manual.

Enter the IP address under which the SMA inverter is logged into your home network as the address. Port is typically 502, e.g. Id is often 3. Then you can first try to select 'SunSpec Solar Inverter' as the device type. If the inverter cannot (meaningfully) be read out in this way, you can try the device type 'SMA Inverter'.

E3/DC devices can be addressed in different ways. You should try 'SunSpec Solar Inverter' as the first device type. Alternatively there is the E3/DC Simple Mode which you/DC Solar Device'. Enter the IP address under which the device is logged into your home network as the address. Port is 502, e.g. Id presumably 1. In simple mode you also have to enter a register under 'Register or power meter' to read out the desired power value (which then relates to all phases together) or a power meter (which allows phase-related power values to be read out). Valid values for power meters are 0-7. Here is a list of the registers. Note: You have to activate Modbus and Modbus//

Select 'SunSpec Solar Inverter' as the device type. Enter the IP address of the Fronius inverter as the address, followed by: 502 as the port number. Fronius typically uses 1 for the inverter and 240 for the smart meter as the ID. You can also try the 200, 201, 202, 203 or 204. For more details, see the documentation for the respective device.

In connection with inverters, Kostal offers a counter that can measure the electricity drawn from the grid bidirectionally. Select 'Kostal Powermeter' as the device type. Enter the IP address of the Kostal inverter as the address, port is often 1502 (e.g. 71 is often used as the ID.

Note: In almost all cases it is better to select / Only if this is not possible should you use 'Kostal Inverter HTTP'.
Select 'Kostal Inverter HTTP' as the device type. Enter the IP address of the Kostal inverter as the address. The version of the inverter must be new enough. If necessary, update the inverter firmware. Tested with a newer Piko 7.0.

The SMA Homemanager transmits its data periodically as UDP multicast to all network participants. Therefore you do not need to enter an address. You have to make sure that your network forwards UDP multicasts. This is often blocked in the WLAN and must therefore be activated in your router.

With devices from SolarLog and Sonnen you can select in the device type which function the device has, e.g. 'SolarLog Production' or 'Sonnen Production HTTP'. Then enter the IP address with which the device is logged into your home network as the address. For SolarLog add port 502, e.g., for Sonnen place an http:// front of it, e.g.

Many thanks, Rainer Z., for these instructions!
There are two options for integration: Modbus RTU (two-wire) and Modbus TCP (via the home network). Modbus TCP must be selected if the Huawei dongle is used. This provides a WLAN or LAN connection. However, older firmware versions often cause problems. Huawei itself recommends the following firmware versions for Modbus TCP: Device minimum firmware version SDongleA-05 V1000R001C00SPC124, SUN2000L V2000R001C00SPC115, SUN2000MA V1000R001C00SPC139 (currently tested with dongle version V100R001C00SPC127 and inverter version V100R001C00S). If necessary, ask the installer to update them with the available packages from FusionSolar website or contact eu_inverter_support(at) The inverter can also be upgraded by the customer provided they have access to the installation menu. Mondbus TCP must also be activated in this installation menu:

  • Connect the mobile phone to the inverter via the inverter's Wi-Fi hotspot. If not configured, the hotspot data is on the dongle as a sticker with a QR code (default: SUN2000-xxxxxxxxxx)
  • Launch the latest FusionSolar app
  • Confirm the message "Access failed"
  • Open the three-dot menu (top right).
  • Select device start-up
  • Log in to the device (e.g. SUN2000-xxxxx-xx) under "Connection recording". Unless the installer has changed the parameters, the password is 00000a
  • Under Settings → Communication configuration → Dongle parameter settings → Modbus TCP set the "Connection" setting to "Enable (unrestricted)".
If Modbus TCP no longer works after a dongle update, this Modbus TCP activation must be repeated. The software of the devices can be updated under Maintenance → "Update device", with the exception of the dongle. The Modbus TCP queries are somewhat time-critical at Huawei, so no two instances should query values. For excess solar charging, the "Huawei SUN 2000 meters" counter should be selected. The IP of the Huawei inverter is to be selected as the IP, as well as its ID (in most cases 1). The purchased electricity counter shows negative values for purchased electricity and positive values for feed-in. Therefore you have to invert the counter in the counter settings in the cFos Charging Manager.

Note: For the cFos Power Brain controller the COM port is always COM1.