27 Replies
where is "Data should be of type number" coming from?
it's not the UI. Also coming from HTTP requests from meta data.
Time for an automation suite in the GitHub action pipeline
@Tony what are u talking about?
@Scott Bender what do you have in basedeltas?
More UI and api tests
a bunch of stuff
I'll play with that...
Yes, we could have better test coverage, but unless you know what the problem is you are jumping the gun
Is it possible to get to this state without making an http request or websocket message event? I understand if you don’t want to discuss, but perhaps there is a way to prevent this by ensuring both will have data boundaries
at this time i have no idea what has happened here. maybe Scott accidentally copypasted Data shoudld be of type as description for stateOfCharge....
No, I checked for that
I can't find that string anywhere
it's two different servers also
so: is that reproducible?
not on all path
that looks like a schema validation error message
it's on my prod server and local test server
Signal K Server
Signal K Node Server
I can look into it this week. Just wanted to make sure it was not obvious
electrical.batteries.1.capacity.timeRemaining
a lot of paths, but not all
I also planning on updating/adding displayName for everything if that is cool with you? Will help with being able to ask Siri for values.
you mean update those in schema files?
yes
Pretty cool . I can ask Siri, “Get the boat summary”, and she will read back the info to me.
With displayName meta, she says "The Apparent Wind Speed is xxx"
I can also ask "What's the Apparent Wind Speed"
not sure if you are following the latest beta's? but this stuff is very neat. Automations are really interesting.
GitHub
specification/schemas/definitions.json at 1978f556d8790be2b3bfdc9ff...
Signal K is a JSON-based format for storing and sharing marine data from different sources (e.g. nmea 0183, 2000, seatalk, etc) - SignalK/specification
...this has been there since forever, it is in @signalk/signalk-schema keyswithmetadata.json...
probably. Don't think I ever looked until now.
GitHub
"Data should be of type number." in metadata description · Issue #6...
Something is picking up erroneously description values that are in definitions.json and they end up in keyswithmetadata.json and in metadata for entries that don't have their own description. O...
but stateOfCharge does have have a description
ah my mistake, please update the issue