fix(birdnet-pipy): wait for API (port 5002) before starting nginx to prevent 502 on ingress

Agent-Logs-Url: https://github.com/alexbelgium/hassio-addons/sessions/4e3f8d6e-aa60-49f1-9091-ec6eee21af29

Co-authored-by: alexbelgium <44178713+alexbelgium@users.noreply.github.com>
This commit is contained in:
copilot-swe-agent[bot]
2026-04-23 12:28:56 +00:00
committed by GitHub
parent 6b0341b4b2
commit 3f991edcd7
3 changed files with 10 additions and 2 deletions

View File

@@ -1,5 +1,8 @@
## 0.6.6 (2026-04-21)
## 0.6.6-1 (2026-04-23)
- Fix 502 Bad Gateway on ingress: nginx now waits for the API server (port 5002) to be ready before starting. Previously, nginx started immediately while the ML model was still loading, causing all API calls to fail with 502 until the model finished loading.
- Update to latest version from Suncuss/BirdNET-PiPy (changelog : https://github.com/Suncuss/BirdNET-PiPy/releases)
## 0.6.4 (2026-04-18)

View File

@@ -96,4 +96,4 @@ schema:
ssl: bool?
slug: birdnet-pipy
url: https://github.com/alexbelgium/hassio-addons/tree/master/birdnet-pipy
version: "0.6.6"
version: "0.6.6-1"

View File

@@ -2,4 +2,9 @@
# shellcheck shell=bash
set -euo pipefail
# Wait for the API server to be ready before exposing the ingress. Without
# this, nginx starts immediately while the model is still loading (can take
# minutes), causing every frontend API call to return a 502 Bad Gateway.
bashio::net.wait_for 5002 127.0.0.1 300
nginx