@pavel.samokha Thanks for that.

To answer my own question: apparently you cannot

@Raimo-Järvi said in [Question] No stupid questions - ask anything here: @SuuntoPartnerTeam Why wouldn’t it work, @egika is doing basically the same as this example in documentation: <eval input="/Settings/Unit/UnitsMode" outputFormat="keyValue 0=Metric!|1=Imperial!" />. Just with icon font and different texts in keyValue formatter. This for example works fine in my Vertical: <div class="f-ico" style="top:calc(50% - 50%e);left:calc(50% - 50%e);"> <eval input="/Fusion/Altitude/PressureTrend" outputFormat="keyValue 1=&#xF280;|2=&#xF281;|3=&#xF282;|4=&#xF283;|5=&#xF284;|6=&#xF285;|7=&#xF286;|8=&#xF287;|9=&#xF288;" /> </div> If input value is not one of the expected values for some reason, changing formatting method doesn’t help. Hi Raimo! Good to see you here! Just found the difference: I was using class=“f-ico-l” (no idea if there ever was an L version of the icons. This does not work. with class=“f-ico” it is working as designed.

After testing a while on a watch has to say that quite difficult to get apps stable state. Seems to crash easily if you have JavaScript in t.html. Of course I could simplify but where is all the fun then… and my apps are quite simple anyway…

@Ecki-D. there’s no debug protocol as far as I know. you could do it the oldschool way - use systemEvent('[tag] message $someData'); to populate the logs, using a ‘tag’ just makes filtering easier when you check the logs after a crash or whatever happened.