Hello Paul M
I don't know if you talk about this specific example: https://github.com/SignalK/SensESP/blob/..._input.cpp
But have in mind that by convention in most of their samples they use underscore as a separator for URL paths or even for variables (which let me say it, i hate ):
const char* analog_in_config_path = "/indoor_illuminance/analog_in";
But when it comes to SignalK path they always use proper notation:
const char* sk_path = "environment.indoor.illuminance";
That being said, if you find a sample where there's an sk_path that uses underscore, you should notify them (or make yourself a PR if you feel confortable with that).
Forgot to mention that dots (.) in SignalK path have a meaning of hierarchy (what is at the right side of the dot belongs to the thing at the left side of the dot), but underscores in the config paths in SensEsp are just replaced by spaces when displayed on the website.
Sorry if i'm explaining basic things, i just don't know you're coding background, or anyone's who reads this
I don't know if you talk about this specific example: https://github.com/SignalK/SensESP/blob/..._input.cpp
But have in mind that by convention in most of their samples they use underscore as a separator for URL paths or even for variables (which let me say it, i hate ):
const char* analog_in_config_path = "/indoor_illuminance/analog_in";
But when it comes to SignalK path they always use proper notation:
const char* sk_path = "environment.indoor.illuminance";
That being said, if you find a sample where there's an sk_path that uses underscore, you should notify them (or make yourself a PR if you feel confortable with that).
Forgot to mention that dots (.) in SignalK path have a meaning of hierarchy (what is at the right side of the dot belongs to the thing at the left side of the dot), but underscores in the config paths in SensEsp are just replaced by spaces when displayed on the website.
Sorry if i'm explaining basic things, i just don't know you're coding background, or anyone's who reads this