diff --git a/docs/mqtt-firmware.md b/docs/mqtt-firmware.md index 16e0a1f..5ebd88c 100644 --- a/docs/mqtt-firmware.md +++ b/docs/mqtt-firmware.md @@ -12,7 +12,7 @@ These instructions cover setting up the MeshCore observer firmware to send to Me ## 1. Flash the Firmware -Open the [MeshCore Observer Flasher](https://observer.gessaman.com/), pick **MQTT Observer Firmware**, select your device, and flash it from the browser. +Open the [MeshCore Observer Flasher](https://observer.gessaman.com/), select your device, select **Repeater**, and flash it from the browser. ## 2. Configure the Observer @@ -44,6 +44,6 @@ The IATA code must match your MeshMapper region, or your observer won't show up. ## Verifying Your Observer -Once your observer is running and connected, it appears in your region's admin panel under the [Observers tab](admins.md#observers) after packets have been received (repeater or companion adverts, or wardriving pings). Its **Brokers** column shows a coloured MeshMapper badge once the broker has heard it. +Once your observer is running and connected, it appears in your region's **Region → Observers** popup on the map after packets have been received (repeater or companion adverts, or wardriving pings). It shows as **Online** with a MeshMapper broker badge once the broker has heard it. If nothing shows up, run `get wifi.status` and `get mqtt.status` on the device console, and confirm `mqtt.iata` matches your region. diff --git a/docs/mqtt-ha.md b/docs/mqtt-ha.md index 2446894..15fe93f 100644 --- a/docs/mqtt-ha.md +++ b/docs/mqtt-ha.md @@ -38,6 +38,6 @@ Click **Submit**, then click **Exit** to return to the integration page. ## Verifying Your Observer -Once your observer is running and connected, it appears in your region's admin panel under the [Observers tab](admins.md#observers) after packets have been received (repeater or companion adverts, or wardriving pings). Its **Brokers** column shows a coloured MeshMapper badge once the broker has heard it. +Once your observer is running and connected, it appears in your region's **Region → Observers** popup on the map after packets have been received (repeater or companion adverts, or wardriving pings). It shows as **Online** with a MeshMapper broker badge once the broker has heard it. If nothing shows up, check the Home Assistant logs for MQTT errors, and confirm the Broker IATA Code matches your region. diff --git a/docs/mqtt-main.md b/docs/mqtt-main.md index eb74fa9..12da75f 100644 --- a/docs/mqtt-main.md +++ b/docs/mqtt-main.md @@ -49,8 +49,8 @@ This method uses the PyMC software, which handles MQTT configuration directly fr **Which broker should I send to?** The MeshMapper broker. MeshMapper also collects from LetsMesh, but that isn't our infrastructure, so we can't guarantee we'll always have access to it. -**Can I use a mobile observer?** It can submit reports while online, but a fixed, always-on observer is a better choice for a region's required listener. A mobile receiver cannot verify a new region while it is offline or away from that region. +**Can I use a mobile observer?** No, mobile observers are highly discouraged. MeshMapper's backend is designed for fixed observers, and a mobile one doesn't provide proper coverage data and gives misleading results in some mapping modes. KiekR mobile observers are dropped at MeshMapper's ingest point. Use a fixed, always-on observer. -**Why is my observer not listed?** A broker connection by itself is not an observer report. Check that it publishes `status` or `packets` on the `meshcore///...` topic, using the region's code. Then check the region admin panel's **Observers** tab and its **Brokers** badges. Allow time for the first report to arrive. +**Why is my observer not listed?** A broker connection by itself is not an observer report. Check that it publishes `status` or `packets` on the `meshcore///...` topic, using the region's code. Then check the region's **Region → Observers** popup on the map. Allow time for the first report to arrive. **Can my region use its own MQTT broker?** Yes. After onboarding, region admins can configure MeshMapper to also pull from their own regional broker in the admin panel under **Settings → MQTT Brokers & Observers**. Provide a reachable host and port, WebSockets transport, and its authentication credentials. MeshMapper subscribes only to that region's topics. Do not publish broker credentials in a public channel. diff --git a/docs/mqtt-pymc.md b/docs/mqtt-pymc.md index 07a72c6..5fd331f 100644 --- a/docs/mqtt-pymc.md +++ b/docs/mqtt-pymc.md @@ -92,6 +92,6 @@ sudo journalctl -u pymc-repeater.service -f | grep MeshMapper ## Verifying Your Observer -Once your observer is running and connected, it appears in your region's admin panel under the [Observers tab](admins.md#observers) after packets have been received (repeater or companion adverts, or wardriving pings). Its **Brokers** column shows a coloured MeshMapper badge once the broker has heard it. +Once your observer is running and connected, it appears in your region's **Region → Observers** popup on the map after packets have been received (repeater or companion adverts, or wardriving pings). It shows as **Online** with a MeshMapper broker badge once the broker has heard it. If nothing shows up, check the logs (`sudo journalctl -u pymc-repeater.service -f`) for MQTT errors, and confirm `iata_code` matches your region. diff --git a/docs/mqtt-python.md b/docs/mqtt-python.md index b5a1ed6..eae0248 100644 --- a/docs/mqtt-python.md +++ b/docs/mqtt-python.md @@ -50,6 +50,6 @@ curl -fsSL https://raw.githubusercontent.com/Cisien/meshcoretomqtt/main/scripts/ ## Verifying Your Observer -Once your observer is running and connected, it appears in your region's admin panel under the [Observers tab](admins.md#observers) after packets have been received (repeater or companion adverts, or wardriving pings). Its **Brokers** column shows a coloured MeshMapper badge once the broker has heard it. +Once your observer is running and connected, it appears in your region's **Region → Observers** popup on the map after packets have been received (repeater or companion adverts, or wardriving pings). It shows as **Online** with a MeshMapper broker badge once the broker has heard it. If nothing shows up, check the logs (`sudo journalctl -u mctomqtt -f`) for MQTT errors, and confirm the IATA code matches your region.