-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Control charging current directly via Modbus #25
Comments
Hi, |
Override the Charging Current in Normal Mode would also be fine. But to make sure, with the actual firmware this is not possible, right? |
Yes, only the commands listed on https://github.com/SmartEVSE/smartevse#modbus-registers (since Version 2.10) |
Hi, |
START/STOP charging is already possible by setting the access bit register 0xA7 |
I'll make the modbus charging current register 0xA6 writeable |
Hey bobosch, that sounds really great, thanks for that! |
Solved with commit 759f2c0 |
BTW: Yes, RS485 settings and the address are hardcoded. |
That's fine, I've also seen it in the EVSE.c I'm already on the same Baudrate and just have to change the address of one of my meters to reserve 1 for the Smart EVSE. |
Hello,
I like the Smart EVSE very much because of its pretty design including the display and it is a economic setup together with the RCM14, very good job!
I would like to integrate Smart EVSE within my Loxone Miniserver via existing Modbus Gateway with some existing SDM630 power meters.
Therefore I would like the visualize the actual state (ready, vehicle connected, charging) in the Loxone App (I think this is already possible) and control the charging current directly via modbus (as I already have all the power and energy information and the necessary logic in loxone).
Is that already possible (maybe I haven’t seen it) or something interesting to integrate in the future?
Maybe it is possible to simply allow an override of the charging current in the Solar Mode.
I would highly appreciate that!
Otherwise: I like the Smart EVSE anyway 😉.
Greetings, Stephan
The text was updated successfully, but these errors were encountered: