Opencomputers can break Wireless Redstone channels

[NeroOneTrueKing]

Your GTNH Discord Username

NeroOneTrueKing#5311

Your Pack Version

2.3.0

Your Server

private server

Java Version

Java 8

Type of Server

Don't know

Your Expectation

I created an OpenComputers program using a Tier 2 Redstone Card to use wireless redstone to control things in my base.

local component = require("component")
local os = require("os")

RS = component.redstone
RS.setWirelessFrequency(1234) -- some frequency, like to turn generators on/off
RS.setWirelessOutput(true)

-- sleep for 5 seconds; the redstone signal remains on
os.sleep(5)

-- turn off the redstone signal
RS.setWirelessOutput(false)

This works fine.

The Reality

But what if the computer crashes before it turns off the signal?

Frequency 1234 remains powered.

When the computer reboots, its Redstone Card believes it isn't sending a signal on frequency 1234:

local component = require("component")
local os = require("os")

RS = component.redstone
RS.setWirelessFrequency(1234) -- some frequency, like to turn generators on/off

RS.getWirelessOutput() -- returns false; I'm not sending a signal on freq 1234
RS.getWirelessInput() -- returns true; something is powering the wireless redstone frequency

RS.setWirelessOutput(false) -- turn it off?
RS.getWirelessInput() -- returns true; something that doesn't exist is still powering the wireless redstone frequency

The wireless redstone channel seems to be permanently on, with no recourse.
I asked in #opencomputers-help and got this response:

Your Proposal

Ideally, the redstone frequency would stop being powered when the computer crashes.
Or alternatively, the redstone card would be able to turn off its signal again when the computer reboots.

At minimum, there should be some way to fix a corrupted wireless redstone frequency.

Final Checklist

• I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying the bug still exists will prompt us to investigate and reopen it once we confirm your report.
• I can reproduce this problem consistently by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.
• I have asked other people and they confirm they also have this problem by follow the exact steps I described above, or this does not need reproducing, e.g. recipe loophole.

[trollolal]

#11096