How to connect Iskraemeco UrbanBox EV charger with Reduxi controller
Reduxi and the Iskraemeco UrbanBox EVSE enable dynamic load management (DLM). It protects the installation and optimizes costs under dynamic pricing strategies.
1 Required equipment
You need the following components:
- Iskraemeco UrbanBox EVSE (it contains a router and a switch)
- Reduxi Controller
- Local LAN network with a switch or router
- Ethernet cables
- Laptop or tablet with internet access to configure the device in Reduxi
2 Connect the UrbanBox to the local LAN network
The Iskraemeco UrbanBox EVSE must be connected to the local LAN network. It contains a router and a switch. Wire both devices correctly.
2.1 Wiring of the router and the switch
Text description of this image
Tall photo of the inside of a cabinet, cropped, with blue hand-drawn arrows. Upper part: a black device with a white label 'A2' and a green and black panel with the text 'Power' (partly cut off); a gold antenna connector with a black cable on its upper left; purple and grey cables with cable ties; a long red wire running down the right side. A context-menu entry 'Kopiraj sliko' [Copy image] is visible at the right edge (screenshot artefact). Lower left: a white Ethernet cable with a transparent RJ45 plug entering the upper Ethernet port of the device, and a red Ethernet cable with a red plug below it in the lower port; two blue arrows point at these cables (one pointing left at the red cable, one pointing up at the white cable); a green terminal block sits below. Lower part of the image: a bundle of blue, red, white and grey wires with cable ties and a green connector.
Text description of this image
Photo of the inside of an outdoor charger cabinet next to its open door hinge, with a blue hand-drawn arrow. Upper left: a terminal block with white labelled wires (a label reading 'DVDC 3.4' is partly visible), red wires and orange lever connectors. A blue arrow starts in the upper middle and points down to a red Ethernet cable plugged into the upper RJ45 port of a white DIN-rail device (the switch). A second red Ethernet cable is plugged into the port below it, a grey Ethernet cable enters a further port, and a red cable with a blue-clipped plug is connected at the bottom of the white device, which has a small green status LED. At the right is the grey door frame with a hinge, a black cable and purple/orange wires. At the bottom of the photo a green-and-yellow wire and a yellow cable lie in front of a grey base and green grass.
3 Configure the UrbanBox
3.1 Router settings
For OCPP communication, set the router correctly. Open the router at http://192.168.2.1:8080.
| Parameter | Value |
|---|---|
| Address | http://192.168.2.1:8080 |
| Username | adm |
| Password | Iskraemeco2024! |
Text description of this image
Screenshot of the InHand Networks router web interface, Network settings for the WAN interface (top of the page cropped). Top menu: System, Network, Services, Firewall, QoS, VPN, Tools. Fields: Interface Mode: WAN; Type: Dynamic Address (DHCP); Shared Connection(NAT): ticked; Default Route: ticked; MAC Address: EC:6E:79:03:C0:FC with buttons Default and Clone; MTU: Default, 1500 (greyed). Buttons: Apply, Cancel.
Text description of this image
Screenshot of the InHand Networks router web interface, LAN interface settings, with a blue arrow. Top: part of a browser bookmarks bar (Jira, Jira Tempo - New, Teams, Lokalni dostop Ami..., Brezžični dostop A...). Menu: System, Network, Services, Firewall, QoS, VPN. Fields: Type: Static IP; MAC Address: EC:6E:79:03:C1:D5 with button Default; IP Address: 192.168.2.1; Netmask: 255.255.255.0; MTU: Default, 1500 (greyed); LAN Mode: Auto Negotiation. Section 'Multi-IP Settings': table with columns IP Address, Netmask, Description, one empty input row and an Add button. Section 'LAN Port Enable': port2: ticked, marked with a blue arrow. Section 'GARP': Enable: not ticked. Buttons: Apply, Cancel.
Text description of this image
Screenshot of the InHand Networks router web interface, Firewall settings (top of the page cropped), with a blue arrow. Menu: System, Network, Services, Firewall, QoS. Fields: Default Filter Policy: Accept (dropdown, marked with a blue arrow); Block Anonymous WAN Requests (ping): not ticked; Filter Multicast: ticked; Defend DoS Attack: ticked; SIP ALG: not ticked. Buttons: Apply, Cancel.
3.2 Switch access for the OCPP settings
| Parameter | Value |
|---|---|
| Address | http://192.168.2.2:8080 |
| Username | tec |
| Password | changeme |
3.3 OCPP settings
Finish the settings in Points 3.1 and 3.2 first. Then define the OCPP settings on the switch (the interface of the EVSE).
lsk.evse.Cfg.cpms.uri to the OCPP URL of the Reduxi server (see Point 5, Point 5.2).lsk.evse.stationId. You need it in Reduxi as device identifier (see Point 5, Point 5.2).Text description of this image
Screenshot of a web browser showing the Iskraemeco EVSE web interface at 192.168.2.2:8080/main.html (address bar warning 'Ni varno' [Not secure]). Browser tabs: Reduxi Cloud, Configurator, Router -> Cellular Router, Iskraemeco EVSE (active). A bookmarks bar is visible (Jira Tempo - New, Teams, Lokalni dostop Ami..., Brezžični dostop A..., Sharepoint Projekti, EIS, EIS IE, EIS Dars d.d). Page menu: Home, Config, Status, Firmware, Logoff, About Us. The Config menu is open with four entries: Software Properties - RW (highlighted red, with a mouse pointer on it and a blue arrow pointing at it), Software Properties - Controller, Software Properties - All, Hardware Properties. Behind the menu a table with columns Component and Status: Door Status: Open (1) in red; CPU Temperature: OK (51); CPU Battery: OK (1).
lsk.evse.Cfg.cpms.uri and lsk.evse.stationId
Text description of this image
Screenshot of a web page listing software properties of the Iskraemeco EVSE as a table: parameter name (blue link) and value. Visible rows: lsk.evse.Cfg.cpms.rfidDefault: ISKRFID; lsk.evse.Cfg.cpms.secProfile: 0; lsk.evse.Cfg.cpms.timeout_s: 30; lsk.evse.Cfg.cpms.unplugConector: empty; lsk.evse.Cfg.cpms.uri: ws://192.168.0.193/ocpp/1.6/json/ (marked with a blue arrow); lsk.evse.Cfg.dl.uriTimeoutS: 30; lsk.evse.Cfg.hmi.Cfg.adv.adv_delay: 10; adv_duration: 10; adv_type: empty; adv_url: empty; program_theme: 0; program_theme_white_end: 1080; program_theme_white_start: 480; template_area: empty; hmi.LightIntensity: 9; hmi.feat.charge.config.maxDuration: 0; maxPrice: 0; maxSOC: 0; hmi.feat.charge.qrCode: 0; hmi.feat.generic.showTariffImage: 0; hmi.lang.defaultLang: empty; hmi.lang.showLangs: gb,pt,sl,eg,ae,sa; hmi.maintenance_page: 0; lsk.evse.Cfg.maintenance.maxDays: 30; lsk.evse.con.1.cfg.session.maxDurationMin: 300; lsk.evse.con.1.cfg.session.maxSOC: 100; lsk.evse.con.1.limCurA: 100; lsk.evse.con.1.limPwrW: 40000; lsk.evse.stationId: Polnilnica1 (marked with a second blue arrow). A mouse pointer is visible in the middle.
4 Log in to the Reduxi web interface
You can open the Reduxi web interface in two ways:
Text description of this image
Screenshot of three Reduxi mobile app screens side by side, with cyan boxes and number badges 2 to 4. Left screen (dashboard, dark theme): menu icon at top left marked with a box and badge 2; 'reduxi' logo; tabs 'Real time data' (active) and 'Statistics'; price 5.79 € and temperature 3.2 °C; energy flow diagram with a house in the centre (-1.25 kW) and icons with values 69.0 W, 1.3 kW, 1.1 kW (red ring), -165.0 W with 97 % (red ring) and 0.0 W values at the bottom; tabs 'Power' and 'Energy'; bottom navigation: Dashboard, Diagnostics, Device control, Settings. Middle screen (side menu): 'reduxi' logo, 'Number of locations: 1233', heading 'Reduxi device management', entries '+ Add Reduxi location' and 'Reduxi devices' (marked with a box and badge 3), then 'My profile' and 'About app'. Right screen (device page): Back; picture of a black Reduxi controller with two Ethernet ports; status 'Connected'; card 'Update available': 'New update is available for your Reduxi device.' with button 'Download and install update'; card 'Connect to configurator': 'Tunnel connection enables remote access to your Reduxi configurator, without need to be connected to the same local network.' with button 'Activate tunnel connection' (marked with a box and badge 4); card 'Unit details' with field 'Unit ID'.
Text description of this image
Screenshot made of two parts side by side. Left part: Reduxi mobile app screen on a dark background. Top: Back button; picture of a black Reduxi controller with two Ethernet ports and a terminal block; status 'Connected' with a Wi-Fi icon. Card 'Update available': 'New update is available for your Reduxi device.' with button 'Download and install update'. Card 'Connect to configurator' with a key icon: 'Tunnel connection enables remote access to your Reduxi configurator, without need to be connected to the same local network.' and button 'Open configurator', marked with a cyan box and number badge 5. Below: card 'Unit details' with a field 'Unit ID' (value not visible). Right part: Reduxi Configurator opened in a browser, marked with a cyan frame and number badge 6. Header: back arrow, 'Tunnel connection', reload icon. Left sidebar with icons (lightning, chip, lightning bolt, bar chart, gear). Page 'Home' with a green link icon. Green notice: 'New patch available. Click here to apply.' with a close X. Time 09:12:56. Energy flow diagram with a house in the centre (1.700 kW) and icons for grid (0.000 kW), solar (1.700 kW), battery (green, 0.000 kW and 0.800 kW), a device at left (0.900 kW), electric vehicle and a charger or device at bottom. Label 'Energy manager' at the bottom.
http://reduxi.local. You can find the controller's IP address in your router's device list or in the Reduxi app under Reduxi devices.admin · Password: admin (factory default)Text description of this image
Screenshot of the Reduxi Configurator login page in a Chrome browser window. The address bar shows 'Not secure' and 'reduxi.local'; the address bar is marked with a cyan box and an enlarged copy of it (cyan box, text 'Not secure reduxi.local') is shown at the left, connected by a cyan line. Page background: light grey line drawing of a house with solar panels (green), a wall box, an inverter, a car and a charger. Top left: 'reduxi configurator' logo. Login box in the centre with title 'Login', a language selector (English flag, 'English'), a username field and a password field, and a dark 'Login' button.
Text description of this image
Screenshot of the Reduxi Configurator web interface after login, light theme. Top left: 'reduxi configurator' logo. Header bar: 'Home' at left, green 'Connected' status at top right. Left sidebar: expanded section 'Devices' with a list of entries, then collapsed sections 'Manager' and 'Configuration' and 'Settings'. Main area: energy flow diagram. House in the centre with ring, value 24.20 kW. Grid icon at top left, 24.20 kW (red dot on its line). Solar icon at top right, value '-'. Left icon (battery or device), 6.700 kW (green dot on its line). Right icons (battery storage and a device), values '-'. EV charger icon at bottom left, 31.00 kW. A further device icon at bottom right. Label 'Energy manager' below the house.
5 Add the UrbanBox to Reduxi
5.1 Add device and basic settings
Log in locally to the Reduxi Configurator (see Point 4) and click + Add device.
Text description of this image
Screenshot of the left sidebar of the Reduxi Configurator. Top: reduxi logo with the text CONFIGURATOR. Collapsed sections: Devices (plus icon) and Strategies (plus icon). Below, two buttons side by side: Add device (plus icon, marked with a blue highlight box) and Add strategy (plus icon). Below them two entries: Settings and Profile. The area to the right of the sidebar is empty white.
In the first step, select the basic settings:
- Device type:
EV charger - Type:
OCPP 1.6 - JSON - Name: a name of your choice
Text description of this image
Screenshot of the Reduxi Configurator add-device wizard, step 1 of 3. Progress bar with three steps: 1 Basic settings (active, black circle), 2 Communication channel (grey), 3 Advanced settings (grey). Heading: Basic settings. Fields: Device type * : empty dropdown; Type * : empty dropdown; Name * : empty text field. Buttons: Back (bottom left), Next (bottom right, dark).
5.2 Device configuration for OCPP
The second step sets up the communication channel for OCPP.
-
Device identifier (station unique identifier): enter the identifier from the Iskraemeco UrbanBox application in the first field. It is the station ID you copied in Point 3, Point 3.3. Example:
Polnilnica1 -
Server OCPP URL: with OCPP JSON 1.6, the Reduxi Controller generates the URL. Copy it from the communication channel and enter it on the switch (see Point 3, Point 3.3). Example:
ws://10.150.120/ocpp/1.6/json/
Text description of this image
Screenshot of the Reduxi Configurator form Communication channel and device configuration. Device identifier *: 1234. Connector *: 1. Charger type *: AC. Energy counter: Default. Allocate power to EVSE when EV is not connected to EVSE: Default. Per phase max. current *: Auto detect from EVSE. Per phase max. current manual override: 32 (hint: In effect when manual override is selected). Forward communication to backend OCPP server: ws://app.eu.tridenstechnology.com/ev-charge/gw-comm/glcharge. Forward measurements to backend OCPP server once every: 30 seconds. Allow new charging session: Forward to backend OCPP server. Controller OCPP JSON 1.6 URL (read-only, with copy icon): ws://10.150.1.120/ocpp/1.6/json. Buttons: Back, Test communication, Next (dark).
5.3 Test communication
Click Test communication at the lower right, below the communication fields. It checks whether OCPP communication is established. If the test succeeds, click Done: only Done creates the device.
Text description of this image
Screenshot of the Reduxi Configurator add-device wizard, step 2 of 3 (Communication channel). Progress bar: 1 Basic settings (black), 2 Communication channel (black, active), 3 Advanced settings (grey). Heading: Communication channel and device configuration. Fields: Device identifier *: my_station_ID1 (text field being edited, green outline); Connector *: 1; Charger type *: AC; Energy counter: Default; Allocate power to EVSE when EV is not connected to EVSE: Default; Per phase max. current *: Manual override; Per phase max. current manual override: 32 (hint below, small); Forward communication to backend OCPP server: empty; Allow new charging session: Always; Controller OCPP JSON 1.6 URL: ws:// address followed by /ocpp/1.6/json. Buttons at the bottom: Back (left), Test communication (marked with a blue box) and Next (right).
The test returns one of two results:
Text description of this image
Screenshot of a dialog titled "Test communication" with a close button (x) at top right, over a dimmed form. Green text: "Successful readout from device". Values: Current L1: 0.0 A; Current L2: 0.0 A; Current L3: 0.0 A; Import active power: 0.0 W; Max. active power: 22080.0 W; Max. current per phase: 32.0 A; Min. active power: 0 W; State name: AVAILABLE. Button at bottom right: Close.
Text description of this image
Screenshot of a dialog titled "Test communication" with a close button (x) at top right, shown over a dimmed page. First box: "Unable to communicate with device." Second box: "Number of devices found on OCPP - JSON 1.6: 0". Button at bottom right: Close.
6 Check the readings
6.1 Last measurements
Check the readings of the new device under Device – Last measurement in the Reduxi Configurator.
Text description of this image
Screenshot of the Reduxi Configurator page "Last measurements" of a DAZE charger (per the existing alt text). Card "Control type": a button group Auto (selected, turquoise), Manual, Off, Boost; timestamp 02. 10. 2024 15:47:17. Card "Current": Current L1 0.00 A; Current L2 0.00 A; Current L3 0.00 A; Max. current per phase 32.00 A; Per phase current setpoint 6.00 A (each with timestamp 02. 10. 2024 15:47:17). Card "Power": Import - active power 0.0 kW; Max. active power 22.1 kW; Min. active power 0.0 kW (timestamp 02. 10. 2024 15:47:17). Card "Energy": Import active energy 5,104.5 kWh (timestamp 02. 10. 2024 15:47:17). Card "Other": Communication error OFF (timestamp 02. 10. 2024 15:47:16); Control type AUTO; Error OFF; State name CABLE_UNPLUGGED... (text cut off with dots); timestamps 02. 10. 2024 15:47:17.
6.2 Enable control by Reduxi
For advanced EVSE control, integrate the device into the strategy of the Reduxi system. Under Devices – Iskraemeco UrbanBox EVSE in the Reduxi Configurator, set the control type to AUTO. Only then do strategy commands affect the EVSE.
To achieve maximum flexibility and energy cost reduction with dynamic prices and dynamic tariffs, define a strategy as described in Strategies for Reduxi controller.
After you add the device, you can monitor and control it in the Reduxi application.
✓ Summary
Preparation (Points 1–2): Collect the cables and a laptop or tablet. Connect the UrbanBox router and switch to the local LAN network.
Iskraemeco UrbanBox (Point 3): Set the router (DHCP, port 2, firewall policy Accept). Open the switch directly. Set the OCPP URL and copy the station ID.
Add to Reduxi (Points 4–5): Log in to the Reduxi web interface. Add an EV charger of type OCPP 1.6 - JSON, enter the device identifier, run Test communication and click Done.
Go live (Point 6): Check the readings. Set the control type to AUTO and define a strategy.
→ Common issues
| Issue | Solution |
|---|---|
| Test communication fails: no device found on OCPP 1.6 JSON | Check the router settings (see Point 3, Point 3.1), the OCPP URL and the station ID on the switch (Point 3.3) and the device identifier in Reduxi (see Point 5, Point 5.2). |
| The switch does not open | Connect directly to the switch (see Point 3, Point 3.2). |
| The EVSE ignores strategy commands | Set the control type to AUTO (see Point 6, Point 6.2). |
| Open configurator does not open or stays empty | The tunnel is not active yet. Wait about 30 seconds and check that the controller is online. |
Login with admin is rejected |
The password was changed during installation. Ask the installer. The Reduxi account password does not work here. |
reduxi.local does not load |
Your device is not in the same network as the controller. Use the IP address or the tunnel connection. |
| Communication test fails, device shows offline | Check reachability, IP address / port / unit ID, and that the protocol is enabled on the device. |