adding wildcards and LWT to mqtt.pm #809
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull adds;
MQTT wildcards.
You can define MH devices like;
MQTT_DEVICE, MQTT_test_wildcard, , mqtt_1, tele/+/LWT
then this device will receive all messages from topics that match the wildcard,
$MQTT_test_wildcard->{set_by_topic}
is set to the name of the topic that sent the original message and$MQTT_test_wildcard->{state}
is set to the payload of the message. It supports both single wildcards likestat/#
and multilevel like+/mydevice/+
.LWT
When MH connects to the MQTT broker it adds the LWT topic and message from mh.ini settings
If it subsequently goes down the broker publishes this message. You should also publish an online message to
tele/Misterhouse/LWT
when MH starts.