GREE Controller 0.14.12

custom_components/gree_controller/manifest.json

@@ -1,7 +1,7 @@
 {
   "domain": "gree_controller",
   "name": "GREE Controller",
-  "version": "0.14.11",
+  "version": "0.14.12",
   "config_flow": true,
   "integration_type": "hub",
   "iot_class": "local_polling",

gree-controller/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.14.12
+
+- Home Assistant add-on now uses the Supervisor-managed Home Assistant Core API connection automatically.
+- Enables `homeassistant_api` for the add-on and authenticates Core API requests with runtime `SUPERVISOR_TOKEN`.
+- Keeps the Supervisor token out of SQLite and prevents add-on UI edits from replacing stored standalone Home Assistant URL/token settings.
+- Standalone installations keep the existing manual Home Assistant URL and Long-Lived Access Token behavior unchanged.
+- Fixes custom select mouse hover/click inside modal dialogs by keeping each dropdown popover inside the same modal top-layer subtree; keyboard behavior is unchanged.
+
 ## 0.14.11
 
 - Replaces font-dependent Unicode glyphs used as Web UI icons with a shared inline SVG icon set.

gree-controller/DOCS.md

@@ -58,6 +58,10 @@ Broadcast zwykle nie przechodzi przez router. Sterowanie unicast może działać
 | `app_token` | opcjonalna ochrona bezpośredniego Web UI/API |
 | `log_level` | `error`, `warn`, `info`, `debug`, `trace` |
 
+### Home Assistant API
+
+Dodatek korzysta automatycznie z wewnętrznego proxy Home Assistant Core (`http://supervisor/core/api/`) i tokenu `SUPERVISOR_TOKEN` przekazywanego przez Supervisor. Nie konfiguruj ręcznie URL ani Long-Lived Access Token dla połączenia kontrolera z Home Assistant. Token Supervisor jest używany tylko w pamięci procesu i nie jest zapisywany w SQLite.
+
 ### Dostęp, dane i bezpieczeństwo
 
 Usługa słucha na TCP `8787`; ingress Home Assistant przekazuje Web UI na ten port. Jeżeli `8787` jest osiągalny z niezaufanej sieci, ustaw `app_token` albo zablokuj port firewallem. Baza jest zapisywana w `/data/gree-controller.db`; konfiguracja używa `backup: cold`, więc dane są objęte backupem dodatku.
@@ -119,6 +123,10 @@ Broadcast normally does not cross routers. Unicast control may work through rout
 | `app_token` | optional protection for direct Web UI/API access |
 | `log_level` | `error`, `warn`, `info`, `debug`, `trace` |
 
+### Home Assistant API
+
+The add-on automatically uses the internal Home Assistant Core proxy (`http://supervisor/core/api/`) and the runtime `SUPERVISOR_TOKEN` provided by Supervisor. Do not configure a Home Assistant URL or Long-Lived Access Token for the controller-to-Home-Assistant connection. The Supervisor token is used only at runtime and is not stored in SQLite.
+
 ### Access, data and security
 
 The service listens on TCP `8787`; Home Assistant ingress proxies the Web UI to that port. If `8787` is reachable from an untrusted network, configure `app_token` or block the port at the firewall. The database is stored in `/data/gree-controller.db`; `backup: cold` keeps it in the add-on backup.

gree-controller/config.yaml

@@ -1,5 +1,5 @@
 name: "GREE Controller"
-version: "0.14.11"
+version: "0.14.12"
 slug: "gree_controller"
 description: "Local GREE HVAC controller with Web UI and Home Assistant integration"
 url: "https://git.linuxiarz.pl/gru/gree-controller-ha-addon/"
@@ -11,6 +11,7 @@ startup: application
 boot: auto
 init: false
 host_network: true
+homeassistant_api: true
 ingress: true
 ingress_port: 8787
 ingress_stream: true