Differences

This shows you the differences between two versions of the page.

--- mqtt [2022/01/15 03:18] – ↷ Links adapted because of a move operation 127.0.0.1
+++ mqtt [2023/02/13 15:39] (current) – [JSON Fetch tool in the WebHMI registers configuration] emozolyak
@@ Line 13: / Line 13: @@
 {{ network:mqtt_comm_tab.png?direct&400 |}}
-In the MQTT tab you set credentials neccessary to connect to the client. If you leave them emty, the client will connect to internal broker.
+In the **MQTT tab** you set credentials neccessary to connect to the client. If you leave them emty, the client will connect to internal broker.
+<WRAP center round important 60%>
+Please note that for TLS type authentification you''ll have to provide the necessary credentials, which are mandatory and should be put into respective fields.
+</WRAP>
 {{ network:mqtt_credentials.png?direct&400 |}}
@@ Line 19: / Line 23: @@
 {{ network:mqtt_server_checkbox.png?direct&400 |}}
+===== JSON Fetch tool in the WebHMI registers configuration =====
+With this tool you can exract values by its keys from JSON structures read as String right in the WebHMI register configuration.
+The usage scheme is as follows:
+{{ :iot:mqtt:json-extractor-app-commented.png?direct |}}
+Let's suppose you have a JSON value received from 7bit AirPoint module:
+{{ :iot:mqtt:json-src-reg-example.png?direct&800 |}}
+To extact individual values from this register, you just clone it and then set the checkbox in the new register properties, type in the key needed and select appropriate type for the final value (int, float, string etc.)
+{{ :iot:mqtt:json-extraction-key_.png?direct&800 |}}
+Now your registers for individual JSON keys are ready:
+{{ :iot:mqtt:json-extracted-registers_.png?direct&800 |}}