v1.1.2 - the page follows the XGS section

v1.1.2 - the page follows the XGS section

• The page goes in the XGS section when os-xgs-npu is installed - among
  the appliance's pages, in OPNsense's order - and under System when it is
  not; os-xgs-npu moves it when it is installed or removed
• The archive an appliance downloads carries what it reads: the
  documentation, the workflows and the repository's tools left out

v1.1.1

v1.1.1 - taking over a channel under SmartFan IV, and the Arabic in opnsense-arabic

• Taking over a channel under an automatic mode works (#3, #31): the mode is switched to manual
  first and read back, then the duty is written and read back. On the XG 330 rev 2 with SYSFAN under
  SmartFan IV the duty register showed the curve's output, so the old order - duty, read back, then
  mode - failed every time. Handing a channel back to an automatic mode is no longer reported as
  failed when the chip shows its curve's output. Compiled on an XGS 136; not yet run on a fan chip.
• The page's and the widget's Arabic is in opnsense-arabic's catalogue (#32, with
  opnsense-arabic v1.0.1): this plugin merges nothing into the GUI's catalogues any more, and the
  installer removes the merge, its boot hook and its pkg trigger an earlier release left.

v1.1

v1.1 - the page in Arabic, laid out like OPNsense's own, and every reading named

• Arabic, and OPNsense's layout. The page and the widget are in Arabic. Settings and Hardware are laid out like OPNsense's own forms, the readings are cards, and the vital readings sit on top as summary cards.
• A fan the board drives itself is shown by its speed. On the Sophos XGS 3300 the fans are tachometers with no duty register. They were drawn as dashes; each now shows its speed and its hour's range on a working bar, and the page says the board is watched only.
• Sensors are named, not keyed.
  • The coprocessor readings that os-xgs-npu's drivers copy for OPNsense's widget are dropped when their originals are read; before, each such sensor appeared twice, once under its sysctl name.
  • Labels say what a sensor is.
  • The coprocessor's cores and the ports' PHYs fold into one card each, as the processor's cores do.
• An update takes effect where nothing is held. A controller that only watches is restarted by the installer, and so by this self-update. One that holds a fan still waits for its owner.

A firewall on v1.0 takes this release by itself within a day.

v1.0

v1.0 - the first release

Gives a repurposed appliance a fan curve again, arranged so that it can never be the reason a fan
stops: a measured floor per fan, a hard floor in the helper that writes the registers, and a
watch-only mode that touches nothing until a curve is chosen. System: Fan Control, and a
dashboard widget.

• install/install.sh builds the port helper on the firewall; nothing controls a fan until the
  owner turns it on, and an update never turns it on.
• Follows this repository's releases by itself: once a day it takes the latest release when it is
  ahead of what is installed, and never goes back. A running controller keeps its code until its
  next start.
• uninstall.sh removes the plugin hook first, so a removal can never stop OPNsense's boot.