Even though the deck resembles the Z-Ranger, the one wire would need to have data written to it, as that's how you make the decks hot swap-able. However, it is not needed since you can force the deck every time in development. Here is some info on doing that: One Wire Write Steps

Hope that helps. Since it looks like at some point I will need to do the one wire either way, I followed the instructions above and changed the following code to fit my deck information: One Wire Code Change

However, the one wire is not even found by the crazyflie. I have been able to read info from other decks. I have never done this before and am fairly new to it. Any advice on what you guys think would be a good step forward would be awesome.

As you noted you can force the deck as a first approach and it should work fine.

If you add a onewire memory that is not programmed, the Crazyflie firmware will only load deck drivers in debug mode, this was intended as a safety features: if the memory is not written there is not way to check for conflict.

If your one-wire board is well soldered and connected, you should see a warning when starting the Crazyflie that one corrupted OW memory is detected. Then it should be possible to write it using the procedure you followed.

Thank you so much! Just wanted to update this in case anybody was looking at it after. Turns out the OW that we bought were bad. We bought some new ones (exact same ones) and was able to do the process of programming it without an issue.