Maybe, but I don’t use the console for tricky ones - I’ll upload my very simple web page of payload formatter testing - edit the code in editor of choice, use the web browsers developer console to debug - breakpoints, single stepping, the whole shebang
Not sure I understand this - you won’t be able to determine if someone is connected via MQTT unless they connect via a broker you host.
I can think of several ways of potentially solving this problem but need some clarity on how TTN is used:
Do users setup their own account on TTN?
How do they currently receive uplinks in to the ESPEasy eco-system?
Does the information end up in a database, if so, which?
Which I guess means, is there some desktop software or web app?
It’s a GitHub issue:
Basically I raised a concern about generic devices (in that case, the Arduino MKR WAN 1310) having a payload formatter defined. I’m not entirely clear if ESPEasy falls under this use case, I suspect about 30% yes but as your core device code supports a wide range of sensors, about 60% no. But just letting you know that having a payload formatter in the device repro seems applicable if the device is set in stone - usually a handful of sensors so a smallish formatter. Other cases it needs careful review. I suspect you fall in to the ‘interesting’ category where in theory the devices could be considered to be fixed but the flip side is that the decoder code is pretty substantial.