User Script Submission update PirateWeatherADV v3

[Nullvoid3771]

*Created with ClaudeAI. If it looks good on your side feel free to add it to the script library. I've tried it within Meshmonitor and it seems to work able to use timed events or auto responder.

Please add my script to the User Scripts Gallery:

Changelog: v3 fixes a timeout issue in the script that caused time events automation trigger to fail with a [ error — "The read operation timed out" ] that problem has been corrected.

Script Name: PirateWeatherADV v3
Description: PirateWeatherADV is a Python weather script for mesh network auto-responders with four output modes:
Location mode — query weather by typing a place name. Works via trigger from another node, or as a Timed Event with a CLI argument. Outputs the classic single-line format:

Weather for Peterborough, Ontario, Canada:

Misty. Currently 40°F (feels like 32°F). Today: High 47°F, Low 38°F. Humidity: 96%, Wind: 9 mph.

7-Day Forecast for Peterborough, Ontario, Canada:

7-Day Forecast - Peterborough, Ontario, Canada:
Sun: Mostly clear starting in the evening.. Hi 44°F/6°C Lo 27°F/-3°C 💧14%
17:21

Mon: Mostly clear until evening, returning overnight.. Hi 39°F/4°C Lo 25°F/-4°C 💧7%
Tue: Partly cloudy until afternoon, returning overnight.. Hi 43°F/6°C Lo 35°F/2°C 💧6%
17:22

Wed: Mostly clear until evening, returning overnight.. Hi 57°F/14°C Lo 36°F/2°C
Thu: Partly cloudy starting in the afternoon.. Hi 58°F/15°C Lo 42°F/5°C
17:22

Fri: Drizzle overnight.. Hi 59°F/15°C Lo 44°F/7°C 💧29%
Sat: Drizzle until evening.. Hi 57°F/14°C Lo 43°F/6°C 💧46%
Image

GPS mode — send just weather with no location and the script automatically uses the requesting node's GPS coordinates, falling back to the local node's GPS if none is provided. Outputs a multi-line emoji format with a reverse-geocoded city name.
Input is flexible — it accepts peterborough,ontario,canada or weather peterborough,ontario,canada, from a trigger, a CLI argument, or an environment variable. It figures out what you meant either way.
All weather data comes from Pirate Weather, location names from OpenStreetMap Nominatim. The only thing you need to supply is a free Pirate Weather API key.

Additional documentation can be found within the script.

Language (Python/JavaScript/Shell): Python
Tags (comma-separated): Weather, API, Geocoding, PirateWeather, V2

Example Trigger: weather — GPS mode, uses node coordinates
weather {location:.+} — location mode, user types a place name
Requirements: Python 3.6+
Pirate Weather API key — free from https://pirateweather.net/
PIRATE_WEATHER_API_KEY set as an environment variable
LOCAL_LAT / LOCAL_LON set if you want a GPS fallback when the requesting node has no coordinates
Internet access from the container (for Pirate Weather and Nominatim)
GitHub Link or Gist: N/A

[Paste your script code here or link to it]

PirateWeatherADV v3.py

[Yeraze]

Thanks for the update, @Nullvoid3771 — and for tracking down the timeout bug!

Verified root cause: I checked the actual server-side enforcement (src/server/meshtasticManager.ts), and both the Auto-Responder path and the Timed Event path kill scripts after 30 seconds (execFileAsync(..., { timeout: 30000 }) on both), not 10 seconds. The comment in the currently-bundled v2 script (and in several docs pages) incorrectly says "10-second script timeout," which is stale/wrong. Your v3 script's TIMEOUT_GEOCODE=5 / TIMEOUT_API=8 / TIMEOUT_REVERSE=5 change is a well-reasoned fix for that — a slow Nominatim/Pirate Weather response could exceed the old 3s/4s/3s per-call socket timeouts long before the actual 30s kill signal, producing exactly the "read operation timed out" error you saw, especially under Timed Events.

I diffed your v3 submission against the currently bundled script and it's a clean, minimal, low-risk change (just the timeout constants + corrected comment) — classifying this as a Bug Report against the bundled example script rather than a fresh feature request, since it's fixing a real defect in already-shipped content.

I have begun work on this issue, in branch claude/vibrant-volta-fymjny. I'll update examples/auto-responder-scripts/PirateWeatherADV.py with your v3 timeout fix and correct the stale "10-second" references in the related docs, then open a PR for review (not merging it myself).

-- Authored by Roger 🤓

---

Generated by Claude Code

[Yeraze]

Opened #3942 with the fix — adopts your v3 timeout constants verbatim (diffed byte-for-byte against your attachment to confirm), plus correcting the same stale "10-second timeout" claim in the automation docs and example README where it was also wrong.

I'll monitor CI on the PR and fix anything that comes up, but I won't merge it myself — that's for @Yeraze to review.

-- Authored by Roger 🤓

---

Generated by Claude Code

[Nullvoid3771]

PirateWeatherADV v3.py this might improve it further with bug fixes just lacks information updated in the docstring if you want to improve on that NodeZer0. (Ran my claude limit.)

[Yeraze]

Reviewed the latest attachment against the version currently in PR #3942 (branch claude/vibrant-volta-fymjny).

Code changes — look solid, low-risk:

1. _fmt_part() (inside _fmt_label()): 1–3 letter alpha tokens are now uppercased regardless of input case (on → ON), not just preserved when already uppercase. Traced the logic — correct.
2. resolve_input(): adds a guard so a location string that normalises to nothing (e.g. input was just commas) falls through cleanly to the existing GPS-coordinate fallback instead of calling geocode_location(''). Traced the control flow past the new guard — it falls through correctly to the FROM_LAT/FROM_LON → LOCAL_LAT/LOCAL_LON → None chain.
3. main() exception handler: redacts PIRATE_WEATHER_API_KEY from any exception text before broadcasting the error on the mesh. Good defensive fix against key leakage if an upstream API error ever echoes the key back.

Docstring gaps (this is the "minimal" part flagged):

• _fmt_label()'s docstring still reads "Abbreviations (ON, NY, CA) are preserved in upper case" — that undersells the new behavior. It should say abbreviations are uppercased regardless of input case (on → ON), not just preserved when already uppercase.
• resolve_input()'s docstring documents the location/GPS resolution order but never mentions the new empty-after-normalisation → GPS fallback path added in this version.

Suggested fixes:

def _fmt_label(location: str) -> str:
    """
    Build a clean display label from a raw location string.
    Splits on commas, capitalises each part carefully so:
      - Short (1-3 letter) alpha tokens are uppercased as abbreviations,
        regardless of input case (on -> ON, ny -> NY, CA -> CA)
      - Apostrophes (St. John's) are not mangled by str.title()
      - Empty parts from double/trailing commas are skipped
    """

    Resolution order for location:
      1. CLI arguments (e.g. Timed Events)
      2. PARAM_location env var (trigger pipeline)
      If the location string normalises to nothing (e.g. just commas),
      resolution falls through to GPS coordinates below instead of erroring.

The rest of the module docstring (TIMEOUTS/SECURITY sections already in this attachment) covers the other changes well — no gaps found there.

@Yeraze — this is a clean follow-up on top of #3942; the three code fixes check out and are worth folding in along with the docstring corrections above. I don't have write access to the branch to push this myself, flagging for whoever picks it up next.

-- Authored by NodeZero 0️⃣