Skip to content

support: Gootu hybrid GT-H2436M14P5 + Wi-Fi.DTU.Plug.01: collector OK, G-ASCII sensors unavailable (probe_timeout) #21

Description

@dmytro-kushnir

Preflight

  • I generated a fresh Support Archive for this report.
  • I will attach the ZIP file to this issue or the first follow-up comment.
  • I searched existing issues first.

Home Assistant version

2026.7.4

EyeBond Local version

Version 0.3.0-beta.1

Support Archive filename

01KYWXPW4YWFZGNKSMEE73BHVS_20260731T202929564790Z

What kind of support issue is this?

Partial support / missing entities

Inverter / collector model

Gootu hybrid GT-H2436M14P5 3.6KW 24V + Wi-Fi.DTU.Plug.01 (WFBLE.DTU.Bar)

What is missing or broken?

Hardware

  • Inverter commercial model: Gootu hybrid GT-H2436M14P5 (24V 3.6KW)
  • Collector: Wi-Fi.DTU.Plug.01 (WFBLE.DTU.Bar)
  • Collector firmware: 7.63.6.191
  • Collector hardware: 6.0.0.0
  • Mode: Cloud + HA
  • HA Container (stable), host networking, same LAN as collector

What I expected

Local monitoring and control in Home Assistant: PV / battery / load / grid sensors populated from the inverter over LAN, similar to live data in the vendor app smartvalue. For example update of batery mode on condition

What actually happened

  1. EyeBond Local found the collector and created:
    • collector device: Wi-Fi.DTU.Plug.01
    • inverter device: EyeBond G-ASCII family (detection confidence: high)
  2. Collector stays online (listening), UDP replies work.
  3. Inverter sensors are almost all Unavailable.
  4. Collector shows Driver not detected, poll context stuck on Inverter detection.
  5. Observed error: eybond_g_ascii:probe_timeout.
  6. No useful live inverter values in HA.

Vendor app

Yes - SmartValue still works: can read and modify inverter parameters on this same logger.

Controls

  • Controls Enabled: False
  • Policy: monitoring only (no_write_capabilities)
  • No write/control attempts were made from HA (nothing to enable/reject yet)

Action right before creating this archive

Opened the EyeBond G-ASCII family device page after a re-add/setup where collector connected but inverter sensors stayed Unavailable, then used Create Support Archive.

Extra context (optional)

  • Device learning was not run (UI said it is useful only after an inverter is actually detected).
  • Seemed like known-family fallback (G-ASCII) rather than a fully matched model: shell device created, but no live register data.

Extra context

01KYWXPW4YWFZGNKSMEE73BHVS_20260731T202929564790Z.zip

Where did you hear about EyeBond Local?

Google

