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
rscp2mqtt offers the option for setting configuration parameters by a config file named .config.
4
+
5
+
Starting with release v3.38 configuration can also be set via environment variables. This simplifies the start of a Docker container, as no .config file is required.
6
+
7
+
If you use both, the environment variables overwrite the parameters set with .config! (Exception: parameters that can be set multiple times).
The parameters FORCE_PUB and INFLUXDB_TOPIC can be set multiple times in the configuration file.
68
+
This is not possible via environment variables, as the values would be overwritten. Therefore, please use FORCE_PUB_01, FORCE_PUB_02, INFLUXDB_TOPIC_01, INFLUXDB_TOPIC_02, INFLUXDB_TOPIC_03 etc.
The prefix of the topics can be configured by the attribute PREFIX. By default all topics start with "e3dc". This can be changed to any other string that MQTT accepts as a topic, max. 24 characters. E.g. "s10" or "s10/1".
113
+
114
+
If your system has more than one battery string (e.g. S10 Pro), you have to configure the parameter BATTERY_STRINGS accordingly.
115
+
Battery topics that belong to a battery string are extended by the number of the battery string.
116
+
Battery modules (DCB topics) are numbered consecutively.
117
+
118
+
Logging can be configured for messages that the home power station output in response to a request.
119
+
Messages are collected including a counter for the number of occurrences.
120
+
The errors will be logged in a bundle at midnight, at the end of the program or by querying with e3dc/set/log/errors.
121
+
This reduces the number of error messages.
122
+
To do this, set in the .config file: `LOG_MODE=BUFFERED`.
123
+
You can also switch off the logging of such messages completely with `LOG_MODE=OFF`.
This software module connects a home power station from E3/DC to an MQTT broker.
9
+
This software module connects a home power station from E3/DC with an MQTT broker. There is also a version that can store data in an InfluxDB.
10
10
11
11
It uses the RSCP interface of the device. The solution is based on the RSCP sample application provided by E3/DC and was developed and tested with a Raspberry Pi, a Linux PC (x86_64) and an Apple MacBook (x86_64).
12
12
13
-
The tool cyclically queries data from the home power station and publishes it to an MQTT broker using these [topics](TOPICS.md).
13
+
The tool cyclically queries data from the home power station and publishes it to the MQTT broker (and the InfluxDB) using these [topics](TOPICS.md).
14
14
15
-
Supported topic areas are:
15
+
It subscribes to the root topic "e3dc/set/#" and forwards incoming requests to the home power station. In this way, the device can be controlled, additional data can be queried and changes can be made to its configuration.
16
16
17
-
- Energy topics for today
18
-
- Current power values
19
-
- Autarky and self-consumption
20
-
- Battery status
21
-
- Energy management (EMS) power settings
22
-
- Data from yesterday and the current week, month and year
23
-
- Values of the power meter (PM)
24
-
- Values of the photovoltaic inverter (PVI)
25
-
- Values of the emergency power supply (EP)
26
-
- Values of wallboxes (WB)
27
-
28
-
For continuous provision of values, you can configure several topics that are published in each cycle. Default: Only modified values will be published.
17
+
Please also take a look at the [release notes](RELEASE.md).
29
18
30
19
## Features
31
20
32
-
- E3/DC [wallbox](WALLBOX.md)topics
21
+
- E3/DC [wallbox](WALLBOX.md)support
33
22
-[InfluxDB](INFLUXDB.md) support
34
-
- Topics for temperatures (battery, PVI)
35
-
- Idle periods
36
-
- System error messages
37
-
- Details of the battery modules (DCB)
38
-
- Units as InfluxDB tags
39
23
- Battery SOC limiter
40
-
- Docker images at https://hub.docker.com/r/pvtom/rscp2mqtt
41
24
-[Dashboard](https://github.com/pvtom/rscp2mqtt-dashboard) is available
42
-
- Configuration of the topics that will be published to InfluxDB (INFLUXDB_TOPIC)
43
-
- Multiple battery strings are supported (BATTERY_STRINGS parameter)
44
-
- Automatic detection of the number of PVI trackers
-[Additional tags and topics](NEWTAGS.md) by configuration
51
-
- Raw data mode
52
-
53
-
Please also take a look at the [release notes](RELEASE.md).
28
+
-[Additional tags and topics](NEWTAGS.md) by configuration and raw data mode
54
29
55
30
## Docker
56
31
57
32
Instead of installing the package you can use a [Docker image](DOCKER.md) for Linux platforms (not MacOS).
58
33
59
-
## Prerequisites
34
+
## Local Installation
35
+
36
+
If the software is to be installed locally rather than via Docker, carry on the following steps:
37
+
38
+
### Prerequisites
60
39
61
40
- An MQTT broker in your environment
62
41
- rscp2mqtt needs the library libmosquitto. For installation please enter:
@@ -75,15 +54,15 @@ On MacOS try
75
54
brew install mosquitto curl
76
55
```
77
56
78
-
## Cloning the Repository
57
+
###Cloning the Repository
79
58
80
59
```
81
60
sudo apt-get install git # if necessary
82
61
git clone https://github.com/pvtom/rscp2mqtt.git
83
62
cd rscp2mqtt
84
63
```
85
64
86
-
## Compilation
65
+
###Compilation
87
66
88
67
To build a program version without InfluxDB use:
89
68
```
@@ -95,7 +74,7 @@ To build a program version including InfluxDB support use:
95
74
make WITH_INFLUXDB=yes
96
75
```
97
76
98
-
## Installation
77
+
###Installation
99
78
100
79
```
101
80
sudo mkdir -p /opt/rscp2mqtt
@@ -111,6 +90,10 @@ cp -a rscp2mqtt /opt/rscp2mqtt
111
90
112
91
## Configuration
113
92
93
+
The tool can be configured in two ways.
94
+
95
+
### Configuration via Config File
96
+
114
97
Copy the config template file into the directory `/opt/rscp2mqtt`
115
98
```
116
99
cp config.template /opt/rscp2mqtt/.config
@@ -124,27 +107,14 @@ nano .config
124
107
```
125
108
The configuration parameters are described in the file.
126
109
127
-
The prefix of the topics can be configured by the attribute PREFIX. By default all topics start with "e3dc". This can be changed to any other string that MQTT accepts as a topic, max. 24 characters. E.g. "s10" or "s10/1".
128
-
129
-
If your system has more than one battery string (e.g. S10 Pro), you have to configure the parameter BATTERY_STRINGS accordingly.
130
-
Battery topics that belong to a battery string are extended by the number of the battery string.
131
-
Battery modules (DCB topics) are numbered consecutively.
132
-
133
-
Find InfluxDB configurations in [InfluxDB](INFLUXDB.md).
134
-
135
-
The parameter FORCE_PUB can occur several times. You can use it to define topics that will be published in each cycle, even if the values do not change. To check the definition, look at the log output after the program start.
110
+
### Configuration via Environment Variables
136
111
137
-
Logging can be configured for messages that the home power station output in response to a request.
138
-
Messages are collected including a counter for the number of occurrences.
139
-
The errors will be logged in a bundle at midnight, at the end of the program or by querying with e3dc/set/log/errors.
140
-
This reduces the number of error messages.
141
-
To do this, set in the .config file: `LOG_MODE=BUFFERED`.
142
-
You can also switch off the logging of such messages completely with `LOG_MODE=OFF`.
143
-
If every event is to be logged: `LOG_MODE=ON`.
112
+
Program parameters can also be set via environment variables. This simplifies the start of a Docker container, as no .config file is required.
113
+
Please find more [here](CONFIG.md).
144
114
145
115
## Program Start
146
116
147
-
Start the program:
117
+
Program start if the tool has been installed locally:
148
118
```
149
119
./rscp2mqtt
150
120
```
@@ -160,7 +130,7 @@ or to show the help page
160
130
If everything works properly, you will see something like this:
161
131
162
132
```
163
-
rscp2mqtt [3.37]
133
+
rscp2mqtt [3.38]
164
134
E3DC system >192.168.178.111:5033< user: >your E3DC user<
0 commit comments