Domnev: Difference between revisions

From Teltonika Networks Wiki
No edit summary
No edit summary
Line 89: Line 89:
[[File:Node-red-subscriber-configuration.png|border|class=tlt-border|1094x1094px]]
[[File:Node-red-subscriber-configuration.png|border|class=tlt-border|1094x1094px]]


# '''Server''': Server name;
<table class="nd-mantable">
# '''Action''': Subscribe to single topic
    <tr>
# '''Topic''': Created topic;
        <th class="left">Number</th>
# '''QoS''': 0;
        <th class="left">Field</th>
# '''Output''': auto-detect;
      <th class="left">Value</th>
# '''Edit''':
    </tr>
# '''Server & Port''': Server IP & Port;
<tr>
# '''Update''':
      <td class="left">1</td>
# '''Done''':
        <td class="left">'''Server'''</td>
      <td class="left">'''Server name'''</td>
    </tr>
<tr>
        <td class="left">2</td>
      <td class="left"">'''Action'''</td>
      <td class="left">'''Subscribe to single topic'''</td>
    </tr>
<tr>
        <td class="left">3</td>
      <td class="left">'''Topic'''</td>
      <td class="left">'''Created topic name'''</td>
    </tr>
<tr>
        <td class="left">4</td>
      <td class="left">'''QoS'''</td>
      <td class="left">'''0'''</td>
    </tr>
<tr>
        <td class="left">5</td>
      <td class="left">'''Output'''</td>
      <td class="left">'''Auto-detect'''</td>
    </tr>
<tr>
        <td class="left">6</td>
      <td class="left">'''Edit'''</td>
      <td class="left">'''Configure MQTT-Broker node'''</td>
    </tr>
 
<tr>
        <td class="left">7</td>
      <td class="left">'''Server'''</td>
      <td class="left">'''Server IP'''</td>
    </tr>
<tr>
        <td class="left">8</td>
      <td class="left">'''Port'''</td>
      <td class="left">'''Used Port'''</td>
    </tr>
 
<tr>
        <td class="left">9</td>
      <td class="left">'''Update'''</td>
      <td class="left">'''Renew MQTT-Broker node configuration'''</td>
    </tr>
 
<tr>
        <td class="left">10</td>
      <td class="left">'''Done'''</td>
      <td class="left">'''Save MQTT in node configuration'''</td>
    </tr>
</table>


=====Results=====
=====Results=====
----
----


====Via HTTP====
====M-Bus Data to Server via HTTP====
This sections contains information on how to send M-Bus data to the server on Node-RED using HTTP protocol.
This sections contains information on how to send M-Bus data to the server on Node-RED using HTTP protocol.
----
----

Revision as of 15:50, 30 January 2023

The information in this page is updated in accordance with 00.07.03.1 firmware version .

Introduction

This article contains instructions on how to send M-Bus data to the server using various protocols.

Configuration overview and prerequisites

Before we begin, let's take a look at the configuration that we are attempting to achieve and the prerequisites that make it possible.

Prerequisites:

  • TRB143;
  • M-Bus device;
  • Server;
  • An end device (PC, Laptop, Tablet, Smartphone) for configuration;

If you're having trouble finding any page or some of the parameters described here on your device's WebUI, you should turn on "Advanced WebUI" mode. You can do that by clicking the "Basic" button under "Mode," which is located at the top-right corner of the WebUI.

Node-RED installation and setup

Configuration

Data to server

Data to Server feature provides you with the possibility to set up data senders that collect data from various sources and periodically send it to remote servers.


Via MQTT

This sections contains information on how to send M-Bus data to the server on Node-RED using MQTT protocol.


Data to Server configuration

File:Mbus data to server MQTT.png

  1. Enable instance;
  2. Name: enter desired instance name;
  3. Data source: M-bus;
  4. Protocol: MQTT;
  5. JSON format: enter what data you would like to send;
  6. URL/Host/Connection string: enter address of server;
  7. Port: enter server port;
  8. Topic: enter desired topic name;
M-Bus configuration

  1. Enable M-Bus;
  2. Enter desired instance name;
  3. Add;

File:M bus instance configuration.png

  1. Enable instance;
  2. Period: enter desired period;
  3. BLOGAS - NAME NEREIKIA

File:M bus slave configuration.png

  1. Enable request configuration;
  2. Slave address: enter desired slave address;
  3. Data type: select desired data type (this time we will be using XML);
  4. Save & apply changes.
Node-RED configuration

Below you can see Node-Red block diagram that is used to receive data:

  • aedes broker
  • MQTT in
  • Debug

File:Node-red-broker-configuration.png
File:Node-red-debug-config.png
  1. MQTT Port: 1883;
  2. WS Bind: port;
  3. Done;

Everything else can be left as default.

  1. Output: msg. payload;
  2. To: debug window;
  3. Done;

Everything else can be left as default.


Number Field Value
1 Server Server name
2 Action Subscribe to single topic
3 Topic Created topic name
4 QoS 0
5 Output Auto-detect
6 Edit Configure MQTT-Broker node
7 Server Server IP
8 Port Used Port
9 Update Renew MQTT-Broker node configuration
10 Done Save MQTT in node configuration
Results

M-Bus Data to Server via HTTP

This sections contains information on how to send M-Bus data to the server on Node-RED using HTTP protocol.


Data to Server configuration

Number Field Value
1 Enable On
2 Name Your desired name
3 Data source M-Bus data
4 Protocol HTTP(s)
5 JSON format What data to send
6 URL/Host/Connection string Server IP address
M-Bus configuration

  1. Enable request configuration;
  2. Slave address: enter desired slave address;
  3. Data type: select desired data type (this time we will be using HEX);
  4. Save & apply changes.
Node-RED configuration

Results

MQTT broker

MQTT Broker is an entity that listens for connections on the specified port and relays received messages to MQTT client.


MQTT broker configuration

M-Bus configuration

Node-RED configuration

Results

See Also

External links