v2.4.2

Fixes

• Folding back on a tap elsewhere now works on iOS (Safari and the companion app): a tap on something that is not clickable sent no click to the page, so what a click elsewhere folds (unfolded sections, the detailed view of the mini card, popups) stayed open. The press and the release are caught instead; a slider dragged out of the card and a scroll do not fold anything.
• Leaving the card (another dashboard view, a conditional card hidden) brings it back in its default state.
• A click could do nothing: Home Assistant updates the card several times a second, and a rewrite of the card between the press and the release replaced the element pressed, so that the click was lost. The card is no longer rewritten while a press is in progress; the pending update is drawn right after the click.
• No focus ring after a mouse click or a tap: the focus is kept across updates only for the keyboard.

v2.4.1

Fixes

• Nginx Proxy Manager: no more upstream health binary sensor per proxy host (#67). NPM does not check its upstreams, so these sensors (shown as Upstream {domain} / Serveur cible {domain}) could only ever be unknown, while the target of each proxy host is already in the Proxy rules sensor and on the card. Those created by 2.4.0 are removed at startup; Zoraxy and Traefik keep theirs.

v2.4.0

Features

• Nginx Proxy Manager support (#65): add it with Settings → Devices & services → Add integration → Reverse Proxy → Nginx Proxy Manager (address of the admin interface, the email and password of an account without two-factor authentication). Its proxy hosts are the proxy rules (with their on/off button on the card and in reverse_proxy.toggle_proxy_rule), its redirection hosts the redirects; access lists, version, and the certificates with their expiry sensors and renewal button (Let's Encrypt certificates) are there too. NPM does not check its upstreams: their health stays unknown. The token is renewed by itself when it expires.

v2.3.0

Features

• show_title and show_subtitle options (also in the visual editor) hide the header's title (the proxy's name) and its subtitle (its web address), separately, for a card placed under a section heading of its own (asked in juju35/ha-vehicle-card#72).

v2.2.1

Maintenance

• No code change: released again to check the installation from the Marketplace.

v2.2.0

Features

• Repairs issues: a certificate expiring within 30 days (warning) or expired (error), and a rule whose upstreams have all been offline for 10 minutes (error), in Settings → Repairs; each goes away by itself once fixed, and with the entry when it is removed.

v2.1.0

Performance

• Translations load on demand: in the release zip, the frontend files keep English only (reverse-proxy-card.js 108 KB → 76 KB) and each other language is its own <file>.i18n.<lang>.js file next to them, fetched the first time a card or the panel needs it. Home Assistant loads the card on every dashboard, so each page used to download and parse all 22 languages to use one. The cards and panel are defined once the page's language has arrived (a few milliseconds), so they render translated from the start.

Maintenance

• The Marketplace now installs the release zip (zip_release), like the other ha-* integrations: the split files are only in it.
• The repository keeps every language in the sources: the release runs scripts/split-frontend.mjs before building the zip, and the Validate workflow checks the split on a copy (every table is rebuilt from the split files and compared).

v2.0.0

Breaking changes

• The integration is now Reverse Proxy (reverse_proxy) and the repository ha-reverse-proxy (the old address redirects). After the update, remove custom_components/zoraxy/ if it is still there and add Reverse Proxy → Zoraxy for your Zoraxy address: the new entry takes over the former Zoraxy entry of the same address, with its device, entities (ids, names, areas, history) and removes it.
• The action zoraxy.toggle_proxy_rule is now reverse_proxy.toggle_proxy_rule; the config_entry_id field is now called Instance.
• Cards: custom:reverse-proxy-card and custom:reverse-proxy-mini-card, served at /reverse_proxy/reverse-proxy-card.js (the old resource is replaced at startup); custom:zoraxy-card and custom:zoraxy-mini-card stay as aliases. The zoraxy_url option is now proxy_url (the old name is still read).

What's new

• Traefik support (v2 / v3): a Traefik entry reads its API (/api/overview, HTTP routers, services, middlewares, entrypoints, version) and gives proxy rules (the @internal ones aside) with their state and upstream health from the services' health checks, redirects from the redirectScheme / redirectRegex middlewares, a middleware count, the TLS flag, the inbound port (the websecure entrypoint) and a version sensor; optional HTTP basic auth when the API sits behind a basicAuth middleware. Traefik's API being read-only and not exposing the ACME certificates, a Traefik entry has no switch, no certificate entity and no rule toggle.
• The config flow starts by asking which reverse proxy to add; the reauth, reconfigure and options dialogs and the error messages name the proxy of the entry.
• Cards: the header shows the brand mark of the proxy (Zoraxy or Traefik) and only the controls its API allows; a Traefik card shows a middleware tile instead of the certificates, the rules' state as plain chips, and its mini card adds the version.
• The Proxy running binary sensor carries proxy_type and features attributes.
• Integration icon: an indigo tile with the server-network glyph and an orange proxy badge, in the style of the other ha-* integrations (no longer the Zoraxy logo).

Internals

• One coordinator per proxy behind a common interface (coordinator.py), entities created from the proxy's features, Traefik screenshots in scripts/screenshots.py.

v1.14.0

What's new

• Cards: the header shows the round server icon of the project page, tinted with the proxy status (green running, red stopped, grey unavailable), with the Zoraxy mark as a badge, as on the other ha-* cards.
• Cards: a click on that header icon opens the Zoraxy web interface (zoraxy_url); the title is plain text.

v1.13.1

Fixes

• Cards: a proxy rule's button now changes the rule of the card's own Zoraxy instance (new optional config_entry_id field of zoraxy.toggle_proxy_rule), shows a failure in a toast, and is disabled for users who are not administrators.
• Upstream health becomes unknown when Zoraxy's uptime monitor log cannot be read for 3 minutes, instead of keeping the last check forever.