Difference between revisions of "Domnev"

From Teltonika Networks Wiki
 
(26 intermediate revisions by the same user not shown)
Line 1: Line 1:
<p style="color:red">The information in this page is updated in accordance with [https://wiki.teltonika-networks.com/view/FW_%26_SDK_Downloads'''00.07.4'''] firmware version .</p>
+
<p style="color:red">The information on this page is updated in accordance with the [https://wiki.teltonika-networks.com/view/FW_%26_SDK_Downloads'''00.07.08'''] firmware version .</p>
==Introduction==
+
__TOC__
 
+
==Summary==
==Configuration overview and prerequisites==
+
This article contains instructions on how to send M-Bus data to the server using various protocols.
  
 +
==Configuration overview & 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.
 
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''':
 
'''Prerequisites''':
* Two RUT/RUTX series routers with RUTOS firmware;
+
* TRB143;
* An end device (PC, Laptop) for configuration;
+
* 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.
 
[[File:Networking rut9 manual webui basic advanced mode.gif|border|center|class=tlt-border|1102x52px]]
 
  
==Topology==
+
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
 +
| series = RUTX
 +
}}
  
RUT1 - RUTX11 as a hub. It will be our "default gateway" for spoke device. RUTX11 has a LAN subnet of 192.168.11.0/24 configured on it, which should be reachable by the spoke.
 
  
RUT2 - RUT955 as a spoke. It will be connecting to a hub for basic internet access. RUT955 has a lan subnet of 192.168.9.0/24 configured on it, which should be reachable by the hub.
+
==Adding M-Bus devices==
 +
To add a new device to the configuration press [[File:Add Button.png|60x90px]] button which is shown below.
  
==RUT1 (Hub) configuration==
+
[[File:Mbus adding new device.png||border|class=tlt-border]]
Start by configuring HUB (RUT1) device. Login to the WebUI, navigate to '''Services → VPN → IPsec''' and add a new IPsec instance. Configure everything as follows.
 
  
'''Note:''' '''''Not specified fields can be left as-is or changed according to your needs.'''''
+
===Device configuration===
===Instance configuration===
 
 
----
 
----
<table class="nd-othertables_2">
+
You will be granted to a new window. Configure your M-Bus device accordingly:
    <tr>
+
 
        <th width=330; style="border-bottom: 1px solid white;></th>
+
# '''Name''': Enter the desired name of the M-Bus device
        <th width=800; style="border-bottom: 1px solid white"; rowspan=2>[[File:IPsec HUB.png|border|class=tlt-border|755x406px|right]]</th>
+
# '''Address type''': select which M-Bus address will be used
    </tr>
+
# '''Primary/Secondary address''': specify M-Bus address
    <tr>
+
 
        <td style="border-bottom: 4px solid white>
+
[[File:Mbus adding new device configuration v3.png|border|class=tlt-border]]
# '''''Enable''''' instance;
+
 
# Authentication method - '''''Pre-shared key;'''''
+
Test if the M-Bus device is reachable by a specified primary/secondary address. To do so click on [[File:Ping_device_option_mbus.png|110x110px]]. You might get on of two outputs:
# Pre-shared key - '''''your desired password;'''''
+
 
        </td>
+
* If you have specified correct primary/secondary address, you will receive:
    </tr>
+
[[File:Mbus device pingable v2.png|border|class=tlt-border|300px]]
</table>
+
 
 +
* If you have specified incorrect primary/secondary address, you will receive (if you do not know what address should be used, refer to the Scanning for available M-Bus devices (PRIDET URL) secion:
 +
[[File:Mbus device not pingable v2.png|border|class=tlt-border|300px]]
 +
 
 +
Once finished, save the configuration by clicking [[File:Savenapply button.png|Savenapply button.png]].
  
===Connection configuration===
+
===Scanning for available M-Bus devices===
 
----
 
----
  
<table class="nd-othertables_2">
+
If you are not sure what address your M-Bus devices have, you can try scanning for the available M-Bus devices. To do so click on [[File:Scan button.png]] button.
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec HUB Connection.png|border|class=tlt-border|753x368px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# Mode - '''''Start;'''''
 
# Type - '''''Tunnel;'''''
 
# Local subnet - '''''0.0.0.0/.0;'''''
 
# Key exchange - '''''IKEv2;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
 +
====Scan settings====
 
----
 
----
<table class="nd-othertables_2">
+
You will be granted to a new window. Configure scan settings accordingly:
    <tr>
+
 
        <th width=330; style="border-bottom: 1px solid white;></th>
+
# '''Scan type''': select which M-Bus address will be scanned
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec HUB Connection Advanced.png|border|class=tlt-border|752x541px|right]]</th>
+
# '''Scan range''': From what M-Bus address scanning will start and M-Bus address until scanning will be performed.
    </tr>
