This is the description of the MQTT API bindings for the Humidity Bricklet 2.0. General information and technical specifications for the Humidity Bricklet 2.0 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 Humidity Bricklet 2.0
setup:
# Get current humidity
subscribe to tinkerforge/response/humidity_v2_bricklet/XYZ/get_humidity
publish '' to tinkerforge/request/humidity_v2_bricklet/XYZ/get_humidity
|
Download (example-callback.txt)
1 2 3 4 5 6 7 8 9 | # Change XYZ to the UID of your Humidity Bricklet 2.0
setup:
# Handle incoming humidity callbacks
subscribe to tinkerforge/callback/humidity_v2_bricklet/XYZ/humidity
publish '{"register": true}' to tinkerforge/register/humidity_v2_bricklet/XYZ/humidity # Register humidity callback
# Set period for humidity callback to 1s (1000ms) without a threshold
publish '{"period": 1000, "value_has_to_change": false, "option": "off", "min": 0, "max": 0}' to tinkerforge/request/humidity_v2_bricklet/XYZ/set_humidity_callback_configuration
|
Download (example-threshold.txt)
1 2 3 4 5 6 7 8 9 10 | # Change XYZ to the UID of your Humidity Bricklet 2.0
setup:
# Handle incoming humidity callbacks
subscribe to tinkerforge/callback/humidity_v2_bricklet/XYZ/humidity
publish '{"register": true}' to tinkerforge/register/humidity_v2_bricklet/XYZ/humidity # Register humidity callback
# Configure threshold for humidity "outside of 30 to 60 %RH"
# with a debounce period of 10s (10000ms)
publish '{"period": 10000, "value_has_to_change": false, "option": "outside", "min": 3000, "max": 6000}' to tinkerforge/request/humidity_v2_bricklet/XYZ/set_humidity_callback_configuration
|
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/
humidity_v2_bricklet/
<UID>/
get_humidity
¶Request: |
|
---|---|
Response: |
|
Returns the humidity measured by the sensor.
If you want to get the value periodically, it is recommended to use the
register/humidity_v2_bricklet/<UID>/humidity
callback. You can set the callback configuration
with request/humidity_v2_bricklet/<UID>/set_humidity_callback_configuration
.
request/
humidity_v2_bricklet/
<UID>/
get_temperature
¶Request: |
|
---|---|
Response: |
|
Returns the temperature measured by the sensor.
If you want to get the value periodically, it is recommended to use the
register/humidity_v2_bricklet/<UID>/temperature
callback. You can set the callback configuration
with request/humidity_v2_bricklet/<UID>/set_temperature_callback_configuration
.
request/
humidity_v2_bricklet/
<UID>/
set_heater_configuration
¶Request: |
|
---|---|
Response: |
|
Enables/disables the heater. The heater can be used to dry the sensor in extremely wet conditions.
The following symbols are available for this function:
For heater_config:
request/
humidity_v2_bricklet/
<UID>/
get_heater_configuration
¶Request: |
|
---|---|
Response: |
|
Returns the heater configuration as set by request/humidity_v2_bricklet/<UID>/set_heater_configuration
.
The following symbols are available for this function:
For heater_config:
request/
humidity_v2_bricklet/
<UID>/
set_moving_average_configuration
¶Request: |
|
---|---|
Response: |
|
Sets the length of a moving averaging for the humidity and temperature.
Setting the length to 1 will turn the averaging off. With less averaging, there is more noise on the data.
New data is gathered every 50ms*. With a moving average of length 1000 the resulting averaging window has a length of 50s. If you want to do long term measurements the longest moving average will give the cleanest results.
* In firmware version 2.0.3 we added the request/humidity_v2_bricklet/<UID>/set_samples_per_second
function. It
configures the measurement frequency. Since high frequencies can result in self-heating
of th IC, changed the default value from 20 samples per second to 1. With 1 sample per second
a moving average length of 1000 would result in an averaging window of 1000 seconds!
request/
humidity_v2_bricklet/
<UID>/
get_moving_average_configuration
¶Request: |
|
---|---|
Response: |
|
Returns the moving average configuration as set by request/humidity_v2_bricklet/<UID>/set_moving_average_configuration
.
request/
humidity_v2_bricklet/
<UID>/
set_samples_per_second
¶Request: |
|
---|---|
Response: |
|
Sets the samples per second that are gathered by the humidity/temperature sensor HDC1080.
We added this function since we found out that a high measurement frequency can lead to self-heating of the sensor. Which can distort the temperature measurement.
If you don't need a lot of measurements, you can use the lowest available measurement frequency of 0.1 samples per second for the least amount of self-heating.
Before version 2.0.3 the default was 20 samples per second. The new default is 1 sample per second.
The following symbols are available for this function:
For sps:
New in version 2.0.3 (Plugin).
request/
humidity_v2_bricklet/
<UID>/
get_samples_per_second
¶Request: |
|
---|---|
Response: |
|
Returnes the samples per second, as set by request/humidity_v2_bricklet/<UID>/set_samples_per_second
.
The following symbols are available for this function:
For sps:
New in version 2.0.3 (Plugin).
request/
humidity_v2_bricklet/
<UID>/
get_spitfp_error_count
¶Request: |
|
---|---|
Response: |
|
Returns the error count for the communication between Brick and Bricklet.
The errors are divided into
The errors counts are for errors that occur on the Bricklet side. All Bricks have a similar function that returns the errors on the Brick side.
request/
humidity_v2_bricklet/
<UID>/
set_status_led_config
¶Request: |
|
---|---|
Response: |
|
Sets the status LED configuration. By default the LED shows communication traffic between Brick and Bricklet, it flickers once for every 10 received data packets.
You can also turn the LED permanently on/off or show a heartbeat.
If the Bricklet is in bootloader mode, the LED is will show heartbeat by default.
The following symbols are available for this function:
For config:
request/
humidity_v2_bricklet/
<UID>/
get_status_led_config
¶Request: |
|
---|---|
Response: |
|
Returns the configuration as set by request/humidity_v2_bricklet/<UID>/set_status_led_config
The following symbols are available for this function:
For config:
request/
humidity_v2_bricklet/
<UID>/
get_chip_temperature
¶Request: |
|
---|---|
Response: |
|
Returns the temperature as measured inside the microcontroller. The value returned is not the ambient temperature!
The temperature is only proportional to the real temperature and it has bad accuracy. Practically it is only useful as an indicator for temperature changes.
request/
humidity_v2_bricklet/
<UID>/
reset
¶Request: |
|
---|---|
Response: |
|
Calling this function will reset the Bricklet. All configurations will be lost.
After a reset you have to create new device objects, calling functions on the existing ones will result in undefined behavior!
request/
humidity_v2_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 Humidity 2.0's name in a human readable form.
request/
humidity_v2_bricklet/
<UID>/
set_humidity_callback_configuration
¶Request: |
|
---|---|
Response: |
|
The period is the period with which the register/humidity_v2_bricklet/<UID>/humidity
callback is triggered
periodically. A value of 0 turns the callback off.
If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.
If it is set to false, the callback is continuously triggered with the period, independent of the value.
It is furthermore possible to constrain the callback with thresholds.
The option-parameter together with min/max sets a threshold for the register/humidity_v2_bricklet/<UID>/humidity
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Threshold is turned off |
'o' | Threshold is triggered when the value is outside the min and max values |
'i' | Threshold is triggered when the value is inside or equal to the min and max values |
'<' | Threshold is triggered when the value is smaller than the min value (max is ignored) |
'>' | Threshold is triggered when the value is greater than the min value (max is ignored) |
If the option is set to 'x' (threshold turned off) the callback is triggered with the fixed period.
The following symbols are available for this function:
For option:
request/
humidity_v2_bricklet/
<UID>/
get_humidity_callback_configuration
¶Request: |
|
---|---|
Response: |
|
Returns the callback configuration as set by request/humidity_v2_bricklet/<UID>/set_humidity_callback_configuration
.
The following symbols are available for this function:
For option:
request/
humidity_v2_bricklet/
<UID>/
set_temperature_callback_configuration
¶Request: |
|
---|---|
Response: |
|
The period is the period with which the register/humidity_v2_bricklet/<UID>/temperature
callback is triggered
periodically. A value of 0 turns the callback off.
If the value has to change-parameter is set to true, the callback is only triggered after the value has changed. If the value didn't change within the period, the callback is triggered immediately on change.
If it is set to false, the callback is continuously triggered with the period, independent of the value.
It is furthermore possible to constrain the callback with thresholds.
The option-parameter together with min/max sets a threshold for the register/humidity_v2_bricklet/<UID>/temperature
callback.
The following options are possible:
Option | Description |
---|---|
'x' | Threshold is turned off |
'o' | Threshold is triggered when the value is outside the min and max values |
'i' | Threshold is triggered when the value is inside or equal to the min and max values |
'<' | Threshold is triggered when the value is smaller than the min value (max is ignored) |
'>' | Threshold is triggered when the value is greater than the min value (max is ignored) |
If the option is set to 'x' (threshold turned off) the callback is triggered with the fixed period.
The following symbols are available for this function:
For option:
request/
humidity_v2_bricklet/
<UID>/
get_temperature_callback_configuration
¶Request: |
|
---|---|
Response: |
|
Returns the callback configuration as set by request/humidity_v2_bricklet/<UID>/set_temperature_callback_configuration
.
The following symbols are available for this function:
For option:
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/
humidity_v2_bricklet/
<UID>/
humidity
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/humidity_v2_bricklet/<UID>/humidity[/<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/humidity_v2_bricklet/<UID>/humidity[/<SUFFIX>]
topic for each registered suffix.
This callback is triggered periodically according to the configuration set by
request/humidity_v2_bricklet/<UID>/set_humidity_callback_configuration
.
The callback payload is the same as request/humidity_v2_bricklet/<UID>/get_humidity
.
register/
humidity_v2_bricklet/
<UID>/
temperature
¶Register Request: |
|
---|---|
Callback Response: |
|
A callback can be registered for this event by publishing to the .../register/humidity_v2_bricklet/<UID>/temperature[/<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/humidity_v2_bricklet/<UID>/temperature[/<SUFFIX>]
topic for each registered suffix.
This callback is triggered periodically according to the configuration set by
request/humidity_v2_bricklet/<UID>/set_temperature_callback_configuration
.
The callback payload is the same as request/humidity_v2_bricklet/<UID>/get_temperature
.
Internal functions are used for maintenance tasks such as flashing a new firmware of changing the UID of a Bricklet. These task should be performed using Brick Viewer instead of using the internal functions directly.
request/
humidity_v2_bricklet/
<UID>/
set_bootloader_mode
¶Request: |
|
---|---|
Response: |
|
Sets the bootloader mode and returns the status after the requested mode change was instigated.
You can change from bootloader mode to firmware mode and vice versa. A change from bootloader mode to firmware mode will only take place if the entry function, device identifier and CRC are present and correct.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
The following symbols are available for this function:
For mode:
For status:
request/
humidity_v2_bricklet/
<UID>/
get_bootloader_mode
¶Request: |
|
---|---|
Response: |
|
Returns the current bootloader mode, see request/humidity_v2_bricklet/<UID>/set_bootloader_mode
.
The following symbols are available for this function:
For mode:
request/
humidity_v2_bricklet/
<UID>/
set_write_firmware_pointer
¶Request: |
|
---|---|
Response: |
|
Sets the firmware pointer for request/humidity_v2_bricklet/<UID>/write_firmware
. The pointer has
to be increased by chunks of size 64. The data is written to flash
every 4 chunks (which equals to one page of size 256).
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
request/
humidity_v2_bricklet/
<UID>/
write_firmware
¶Request: |
|
---|---|
Response: |
|
Writes 64 Bytes of firmware at the position as written by
request/humidity_v2_bricklet/<UID>/set_write_firmware_pointer
before. The firmware is written
to flash every 4 chunks.
You can only write firmware in bootloader mode.
This function is used by Brick Viewer during flashing. It should not be necessary to call it in a normal user program.
request/
humidity_v2_bricklet/
<UID>/
write_uid
¶Request: |
|
---|---|
Response: |
|
Writes a new UID into flash. If you want to set a new UID you have to decode the Base58 encoded UID string into an integer first.
We recommend that you use Brick Viewer to change the UID.
request/
humidity_v2_bricklet/
<UID>/
read_uid
¶Request: |
|
---|---|
Response: |
|
Returns the current UID as an integer. Encode as Base58 to get the usual string version.