Can you share your rs482 Modbus connection settings on converter.
Can you start stop/charging and change charging current or just read the values?
I can start, stop, change the charging current and of course read the values.
As for the port settings I did not play with it much, just set the same values on both ends (ABB Terra AC TAC-W11-G5 and the RS485 to Wifi converter with Modbus support)
Below are my settings:
ABB Terra AC
Modbus Address 1
Baud Rate 19200
Parity Even
Stop Bit 1
Data Bit 8
RS485 to Wifi Converter
Baud Rate 19200
Data Bit 8
Parity Bit Even
Stop Bit 1
CTSRTS Disable
Pack Interval 20
Pack Size 1400
Com Heart OFF
Modbus Enabled Protocol Coversion
1 Like
Trying to setup (device without screen). Firmware is 1.8.34 and latest Andoird app.
What IP address should be given in device? I have tried my own and HA address, but get an error while storing setup to device.
As far as I know you can’t configure Modbus TCP/ip on device without LCD screen. You need rs482 Modbus to lan/wifi converter.
Then you have to set static IP address for converter and put that IP adress and port number in integration.
On models with display you have to enable Modbus TCP/IP with TerraConfig app (as described in one of the earlier posts). There you set IP adress and port number for charger (which must be free on your network). This IP adress and port number is then put in integration to connect. Connection to charger must be via LAN cable as Modbus TCP/IP over WIFi is not supported by the charger.
Dear collegues,
first of all - thank you JernejHren et al for this great implementation.
I want to share to the community how I successfully integrated the Wallbox without LCD (ABB Terra AC / 6AGC082156) into HA. As already mentioned, you need a Modbus TCP interface.
I used the DR134 having a LAN interface, can be bought at ali… and configured it as followed:
- enable “local controller - Modbus RTU(RS485)” in the Terraconfig App. I set modbus-Adress to 1 and Baudrate to 57600.
- Connect the DR134 to the Terra AC with RS485 A->A and B->B. I used a 20cm shielded cable, shield to GND at charger. No termination.
- Power the DR134 (e.g. USB PSU). red light turns on.
- connect DR134 to LAN and follow the tutorial: access as 192.168.0.7 with admin/admin, set IP to desired IP.
- Having logged in, set Port Parameter to Baud Rate acc. to your settings in TerraConfig App (e.g. 57600/8bit/1stop/None), Local Port Number to 502, Work Mode = TCP Server:
- EDGE Gateway: Working Mode: Modbus Multi Host Poll
- Integrate according the description of custom integration of JernejHren and the IP adress you set at the DR134
Disclamer: Work according to your country regulation concerning AC-power or/and let a professional do this work! No garantee, do this at your own risk.
3 Likes
The error comes when you want to store the configuration with enable Modbus over TCP on the version without display. This is not specifig defined in the product specification, however I found this out when I compared both installation manuals.
I have released new version 0.1.3
This release focuses on improving diagnostic capabilities and completing state reporting with minimal structural changes.
Features & Improvements
Detailed Error Code Translation:
The Error Code sensor now displays a textual description (e.g., "Over Voltage," "Residual Current Detected") instead of the raw Modbus number.
Adds a comprehensive mapping table for all known Modbus error codes (0x0002 to 0x4000).
Complete Socket Lock Status:
Added the dedicated Socket Lock State sensor.
Updated the underlying mapping to accurately cover all five possible states (0, 1, 17, 257, 273), ensuring correct status reporting (e.g., "No cable plugged," "Cable connected, locked").
2 Likes
Had to release new version for switches to reflect correct status with new possibilities from previous release:
Switch Logic Improvements
This update refines the behavior of the charging and locking switches to better reflect the actual hardware state.
Charging Switch
Support for Paused State: The switch now correctly reports as On when the charger is in State D/F (Paused/Fault). This prevents the switch from toggling off during scenarios like solar charging pauses (when current drops below 6A) while the session is still active.
Cable Lock Switch
Fix for Locked State Detection: Fixed a bug where the switch showed Off if the cable was locked but no vehicle was connected. The logic now correctly accounts for Modbus value 17 (Cable connected, locked) in addition to value 273 (Cable & EV connected, locked).
Thanks for clarifying this. I ordered Ethernet/RS485 converter.
Just wondering if it is possible to run this GitHub - valexi7/ABB-Terra-Modbus-RTU-Bridge: ABB Terra AC EV3-compat Modbus RTU slave fed from HomeWizard P1 via HA in parallel or way better to have this functionality in same integration.
Charging station supports one active connection when using Modbus tcp/IP. I am not sure how it works over Modbus rtu RS 485.
I use separate automation which reads my Shelly 3 em pro power meter and then starts car charging when my car is connected and there is enough available electricity to not go over the limit. It automatically adjust charging current to stay under limit. It is still work in progress and is useful only in Slovenia but you can take a look: home-assistant-blueprints/automation/EvLoadManagement at main · JernejHren/home-assistant-blueprints · GitHub
Hi all,
For those of you using the ABB Terra AC Modbus integration and struggling with setting up reliable Dynamic Load Balancing or Solar charging via automations, I’ve built a custom component to handle the logic.
It’s called EVSCI . I developed it specifically because I wanted reliable load management for my ABB charger.
It handles:
-
Dynamic Load Balancing (protecting your main fuse).
-
Solar Charging (PV Only / Min + PV).
-
Session Persistence: It correctly keeps the session alive (0A) during power dips instead of terminating it.
It takes the entities provided by the ABB Modbus integration (Current Limit Number & Charging Switch) and manages them automatically.
You can find it here: https://github.com/JernejHren/EVSCI
P.S. It requires a sensor that reports the current Tariff Block (as an integer 1-5). This is used to determine the power limit for the current time of day.
1 Like
First month behind with this integration. Managed to make load balancing using data from Homewizard P1 energy meter.
One thing that I do not understand. How the starting and stoping charging works compared to ABB app? There is something I do not understand. When I stop charging via integration the restart does not work. I needs to be started from phone app.
I haven’t found a good solution for starting/tracking/pausing/stopping charging session. As already partly described in readme on GitHub: GitHub - JernejHren/ABB-Terra-AC
Per abb Modbus documentation we can send start charging command and stop charging command. There is no way to check in which state is charging station.
Current start/stop switch works in a way that it sends start charging command waits for 7 seconds, checks for charging state and assumes the state of charging station. When assumption is wrong it stops working as expected
The work around for pausing charging is to set charging current to 0 amps.
The other workaround for restarting session manually is starting, stopping and finally starting session through integration UI.
The abb app works through OCPP protocol which works differently than Modbus.
If anyone have any suggestion how to implement start/stop session better I am open to it.
Hi,
I made a test and replaced that start stop switch with separate start and stop buttons. Quickly tested it work quite fine, no need any additional clicks.
I can send the test code to you if you want to evaluate.
I tried that solution before I published integration but did not like it, because with buttons there is no way of knowing if charging session is already started or not.
The best solution is not to use stop charging command when you want to pause charging but use charging current 0A instead as charging station supports that. In this way you use start command at the beginning of charging session and stop command at the end and you always know if charging session is active or not.
I use my evsci integration for adjusting charging for two months without any start stop problems