I will ask a glaringly naive question. How can Tripoli approve wireless remote switches that are user assembled? And before you say: "motors are certified predicated on proper assembly by the end user following provided manufacturers instructions", I would argue that soldering a board with many components is far more complicated than assembling a motor.
I'm going to assume for discussion that you're referring to eggtimer kits, and not self-designed/self-made altimeters.
Since an eggtimer kit has switching done via electronics, I can see these failure modes:
1. Software programming failure... basically the code causes an event (or fails to cause an event) incorrectly.
2. Component failure.. technical problem with one or more of the components, causing them to act in an unplanned way
3. Assembly error.. something was assembled wrong in building the altimeter.. soldering, switched components, bridges, etc.
4. Usage error.. something wrong with the usage of it- battery not wired up correctly, av bay wiring errors, etc.
5. Environmental error... something about the operational environment causes an unforseen problem- humidity, temperature extremes, dropped too hard before launch etc.
I would argue in this case that #1, #4, and #5 are not unique to eggtimer products, and are problems that could be seen with commercial altimeters.
As for #2
2.1 Component failures could be present in any altimeter- quality control out of the box basically. I guess you could say that this is a problem that's not unique to eggtimer products.
2.2 Component failure could happen based on #3 above (soldering looks good, but maybe a component was damaged by heat). I'll presume for the sake of discussion that this is more likely in a self assembled altimeter than commercially bought. More on this further down.
For #3.
3.1 Assembly error is caused by vague or incorrect instructions- basically the user is doing everything incorrectly, but the written procedure is wrong or not clear enough
3.2 Assembly error caused by soldering activity. User is following instructions, but assembles the circuit in a way that does not fit the design/schematic. Shorts, improper component placement, missed solder joints, etc. Also could include 3.2.a- solder joints that "kinda" work, but are not mechanically strong... cold shorts, etc.. basically something that works sometimes, but could work loose on vibration, environmental changes, etc.
So for discussion point, I'd like to cover 2.2, 3.1, and 3.2
Quickest first- 3.1. As far as electronic kits go, I've never seen instructions as thorough as the eggtimer ones. I'm sure better ones exist, but given that
@cerving has had his products out for several years, and have not seen any commentary about "I have no idea what it's telling me to do", I'd think that we could argue that the instructions are pretty solid. You could make a case for someone who's completely green reading it completely wrong, but are they likely to completely misread the instructions, and yet build an altimeter that is functional enough to stick in an av bay, seem like it's working, and still have an electronic deployment/ignition unplanned event? I see this kind of event as more likely being related to 2.2 (assembly failure) than instructions directly?
As for 2.2 and 3.2... let's assume that the person did the best of their abilities in soldering, but yet there is something wrong that they did not immediately detect while assembling.
Possible failure results here:
a. Altimeter does not function at all (doesn't turn on, doesn't do anything).
b. Altimeter turns on but does not function- basically beeps, but doesn't have any output (deployment charges, motor ignition, etc)
c. Altimeter turns on, seems to function, but does not function completely (drogue deployment charge goes off, but not the main, etc)
d. Altimeter turns on, seems to function, but functions are done at the wrong times (deployment goes off as soon as the altimeter is turned on, main comes out when it's supposed to be the drogue, etc)
e. Altimeter turns on, functions fine at one launch, but then fails at a different launch. For the sake of argument I'd like to limit this to point 3.2.a above (cold shorts, etc)
For the sake of argument, let's assume that these failure modes are specific to this altimeter, and not av bay assembly errors (#4 above).
I highly doubt for point a. that anyone with their right mind would stick this in an av bay and have it do any kind of critical function (more than a ride along).
For b, c, and d, I'd like to discuss these together. I think these are probably the crux of the discussion here.
These activities are mitigated in two possible ways:
1. Self checks on the startup of the altimeter. Basically the altimeter software is checking the circuit and warns the user if it finds something not kosher. This process should be the same for the user for all altimeters, not just self-assembled ones. They should be aware of error codes and what they mean, and react accordingly. I would also argue that anyone who has an altimeter will plug it in and test it out before putting any charges in it... be it commercial or self built.
2. User testing of the altimeter... using LEDs or whatever to check the actual deployment process in a safe manner. For sake of discussion, let's assume that this is not done with regularity or properly.
So basically we come down to the major failure points:
Point e- Altimeter is flaky- basically works some times, but not all the time. Unreliable, but maybe the unreliability is not noticeable to the user until it happens.
Point 2 above- Altimeter never really worked properly due to assembly errors, and wasn't caught until too late.
So then there's 3 failure modes, in my opinion
1. Fail hard- Negative event happens when it's not supposed to. Motor ignites at the RSO. Main parachute comes out when the rocket is on the rail, etc.
2. Fail hard(2)- Event fails to happen when it's supposed to. No drogue at apogee, etc.
3. Fail soft- Event fails to happen, but doesn't cause an issue. No second stage ignition, but rocket comes down safely under chute.
As for these events, I'll focus on 1+2 (although 3 is also a failure).
For this to be a problem with self assembled altimeters, we have to assume a failure point that is not caught by the software. In my layman's experience with electronics, 95% of the time this is related to "power" being somewhere where it shouldn't be. Basically there's a live voltage on the output connector. Or something isn't properly connected to ground where it should be.
So my question related to this are:
1. Is there ever a case where this is not caught by software.
2. And occurs in a failure mode that's specific to self assembly (soldering of components on the board)
3. And is not caught by the user beforehand?
I can't speak for everyone, but I think this case is very likely low, compared to people self assembling av bays above (#4 at the top), which is much more prone to error. I would also argue that any failure related to self assembly has a high linkage to #4 (self assembled av bay) and mitigating point #2- user testing of altimeter. These are things that should be checked regardless of where the altimeter came from.