This is the description of the MQTT API bindings for the UV Light Bricklet. General information and technical specifications for the UV Light Bricklet are summarized in its hardware description.
An installation guide for the MQTT API bindings is part of their general description.
The example code below is Public Domain (CC0 1.0).
1 2 3 4 5 6 | # Change XYZ to the UID of your UV Light Bricklet
setup:
# Get current UV light
subscribe to tinkerforge/response/uv_light_bricklet/XYZ/get_uv_light
publish '' to tinkerforge/request/uv_light_bricklet/XYZ/get_uv_light
|
Download (example-callback.txt)
1 2 3 4 5 6 7 8 9 10 11 | # Change XYZ to the UID of your UV Light Bricklet
setup:
# Handle incoming UV light callbacks
subscribe to tinkerforge/callback/uv_light_bricklet/XYZ/uv_light
publish '{"register": true}' to tinkerforge/register/uv_light_bricklet/XYZ/uv_light # Register uv_light callback
# Set period for UV light callback to 1s (1000ms)
# Note: The UV light callback is only called every second
# if the UV light has changed since the last call!
publish '{"period": 1000}' to tinkerforge/request/uv_light_bricklet/XYZ/set_uv_light_callback_period
|
Download (example-threshold.txt)
1 2 3 4 5 6 7 8 9 10 11 12 | # Change XYZ to the UID of your UV Light Bricklet
setup:
# Get threshold callbacks with a debounce time of 10 seconds (10000ms)
publish '{"debounce": 10000}' to tinkerforge/request/uv_light_bricklet/XYZ/set_debounce_period
# Handle incoming UV light reached callbacks
subscribe to tinkerforge/callback/uv_light_bricklet/XYZ/uv_light_reached
publish '{"register": true}' to tinkerforge/register/uv_light_bricklet/XYZ/uv_light_reached # Register uv_light_reached callback
# Configure threshold for UV light "greater than 75 mW/m²"
publish '{"option": "greater", "min": 750, "max": 0}' to tinkerforge/request/uv_light_bricklet/XYZ/set_uv_light_callback_threshold
|
All published payloads to and from the MQTT bindings are in JSON format.
If an error occures, the bindings publish a JSON object containing the error message as member _ERROR
.
It is published on the corresponding response topic: .../response/...
for .../request/...
and .../callback/...
for .../register/...
.
request/
uv_light_bricklet/
<UID>/
get_uv_light
¶Request: |
|
---|---|
Response: |
|
Returns the UV light intensity of the sensor. The sensor has already weighted the intensity with the erythemal action spectrum to get the skin-affecting irradiation.
To get UV index you just have to divide the value by 250. For example, a UV light intensity of 500 is equivalent to an UV index of 2.
If you want to get the intensity periodically, it is recommended to use the
register/uv_light_bricklet/<UID>/uv_light
callback and set the period with
request/uv_light_bricklet/<UID>/set_uv_light_callback_period
.
request/
uv_light_bricklet/
<UID>/
get_identity
¶Request: |
|
---|---|
Response: |
|
Returns the UID, the UID where the Bricklet is connected to, the position, the hardware and firmware version as well as the device identifier.
The position can be 'a', 'b', 'c', 'd', 'e', 'f', 'g' or 'h' (Bricklet Port). A Bricklet connected to an Isolator Bricklet is always at position 'z'.
The device identifier numbers can be found here. If symbolic output is not disabled, the device identifier is mapped to the corresponding name in the format used in topics.
The display name contains the UV Light's name in a human readable form.
request/
uv_light_bricklet/
<UID>/
set_uv_light_callback_period
¶Request: |
|
---|---|
Response: |
|
Sets the period with which the register/uv_light_bricklet/<UID>/uv_light
callback is triggered
periodically. A value of 0 turns the callback off.
The register/uv_light_bricklet/<UID>/uv_light
callback is only triggered if the intensity has changed since
the last triggering.
request/
uv_light_bricklet/
<UID>/
get_uv_light_callback_period
¶Request: |
|
---|---|
Response: |
|
Returns the period as set by request/uv_light_bricklet/<UID>/set_uv_light_callback_period
.
request/
uv_light_bricklet/
<UID>/
set_uv_light_callback_threshold
¶Request: |
|
---|---|
Response: |
|
Sets the thresholds for the register/uv_light_bricklet/<UID>/uv_light_reached
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Callback is turned off |
'o' | Callback is triggered when the intensity is outside the min and max values |
'i' | Callback is triggered when the intensity is inside the min and max values |
'<' | Callback is triggered when the intensity is smaller than the min value (max is ignored) |
'>' | Callback is triggered when the intensity is greater than the min value (max is ignored) |
The following symbols are available for this function:
For option:
request/
uv_light_bricklet/
<UID>/
get_uv_light_callback_threshold
¶Request: |
|
---|---|
Response: |
|
Returns the threshold as set by request/uv_light_bricklet/<UID>/set_uv_light_callback_threshold
.
The following symbols are available for this function:
For option:
request/
uv_light_bricklet/
<UID>/
set_debounce_period
¶Request: |
|
---|---|
Response: |
|
Sets the period with which the threshold callbacks
are triggered, if the thresholds
keep being reached.
request/
uv_light_bricklet/
<UID>/
get_debounce_period
¶Request: |
|
---|---|
Response: |
|
Returns the debounce period as set by request/uv_light_bricklet/<UID>/set_debounce_period
.
Callbacks can be registered to receive
time critical or recurring data from the device. The registration is done
with the corresponding .../register/...
topic and an optional suffix.
This suffix can be used to deregister the callback later.
Note
Using callbacks for recurring events is always preferred compared to using getters. It will use less USB bandwidth and the latency will be a lot better, since there is no round trip time.
register/
uv_light_bricklet/
<UID>/
uv_light
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/uv_light_bricklet/<UID>/uv_light[/<SUFFIX>]
topic with the payload "true".
An added callback can be removed by publishing to the same topic with the payload "false".
To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.
If the callback is triggered, a message with it's payload is published under the corresponding .../callback/uv_light_bricklet/<UID>/uv_light[/<SUFFIX>]
topic for each registered suffix.
This callback is triggered periodically with the period that is set by
request/uv_light_bricklet/<UID>/set_uv_light_callback_period
. The callback payload is the UV Light
intensity of the sensor.
The register/uv_light_bricklet/<UID>/uv_light
callback is only triggered if the intensity has changed
since the last triggering.
register/
uv_light_bricklet/
<UID>/
uv_light_reached
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/uv_light_bricklet/<UID>/uv_light_reached[/<SUFFIX>]
topic with the payload "true".
An added callback can be removed by publishing to the same topic with the payload "false".
To support multiple (de)registrations, e.g. for message filtering, an optional suffix can be used.
If the callback is triggered, a message with it's payload is published under the corresponding .../callback/uv_light_bricklet/<UID>/uv_light_reached[/<SUFFIX>]
topic for each registered suffix.
This callback is triggered when the threshold as set by
request/uv_light_bricklet/<UID>/set_uv_light_callback_threshold
is reached.
The callback payload is the UV Light intensity of the sensor.
If the threshold keeps being reached, the callback is triggered periodically
with the period as set by request/uv_light_bricklet/<UID>/set_debounce_period
.