Lack of "set" echo means not logging e.g. set/relay/on

[mitra42]

There is an issue where logger is not capturing things like a change to the relay

Diagnosis:

• Logger isn't logging set - that is (I think) temporarily fixed
  • undo when fixed
• Needs to echo back form node when set takes effect.
• Once echoing, UX should ignore "set" and only listen to !set

What happens normally - for e.g. a sensor reading
e.g. SensorHT::set calls OUTFloat::set calls "send" and "sendWired"

• Check - can we do this in System_Base::dispatchTwig

Cases this occurs ....

• WiFi - No action needed as special case and only (SPIFFS or Captive) set
• Power - doesnt' have "Inputs" (maybe it could, but not sure if that is an advantage).
  • so echo from SystemPower::dispatchTwig
• mqtt/hostname - not changeable via UX, and currently no meaningful alternative
  • probably dont need to echo BUT will need to see the sequence if reads different mqtt, does it resend etc
  • test by entering bad MQTT in main.cpp and correct in /dat
• frugal-iot - echo all back, but note also doing stuff so can change frugal-iot/project which is different
• captive - language_code - echo (maybe in System_Base::dispatchTwig)
• */wired handled in OUT::dispatchLeaf and IN::dispatchLeaf - both need to echo and won't be caught by dispatchTwig
• */max etc handled ine.g. OUTfloat::/dispatchLeaf - should echo (not in OUT::dispatchLeaf as only echo if actually matches a parameter