+
[[File:Mbus scan.png|border|class=tlt-border]]
    <tr>
+
 
        <td style="border-bottom: 4px solid white>
+
To start the scan click on [[File:Start scan button.png]] button.
# '''''Enable''''' '''''Local firewall;'''''
 
# Remote source IP - '''''10.20.30.0/24;'''''
 
# Remote DNS '''''9.9.9.9;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
===Proposal configuration===
+
====Found devices====
 
----
 
----
 +
Once the scan is finished you should see the list of M-Bus devices that TRB143 were able to find:
 +
 +
[[File:Mbus scanned devices add.png|border|class=tlt-border]]
 +
 +
You can either [[File:Pencil2.png]] '''(1)''' M-Bus devices primary address or [[File:Add Button.png|60x90px]] '''(2)''' to the M-Bus devices list.
 +
 +
==Gathering M-Bus data==
 +
 +
If the device successfully added to the list, under the General settings you should see that the Status changes to <span style="color:green">Active</span>.
  
<table class="nd-othertables_2">
+
[[File:Mbus status active v2.png|border|class=tlt-border]]
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec Phase1.png|border|class=tlt-border|742x254px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# Encryption - '''''AES256;'''''
 
# Authentication - '''''SHA512;'''''
 
# DH group - '''''ECP521;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
 +
===Data collecting groups===
 
----
 
----
<table class="nd-othertables_2">
+
To reach data collecting groups configuration press [[File:Pencil2.png]] button. [[File:Add Button.png|60x90px]] button lets you to create a new instance.
    <tr>
+
 
        <th width=330; style="border-bottom: 1px solid white;></th>
+
[[File:Mbus data collect overview.png|border|class=tlt-border]]
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec Phase2.png|border|class=tlt-border|748x257px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# Encryption - '''''AES128;'''''
 
# Authentication - '''''SHA256;'''''
 
# DH group - '''''ECP521;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
==RUT2 (Spoke) configuration==
+
====Data collecting group instance====
Login to the RUT2 WebUI, navigate to '''Services → VPN → IPsec''' and add a new IPsec instance. Configure everything as follows.
 
===Instance configuration===
 
 
----
 
----
<table class="nd-othertables_2">
 
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec SPOKE.png|border|class=tlt-border|742x399px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# '''''Enable''''' instance;
 
# Remote endpoint - '''''RUT1 public IP;'''''
 
# Authentication method - '''''Pre-shared key;'''''
 
# Pre-shared key - the '''''same password''''' you have '''''set on''''' '''''RUT1''''' when configuring '''''HUB instance;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
===Connection configuration===
+
Each data collection group contains the following information. Configure device accordingly:
 +
 
 +
# '''Enabled''': on
 +
# '''Name''': desired name of the instance
 +
# '''Period''': desired time duration between data retrievals
 +
# '''Data type''': desired data type to process the received data. Depending on your needs you can select between 5 different data types: '''JSON, XML, ASCII, Hexadecimal''' and '''Binary'''.
 +
 
 +
[[File:Mbus data collect group v2.png|border|class=tlt-border]]
 +
 
 +
You can check if your configuration works accordingly by pressing the [[File:Mbus test button.png]] button. You should see the data in a pop-up field:
 +
 
 +
[[File:Mbus TEST output.png|border|class=tlt-border]]
 +
 
 +
====Group values====
 
----
 
----
 +
To reach group values configuration press [[File:Pencil2.png]] button:
 +
 +
[[File:Mbus edit group values.png|border|class=tlt-border]]
 +
 +
There you can adjust additional settings:
 +
 +
# '''Enable''': Enable/disable data group value.
 +
# '''FCB toggle''': FCB (Frame Count-Bit), one-bit counter for reliable server-client communication.
 +
# '''Manufacturer information''': Select to include manufacturer information in the payload.
 +
# '''Selected parameters''': Select to include the all parameters saved from device, or a custom subset of them. If the custom is selected you can specify '''frame''', '''record''' numbers and also a '''paramater'''
 +
 +
[[File:Mbus device groupsa.png|border|class=tlt-border]]
  
<table class="nd-othertables_2">
 
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec SPOKE Connection.png|border|class=tlt-border|761x280px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# Mode - '''''Start;'''''
 
# Type - '''''Tunnel;'''''
 
# '''''Enable''''' '''''default route;'''''
 
# Key exchange - '''''IKEv2;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
===Proposalconfiguration===
+
==Sending data to the server==
 +
