Improve section about mqttwarn
#70
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.
Dear Jan-Piet and Christoph,
following up on giving some love to the mqttwarn documentation recently, I am also submitting a patch to slightly improve the corresponding section here.
With kind regards,
Andreas.
P.S.: Outlook
As I observed JP signalled interest in ntfy the other day, I referenced it within the updated section.
ntfy
mqtt-tools/mqttwarn#638I believe it would be sweet to work on a dedicated »Forward events from OwnTracks to ntfy« tutorial similar to the Frigate/ntfy integration tutorial on behalf of a subsequent iteration on the mqttwarn documentation, and also reference this here afterwards. Problem is: I don't know much about OwnTracks, so I may need your assistance.