6 |
7 | Fully configurable Mqtt to Mqtt gateway.
8 |
9 | - **Backend**: NodeJS, Express, Mqttjs, Aedes Mqtt Broker, Webpack
10 | - **Frontend**: Vue, [Vuetify](https://github.com/vuetifyjs/vuetify)
11 |
12 | ## Why
13 |
14 | There is almost an MQTT gateway for every protocol out there.
15 |
16 | The problem is every gateway maps reads and writes in different ways depending on the protocol used. There isn't a standard way to map a protocol in MQTT topics and also there isn't a standard payload, some sends a JSON payload with different properties (like `val` or `value` or `data` for the value and `tms` `time` `timestamp` for the timestamp/date), others use a payload with just a numeric value.
17 |
18 | This gateway inits an MQTT broker that sits between your MQTT gateways (or devices) and your broker to parse incoming/outgoing MQTT messages from/to your broker in the format you need.
19 |
20 | Here is an example schema of how it works:
21 |
22 | 
23 |
24 | Note here there are some bold text **GET/SET** **from/to**. More about them in docs
25 |
26 | ## :electric_plug: Installation
27 |
28 | ``` bash
29 | # Clone repo
30 | git clone https://github.com/robertsLando/
31 |
32 | cd Mqtt2Mqtt
33 |
34 | # install dependencies
35 | npm install
36 |
37 | # build for production with minification
38 | npm run build
39 |
40 | # Start the server
41 | npm start
42 | ```
43 |
44 | ## Usage
45 |
46 | Once the app is running open the web browser to 
9 | Press '+' to add a property map
139 |Write the function here. Args are topic and payload. The function must return an Object or an Array of Objects like:{topic : "the/topic", payload: "{"temp": 20}"}. Attention: both payload and topic must be type of string
<%= error.stack %>4 | --------------------------------------------------------------------------------