in red
(2019-09-30, 08:52 PM)glowntiger Wrote: Thanks…. ;-)
a further question:
I´m a little bit confused
on your new i2c app you use a signalk key to be send like:
"OPsensors.I2C."+name...
that is not a SK key, it is the source of the SK key. The key is "path"
The fast explanation: when SK data is converted from NMEA (0183 or 2000) the key used to define sources is "source" (https://github.com/SignalK/specification...lta-format)
but when you are creating custom data you have to use the key "$source" to define the source, as you can see in the i2c example you sent.
To understandable:
Must the key send conform to the signalk reference? : https://github.com/SignalK/specification...cs/keys.md
or can I send like OPsensors.1wire.Outsidetemp and map the data in signalk ?
You can send your own keys but it is recommended that you use the SK reference so third party applications can know what data are they dealing with.
Until now I have never used signalk
Is there anywere a file were i can found all Keys for menü construction? In your selectKey.py there is a reference to "keyswithmetadata.json". I can not found the file? I have installed signalk...
After installing SK that file sis in /usr/lib/node_modules/signalk-server/node_modules/@signalk/signalk-schema/dist/keyswithmetadata.json
You have an example to select the SK in i2c app, let me know if you have any doubt.