Inconsistent inversion logic on digital inputs and digital outputs

[flyte]

When DigitalInputChangedEvent is fired, from_value and to_value uses the actual logic level of the GPIO pin which is affected by inversion, whereas when DigitalOutputChangedEvent is fired, it uses the abstract "on" or "off" which is inversion agnostic.

Along with adding these logic-level classes to the developer documentation, make it consistent which of them are being used at any given moment throughout the codebase.

[heffneil]

I have tried using inverted: true and inverted: yes for my inputs but they always show the opposite of how I would like them to report. Am I missing something or some syntax? Thanks!