This project allows you to set the charge speed of a Shell Recharge Advanced 3.0 charging point by emulating a Xemex CSMB.
ESPhome device acting as a Xemex CSMB by simulating a Modbus RTU Slave/Client/Server that can be polled by a master (e.g. a EV Wallbox like Shell Recharge Advanced 3.0) and delivers IREGs and HREGs which can be controlled arbitrarily. Currently I'm including a Home Assistant automation that uses values from my Shelly 3EM. It's based on the work from NMOptimization. Originally posted on a thread called My New Motion integration EV Charging from Shell newmotion
The Xemex CSMB is used to measure the current on up to 3 phases. Based on the actual current measurements, the Shell Recharge 3.0 can decrease or increase the power that can be consumed by the connected car.
https://xemex.eu/products/meters-sensors/csmb/
https://xemex.eu/wp-content/uploads/2021/07/User-manual-CSMB-1.0.pdf
Page 9 of the user manual contains info on the supported modbus functions.
https://a.storyblok.com/f/85281/x/e035ddb473/17srqic01_advanced-3-0_quick-installation-guide.pdf
https://my-instructions.com/shellrecharge/advanced-3.0/?locale=en-GB
https://esphome.io/components/modbus_controller.html
https://www.modbustools.com/modbus.html
- Connect ESP32 dev board to RS485 module.
- Connect RS485 A and B connectors to the A and B wire that goes to the Shell Recharge 3.0 Wallbox.
- Build and flash the firmware based on the sample ESPHome config.
- Add new device in HomeAssistant.
- Now you should be able to set the ctXcurrent numbers. When you set them using HomeAssistant, the values are also reported to your Wallbox.
- Setup an automation to configure the charge speed. Here you can find a charge automation
- Set the input_number main_maximal_current to the correct value
- My house has a single phase - 40 A connection to the power grid. The house also has a photovoltaic installation that delivers up to 5kW peak. My automation tries to optime power consumption from the sun.
- In a sister project, I've pulled all data from my Xemex CSMB.
- The real CSMB has 1 CT connected to CT1. Using my custom modbus client, I could see that the register for CT1 contained the actual current. The other to registers ( CT2 and CT3 ) had a non-changing value, which I took over in the ESPHome config.
- Immediately after booting, the Shell Recharge 3.0 Wallbox first requests the Device Code register (0x4002). It expects '20802' as a response. If not, it'll continue retrying.
- The Shell Recharge 3 Wallbox requests the 3 CT registers every 2 seconds.
- You have to know what the max Current ( in Amps ) setting is on your Wallbox. In my case, this was set to 37.8 Amps. As soon as the fake CSMB starts reporting values higher than 37.8 Amps, my charging would decrease. Set the input_number main_maximal_current to the correct value.
- The wallbox refuses to limit the current to a value lower than 8A. If you try to do so, the wallbox will set its limit to 0A and charging will stop (even if the car supports charging at a lower current).
Some info on the sensors that I used in the Automation.
-
shell3em_main_current is the current on my cable between grid and house. This number is always positive, even if my house ( thanks to the pv - solar panels ) is producing more electricity than it consumes. If it reads 5 Amp, it can be that my house is consuming 5 Amp from the grid, or it can be that my house is delivering 5 Amp to the grid.
-
shell3em_main_power_factor is the power factor which ranges between -1 and 1. If the number is negative, that means that my house is producing more energy than it consumes which means that the excess energy is delivered to the grid. If the number is positive, the house is consuming from the grid. Usually the value is either very close to 1 when consuming, or very close to -1 when delivering to the grid.
Multiplying the 2 previous parameters give me a single number with the total of Amps consumed. Negative numbers for delivering.
- shelly3em_laadpaal_current is the current on the "laadpaal". "Laadpaal" is Dutch for Wall Charger. Since I know that the Wall Charger will always consume energy, I didn't multiply the number with its corresponding power_factor.
In one of my dashboards I created a dropdown menu which allows me to set the charge mode that is used by the charge automation.
type: custom:mushroom-select-card
entity: input_select.charge_mode
secondary_info: last-changed
The Charge speed is set to the value in input_number.chargepoint_manual_current . Note that total consumption can be higher or lower based on other consumers and producers of power. The screemshot was taken at night time, so solar panels didn't produce anything.
The total house consumption stays at the value in input_number.main_manual_current . Note that it the charge speed will go up or down based on other electrical consumers ( washing machines, toaster,... ) or producers ( typically solar panels or your in-house fusion reactor ).
Note on picture: as you can see, the charging session started as Max Speed
Note that this show the wiring that I created. Other configurations are possible.
Power: I removed the micro-usb plug from an old USB cable and looked for the Ground (GND) and +5V wires. Using a bread board, I made the following connections.
- connect the GND wire from the USB cable to both a GND Pin on the ESP32 and the GND Pin on the RS485.
- connect the -5V wire from the USB cable to both the 5V Pin on the ESP32 and the VCC Pin on the RS485.
Data
- connect a wire between the ESP32 G18 and the RS485 TXD Pin
- connect a wire between the ESP32 G19 and the RS485 RXD Pin
Link to product page on Azdelivery.de
Link to amazon.com.be