This section contains information on how to send M-Bus data to the server using MQTT and HTTP protocols.
 +
 
 +
===Data to Server configuration===
 
----
 
----
<table class="nd-othertables_2">
+
To set up Data to Server, navigate to Services → Data to Server. Enter desired name of the instnace and hit [[File:Add Button.png|60x90px]] button which is shown below.
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec Phase1.png|border|class=tlt-border|742x254px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# Encryption - '''''AES256;'''''
 
# Authentication - '''''SHA512;'''''
 
# DH group - '''''ECP521;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
 +
[[File:Mbus data to server create.png|border|class=tlt-border]]
 +
 +
===Data configuration===
 
----
 
----
<table class="nd-othertables_2">
 
    <tr>
 
        <th width=330; style="border-bottom: 1px solid white;></th>
 
        <th width=800; style="border-bottom: 1px solid white;" rowspan=2>[[File:IPsec Phase2.png|border|class=tlt-border|748x257px|right]]</th>
 
    </tr>
 
    <tr>
 
        <td style="border-bottom: 4px solid white>
 
# Encryption - '''''AES128;'''''
 
# Authentication - '''''SHA256;'''''
 
# DH group - '''''ECP521;'''''
 
        </td>
 
    </tr>
 
</table>
 
  
==Testing configuration==
+
[[File:Mbus data to server configuration.png|border|class=tlt-border]]
After we establish the tunnel, we may observe the following information:
+
 
===RUT1 (Hub) side===
+
 
 +
Once finished configuring Data configuration tab click on [[File:Mbus data to server collection edit.png|160x160px]] button.
 +
 
 +
===Collection configuration===
 
----
 
----
<pre>ipsec status all</pre>
 
  
<pre>
+
[[File:Mbus data to server collection configuration.png|border|class=tlt-border]]
root@Teltonika-RUTX12:~# ipsec statusall
 
Status of IKE charon daemon (strongSwan 5.9.2, Linux 5.4.231, armv7l):
 
  uptime: 74 minutes, since Mar 21 08:52:39 2023
 
  worker threads: 11 of 16 idle, 5/0/0/0 working, job queue: 0/0/0/0, scheduled: 2
 
  loaded plugins: charon aes des sha2 sha1 md4 md5 random nonce x509 revocation constraints pubkey pkcs1 pkcs8 pgp pem openssl gmp xcbc hmac kernel-netlink socket-default stroke vici updown eap-identity eap-mschapv2 xauth-generic
 
Virtual IP pools (size/online/offline):
 
  10.20.30.0/24: 254/1/0
 
Listening IP addresses:
 
  84.xxx.xxx.xxx
 
  192.168.11.1
 
  fd93:51e6:6fe8::1
 
Connections:
 
  HUB-HUB_c:  %any...%any  IKEv2
 
  HUB-HUB_c:  local:  uses pre-shared key authentication
 
  HUB-HUB_c:  remote: uses pre-shared key authentication
 
  HUB-HUB_c:  child:  0.0.0.0/0 === dynamic TUNNEL
 
Security Associations (1 up, 0 connecting):
 
  HUB-HUB_c[2]: ESTABLISHED 74 minutes ago, 84.xxx.xxx.xxx[84.xxx.xxx.xxx]...88.xxx.xxx.xxx[192.168.86.197]
 
  HUB-HUB_c[2]: IKEv2 SPIs: ded11f31c20352dc_i 58ebc8d96264c21e_r*, pre-shared key reauthentication in 89 minutes
 
  HUB-HUB_c[2]: IKE proposal: AES_CBC_256/HMAC_SHA2_512_256/PRF_HMAC_SHA2_512/ECP_521
 
  HUB-HUB_c{3}:  INSTALLED, TUNNEL, reqid 1, ESP in UDP SPIs: c27cb140_i c7382615_o
 
  HUB-HUB_c{3}:  AES_CBC_128/HMAC_SHA2_256_128/ECP_521, 215536 bytes_i (1981 pkts, 1s ago), 126021 bytes_o (499 pkts, 1s ago), rekeying in 14 minutes
 
  HUB-HUB_c{3}:  0.0.0.0/0 === 10.20.30.1/32
 
</pre>
 
  
<pre> /tmp/ipsec/ipsec.conf </pre> command output:
+
Once finished configuring Collection configuration tab click on [[File:Mbus data to server server button.png|160x160px]] button.
<pre>
 
root@Teltonika-RUTX12:~# cat /tmp/ipsec/ipsec.conf
 
# generated by /etc/init.d/ipsec
 
version 2
 
  
conn HUB-HUB_c
+
===Server configuration===
  left=%any
