fix: use neutral PI30 VMII identity and document Victor support

Author: Maksym Shtembuliak

CHANGELOG.md

@@ -9,6 +9,10 @@ the GitHub release body should be rendered from the matching version section her
 
 ### Added
 
+- Victor NM-PRO-6.2KW in the supported model catalog, backed by the owner's
+  PI30 archive and specifically reported working controls. It reuses the
+  existing VMII profile; no new device commands are introduced.
+
 - MUST PV3300 Support Archives can collect the optional documented BMS/SOC
   block with one bounded read. This is diagnostic evidence only; normal polling
   and sensor exposure are unchanged until firmware support is confirmed.
@@ -61,6 +65,10 @@ the GitHub release body should be rendered from the matching version section her
 
 ### Fixed
 
+- Shared PI30 `VMII-NXPW5KW` identification no longer labels every matching
+  inverter as PowMr 4.2kW. It displays a neutral firmware-family name while
+  preserving the old name as a compatibility alias, the profile and entity IDs.
+
 - MUST PV/PH18 controls no longer claim local write verification based only on
   cloud-catalog presence. All 27 document-backed controls require Full Control;
   the 20 previously shown in Auto are now correctly untested. No inverter

catalog/inverter_models/models/powmr_4_2kw.json

@@ -39,7 +39,9 @@
       "The same inverter also responds to the local SmartESS 0925 Modbus map through the legacy EyeBond binary tunnel; the commercial model is PowMr 4.2kW, while the raw inverter model reports VMII-NXPW5KW."
     ]
   },
-  "known_limitations": [],
+  "known_limitations": [
+    "The PI30 QMN identity VMII-NXPW5KW is shared with other commercial models and powers. Automatic detection uses the neutral PI30 VMII-NXPW5KW label; it does not uniquely identify PowMr or a 4.2 kW rating."
+  ],
   "knowledge_summary": "PowMr 4.2KW with raw model number VMII-NXPW5KW. The inverter supports PI30 ASCII and the local SmartESS 0925 Modbus runtime through the legacy EyeBond binary tunnel.",
   "source_keys": [
     "fixture_pi30_vmii_nxpw5kw"

catalog/inverter_models/models/victor_nm_pro_6_2kw.json

@@ -0,0 +1,37 @@
+{
+  "schema_version": 1,
+  "model_key": "victor_nm_pro_6_2kw",
+  "manufacturer": "Victor",
+  "model": "NM-PRO-6.2KW",
+  "aliases": [],
+  "lifecycle": "supported",
+  "variants": [
+    {
+      "variant_key": "pi30_vmii_nxpw5kw",
+      "label": "PI30 VMII-NXPW5KW, 25-field 6200 W / 48 V rating",
+      "device_descriptor_keys": ["pi30_vmii_nxpw5kw"],
+      "known_firmware": ["VERFW:00021.12", "VERFW2:00000.00"]
+    }
+  ],
+  "validation": {
+    "hardware": "captured",
+    "telemetry": "confirmed",
+    "controls": "partial"
+  },
+  "coverage": {
+    "runtime_control_surface": "available",
+    "smartess_control_surface": "unknown",
+    "vendor_register_map": "unknown",
+    "notes": [
+      "Uses the existing PI30 VMII profile; no new commands, transport or wider write ranges are introduced.",
+      "The owner confirmed Output Source Priority, Charge Source Priority and battery bulk, float, cut-off and recharge voltage controls on integration 0.1.53. Other controls and firmware variants are not confirmed by this report."
+    ]
+  },
+  "known_limitations": [
+    "QMN reports the shared VMII-NXPW5KW identity, not a unique Victor retail model. Automatic detection therefore displays PI30 VMII-NXPW5KW; the public catalog records the owner-reported brand separately.",
+    "QVFW3 and optional QET/QLT/QT energy commands returned NAK in the supplied archive.",
+    "Hardware confirmation was supplied for integration 0.1.53; replay on current code does not replace a current-version hardware test."
+  ],
+  "knowledge_summary": "Victor NM-PRO-6.2KW is confirmed by the issue #54 owner and support archive as a 6200 W / 48 V PI30 inverter using the shared VMII-NXPW5KW profile, with working telemetry and a specifically reported subset of controls.",
+  "source_keys": ["support_archive_issue_54_victor_nm_pro_6_2kw"]
+}

catalog/inverter_models/sources/support_archive_issue_54_victor_nm_pro_6_2kw.json

@@ -0,0 +1,18 @@
+{
+  "schema_version": 1,
+  "source_key": "support_archive_issue_54_victor_nm_pro_6_2kw",
+  "kind": "support_archive",
+  "title": "Victor NM-PRO-6.2KW PI30 archive and owner control report",
+  "reference": "project-issue:54",
+  "captured_at": "2026-09-30",
+  "visibility": "public",
+  "summary_publishable": true,
+  "summary": "The owner identifies the unit as Victor NM-PRO-6.2KW and reports working telemetry on integration 0.1.53. The archive records QPI=PI30, shared QMN=VMII-NXPW5KW, a 25-field QPIRI response rated 6200 W / 48 V, live QPIGS, QFLAG, QMOD and firmware replies. The owner explicitly confirms Output Source Priority, Charge Source Priority and battery bulk, float, cut-off and recharge voltage changes. The read-only archive itself is not a write trace, and the report does not qualify every inherited control or uniquely identify the brand from QMN.",
+  "assertions": [
+    "commercial_identity",
+    "runtime_compatibility",
+    "telemetry_validation",
+    "hardware_test",
+    "write_validation"
+  ]
+}

custom_components/eybond_local/protocol_catalogs/inverter_catalog.json

@@ -2689,7 +2689,10 @@
   {
    "entry_key": "pi30_vmii_nxpw5kw",
    "surface_key": "pi30_vmii_full",
-   "model_name": "PowMr 4.2kW",
+   "model_name": "PI30 VMII-NXPW5KW",
+   "aliases": [
+    "PowMr 4.2kW"
+   ],
    "priority": 220,
    "anchors": [
     {
@@ -2703,7 +2706,8 @@
    ],
    "provenance": {
     "sources": [
-     "fixture:pi30-vmii-nxpw5kw-live-capture"
+     "fixture:pi30-vmii-nxpw5kw-live-capture",
+     "project-issue:54"
     ],
     "confidence": "capture-derived"
    }

docs/generated/INVERTER_MODEL_CATALOG.generated.md

@@ -4,7 +4,7 @@ Generated by `tools/model_catalog.py`. Do not edit by hand.
 
 - Model catalog version: 2026.08.2
 - Runtime inverter catalog version: 2026.08.8
-- Models: 20 | Variants: 22
+- Models: 21 | Variants: 23
 
 ## How To Read This Catalog
 
@@ -45,6 +45,7 @@ This page describes what has been confirmed for a specific inverter model or mod
 | MUST-compatible | PV3300 | must_pv_ph18 | anchors | full | partial | partial | captured |
 | Sandisolar | SD 11KP48V WIFI | modbus_smg | fingerprint | full | partial | partial | captured |
 | SRNE-compatible | Modbus family | srne_modbus | anchors | partial | partial | none | none |
+| Victor | NM-PRO-6.2KW | pi30 | anchors | full | confirmed | partial | captured |
 | Yingfa | YF6.2K-LEL-1B | pi30 | anchors | full | confirmed | partial | captured |
 | ZL Power | GSIII 12 kW | eybond_09c1 | anchors | partial | partial | none | captured |
 
@@ -449,7 +450,8 @@ Runtime descriptors with no specific commercial model record. These are generic
       - Protocol: pi30 | Detection: anchors (protocol.protocol_id=PI30; identity.model_number=VMII-NXPW5KW)
       - Tier: full | Read-only: no | Profile: pi30_ascii/models/vmii_nxpw5kw.json | Schema: pi30_ascii/models/vmii_nxpw5kw.json
       - Capabilities: 20 (tested 20); support tiers: standard 20 | Telemetry: 77 measurements, 16 binary sensors
-- Known limitations: —
+- Known limitations:
+  - The PI30 QMN identity VMII-NXPW5KW is shared with other commercial models and powers. Automatic detection uses the neutral PI30 VMII-NXPW5KW label; it does not uniquely identify PowMr or a 4.2 kW rating.
 - Evidence: 1 source(s)
 
 ### Sandisolar — SD 11KP48V WIFI (`sandisolar_sd_11kp48v_wifi`)
@@ -523,6 +525,30 @@ Runtime descriptors with no specific commercial model record. These are generic
   - Detection relies on the product-info register block containing an SRNE-like marker; commercial model names may need follow-up catalog entries.
 - Evidence: 1 source(s)
 
+### Victor — NM-PRO-6.2KW (`victor_nm_pro_6_2kw`)
+
+- Lifecycle: supported
+- Aliases: —
+- Validation: hardware captured, telemetry confirmed, controls partial
+- Coverage: runtime available, cloud unknown, vendor map unknown
+  - Coverage notes:
+    - Uses the existing PI30 VMII profile; no new commands, transport or wider write ranges are introduced.
+    - The owner confirmed Output Source Priority, Charge Source Priority and battery bulk, float, cut-off and recharge voltage controls on integration 0.1.53. Other controls and firmware variants are not confirmed by this report.
+- Summary: Victor NM-PRO-6.2KW is confirmed by the issue #54 owner and support archive as a 6200 W / 48 V PI30 inverter using the shared VMII-NXPW5KW profile, with working telemetry and a specifically reported subset of controls.
+- Variants:
+  - `pi30_vmii_nxpw5kw` — PI30 VMII-NXPW5KW, 25-field 6200 W / 48 V rating
+    - Descriptors: pi30_vmii_nxpw5kw
+    - Known firmware: VERFW:00021.12, VERFW2:00000.00
+    - `pi30_vmii_nxpw5kw` → surface `pi30_vmii_full` (driver pi30, variant vmii_nxpw5kw)
+      - Protocol: pi30 | Detection: anchors (protocol.protocol_id=PI30; identity.model_number=VMII-NXPW5KW)
+      - Tier: full | Read-only: no | Profile: pi30_ascii/models/vmii_nxpw5kw.json | Schema: pi30_ascii/models/vmii_nxpw5kw.json
+      - Capabilities: 20 (tested 20); support tiers: standard 20 | Telemetry: 77 measurements, 16 binary sensors
+- Known limitations:
+  - QMN reports the shared VMII-NXPW5KW identity, not a unique Victor retail model. Automatic detection therefore displays PI30 VMII-NXPW5KW; the public catalog records the owner-reported brand separately.
+  - QVFW3 and optional QET/QLT/QT energy commands returned NAK in the supplied archive.
+  - Hardware confirmation was supplied for integration 0.1.53; replay on current code does not replace a current-version hardware test.
+- Evidence: 1 source(s)
+
 ### Yingfa — YF6.2K-2K-LEL-IF (`yingfa_yf6_2k_2k_lel_if`)
 
 - Lifecycle: research

docs/user/RUNTIME_AND_INVERTER.md

@@ -17,6 +17,20 @@ The inverter may appear after the collector. A slow protocol or a Full scan can
 take more than one normal polling interval. **Poll Context** shows whether the
 integration is detecting an inverter, reading it, or only checking the collector.
 
+### PI30 names shared by several brands
+
+Some inverters report a firmware identifier instead of their retail model.
+For example, `VMII-NXPW5KW` appears on both PowMr and Victor units, including
+different power ratings. These devices appear as **PI30 VMII-NXPW5KW**; the
+name alone does not mean 5 kW, 4.2 kW, or a particular brand. Rated power is read
+separately from the inverter.
+
+Older builds labelled this shared profile **PowMr 4.2kW**. The corrected name
+keeps the same protocol, profile, controls and entity IDs. You do not need to
+delete and add the device again. A custom name set in Home Assistant is retained.
+The model catalog lists confirmed retail models separately; it does not turn a
+shared firmware identifier into a unique brand match.
+
 ## Polling and inverter detection
 
 Open **Settings → Devices & Services → EyeBond Local → Configure → Polling and

tests/test_compiled_detection_catalog.py

@@ -153,6 +153,21 @@ def test_unique_persisted_model_resolves_exact_untested_control_surface(self) ->
         self.assertEqual(legacy_descriptor.key, descriptor.key)
         self.assertEqual(legacy_surface.key, surface.key)
 
+    def test_vmii_neutral_name_preserves_legacy_surface_without_brand_inference(self) -> None:
+        old = resolve_unique_persisted_model_surface("PowMr 4.2kW")
+        new = resolve_unique_persisted_model_surface("PI30 VMII-NXPW5KW")
+        self.assertIsNotNone(old)
+        self.assertIsNotNone(new)
+        self.assertEqual(old[0].key, "pi30_vmii_nxpw5kw")
+        self.assertEqual(old, new)
+        self.assertEqual(new[1].variant_key, "vmii_nxpw5kw")
+        self.assertEqual(new[1].profile_name, "pi30_ascii/models/vmii_nxpw5kw.json")
+        self.assertTrue(model_names_share_catalog_identity("PowMr 4.2kW", "PI30 VMII-NXPW5KW"))
+        # A public retail catalog entry is not a runtime identity alias. The
+        # same QMN is shared by multiple brands and another (MAX) response shape.
+        self.assertIsNone(resolve_unique_persisted_model_surface("Victor NM-PRO-6.2KW"))
+        self.assertFalse(model_names_share_catalog_identity("PI30 VMII-NXPW5KW", "PI30 6200"))
+
     def test_persisted_model_resolution_fails_closed_when_alias_is_ambiguous(self) -> None:
         catalog = load_compiled_detection_catalog()
         ambiguous = replace(

tests/test_model_catalog.py

@@ -87,6 +87,19 @@ def _ok_model(key: str = "mdl_a", descriptor: str = "smg_6200", **overrides) ->
 
 
 class RealCatalogTests(unittest.TestCase):
+    def test_victor_6200_uses_shared_pi30_surface_with_partial_write_evidence(self):
+        models = {m["model_key"]: m for m in load_models()}
+        victor = models["victor_nm_pro_6_2kw"]
+        self.assertEqual(victor["validation"], {"hardware": "captured", "telemetry": "confirmed", "controls": "partial"})
+        self.assertEqual(_primary_resolution(victor, RUNTIME).surface_key, "pi30_vmii_full")
+        self.assertEqual(_primary_resolution(models["powmr_4_2kw"], RUNTIME).surface_key, "pi30_vmii_full")
+        self.assertEqual(victor["variants"][0]["device_descriptor_keys"], ["pi30_vmii_nxpw5kw"])
+        self.assertIn("support_archive_issue_54_victor_nm_pro_6_2kw", victor["source_keys"])
+        source = next(s for s in load_sources() if s["source_key"] == victor["source_keys"][0])
+        self.assertIn("write_validation", source["assertions"])
+        self.assertIn("0.1.53", source["summary"])
+        self.assertIn("Charge Source Priority", source["summary"])
+
     def test_issue_6_correction_does_not_remove_independent_issue_27_evidence(self):
         models = {m["model_key"]: m for m in load_models()}
         unresolved = models["yingfa_yf6_2k_2k_lel_if"]

tests/test_pi30_driver.py

@@ -286,7 +286,7 @@ async def test_probe_maps_vmii_model_number_to_display_name(self) -> None:
         inverter = await driver.async_probe(transport, target)
 
         assert inverter is not None
-        self.assertEqual(inverter.model_name, "PowMr 4.2kW")
+        self.assertEqual(inverter.model_name, "PI30 VMII-NXPW5KW")
         self.assertEqual(inverter.details["model_number"], "VMII-NXPW5KW")
         self.assertEqual(inverter.profile_name, "pi30_ascii/models/vmii_nxpw5kw.json")
         self.assertEqual(inverter.register_schema_name, "pi30_ascii/models/vmii_nxpw5kw.json")
@@ -346,11 +346,42 @@ async def test_probe_selects_vmii_model_overlay_when_model_number_matches(self)
         inverter = await driver.async_probe(transport, target)
 
         assert inverter is not None
-        self.assertEqual(inverter.model_name, "PowMr 4.2kW")
+        self.assertEqual(inverter.model_name, "PI30 VMII-NXPW5KW")
         self.assertEqual(inverter.variant_key, "vmii_nxpw5kw")
         self.assertEqual(inverter.profile_name, "pi30_ascii/models/vmii_nxpw5kw.json")
         self.assertEqual(inverter.register_schema_name, "pi30_ascii/models/vmii_nxpw5kw.json")
 
+    async def test_victor_6200_vmii_rating_and_telemetry_do_not_infer_retail_brand(self) -> None:
+        """Issue54 response shape, with a synthetic serial and no live writes."""
+        from custom_components.eybond_local.metadata.profile_loader import load_driver_profile
+
+        target = ProbeTarget(devcode=0x0994, collector_addr=1, device_addr=0)
+        replies = {
+            "QPI": "PI30", "QID": "99000000000054", "QMN": "VMII-NXPW5KW",
+            "QPIRI": "230.0 26.9 230.0 50.0 26.9 6200 6200 48.0 46.0 42.0 55.2 54.6 2 030 030 1 0 1 1 01 0 0 54.0 0 1",
+            "QFLAG": "EabkuxzDjvy", "QMOD": "L",
+            "QPIWS": "10000000000000000000000000000000",
+            "QVFW": "VERFW:00021.12", "QVFW2": "VERFW2:00000.00",
+            "QPIGS": "232.1 50.0 232.1 50.0 0440 0227 007 429 54.60 000 100 0043 00.0 000.0 00.00 00000 00010101 00 00 00000 110",
+            "Q1": "00 00 00 000 042 030 043 00 00 000 0030 0000 13",
+            "QVFW3": "NAK", "QET": "NAK", "QLT": "NAK", "QT": "NAK",
+        }
+        transport = _FakeTransport({(target.devcode, target.collector_addr, k): v for k, v in replies.items()})
+        driver = Pi30Driver()
+        inverter = await driver.async_probe(transport, target)
+        self.assertIsNotNone(inverter)
+        self.assertEqual(inverter.model_name, "PI30 VMII-NXPW5KW")
+        self.assertEqual(inverter.variant_key, "vmii_nxpw5kw")
+        self.assertEqual(inverter.details["output_rating_active_power"], 6200)
+        self.assertEqual(inverter.details["battery_rating_voltage"], 48)
+        profile = load_driver_profile("pi30_ascii/models/vmii_nxpw5kw.json")
+        self.assertEqual({c.key for c in inverter.capabilities}, {c.key for c in profile.capabilities})
+        values = await _read_values(driver, transport, inverter)
+        self.assertEqual(values["battery_voltage"], 54.6)
+        self.assertEqual(values["output_active_power"], 227)
+        self.assertEqual(values["operating_mode"], "Line")
+        self.assertTrue(all(command.startswith("Q") for command in transport.commands))
+
     async def test_probe_collects_variant_detection_facts(self) -> None:
         driver = Pi30Driver()
         target = ProbeTarget(devcode=0x0994, collector_addr=0x01, device_addr=0)