Hoeken - I'm pushing deltas to sensors.cyclops....
I'm pushing deltas to sensors.cyclops.{name}.*
10 Replies
You should not put data under sensors.*. That’s for info about sensors, not data from sensors.
any suggestion on a better path?
What kind of data is it?
its load cell data eg. shrouds and forestay loads.
[{"id": "CyclopszHJQ", "title": "Port", "station": 0, "units": "tonne", "value": "1.73", "rssi": -81, "time": 1739901487.861421, "age": 5.368212461471558, "status": 0}, {"id": "CyclopsNucy", "title": "Starboard", "station": 0, "units": "tonne", "value": "1.62", "rssi": -60, "time": 1739901476.7394996, "age": 16.49303388595581, "status": 0}]
sample json from the device
currently looks like this
or it could just be sensors.cyclops.port.value if using UDP streaming as it doesnt contain metadata
Hmm. Not sure what the root of this should be. Maybe someone else will have an idea…
I'm happy to change things to follow the SignalK style more, open to suggestions.
in general the paths describe "what is this data, in generic terms" and source defines "what is producing this data"
like we have
environment.wind.angleApparent, not sensors.lcjcapteurs.angle
so that when somebody creates a fancy wind UI gauge they can latch onto the data by default and only if there are multiple sources for the data (multiple windvanes) the user needs to pick the source or even care where the data is coming from
SK is also "SI Units by default", so the value should be in Newtons and the unit, labels etc in metadata
then there's the issue of identifying what the measurement is about - not unlike what we are doing with electrical.batteries.[id].<measure>, so this could be maybe rigging.[id].tension ? like rigging.forestay.tension?
the rssi, battery level etc data about the sensor itself might be under sensors 🤔@Teppo Kurki that sounds good to me. i'll go ahead and implement those changes.
Pushed a v1.2 with SI values going to rigging.{name}.tension and sensor metadata going to sensors.cyclops.{name}.*