I think this was my mistake — in #2280, as part of "inlining" a v1 E-ink component that was reused by Pre-Fares (😬), I removed code in these conditionals that was calling toUpperCase on the type field before comparing it. Since the type was defined as uppercase (which this PR fixes), I assumed that was an accurate reflection of what the server sent. In reality it was probably that the v1 code used uppercase and v2 used lowercase, and to make the component work with both screen types, this toUpperCase was thrown in.