I've thought of a possible case that says the interface should not expect
specific (like a sensor is only on or off) but instead that value should be
part of the systemName like the rest of the path. The example would be
turnouts using servos. Here the normal or reverse is simply two different
values at the end of the paths. This also deals with the case of hardware
that might be user configurable, but the owning user got the hardware but
doesn't know how or is missing some interface for editing the MQTT end
device to make it use our concept of values for the states (of on or off).
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org
Ken Cameron