Instructions for some EVSEs, 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

With the newer models connect.home,,, the RFID card must be taught in the box so that it authorises charging. In the Charging Manager, do not create an RFID for the user with the function "Authorise charging" or assign it to the box.

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". For the network, select WLAN or LAN depending on the connection; for WLAN, also enter the SSID and the WLAN password. After the wallbox has connected to the network, the backend can be configured. Enter ws://x.x.x.x:p/ as the backend URL, where x.x.x.x 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). 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 a "wss". Under "ChargeBox ID", enter the name under which the wallbox reports to the backend, e.g. LP000123 or CP456. If the wallbox is also to authenticate itself with a password, this can be entered as an option. In this case, the user name must contain the same value as the ChargeBox ID field.

OCPP: Setup via the wallbox 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 accessed via HTTPS (port 443) under the IP address of the wallbox. First, a connection to the network must be established as described above. Then the IP address of the wallbox must be determined using the router used (e.g. The web interface can then be accessed via a browser. Please ignore certificate warnings. Log in with "admin" and enter the PUK of the eBox as the password.
The OCPP configuration is done in the menu "ECU", submenu "OCPP". Under ChargeBox Identity, a name is selected under which the eBox reports to the OCPP backend, e.g. LP000123 or CP456. For the End-Point URI, enter the URI of the OCPP backend, e.g. ws:// for unencrypted or wss:// for encrypted connections. If the eBox is to authenticate itself additionally with a password, this can be entered under "Password". In this case, the user name must be the same as the ChargeBox Identity. All other parameters can be left at their default values. The parameter "Use relative meter readings" should not be activated. The parameter "Validate server certificate" must not be activated. The settings are accepted with "OK". If necessary, restart the eBox via the menu "System -> Reset -> Router restart".

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

As of firmware 1.3.26, the innogy eBox can also be operated via Modbus TCP. The innogy eConfig app can be used to find out which firmware version is available. The web interface of the eBox can be set up and called up as described above. The Modbus settings are made in the menu LDP1 -> Load management. 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. Under Port, the TCP port to be used can be selected. For Modbus, this is 502 or 5555 by default. Click "OK" to accept the settings. If necessary, restart the eBox via the menu "System -> Reset -> Router restart".

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

Here you need a two-wire connection with twisted cable (bell wire, network cable). In the housing of the eMH1 you will find an RJ12 socket that is connected to RS485 on the 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 is not accessible. Address is COM1,38400,8,E,1 (under Windows and Raspberry possibly other COM port, e.g. COM3). You may have to set the EVSE to "Standalone" in the ABL configuration programme confcab. The Modbus ID here can also be set to values from 1 to 16 if required.

These wallboxes should be connected via OCPP. They have 2 connectors, i.e. one Wallbox tile must be set up per connector. The second connector is 120 degrees out of phase. However, the wallbox does not tell the Charging Manager this, so you have to remember to set the phase rotation of the second connector to 120 degrees when setting it up.

In the cFos Charging Manager, enter the serial number of the wallbox (e.g. EH123ABC) in the Address field. The ID field is meaningless. In the Easee configuration under of the associated location, select 'cFos eMobility' as the technical operator. RFIDs can only be read by Charging Manager if the access authorisation of the charging station is set to 'private' in the Easee configuration.

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

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

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

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

Last tested successfully with Autoaid firmware 1.1.805. To set up the box, download the app EVSE Mesh from the App Store. Instead of the EN+ backend, the IP address and port of the cFos Charging Manager must be entered. If the IP address of the cFos Charging Manager is and the port is 19520, you must 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 entered as the address. The Charge Point Id is the serial number of the wallbox starting with SN. It is displayed in the app.

Set the identification to "inactive" in the wallbox setup. Charging station type to "stand-alone solution". It may be necessary to assign a fixed IP address so that the wallbox is available in the LAN (possibly deactivate the wallbox's DHCP server). Under "Energy management", set the options "Charge current throttled" to 6A and "Local power reduction" to 16A. Possibly only one charging point possible under Modbus. In the cFos Charging Manager, enter the address of the wallbox and port 502, e.g., set ID to 255. If you want to operate the wallbox with OCPP, enter a ws:... as the URL of the backend. as the URL of the backend, not a wss:

You can select Mennekes Amtron as the device type, as this wallbox has the same controller from ebee or Bender.

OCPP: You must set the parameter "AllowMaxChargingProfile" to "true" in the OCPP configuration of the Hypercharger so that the cFos Charging Manager can control the charging current via OCPP.
Modbus: New Hyperchargers from version 4.0 (HYC_400) have good Modbus support. The Modbus TCP server must be activated and writing via Modbus must be permitted. You should set the failsafe timeout to 180sec or higher. In addition, the connector number, starting with 0, must be entered in the tile settings under "Connector".

Modbus: You must activate Modbus in the charging station (BigEndian). Modbus ID 1 is used for global values such as serial number. Modbus ID 2 is the first charging station or the first plug of a fast charger, Modbus ID 2, the second charging station, and so on. Normally enter 0 as the plug number. Only the total charging power is transmitted via Modbus, i.e. the exact phase use should be set in the Charging Manager in the "Phases" parameter.

The SMA EV Charger is controlled via HTTP. To set the charging current, the cFos Charging Manager uses the parameter "Parameter.Inverter.AcALim". This could be stored by the SMA Charger in its flash memory, which only allows a limited number of write cycles. We have asked SMA in vain whether setting the charging current wears out this memory and have therefore included a parameter called "Update delay" in our setup. This delays the increase of the charging current after the last setting by the set number of seconds. Decreasing is always immediate. You can set this parameter yourself at your discretion as a compromise between fast regulation and low wear.

Log in to the TerraConfig Service Portal with your access data. Set up another OCPP server there. Enter any name that uniquely describes the configuration. Select "ws" for unencrypted and "wss" for encrypted connections. If the charging manager and the wallbox are in the same local network, unencrypted connections are usually sufficient. If you choose encrypted connections, make sure that the field "OCPP Server TLS" in the Charging Manager under "Settings" is set to "On" or "Detect". Also note the "OCPP Server Port" entered there (19520 by default). In TerraConfig, enter the IP address of the Charging Manager under URL, followed by a colon and the OCPP server port, e.g. Select "OCPP 1.6-J" as the protocol in TerraConfig. Save these settings.

In the TerraConfig app, which you use to configure your wallbox, select the OCPP server profile you just created in the OCPP settings, which should now appear in the list of available profiles.

If you have not already done so, add a new wallbox in the Charging Manager. Select "EVSE with OCPP 1.6" as the device type. Under Address, enter the serial number of your wallbox, e.g. TACW2241234G5678. The ID field corresponds to the connector ID, always "1" for wallboxes with one connector. Save these settings.

In the tile for the created wallbox, the first line should initially show "Offline / Off". A successful connection of the wallbox to the Charging Manager can be recognised by the fact that this line changes to "Waiting / Off". Furthermore, "EVSE OCPP" is initially displayed at the bottom of the tile. After a successful connection, detailed information about the wallbox (manufacturer, model, firmware, serial number) is displayed there.

Modbus: Currently the TCP stack of the ABB Terra does not seem to be working properly. You can try activating the "Keep TCP connection" option in the cFos Charging Manager. Maybe it will work better then. Under Modbus there is no counter for the total kWh charged. The recommendation is therefore to use OCPP with the ABB Terra.

Wallboxes that are integrated into the ChargePoint Cloud (has-to-be), e.g. CP4320. In the device configuration, select "ChargePoint" under Device type. Under Address, enter the ChargePoint Station ID in the format CPNID:StationIdentifier, e.g. "2:1234567". If the station ID is not known, the serial number, the MAC address or the name of the station can also be entered under Address. In this case, the entry must uniquely identify the station. Under ID, select the port number. For charging stations with a connector, the port number is always 1. In the User and Password fields, enter your login data for the ChargePoint Cloud. Under Phases you must select which phases are actually connected. The Charging Manager cannot determine the phase usage because the Cloud does not provide the necessary measured values. Measured values are transmitted with delays of up to 5min. Therefore, set up sufficient control reserve.

The eHome is connected with Modbus RTU. Select 9600,8,e,1 as COM parameter, but you might also need 19200 instead of 9600 and n instead of e and 2 instead of 1 stop bit. The Modbus ID is 1 by default. If you use several wallboxes, you must set the Modbus ID of the wallboxes to unique values by writing register 0. In the wallbox settings of the cFos Charging Manager, the option "Leave charging activated" must be switched on for this wallbox, otherwise the wallbox will not notice whether the charging cable is plugged in when it is deactivated.

Connection via OCPP: Load management via OCPP must be activated in the Circontrol eVolve. To do this, the "Power Balance" field must be set to "enabled" in the configuration menu of the wallbox under "Configuration", sub-item "Charge". Then "OCPP Smart Charging" must be selected there.

For this wallbox, the parameter Charging current PWM must be set to 0 in its Web UI under Load management.

Connection via OCPP: In the OCPP configuration of the wallbox, the IP address of the cFos Charging Manager (e.g. and the OCPP server port set in it (e.g. 19520) are entered as follows: ws://
Furthermore, note the value entered in the configuration of the wallbox under "Customer Ident No.". Enter this value in the Charging Manager in the device configuration in the "Address" field. Select "EVSE with OCPP 1.6" as the device type

Please install at least firmware v3.89 in the Vestel Wallbox. Modbus: The Vestel uses 502 as the default port, so the address must be e.g. ID is 255.

The default charging power must be set to 1kW in the configuration UI of the charger. (Self) Then this charging station cannot be switched off completely, but always charges with at least 250W.

In the Web UI of the wallbox, change the "Card Type" parameter from "Start/Stop" to "Billing Card".

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 pair wire (bell wire, telephone line, network cable). As the switching outputs are normally semiconductor outputs, the S0 lines on the meter may have to be changed. When connecting to the cFos Power Brain Controller, avoid 12V short circuits, which can destroy the controller. Click here for detailed information on S0 meters.

Select the appropriate meter type and use a two-wire line (telephone line / network cable) to wire contacts A to A and B to B, thus creating a bus. For line lengths of 10m or more, we recommend terminating resistors of 120 Ohm, 1/4 Watt at both ends of the bus. Since A and B are not standardised, 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 on which your two-wire line is connected: For the cFos Power Brain Controller always COM1. For 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 of the meter. For ABB usually 19200,8,N,1, for Eastron 9600,8,N,1, for Orno and ZZ4 D513020 9600,8,E,1. Each device on Modbus RTU (two-wire) must have a unique ID. If you operate several units on one bus, you may have to change the ID in the units. This can be done either using the control buttons of the meter or with the Modbus UI in the Charging Manager under "Configuration".

For the Bauer BSM, select SunSpec as the device type, the COM port to which you have connected the 2-wire connection. Select 19200,8,E,1 as the interface parameter and 42 as the ID. If you have set other parameters in the meter, select them accordingly.

The Powerfox meter sends its data to the manufacturer's cloud. You can then retrieve this data with the cFos Charging Manager. Enter the following address: Here, 'user' is your user name and 'pwd' your password. If your user name contains an @, you must replace it with %40, e.g. becomes Certain special characters must not appear in a URL. You must write these using % coding, e.g. replace ? with %3f.

The Shelly 3EM is logged into the house network and can then be addressed via HTTP API. The address is then e.g. http://user:pwd@ Here, 'user' is your user name and 'pwd' your password (if your user name contains an @, you must replace this with %40, e.g. becomes

Select "Elgris Smartmeter" as the device type. The meter can be integrated via Modbus TCP. Enter the address with which the meter is registered in the house network and port 502, e.g. Id is usually 1.

We recommend that you always try device type 'SunSpec Solar Inverter' first for PV equipment. Enter the IP address under which the device is registered in your home network as the address. The port is often 502 (or 1502), e.g. You may also need to enter the ID correctly, as some manufacturers display different devices under certain IDs (e.g. Fronius, see below). If necessary, see the manufacturer's documentation. Modbus TCP must also be enabled for some devices. For SMA, set the ID of the device plus 123 as the ID in the Charging Manager (e.g. 126 if 3 is configured in the SMA device).
SunSpec always works with big-endian values. Make sure that your device is set to "big-endian", e.g. Kostal.
SunSpec is a standardisation for different device models. Several models can be mapped in one device, which you can select (if necessary). Click here for information on SunSpec parameters. You can also 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 "SunSpec Model Index" to ensure that the Charging Manager skips the registers of the previous models. You can find out more about the respective SunSpec start register and the sequence of SunSpec models in your device in the manufacturer's manual.
With Solaredge, you can still use 40121, 40295 and 40469 as SunSpec Start Registers, as Solaredge may have added further counters there.

The cFos Charging Manager also tries to find storages that are readable according to SunSpec. If your storage supports SunSpec, you can select SunSpec for this meter device type.

Enter the IP address under which the SMA inverter is registered in your home network as the address. Port is typically 502, e.g. Id is often 3. You can read out many inverters with the meter type "SMA Inverter". However, we recommend reading out the SMA devices using SunSpec. To do this, you must add 123 to the Modbus ID set in the device. For example, with a Modbus ID of 3 entered in the SMA inverter, you must then set 126 as the ID in the cFos Charging Manager.
Storage devices (e.g. Sunny Boy Storage / SBS) can be controlled as 1- or 3-phase inverters under SunSpec. In this case, SMA delivers negative values during charging and positive values during discharging. In this case, you must enter -1 as the factor instead of 1 in the settings of the counter tile in the Charging Manager.

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

Select 'SunSpec Solar Inverter / Meter' as the device type. Enter the IP address of the Fronius inverter as the address, followed by :502 as the port number. As Id, Fronius typically uses 1 for the inverter (with and without battery storage) and 240 for the Smartmeter (you can also try 200, 201, 202, 203 or 204). Battery storage is sometimes included with the inverter and sometimes with the Smartmeter. For details on setting the Modbus ID, see the documentation for the respective device. If the cFos Charging Manager finds an additional model for the battery storage, there is a "+Bat" under the extended information in the display. Fronius Hybrid devices display the battery storage counters in the SunSpec model for MPPT modules. Here you must select "MPPT Module" as the SunSpec model and typically #3 as the model index. The Charging Manager then displays the charging and discharging power of the battery storage. For hybrid units, the inverter power display can sometimes be a mix of PV strings and battery storage. To determine only the solar generation you can set up 1-2 meters of the type "Sunspec Solar Inverter / Meter" with MPPT modules #1 (and #2). In addition, we offer "Fronius...HTTP" meter definitions for purely reading out the inverter, grid reference meter or battery storage, if only inconsistent values can be read out via Modbus for hybrid inverters.

In connection with inverters, Kostal offers a meter that can measure the mains supply 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 the device type 'SunSpec Solar Inverter / Meter' for Kostal inverters and Smartmeters. 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 firmware of the inverter. Tested with a newer Piko 7.0.

The KSEM can be operated as device type SunSpec with its IP address and port 502, e.g. Enter 0 as ID.

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

For SolarLog and Sonnen devices, you can select which function the device has in the device type, 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 the port 502, e.g., for Sonnen add a http:// in front, e.g.

Many thanks, Rainer Z., for these instructions!
There are two possibilities for integration: Modbus RTU (two-wire) and Modbus TCP (via the domestic network). Modbus TCP should be selected if the Huawei dongle is used. This provides a WLAN or a 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 V100R001C00SPC141). 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 updated by the customer, provided that access to the installation menu is available. Likewise, Modbus TCP must be activated in this installation menu

  • Connect the mobile phone to the inverter via the inverter's Wi-Fi hotspot. If not configured, the data for the hotspot is on the dongle as a sticker with QR code (default: SUN2000-xxxxxxxx)
  • Start the current FusionSolar app
  • Confirm the message "Access failed"
  • Open the three-point menu (top right)
  • Select start-up of the unit
  • Log on to the unit (e.g. SUN2000-xxxxx-xx) under "Connection recording". If the installer has not 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 functions after a dongle update, this Modbus TCP activation must be repeated. Under Maintenance → "Update device", the software of the devices can be updated, with the exception of the dongle. The Modbus TCP queries are somewhat time-critical with Huawei, so no two instances should query values. For PV surplus charging (solar surplus charging), the meter "Huawei SUN 2000 Meter" is to 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 port is 502, e.g. The grid reference meter shows negative values for grid reference and positive values for feed-in. Therefore, you must invert the counter in the counter settings in the cFos Charging Manager.

With Victron, various devices can be integrated under a "Modbus control device". The Modbus ID determines which device is reached. You must first determine the Modbus ID of the desired device for your device using the Victron documentation or in their web interface (Remote Console) under Settings -> Services -> Modbus TCP -> Available services.
Then select the appropriate device as the device type in the cFos Charging Manager, enter the IP address and port 502 as the address and then set the appropriate Modbus ID as the ID. The meter type available for selection in the cFos Charging Manager is "Victron Energy Meter" as the grid reference meter (for Victron "Energy Meter") and "Victron Sys Battery" (the battery storage system shown under "System" for Victron).

For the address, enter http://user:passwort@ip_address, where user is your user name, password is your password for the logger and ip_address is the IP address with which the logger is logged into your house network, e.g. http://claus:test1234@
For Sofarsolar, there are also devices that speak Modbus TCP or Modbus RTU (two-wire). Here we have prepared meter definitions and are still looking for people to test with.

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