Merge pull request #2715 from jimklimov/issue-2692-nhs-ser-refactor

Refactor `nhs_ser` driver

docs/new-drivers.txt

@@ -124,7 +124,9 @@ and it doesn't appear to be connected, display an error and exit. This
 is the last time your driver is allowed to bail out.
 
 This is usually a good place to create variables like `ups.mfr`,
-`ups.model`, `ups.serial`, and other "one time only" items.
+`ups.model`, `ups.serial`, determine and declare supported instant
+commands (maybe model-dependent, typically for all devices supported
+by the driver), and other "one time only" items.
 
 upsdrv_updateinfo
 ~~~~~~~~~~~~~~~~~
@@ -740,6 +742,12 @@ If your hardware and driver can support a command, register it.
 
 	dstate_addcmd("load.on");
 
+Don't forget to define the implementation for such commands in a common
+method, and register that your driver has an instant command handler at
+all -- with a line in `upsdrv_initinfo()` like:
+
+	upsh.instcmd = blazer_instcmd;
+
 Delays and ser_* functions
 --------------------------
 

docs/nut-names.txt

@@ -446,7 +446,8 @@ Valid SPECs
 
 NOTE: For cursory readers -- the following couple of tables lists just the
 short `SPEC` component of the larger `DOMAIN.CONTEXT.SPEC` naming scheme
-for phase-aware values, as discussed in other sections of this chapter.
+for phase-aware values, as discussed in other sections of this chapter just
+above. These are NOT to be used verbatim as complete data-point names!
 
 Valid with/without context (i.e. per phase or aggregated/averaged)