The used nomenclature for variables in the app include that the measured values are named with the prefix "measure_" - this means, that if the token "sensor" is used to compose a log message like shown in the example below, text will be "[Device name]: measure_moisture is too low ([value])".
Although the logic in naming the variable is obvious and has many advantages, I suggest the variables for the measured values are names without the prefix (only "moisture", e.g.) in order to make composed messages more "clean" and ordinary language-like.
This would also prevent the situation that a message read out would like "[Device name]: measure-underscore-moisture is too low ([value] :-)
The used nomenclature for variables in the app include that the measured values are named with the prefix "measure_" - this means, that if the token "sensor" is used to compose a log message like shown in the example below, text will be "[Device name]: measure_moisture is too low ([value])".
Although the logic in naming the variable is obvious and has many advantages, I suggest the variables for the measured values are names without the prefix (only "moisture", e.g.) in order to make composed messages more "clean" and ordinary language-like. This would also prevent the situation that a message read out would like "[Device name]: measure-underscore-moisture is too low ([value] :-)