Activity

  1. changed the title [-]support: Gootu hybrid + Wi-Fi.DTU.Plug.01: collector OK, G-ASCII sensors unavailable (probe_timeout)[/-] [+]support: Gootu hybrid GT-H2436M14P5 + Wi-Fi.DTU.Plug.01: collector OK, G-ASCII sensors unavailable (probe_timeout)[/+] on Aug 1, 2026
  2. dmytro-kushnir commented on Aug 1, 2026

    @dmytro-kushnir
    Author

    Додатково надсилаю proxy capture (трейс) під час роботи зі SmartValue.
    Під час захоплення змінив режим заряду: з «заряд АКБ тільки з GRID» на «заряд тільки

    01KYY43V6MX29W2VPHYB6Y8TT7_20260801T074058379080Z.zip

    з PV».
    ZIP: 01KYY43V6MX29W2VPHYB6Y8TT7_20260801T074058379080Z.zip

  3. dmytro-kushnir commented on Aug 1, 2026

    @dmytro-kushnir
    Author

    Оновлення:

    Після перемикання на режимHome Assistant only локальний моніторинг іноді запускається:

    • драйвер eybond_g_ascii
    • detection confidence: high
    • сенсори (батарея / мережа / PV / навантаження тощо)

    У режимі Cloud + HA була помилка eybond_g_ascii:probe_timeout, сенсори не з’являлись.

    Окремо щодо керування:
    у профілі EyeBond G-ASCII family інвертор визначається, але немає controls для зміни параметрів - видно переважно read-only сенсори на кшталт Charging Mode Code.

    UPD1:
    Єдина проблема зараз - це те, що через деякий час нотифікації не приходять на колектор чи інвертор. Хоча автоматизовані контрол запити відпрацьовують. Потрібно вручну давати коллбек на коллектор. Працюю лише в Home Assistant only режимі оскільки в Cloud + HA не працює інвертор через помилку probe_timeout.

    Poll interval автоматично зменшуєтсья з 120 до 16 секунд, працює якийсь час, потім івенти не приходять і він знову вертається до 120 секунд.

    UPD2, додав можливості керування через додаткові конфігурації а також схему свого інвертора:

    { "name": "gootu-local", "description": "Single local patch vs upstream ha-eybond-local: Gootu Hybrid 24V catalog + CPR/OPR profile + day/night CPR schedule.", "version": 1, "profile_filename": "gootu_hybrid_24v.json", "profile": { "profile_key": "eybond_g_ascii_gootu_hybrid_24v", "title": "Gootu Hybrid 24V", "driver_key": "eybond_g_ascii", "protocol_family": "eybond_g_ascii", "capability_defaults": { "tested": true, "provenance": "inferred", "support_tier": "standard", "enabled_default": true, "requires_confirm": false, "support_notes": "Local Gootu hybrid 24V/3.7kW profile (not upstream). CPR verified; OPR added (test once). CHGC/GCC skipped — no effect on Battery Type Code 4." }, "groups": [ { "key": "output", "title": "Output", "order": 100, "description": "How the inverter prioritizes utility, PV, and battery for AC output.", "icon": "mdi:transmission-tower-export" }, { "key": "charging", "title": "Charging", "order": 200, "description": "Battery charge-source priority.", "icon": "mdi:battery-charging" } ], "capabilities": [ { "key": "charging_priority", "title": "Charging Priority", "group": "charging", "order": 100, "register": -1, "value_kind": "enum", "command": "CPR", "command_map": { "12336": "CPR00", "12337": "CPR01", "12338": "CPR02", "12339": "CPR03" }, "enum_map": { "12336": "Utility first", "12337": "PV first", "12338": "Utility + PV", "12339": "PV only" }, "read_key": "g_ascii_setting_charging_priority", "change_summary": "Changes which source has priority for battery charging (SmartValue charge mode)." }, { "key": "output_priority", "title": "Output Priority", "group": "output", "order": 100, "register": -1, "value_kind": "enum", "command": "OPR", "command_map": { "12336": "OPR00", "12337": "OPR01", "12338": "OPR02" }, "enum_map": { "12336": "Utility first", "12337": "PV first", "12338": "PV > Battery > Utility" }, "read_key": "g_ascii_setting_output_priority", "change_summary": "Changes output source priority. Verify ACK on this Gootu before automating." } ] }, "catalog": { "surface": { "key": "eybond_g_ascii_gootu_hybrid_24v", "protocol_key": "eybond_g_ascii", "driver_key": "eybond_g_ascii", "variant_key": "gootu_hybrid_24v", "profile_name": "eybond_g_ascii/models/gootu_hybrid_24v.json", "register_schema_name": "eybond_g_ascii/base.json", "tier": "full", "read_only": false, "support_capture_policy": "eybond_g_ascii" }, "device": { "entry_key": "gootu_hybrid_24v", "surface_key": "eybond_g_ascii_gootu_hybrid_24v", "model_name": "Gootu Hybrid 24V 3.7kW", "priority": 125, "family_fallback": false, "anchors": [ { "key": "protocol.protocol_id", "equals": "EYBOND_G_ASCII" }, { "key": "rating.output_voltage", "equals": 230 }, { "key": "rating.output_current", "equals": 15 }, { "key": "rating.battery_voltage", "equals": 24 }, { "key": "rating.frequency", "equals": 50 }, { "key": "firmware.software_version", "equals": "4.007" } ], "provenance": { "sources": [ "Local HA-only + SmartValue proxy: F/SVFW 230V/15A/24V/50Hz + SVFW 4.007; Gootu hybrid 24V 3.7kW.", "CPR00/CPR03 ACK verified; OPR exposed locally — verify before automating." ], "confidence": "offline-fingerprint-user-reported-model" } } }, "schedule": { "entity_id": "select.gootu_hybrid_24v_3_7kw_charging_priority", "day_option": "Utility first", "quiet_option": "PV only", "day_start": "09:00:00", "quiet_start": "21:00:00", "timezone_note": "Uses Home Assistant local time (Europe/Kyiv via Docker TZ).", "idea": "Day from 09:00: Utility first. From 21:00 through morning: PV only (quiet)." } }

  4. groove-max commented on Aug 18, 2026

    @groove-max
    Owner

    v0.3.0-beta.2 now includes a model-specific Gootu GT-H2436M14P5 profile: https://github.com/groove-max/ha-eybond-local/releases/tag/v0.3.0-beta.2

    It uses the exact captured G-ASCII F/SVFW fingerprint, exposes the matching telemetry, and includes only the charging-priority writes that were supported by the captured device evidence. Speculative output-priority writes were intentionally not added.

    Please retest normal sensor updates and, if you use controls, verify only the exposed charging-priority controls. Attach a fresh Support Archive if the probe still times out or any values look implausible.

  5. groove-max commented on Aug 24, 2026

    @groove-max
    Owner

    Профіль Gootu GT-H2436M14P5 та підтверджені команди Charging Priority залишаються у v0.3.0-beta.4. У цій версії також виправлено втрату моделі під час старту, пізнє створення сутностей і роботу callback-сесій через маршрутизовані адреси.

    Будь ласка, оновіть існуючий entry та перевірте спочатку звичайне оновлення сенсорів у Cloud + HA. Якщо eybond_g_ascii:probe_timeout більше не з’являється, окремо перевірте лише ті Charging Priority controls, які вже були підтверджені вашим capture. Якщо проблема залишиться, потрібен свіжий Support Archive з beta.4 — без нового proxy capture на першому кроці.

  6. mikehardy commented on Sep 15, 2026

    @mikehardy
    Contributor

    Hey — one small cross-link.

    In #45, the middle commit (fix: discriminate callback AABB MPPT frames from FC4) hardens how framed/AT callback sessions treat side-channel vs FC4 traffic and avoids flipping negotiated forward mode when harvesting bare aabb. Your thread is G-ASCII / Cloud+HA rather than short-ASCII, so this may not change your day — but if dual-path / probe_timeout weirdness is still in play on current builds, that commit is the data-pathway hardening from our side.

    Not claiming it fixes #21; just putting the pointer where someone hunting transport bugs might find it.

    Cheers,
    Mike

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions