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
+6-9Lines changed: 6 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,25 +35,22 @@ RabbitMQ already excels at message durability and routing, but traditionally the
35
35
## Installation
36
36
37
37
This plugin works only with modern versions of RabbitMQ 4.x based on AMQP 1.0.
38
+
You can [build from source](https://www.rabbitmq.com/plugin-development.html) or you can download the latest release build from GitHub. Then, unzip and place the `rabbitmq_web_ocpp-4.x.x.ez` file into your `/etc/rabbitmq/plugins/` folder.
38
39
Like all plugins, it [must be enabled](https://www.rabbitmq.com/plugins.html) before it can be used:
39
40
40
41
```bash
41
42
# this might require sudo
42
43
rabbitmq-plugins enable rabbitmq_web_ocpp
43
44
```
44
45
45
-
## Documentation
46
-
47
-
For all configuration options, please refer to the nearly identical plugin, [RabbitMQ Web MQTT guide](https://www.rabbitmq.com/web-mqtt.html).
48
-
46
+
Detailed instructions on how to install a plugin into RabbitMQ broker can be found [here](https://www.rabbitmq.com/plugins.html#installing-plugins).
49
47
50
-
## Building From Source
48
+
Note that release branches (`v4.1.x` vs. `main`) and target RabbitMQ version need to be taken into account
This directory contains Python examples for handling OCPP (Open Charge Point Protocol) messages using RabbitMQ native OCPP to AMQP plugin. It uses the popular python OCPP lib, [mobilityhouse/ocpp](https://github.com/mobilityhouse/ocpp).
4
+
5
+
## Files
6
+
7
+
-`server.py` - CSMS / OCPP server
8
+
-`amqp_charge_point.py` - Overrides the original ChargePoint class
9
+
-`requirements.txt` - Python dependencies
10
+
11
+
## Key Differences from traditional WebSocket Approach
12
+
13
+
- Uses RabbitMQ message broker for communication
14
+
- Messages are persistent and can survive connection drops
0 commit comments