+
----
  right=%any
 
  leftfirewall=yes
 
  rightfirewall=no
 
  ikelifetime=3h
 
  lifetime=1h
 
  margintime=9m
 
  keyingtries=3
 
  dpdaction=none
 
  dpddelay=30s
 
  dpdtimeout=90s
 
  leftauth=psk
 
  rightauth=psk
 
  rightsourceip=10.20.30.0/24
 
  auto=start
 
  leftsubnet=0.0.0.0/0
 
  rightdns=9.9.9.9
 
  aggressive=no
 
  forceencaps=no
 
  type=tunnel
 
  keyexchange=ikev2
 
  esp=aes128-sha256-ecp521!
 
  ike=aes256-sha512-ecp521!
 
</pre>
 
  
===RUT2 (Spoke) side===
+
====HTTP configuration====
 
----
 
----
  
<pre>
+
[[File:Mbus data to server HTTP configuration.png|border|class=tlt-border]]
root@Teltonika-RUT955:~# ipsec statusall
 
Status of IKE charon daemon (strongSwan 5.9.2, Linux 5.4.229, mips):
 
  uptime: 23 hours, since Mar 20 12:21:06 2023
 
  worker threads: 11 of 16 idle, 5/0/0/0 working, job queue: 0/0/0/0, scheduled: 9
 
  loaded plugins: charon aes des sha2 sha1 md4 md5 random nonce x509 revocation constraints pubkey pkcs1 pkcs8 pgp pem openssl gmp xcbc hmac kernel-netlink socket-default stroke vici updown eap-identity eap-mschapv2 xauth-generic
 
Listening IP addresses:
 
  192.168.86.197
 
  192.168.9.1
 
  fd35:98cd:61f0::1
 
Connections:
 
passth_SPOKE_ph2_1_lan:  %any...%any  IKEv1/2
 
passth_SPOKE_ph2_1_lan:  local:  uses public key authentication
 
passth_SPOKE_ph2_1_lan:  remote: uses public key authentication
 
passth_SPOKE_ph2_1_lan:  child:  192.168.9.0/24 === 192.168.9.0/24 PASS
 
SPOKE-SPOKE_c:  %any...84.15.162.30  IKEv2
 
SPOKE-SPOKE_c:  local:  uses pre-shared key authentication
 
SPOKE-SPOKE_c:  remote: [84.15.162.30] uses pre-shared key authentication
 
SPOKE-SPOKE_c:   child:  dynamic === 0.0.0.0/0 TUNNEL
 
Shunted Connections:
 
passth_SPOKE_ph2_1_lan:  192.168.9.0/24 === 192.168.9.0/24 PASS
 
Security Associations (1 up, 0 connecting):
 
SPOKE-SPOKE_c[431]: ESTABLISHED 77 minutes ago, 192.168.86.197[192.168.86.197]...84.15.162.30[84.15.162.30]
 
SPOKE-SPOKE_c[431]: IKEv2 SPIs: ded11f31c20352dc_i* 58ebc8d96264c21e_r, pre-shared key reauthentication in 77 minutes
 
SPOKE-SPOKE_c[431]: IKE proposal: AES_CBC_256/HMAC_SHA2_512_256/PRF_HMAC_SHA2_512/ECP_521
 
SPOKE-SPOKE_c{14}:  INSTALLED, TUNNEL, reqid 1, ESP in UDP SPIs: c7382615_i c27cb140_o
 
SPOKE-SPOKE_c{14}:  AES_CBC_128/HMAC_SHA2_256_128/ECP_521, 136768 bytes_i (536 pkts, 6s ago), 235975 bytes_o (2169 pkts, 1s ago), rekeying in 13 minutes
 
SPOKE-SPOKE_c{14}:  10.20.30.1/32 === 0.0.0.0/0
 
</pre>
 
  
 +
====MQTT configuration====
 +
----
  
<pre>
+
[[File:Mbus data to server MQTT configuration.png|border|class=tlt-border]]
root@Teltonika-RUT955:~# cat /tmp/ipsec/ipsec.conf
 
# generated by /etc/init.d/ipsec
 
version 2
 
 
 
conn passth_SPOKE_ph2_1_lan
 
  type=passthrough
 
  leftsubnet=192.168.9.1/24
 
  rightsubnet=192.168.9.1/24
 
  auto=route
 
  
