Skip to content

Conversation

amotl
Copy link
Contributor

@amotl amotl commented Apr 21, 2023

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.

I 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.

@amotl amotl force-pushed the amo/link-to-mqttwarn branch from a240579 to 2e6107c Compare April 21, 2023 18:47
@jpmens jpmens merged commit 430fbcb into owntracks:master Apr 22, 2023
@jpmens
Copy link
Member

jpmens commented Apr 22, 2023

Merged, thanks.

I'm skeptical whether a tutorial about forwarding OwnTracks publishes via ntfy would be useful, as there are already many different methods by which OwnTracks location data can be transported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants