Added note to Owntracks about mqtt_topic parameter requirement for Zanzito usage#4949
Conversation
|
Thank you @simpss! Nice first contribution to our documentation my friend 🏅 Can be merged as soon as the build passes. |
|
|
||
| <p class='note'> | ||
| The Android app for OwnTracks is no longer developed or supported, Zanzito is a drop in replacement for OwnTracks MQTT. | ||
| The Android app for OwnTracks is no longer developed or supported, Zanzito is a drop in replacement for OwnTracks MQTT. |
There was a problem hiding this comment.
Development on the android app for owntracks has resumed.
There was a problem hiding this comment.
That is good to know! Maybe create a PR @MartinHjelmare? 🤔
…nzito usage (home-assistant#4949) * Added note about mqtt_topic parameter change requirement for Zanzito usage * ✏️ Minor updates
|
I have reverted this PR. OwnTracks documentation should only be about OwnTracks. If Zanzito is suggesting to use this integration to integrate the app, they should mention that in their own docs. By integrating it in our docs we're indicating that it's an official supported feature, which it is not. |
|
Good point @balloob |
|
I agree, and as it turns out, the mqtt_topic parameter was not the only incompatible thing. Zanzito protocol is completely different and deserves its own component. |
4 participants
Description:
As Zanito publishes to
zanzito/...by default and there is no way to find this out without debugging MQTT traffic i've added a note about it in the docs.Checklist:
current. New documentation for platforms/components and features should go tonext.