Thanks for the further clarification.
I am familiar with open source licenses and I think I wasn't clear on my first messages. I actually wasn't even clear on what to ask
The software I am building uses an different architecture and behaviour. Nothing is based on in the RA's code. So, software licensing in terms of software features is out of the equation.
I also have no intention to replicate RA's hardware at the moment. However, that Reef AI is doing sounds like a good idea.
At the moment, all I intend is to make my controller compatible to some RA's devices, for example the Power Bar. So, I don't need to spend time designing one myself and if I am successful, it helps boosting RA's sales. I would either resell RA parts, like Reef AI, or redirect the buyer to RA's website.
In order to do that, I need to read the circuit schematics, to understand the wiring. Also, read the code to understand the communication protocols. That is where the licensing isn't clear for me.
Can I make a closed source controller that is compatible to RA's pinouts and protocols? If so, can I call it "Compatible with Reef Angel XYZ device"?
That requires me to read RA's Open source code and hardware, in order to reverse engineer it and make it work in my platform.
Can I re-design a single RA Open Source peripheral, like Power Board or Leak Detector, as long as I keep it open source with the same license, without the need to open source the main controller that connects to this peripheral?
In this case I would open source the reverse engineered library that wraps the communication protocol.