"mqtt-use-json-format-for-default-downlink-topics-hint":"When enabled, the platform will use Json payload format to push attributes and RPC via the following topics: <b>v1/devices/me/attributes/response/$request_id</b>, <b>v1/devices/me/attributes</b>, <b>v1/devices/me/rpc/request/$request_id</b>, <b>v1/devices/me/rpc/response/$request_id</b>. This setting does not impact attribute and rpc subscriptions sent using new (v2) topics: <b>v2/a/res/$request_id</b>, <b>v2/a</b>, <b>v2/r/req/$request_id</b>, <b>v2/r/res/$request_id</b>. Where <b>$request_id</b> is an integer request identifier.",
"mqtt-send-ack-on-validation-exception":"Send PUBACK on PUBLISH message validation failure",
"mqtt-send-ack-on-validation-exception-hint":"By default, the platform will close the MQTT session on message validation failure. When enabled, the platform will send publish acknowledgment instead of closing the session.",
"mqtt-protocol-version":"Protocol version",
"snmp-add-mapping":"Add SNMP mapping",
"snmp-mapping-not-configured":"No mapping for OID to time series/telemetry configured",
"snmp-timseries-or-attribute-name":"Time series/attribute name for mapping",