conn SPOKE-SPOKE_c
+
Once finished configuring Server configuration tab click on [[File:Savenapply button.png|Savenapply button.png]] button.
  left=%any
 
  right=84.15.162.30
 
  leftsourceip=%config
 
  leftfirewall=yes
 
  rightfirewall=no
 
  ikelifetime=3h
 
  lifetime=1h
 
  margintime=9m
 
  keyingtries=3
 
  dpdaction=none
 
  dpddelay=30s
 
  dpdtimeout=90s
 
  leftauth=psk
 
  rightauth=psk
 
  rightsubnet=0.0.0.0/0
 
  auto=start
 
  aggressive=no
 
  forceencaps=no
 
  type=tunnel
 
  keyexchange=ikev2
 
  esp=aes128-sha256-ecp521!
 
  ike=aes256-sha512-ecp521!
 
</pre>
 
  
  
== See also ==
+
==See Also==
  
== External links ==
+
==External links==
 +
[https://flespi.io/#/ Flespi.io]

Latest revision as of 09:32, 22 August 2024

The information on this page is updated in accordance with the 00.07.08 firmware version .

Summary

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

Configuration overview & 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 this 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 "Advanced" button, located at the top of the WebUI.

Networking rutos manual webui basic advanced mode 75.gif


Adding M-Bus devices

To add a new device to the configuration press Add Button.png button which is shown below.

Mbus adding new device.png

Device configuration


You will be granted to a new window. Configure your M-Bus device accordingly:

  1. Name: Enter the desired name of the M-Bus device
  2. Address type: select which M-Bus address will be used
  3. Primary/Secondary address: specify M-Bus address

Mbus adding new device configuration v3.png

Test if the M-Bus device is reachable by a specified primary/secondary address. To do so click on Ping device option mbus.png. You might get on of two outputs:

  • If you have specified correct primary/secondary address, you will receive:

Mbus device pingable v2.png

  • If you have specified incorrect primary/secondary address, you will receive (if you do not know what address should be used, refer to the Scanning for available M-Bus devices (PRIDET URL) secion:

Mbus device not pingable v2.png

Once finished, save the configuration by clicking Savenapply button.png.

Scanning for available M-Bus devices


If you are not sure what address your M-Bus devices have, you can try scanning for the available M-Bus devices. To do so click on Scan button.png button.

Scan settings


You will be granted to a new window. Configure scan settings accordingly:

  1. Scan type: select which M-Bus address will be scanned
  2. Scan range: From what M-Bus address scanning will start and M-Bus address until scanning will be performed.

Mbus scan.png

To start the scan click on Start scan button.png button.

Found devices


Once the scan is finished you should see the list of M-Bus devices that TRB143 were able to find:

Mbus scanned devices add.png

You can either Pencil2.png (1) M-Bus devices primary address or Add Button.png (2) to the M-Bus devices list.

Gathering M-Bus data

If the device successfully added to the list, under the General settings you should see that the Status changes to Active.

Mbus status active v2.png

Data collecting groups


To reach data collecting groups configuration press Pencil2.png button. Add Button.png button lets you to create a new instance.

Mbus data collect overview.png

Data collecting group instance


Each data collection group contains the following information. Configure device accordingly:

  1. Enabled: on
  2. Name: desired name of the instance
  3. Period: desired time duration between data retrievals
  4. Data type: desired data type to process the received data. Depending on your needs you can select between 5 different data types: JSON, XML, ASCII, Hexadecimal and Binary.

Mbus data collect group v2.png

You can check if your configuration works accordingly by pressing the Mbus test button.png button. You should see the data in a pop-up field:

Mbus TEST output.png

Group values


To reach group values configuration press Pencil2.png button:

Mbus edit group values.png

There you can adjust additional settings:

  1. Enable: Enable/disable data group value.
  2. FCB toggle: FCB (Frame Count-Bit), one-bit counter for reliable server-client communication.
  3. Manufacturer information: Select to include manufacturer information in the payload.
  4. Selected parameters: Select to include the all parameters saved from device, or a custom subset of them. If the custom is selected you can specify frame, record numbers and also a paramater

Mbus device groupsa.png


Sending data to the server

This section contains information on how to send M-Bus data to the server using MQTT and HTTP protocols.

Data to Server configuration


To set up Data to Server, navigate to Services → Data to Server. Enter desired name of the instnace and hit Add Button.png button which is shown below.

Mbus data to server create.png

Data configuration


Mbus data to server configuration.png


Once finished configuring Data configuration tab click on Mbus data to server collection edit.png button.

Collection configuration


Mbus data to server collection configuration.png

Once finished configuring Collection configuration tab click on Mbus data to server server button.png button.

Server configuration


HTTP configuration


Mbus data to server HTTP configuration.png

MQTT configuration


Mbus data to server MQTT configuration.png

Once finished configuring Server configuration tab click on Savenapply button.png button.


See Also

External links

Flespi.io