Skip to content

Model validation report

Jump to bottom
zampix1 edited this page Jul 15, 2026 · 4 revisions

Model validation report

IT - Quando usare Discussion o Issue

Se stai provando un modello vicino all'INT-14 ma non ancora validato, parti da una Discussion:

https://github.com/zampix1/ha-inkbird-int14/discussions/new?category=q-a

Il thread principale di coordinamento e' questo:

https://github.com/zampix1/ha-inkbird-int14/discussions/1

Apri invece una Issue quando hai un comportamento riproducibile: una lettura sbagliata, una write che fallisce sempre, un profilo con numero sonde errato, o un log che punta a un bug del componente.

https://github.com/zampix1/ha-inkbird-int14/issues/new?template=model_validation_report.yml

IT - Cosa serve davvero

  • modello esatto scritto su termometro, scatola o manuale;
  • profilo selezionato nel config flow;
  • versione Home Assistant e versione integrazione;
  • trasporto provato: Auto, BLE only, ESPHome Bluetooth Proxy, Tuya LAN, cloud history;
  • quante sonde fisiche mostra l'app;
  • quante temperature/canali mostra l'app;
  • screenshot redatti della schermata sonda, se aiutano;
  • quale canale cambia quando scaldi punta, parte centrale e ambiente della probe;
  • quali temperature compaiono e quali restano sconosciute;
  • frequenza degli aggiornamenti e valore di BLE fallback direct-read interval, distinguendo notifiche spontanee e letture dirette;
  • durata approssimativa della sessione BLE, motivo disconnessione e tempo necessario alla riconnessione;
  • stato batteria/ricarica/sonde, soprattutto se resta sempre al 100%;
  • write provate: unita, backlight, target, timer, calibrazione;
  • log redatti solo se aiutano a capire il problema.

IT - Cosa non mandare

Non pubblicare valori reali di:

  • indirizzi BLE;
  • IP LAN;
  • device ID;
  • local key;
  • token, API key, API secret o credenziali cloud;
  • nomi Wi-Fi;
  • screenshot con dati privati;
  • entity ID Home Assistant che contengono nomi personali o luoghi privati.

Usa placeholder come:

AA:BB:CC:DD:EE:FF
192.0.2.10
example-device-id
example-local-key

EN - Discussion or Issue

If you are testing a model close to INT-14 but not validated yet, start with a Discussion:

https://github.com/zampix1/ha-inkbird-int14/discussions/new?category=q-a

The main coordination thread is here:

https://github.com/zampix1/ha-inkbird-int14/discussions/1

Open an Issue when the behavior is reproducible: wrong reading, repeatable write failure, wrong probe count, or a log that points to an integration bug.

https://github.com/zampix1/ha-inkbird-int14/issues/new?template=model_validation_report.yml

EN - Useful data

  • exact model printed on the device, box or manual;
  • selected profile in the config flow;
  • Home Assistant version and integration version;
  • transport tested: Auto, BLE only, ESPHome Bluetooth Proxy, Tuya LAN, cloud history;
  • how many physical probes the app shows;
  • how many temperatures/channels the app shows;
  • redacted screenshots of the probe screen, if useful;
  • which channel changes when you heat the tip, middle/body and ambient section of the probe;
  • which temperatures populate and which stay unknown;
  • update frequency and the BLE fallback direct-read interval value, separating unsolicited notifications from direct reads;
  • approximate BLE session duration, disconnect reason and reconnect delay;
  • battery/charging/probe state, especially repeated 100% values;
  • writes tested: unit, backlight, target, timer, calibration;
  • redacted logs only when they help explain the issue.

EN - Do not post

Do not publish real:

  • BLE addresses;
  • LAN IPs;
  • device IDs;
  • local keys;
  • tokens, API keys, API secrets or cloud credentials;
  • Wi-Fi names;
  • screenshots with private data;
  • Home Assistant entity IDs containing personal names or private locations.

Use placeholders:

AA:BB:CC:DD:EE:FF
192.0.2.10
example-device-id
example-local-key

Clone this wiki locally