Redeem does not crash immediately when it doesn't detect a Cape

[goeland86]

This particular else should make Redeem fail immediately, to clarify why it failed to the user.

redeem/redeem/Redeem.py

Line 147 in 00071ca

self.revision = "0B3A"

[Wackerbarth]

I don't think that your suggestion is the appropriate behavior. Redeem should never "crash". Since it is chosen to use OP as the user interface, when Redeem is not properly configured either because of failure to detect appropriate hardware, or a software misconfiguration, it should still interact with OP and deliver error responses to any commands received.

[goeland86]

Perhaps crashing isn't the right action, but it shouldn't pretend it has a replicape attached to it - as @ThatWileyGuy describes it, it will crash later on. Changing this to crash immediately at least means that a user will see that the cape not being detected is the main reason it failed to start, instead of later when it tries to address an I2C device that isn't present.