Lua Assertion read_pin always returns 1, making programmatic tool verification unusable

I believe since upgrading to FBOS 13.0.1 (but uncertain if 100% correlated) my Assertion `read_pin` function always returns one, causing my "tool mount/unmount" sequences to fail and abort the parent sequence.

I had believed my UTM got water inside (I have a Genesis v1.2, so the UTM is two parts), but I took it apart and it wasn't the issue. **Furthermore, manually reading the Tool Verification pin from the Sensors screen has always been proven to be 100% accurate when manually testing it and attaching or detaching a tool by hand.**

Because manually reading the pin works everytime, I can only conclude that recently the `read_pin` function has become bugged.

Here is my implementation:


Also, please note that the Assertion `IF TEST FAILS` filter is empty and shows nothing when clicked. I'm not sure what was there when I created the sequence, and maybe this is related? The same goes for the Send Message `TYPE` and checkboxes. I'm certain those checkboxes had labels before, for sending messages to email, toast, etc.