mkaiser/Sungrow-SHx-Inverter-Modbus-Home-Assistant v0.1.0a29

on GitHub

0.1.0a29: the diagnosis and its capability tests

The device survey is now the diagnosis, in two modes:

• Run read-only diagnosis reads your inverter and writes nothing.
• Run diagnosis with capability tests reads the same, then runs the
  capability test (until now the control test): it writes each setting,
  checks it and puts it back.

Both end with a report of feature sets (forced charge and discharge, the
battery limits, the feed-in limit, cutting PV, the schedules, the site import
limit, forced startup, backup, load control, stop and start), each with how far
this run tested it: confirmed, wrong scale, write refused, inconclusive,
readable, not available or not read.

New:

• Forced startup under low SoC is a switch rather than a button: on wakes
  an inverter waiting in low-SoC standby and keeps it running, off sends it
  back. Created where a watched write is on record (SH-RT on P023).
• A forced startup check: diagnosis.sh tests <host> --forced-startup, or
  the run_capability_test action with forced_startup: true, run while the
  inverter is in standby with its battery at the minimum and no PV.

Renamed, with your settings carried over:

• device-survey/ is device-diagnosis/, and its launcher is
  scripts/diagnosis.sh (.cmd on Windows); diagnosis.sh tests ...
  replaces survey.sh control ....
• The actions are run_diagnosis and run_capability_test. An automation
  calling run_survey or run_control_test needs the new name.
• Your options, permissions and entity ids carry over on the first start, and
  so does an unfinished test's snapshot, which its repair still puts back.