I think you’re making this harder than it needs to be. A case is just several ifs after each other. Like this:
If you’d prefer if/else if, it would be something like this:
The problem is that you cannot create a device with more than two outputs (three, including the error output). The only way I can see this done with a device is to set a variable and then check this - but that would just do the same as these, only take more time and introduce more ways for it to break.
That should work. The If/ Else if construction then again is over complicated. The first one should do the trick
I really don’t see the point of a case switch actually. In Javascript, a case switch statement is underneath the hood, just a bunch of if/else statements that are being evaluated after each other from the top to the bottom. This is way you also need a break statement. The case switch uses a very confusing ternary and also often requires poor encapsulation (closures) that don’t follow pure programming guidelines like the principle of immutability. This is why the case switch is being abandoned in favor of early returns (if statements), object lookups, or other higher order methods that properly implement encapsulation and immutability.
A case switch card in Homey, might be feasible, and it might look a bit nicer than just a bunch of when cards in series, but it’s a hell of a lot more difficult to develop properly from both a technical standpoint and a visual standpoint. And it doesn’t even solve a real world problem. You can simply achieve the same thing like this:
The point of a case statement is, that it is a lot less messy. You have one variable or piece of logic to evaluate and from a complete list of values only one can be valid. I like it way more than all sort of nested If…then… else statements
It is also tool depending. For example in Excel it would be a breeze to have a case option.
And in the end I think it is mostly personal preference
