-
Notifications
You must be signed in to change notification settings - Fork 338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strict mode: missing type "object" for keyword "properties" #2887
Comments
I see this too. About 12 of these lines:
|
I'm also seeing this. Would it be related to #2811 (comment), or is this a different sense of the word "property"? I'm new to webthings and have been shaving a lot of yacks, so it could be something else, but it seems like this is related to "no property found" messages I get from the Here's what I'm seeing when I start the server, with many redundant lines clipped to keep this at least in the same universe as reasonable:
|
I'm having this problem too, how can i fix it? |
I think it means that the adapter add-on is sending an IPC message to the gateway which doesn't match the expected format. Specifically, a member called "properties" does not have the type "object". Whatever message the adapter is sending may be failing to validate against this line in the JSON schema, but I'm not sure why. I think it is expecting the properties member of a Thing Description to be an object, but getting something other than an object. I don't think this is actually a functional bug just a strict validation error, but it would be good to figure out if there's a problem with the schema or the messages being sent by adapters. |
Hello guys,
anyone know what this warning and sometime error is :
2021-11-04 16:34:58.024 WARN : strict mode: missing type "object" for keyword "properties" at "https://raw.githubusercontent.com/WebThingsIO/gateway-addon-ipc-schema/master/messages/definitions.json#/allOf/1" (strictTypes)
using the latest clone from master.
and when you add any addon it shows this:
The text was updated successfully, but these errors were encountered: