SRNE/Easun iSolar SMX-II 3.6

[tac2sc]

Added support for Easun iSolar SMX-II 3.6kw

Якщо що, мiй телеграм tac2sc

01M3CFTB76M49ZSWYE42GR0DBQ_20260925T143722836190Z.zip

• 103 readable values across 30 safely separated blocks: telemetry, settings, versions, date/time, temperatures, and daily and cumulative energy.
• Fixed the missing transformer temperature register 546.
• Fixed the word order of 32-bit energy counters to u32_low_first.
• Removed the problematic wide request for registers 256–273; separate ranges are now used.
• Added 36 control capabilities.
• Standard settings are written using FC06.
• Power control uses FC16 with read-modify-write, preserving adjacent bits.
• After a write, the value is verified twice:
  1. An immediate read of the exact register.
  2. Another check during the full polling cycle.
• Settings are also available as disabled-by-default diagnostic sensors, even when writing is not enabled.
• Unsupported optional ranges do not block core telemetry.
• Passwords, reserved registers, the RS485 address, parallel/BMS topology, and ambiguous bitfield registers were intentionally left non-writable.
  Verification:
• 175 profile-specific tests passed.
• All 14 affected test modules passed.
• Python compilation, documentation, and model-catalog checks passed.
• The patch passed git apply --check against a clean copy.

[groove-max]

Thanks for putting this together, and sorry for the slow review. The smaller read blocks and settings readbacks look useful. There are a few things to address before we can merge this:

1. Please submit the source changes against current main. Right now the PR adds a .patch file, so merging it would not actually enable the support.
2. Keep the SMX-II profile separate from generic SRNE support and select it only from reliable device identification. The battery controls currently assume a 24 V system (20–33 V limits), which we can't safely apply to every SRNE inverter. Please include tests showing that other or unidentified SRNE devices don't receive these controls.
3. Keep the controls untested unless we have confirmation for the matching device and commands. The attached support archive was collected through the SMG driver; it doesn't establish the SRNE configuration registers or the successful writes needed for the two tested=true flags.

The controls can be part of the contribution, but their availability needs to be qualified separately from telemetry, rather than enabled across the whole family. I'll leave the PR open for an updated version.

[tac2sc]

ok

I also have an Anenji 5 kW inverter and have been seeing occasional collector disconnects.

One possible cause is the periodic Wi-Fi scan: INTPARA49 appears to request a nearby Wi-Fi scan every minute as part of the background polling cycle.

I disabled this query from runtime polling and left Wi-Fi scans available only on demand in the settings flow:

custom_components/eybond_local/collector/at_runtime.py

-    CollectorAtQueryDefinition(
-        "INTPARA49",
-        "Nearby Wi-Fi scan list reported by the collector.",
-        _decode_text_value("collector_wifi_scan_list"),
-        frozenset({"collector_wifi_scan_list"}),
-    ),
+    # Keep Wi-Fi scans on demand in the settings flow, not background polling.

This may help avoid unnecessary load on the collector and reduce disconnects.