@@ -4,6 +4,28 @@ All notable changes to this project are documented here. The format is based on
 [Keep a Changelog](https://keepachangelog.com/), and this project adheres to
 [Semantic Versioning](https://semver.org/).
 
+## [0.1.7] - 2026-07-02
+
+### Added
+- **Separate STATUS and COM LEDs, like a factory collector.** A new `com_led_pin`
+  drives an inverter-communication activity LED alongside the existing `status_led_pin`
+  connection-state LED. With both pins, each LED has one job. With only `status_led_pin`
+  (single-LED dev boards) that LED shows both — solid when the bridge is connected and
+  idle, flickering while the inverter is talked to. With only `com_led_pin` it is a pure
+  activity light. Each pin takes the full pin schema, so per-pin `inverted:` is available.
+
+### Changed
+- **The activity (COM) indicator now flickers instead of holding lit, and reflects real
+  inverter transactions only.** It is armed by inverter UART traffic — a forward and the
+  reply *while that forward is awaiting a response* — never by HA↔bridge TCP chatter, and
+  it *toggles* (capped at ~10 Hz) rather than staying lit for an activity window, so a
+  heavy read/write load reads as a fast flicker and never a solid glow.
+- **Idle-line RX noise no longer lights the COM LED.** Bytes arriving on the inverter UART
+  when no forward is pending (electrical noise on a floating/unwired RX, or an idle bus)
+  are ignored, so a bridge connected to HA before its inverter is wired or powered on
+  stays solid instead of flickering constantly.
+- `BRIDGE_VERSION` bumped to `0.1.7`.
+
 ## [0.1.6] - 2026-07-01
 
 ### Changed
@@ -74,6 +96,7 @@ Home Assistant integration. Highlights:
 - Status LED indication and the `AT+VDTU` virtual-bridge capability probe.
 - Web installer (GitHub Pages) for the ESP8266 and ESP32 presets.
 
+[0.1.7]: https://github.com/groove-max/esp-eybond-collector/compare/v0.1.6...v0.1.7
 [0.1.6]: https://github.com/groove-max/esp-eybond-collector/compare/v0.1.5...v0.1.6
 [0.1.5]: https://github.com/groove-max/esp-eybond-collector/compare/v0.1.4...v0.1.5
 [0.1.0]: https://github.com/groove-max/esp-eybond-collector/releases/tag/v0.1.0
 
@@ -29,7 +29,7 @@ The bridge stays on your LAN and does not connect to SmartESS cloud.
 - ESPHome features: OTA updates, logs, captive portal, and optional ESPHome entities.
 - Wi-Fi management from EyeBond Local where supported.
 - Optional runtime UART baud-rate select on ESP8266/ESP32 when you add the board through the ESPHome integration.
-- Built-in status LED indication on the release presets.
+- Built-in status LED indication on the release presets, with an optional `com_led_pin` for a separate inverter-communication LED.
 
 What you do **not** get:
 
@@ -152,6 +152,8 @@ Release presets use one pinout for all physical links:
 
 For TTL and RS232, use TX/RX/GND and leave the DE/RE pin unconnected. For RS485, connect DE and RE together to the listed DE/RE pin.
 
+The onboard LED in the table is `status_led_pin`; on a single LED it shows both connection state and an inverter-communication flicker. Add an optional `com_led_pin` for a dedicated communication LED — see [Status and COM LEDs](docs/FLASHING.md#status-and-com-leds).
+
 ---
 
 ## Adding it to Home Assistant
 
@@ -29,7 +29,7 @@
 - Можливості ESPHome: OTA-оновлення, журнали, сторінка налаштування Wi-Fi і додаткові сутності ESPHome.
 - Керування Wi-Fi з EyeBond Local там, де це підтримується.
 - Необов'язковий перемикач швидкості UART на ESP8266/ESP32, якщо додати плату через інтеграцію ESPHome.
-- Індикацію стану через вбудований світлодіод плати.
+- Індикацію стану через вбудований світлодіод плати, з необов'язковим `com_led_pin` для окремого світлодіода зв'язку з інвертором.
 
 Чого тут **немає**:
 
@@ -152,6 +152,8 @@ select:
 
 Для TTL і RS232 використовуйте TX/RX/GND і не підключайте DE/RE. Для RS485 з'єднайте DE та RE разом і підключіть до вказаного DE/RE-піна.
 
+Світлодіод у таблиці — це `status_led_pin`; на одному світлодіоді він показує і стан підключення, і мерехтіння зв'язку з інвертором. Додайте необов'язковий `com_led_pin` для окремого світлодіода зв'язку — див. [Світлодіоди стану (STATUS) і зв'язку (COM)](docs/FLASHING.uk.md#світлодіоди-стану-status-і-звязку-com).
+
 ---
 
 ## Додавання в Home Assistant
 
@@ -31,6 +31,7 @@
 CONF_COLLECTOR_ADDR = "collector_addr"
 CONF_FLOW_CONTROL_PIN = "flow_control_pin"
 CONF_STATUS_LED_PIN = "status_led_pin"
+CONF_COM_LED_PIN = "com_led_pin"
 CONF_BLE_PROVISIONING = "ble_provisioning"
 
 eybond_collector_ns = cg.esphome_ns.namespace("eybond_collector")
@@ -65,6 +66,7 @@ def _validate_pn(value):
             cv.Optional(CONF_COLLECTOR_ADDR, default=0x01): cv.hex_uint8_t,
             cv.Optional(CONF_FLOW_CONTROL_PIN): pins.gpio_output_pin_schema,
             cv.Optional(CONF_STATUS_LED_PIN): pins.gpio_output_pin_schema,
+            cv.Optional(CONF_COM_LED_PIN): pins.gpio_output_pin_schema,
             cv.Optional(CONF_BLE_PROVISIONING, default=False): cv.boolean,
         }
     )
@@ -118,6 +120,9 @@ async def to_code(config):
     if CONF_STATUS_LED_PIN in config:
         pin = await cg.gpio_pin_expression(config[CONF_STATUS_LED_PIN])
         cg.add(var.set_status_led_pin(pin))
+    if CONF_COM_LED_PIN in config:
+        pin = await cg.gpio_pin_expression(config[CONF_COM_LED_PIN])
+        cg.add(var.set_com_led_pin(pin))
     if config[CONF_BLE_PROVISIONING]:
         cg.add_define("USE_EYBOND_BLE")
         cg.add(var.set_ble_provisioning(True))
@@ -138,6 +138,11 @@ class CollectorCore {
   bool connected() const { return link_state_ == LinkState::CONNECTED; }
   const std::string &server_host() const { return server_host_; }
   uint16_t server_port() const { return server_port_; }
+  // True only while a forwarded request is awaiting its inverter reply, so a "com"
+  // activity LED lights for real transactions and not idle-line noise on a floating
+  // or disconnected UART RX (which a connected bridge would otherwise show as constant
+  // flicker whenever the inverter is unwired or powered off).
+  bool awaiting_uart_response() const { return bridge_state_ == BridgeState::WAITING_RESPONSE; }
 
  private:
   enum class LinkState : uint8_t { DISCONNECTED, CONNECTING, CONNECTED };
 
@@ -39,10 +39,20 @@ namespace eybond_collector {
 
 static const char *const TAG = "eybond_collector";
 
+// Status/com LED timing.
+static const uint32_t STATUS_FAST_BLINK_MS = 250;   // no Wi-Fi
+static const uint32_t STATUS_SLOW_BLINK_MS = 1000;  // Wi-Fi up, bridge not connected
+static const uint32_t COM_FLICKER_MS = 50;          // com toggle cap -> ~10 Hz flicker, never solid
+static const uint32_t COM_HOLD_MS = 120;            // treat as "data flowing" for this long after an event
+
 void EybondCollector::setup() {
   if (status_led_pin_ != nullptr) {
     status_led_pin_->setup();
-    this->write_status_led_(false);
+    this->write_led_(status_led_pin_, &status_led_state_, false);
+  }
+  if (com_led_pin_ != nullptr) {
+    com_led_pin_->setup();
+    this->write_led_(com_led_pin_, &com_led_state_, false);
   }
 
   baud_pref_ = global_preferences->make_preference<uint32_t>(BAUD_PREF_HASH);
@@ -117,7 +127,7 @@ void EybondCollector::loop() {
       core_->on_tcp_closed(now);
     }
     this->process_reboot_(now);
-    this->update_status_led_(now);
+    this->update_leds_(now);
     return;
   }
 
@@ -158,7 +168,6 @@ void EybondCollector::loop() {
       if (read_len <= 0) {
         break;
       }
-      this->note_activity_(now);
       core_->on_tcp_data(buffer, static_cast<size_t>(read_len), now);
       available = tcp_.available();
     }
@@ -170,7 +179,11 @@ void EybondCollector::loop() {
     if (!this->read_byte(&byte)) {
       break;
     }
-    this->note_activity_(millis());
+    // Only inverter bytes answering a pending forward are real comms; idle-line
+    // noise on a floating/disconnected RX must not light the com LED.
+    if (core_->awaiting_uart_response()) {
+      this->note_activity_(millis());
+    }
     core_->on_uart_data(&byte, 1, millis());
   }
 
@@ -179,7 +192,7 @@ void EybondCollector::loop() {
   this->process_wifi_apply_(millis());
   this->process_reboot_(millis());
   this->poll_wifi_scan_(millis());
-  this->update_status_led_(millis());
+  this->update_leds_(millis());
 }
 
 bool EybondCollector::query_param(uint8_t parameter, std::string *out) {
@@ -668,7 +681,6 @@ void EybondCollector::tcp_connect(const std::string &host, uint16_t port) {
 
 void EybondCollector::tcp_send(const uint8_t *data, size_t len) {
   if (tcp_up_) {
-    this->note_activity_(millis());
     tcp_.write(data, len);
   }
 }
@@ -698,45 +710,77 @@ void EybondCollector::uart_send(const uint8_t *data, size_t len) {
 }
 
 void EybondCollector::note_activity_(uint32_t now) {
-  status_led_activity_until_ms_ = now + 90;
-}
-
-void EybondCollector::update_status_led_(uint32_t now) {
-  if (status_led_pin_ == nullptr) {
+  // Armed only by inverter UART traffic (forward TX + inverter reply), never by
+  // HA<->bridge TCP chatter, so the com indicator means real inverter comms.
+  last_activity_ms_ = now;
+}
+
+// Two logical indicators, like the factory collector's STATUS and COM LEDs:
+//   * STATUS = connection state: fast blink (no Wi-Fi), slow blink (Wi-Fi but no
+//     bridge), solid (bridge connected).
+//   * COM = inverter communication: flickers while data flows on the UART, dark
+//     when idle. It TOGGLES (capped at COM_FLICKER_MS) rather than holding lit, so
+//     heavy load reads as a fast flicker and never as a solid glow.
+// Two pins -> each drives its own LED. Only status_led_pin (single-LED dev boards)
+// -> the status LED also carries com: solid when connected+idle, flickering while
+// inverter data flows. Only com_led_pin -> a pure activity light.
+void EybondCollector::update_leds_(uint32_t now) {
+  const bool wifi_up = network::is_connected();
+  const bool linked = wifi_up && tcp_up_;
+  const bool active = linked && (now - last_activity_ms_) < COM_HOLD_MS;
+
+  const bool have_status = status_led_pin_ != nullptr;
+  const bool have_com = com_led_pin_ != nullptr;
+  if (!have_status && !have_com) {
     return;
   }
 
-  if (!network::is_connected()) {
-    // Wi-Fi is not connected yet: quick blink so the board is visibly alive.
-    if (now - status_led_last_toggle_ms_ >= 250) {
-      this->write_status_led_(!status_led_state_);
-      status_led_last_toggle_ms_ = now;
+  // COM flicker phase.
+  if (active) {
+    if (now - com_last_toggle_ms_ >= COM_FLICKER_MS) {
+      com_phase_ = !com_phase_;
+      com_last_toggle_ms_ = now;
     }
+  } else {
+    com_phase_ = false;
+  }
+  if (have_com) {
+    this->write_led_(com_led_pin_, &com_led_state_, com_phase_);
+  }
+
+  if (!have_status) {
     return;
   }
 
-  if (!tcp_up_) {
-    // Wi-Fi is up, but EyeBond Local is not connected yet: slow blink.
-    if (now - status_led_last_toggle_ms_ >= 1000) {
-      this->write_status_led_(!status_led_state_);
+  // STATUS LED (also carries com when it is the only LED).
+  bool target;
+  if (!wifi_up) {
+    if (now - status_led_last_toggle_ms_ >= STATUS_FAST_BLINK_MS) {
+      status_led_phase_ = !status_led_phase_;
       status_led_last_toggle_ms_ = now;
     }
-    return;
+    target = status_led_phase_;
+  } else if (!linked) {
+    if (now - status_led_last_toggle_ms_ >= STATUS_SLOW_BLINK_MS) {
+      status_led_phase_ = !status_led_phase_;
+      status_led_last_toggle_ms_ = now;
+    }
+    target = status_led_phase_;
+  } else if (have_com) {
+    target = true;  // dedicated com LED exists -> status LED is a pure link light
+  } else {
+    target = active ? com_phase_ : true;  // single LED: solid when idle, flicker on traffic
+    status_led_phase_ = target;
   }
-
-  // Connected: a combined RX+TX activity light — lit while data is flowing on
-  // either the network (TCP) or the inverter (UART) side, dark when idle. The
-  // activity window is (re)armed by note_activity_() on every send/receive, so a
-  // single packet gives a ~90 ms flash and a burst holds the LED on.
-  this->write_status_led_(static_cast<int32_t>(status_led_activity_until_ms_ - now) > 0);
+  this->write_led_(status_led_pin_, &status_led_state_, target);
 }
 
-void EybondCollector::write_status_led_(bool on) {
-  if (status_led_pin_ == nullptr || status_led_state_ == on) {
+void EybondCollector::write_led_(GPIOPin *pin, bool *state, bool on) {
+  if (pin == nullptr || *state == on) {
     return;
   }
-  status_led_pin_->digital_write(on);
-  status_led_state_ = on;
+  pin->digital_write(on);
+  *state = on;
 }
 
 std::string EybondCollector::wifi_rssi() {
 
@@ -71,6 +71,7 @@ class EybondCollector : public Component, public uart::UARTDevice, private eybon
   void set_collector_addr(uint8_t addr) { core_config_.collector_addr = addr; }
   void set_flow_control_pin(GPIOPin *pin) { flow_control_pin_ = pin; }
   void set_status_led_pin(GPIOPin *pin) { status_led_pin_ = pin; }
+  void set_com_led_pin(GPIOPin *pin) { com_led_pin_ = pin; }
   void set_ble_provisioning(bool enabled) { ble_enabled_ = enabled; }
 
   // Runtime inverter-UART re-baud (select entity, AT+UART=, FC=3 param 34).
@@ -104,8 +105,8 @@ class EybondCollector : public Component, public uart::UARTDevice, private eybon
   void poll_wifi_scan_(uint32_t now);
   void configure_fallback_ap_(const std::string &pn);
   void note_activity_(uint32_t now);
-  void update_status_led_(uint32_t now);
-  void write_status_led_(bool on);
+  void update_leds_(uint32_t now);
+  void write_led_(GPIOPin *pin, bool *state, bool on);
   std::string uart_settings_string_() const;
   void restore_persisted_baud_rate_();
   void persist_baud_rate_(uint32_t baud);
@@ -143,8 +144,16 @@ class EybondCollector : public Component, public uart::UARTDevice, private eybon
   GPIOPin *flow_control_pin_{nullptr};
   GPIOPin *status_led_pin_{nullptr};
   bool status_led_state_{true};
-  uint32_t status_led_activity_until_ms_{0};
+  bool status_led_phase_{false};
   uint32_t status_led_last_toggle_ms_{0};
+
+  // Communication (com) LED: its own pin, or overlaid on the status LED when no
+  // com pin is set (single-LED dev boards). Flickers on inverter UART traffic.
+  GPIOPin *com_led_pin_{nullptr};
+  bool com_led_state_{true};
+  bool com_phase_{false};
+  uint32_t com_last_toggle_ms_{0};
+  uint32_t last_activity_ms_{0};
   std::string pn_override_;
   uint16_t udp_port_{58899};
   std::string static_server_host_;
 
@@ -9,7 +9,7 @@ namespace eybond {
 
 // Bridge firmware version, embedded in the FC=2 param-6 hardware_version marker
 // ("esp-collector/<version>/<platform>") the integration keys the bridge on.
-constexpr const char *BRIDGE_VERSION = "0.1.6";
+constexpr const char *BRIDGE_VERSION = "0.1.7";
 
 struct CollectorProfile {
   std::string pn;  // set at startup (config override or synthesized from MAC)
 
@@ -103,7 +103,7 @@ Open the YAML and check:
 - `board:` matches your ESP board;
 - `tx_pin` and `rx_pin` match your wiring;
 - `flow_control_pin` is set when you use a classic RS485 module with DE/RE;
-- `status_led_pin` matches the board's built-in LED if you want status indication;
+- `status_led_pin` / `com_led_pin` drive the status and communication LEDs (see below);
 - `baud_rate` matches the inverter family.
 
 The ready-made browser firmware starts at `9600`. Typical baud rates:
@@ -204,24 +204,49 @@ On BK72xx / LibreTiny, runtime baud-rate switching is not available. Change `bau
 
 The ESP32 BLE profile is YAML-only in the first release. BLE + Wi-Fi is large, so to fit the default 4 MB app partition the profile omits `api:`, `captive_portal:` and the baud `select:` (BLE provisioning replaces the captive portal; the EyeBond Local integration uses its own protocol, not the ESPHome API). OTA still works. To add those back, use a board with more flash and a larger app-partition layout — otherwise the image silently overflows and the board boot-loops.
 
-## Status LED
+## Status and COM LEDs
 
-The release presets use the board's built-in LED:
+The bridge drives two logical indicators, like a factory collector's **STATUS** and
+**COM** LEDs — configured with `status_led_pin` and `com_led_pin` (either or both):
+
+- **STATUS** — connection state.
+- **COM** — inverter communication activity.
+
+The release presets wire a single built-in LED to `status_led_pin`:
 
 - Wemos D1 mini: GPIO2 / D4, inverted.
 - ESP-WROOM-32 DevKit: GPIO2.
 
 On ESP32, GPIO2 is a boot strapping pin. The built-in LED is fine on typical DevKit boards, but do not add external pull-up/down resistors or heavy loads to GPIO2.
 
-Indication:
+How the configured pins map to behaviour:
+
+| Configured pins | Behaviour |
+|---|---|
+| `status_led_pin` only (single-LED dev boards) | One LED shows **both**: the connection state, plus a com flicker overlaid whenever the inverter is talked to. |
+| `status_led_pin` + `com_led_pin` | STATUS and COM each drive their own LED. |
+| `com_led_pin` only | A pure activity light: dark when idle, flickers on inverter traffic. |
+
+STATUS indication:
 
-| LED | State |
+| STATUS LED | State |
 |---|---|
 | Fast blink | The board is not connected to Wi-Fi yet. |
 | Slow blink | Wi-Fi is connected, but EyeBond Local has not connected to the bridge yet. |
-| Dark, flickers on traffic | The bridge is connected: the LED stays off when idle and flickers in time with data moving between Home Assistant, the bridge, and the inverter. |
+| Solid on | The bridge is connected and idle. |
+
+COM indication:
+
+| COM LED | State |
+|---|---|
+| Dark | No inverter traffic. |
+| Flicker | Data is flowing to/from the inverter (a forward and its reply). The LED *toggles* rather than holding lit, so heavy load reads as a fast flicker and never a solid glow. |
+
+In the single-LED combined mode, the "solid on" connected state is briefly interrupted
+by the com flicker whenever the inverter is polled.
 
-If your board uses another LED pin or inverted logic, adjust `status_led_pin` in YAML.
+Each pin takes the full pin schema, so per-pin inversion is available, e.g.
+`status_led_pin: { number: GPIO2, inverted: true }`.
 
 ## Troubleshooting