You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-10Lines changed: 12 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Remotely monitors and controls a Mercedes-Benz Wallbox Home EV Charger via The T
6
6
7
7
This monitor allows [Home Manager](https://github.com/roscoe81/Home-Manager) to interwork with an EV charger over LoRaWAN via The Things Network. It can monitor the state of the EV charger, as well as performing lock outlet, unlock outlet and reset charger commands using the EV charger's Modbus RS485 interface (* See note about downlink command timing). The Things Network is used to support charger locations that aren't able to provide wifi coverage (e.g. in a basement garage). It requires customised TTN payload formats that can be found [here](https://github.com/roscoe81/ev-charger-monitor/tree/main/TTN%20Payload%20Formats) and the setup of a mosquitto bridge on the Home Manager side of the system.
8
8
9
-
* Note that the TTN functionality provides timely uplinking of charger state data, but downlink data (i.e. commands to the charger) are only sent after an uplink message. Therefore commands to the charger are not sent immediately and will be delayed. This does impact the functionality, but it's been minimised by varying the loop timings, based on the charger state.
9
+
* Note that the TTN functionality provides timely uplinking of charger state data, but downlink data (i.e. commands to the charger) are only sent after an uplink message. Therefore commands to the charger are not sent immediately and will be delayed. This does impact the functionality, but it's been minimised by varying the state heartbeat frequency, based on the charger state.
@@ -17,29 +17,31 @@ The [monitor](https://github.com/roscoe81/ev-charger-monitor/tree/main/Photos) u
17
17
## Operation
18
18
The system can sense the following charger states:
19
19
20
-
1. "Not Connected": The EV is not connected to the charger
20
+
1. "Not Connected": The EV is not connected to the charger. Charger state heartbeats are sent over TTN every 2 hours when in this state.
21
21
22
-
2. "Connected and Locked": The EV is connected to the charger and the key switch on the charger has not been turned to start charging
22
+
2. "Connected and Locked": The EV is connected to the charger and the key switch on the charger has not been turned to start charging. Charger state heartbeats are sent over TTN every 5 minutes when in this state.
23
23
24
-
3. "Charging": The charger is charging the EV battery
24
+
3. "Charging": The charger is charging the EV battery. Charger state heartbeats are sent over TTN every 15 minutes when in this state.
25
25
26
-
4. "Charged": The EV is charged to the required level. This state is normally triggered by the EV advising the charger.
26
+
4. "Charged": The EV is charged to the required level. This state is normally triggered by the EV advising the charger. Charger state heartbeats are sent over TTN every 30 minutes when in this state.
27
27
28
-
5. "Disabled": The charger has been set to "Lock Outlet" or "E0" mode and is disabled.
28
+
5. "Disabled": The charger has been set to "Lock Outlet" or "E0" mode and is disabled. Charger state heartbeats are sent over TTN every 15 minutes when in this state.
29
29
30
30
6. "E2": Not currently used but allows for future maintenance activity enhancements (e.g. setting Device ID).
31
31
32
32
The system has the following control functions (* See above note about command timing):
33
33
34
34
1. "Reset Charger": It's found that this can be used to commence EV charging when the charger is in the "Connected and Locked" state - even if the charger's key switch is still in the locked state.
35
35
36
-
2. "Lock Outlet": Places the charger in an error mode and interrupts the charging process. This shouldn't be necessary because the EV will stop the charging process when the desired charge level is met.
36
+
2. "Lock Outlet": Places the charger in an error mode (E0)and interrupts the charging process. This shouldn't be necessary because the EV will stop the charging process when the desired charge level is met.
37
37
38
-
3. "Unlock Outlet": Takes the charger out of error mode
38
+
3. "Unlock Outlet": Takes the charger out of error mode (E0).
39
39
40
-
ACKs are uplinked via TTN when each control command has been received. There's the potential to add Status Report and Serial Number/Device Type request commands in the future.
40
+
ACKs are uplinked via TTN when each control command has been received.
41
41
42
-
The charger states can be monitored and charger commands can be sent by using the Apple Home [App](https://github.com/roscoe81/ev-charger-monitor/blob/main/Photos/IMG_5273.PNG) and [Home Manager](https://github.com/roscoe81/Home-Manager). They can also be used to schedule charging using an Apple Home App Automation.
42
+
There's the potential to add Status Report and Serial Number/Device Type request commands in the future.
43
+
44
+
The charger states can be monitored and charger commands can be sent by using the Apple Home [App](https://github.com/roscoe81/ev-charger-monitor/blob/main/Photos/IMG_5273.PNG) and [Home Manager](https://github.com/roscoe81/Home-Manager). They can also be used to schedule charging times to benefit from time-of-use electricity tariffs, through an Apple Home App Automation. Other monitoring and control apps could be developed by using the TTN API(mqtt).
43
45
44
46
## License
45
47
This project is licensed under the MIT License - see the LICENSE.md file for details
0 commit comments