DeviceBinaryInputEvent expects binary input state, not value state.
This is another behavior change present in !461 (closed). I want an explicit ACK / NACK from you, @mtross.
I discovered this problem because the enum type passed to BinaryInputEvent at this place
does not match enum type passed in ModelMaintenance::onBinaryInputEvent
.
It may be that higher level code (plugins, ...) are implemented with this "bug" in mind and doing this change would break them.