emoncms/scripts/phpmqtt_input.php
No, as I said this was a personal recommendation. Over the years I have all too often found many errors have found to be caused by use of unexpected chars, spaces and quotes being the worst offenders in my opinion. I have learnt that keeping it simple is so much easier, we have seen issues in the past with certain characters in feed names in emoncms, wifi psk’s in the wifi module and also the user login names on emoncms etc.
Not all characters can be fully used in emoncms. For example, if you start adding commas, curly braces, colons, equal signs and quote marks to input and feed names, what happens to the JSON output from api calls to list inputs and feeds? That’s just one “other convention”. There is php, javascript, html, ajax, sql etc to consider too as those input and feed names will need processing, displaying and storing too.
I’m not suggesting it cannot be done, but to make an emoncms capable of utilizing all chars across the board would probably be a mean task. It may be easier for both the devs and the users to have clearly defined restrictions, that are then coded into emoncms so that error handling can be improved and notify the user “Oi! that’s an illegal character!” rather than silently doing nothing, something quite unexpected or falling over completely.
Also see “Don’t understand configuring inputs from an external node” for a similar issue with underscores.