You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't tested this with real video camera hardware recently.
I've noticed that the video property affordance looks wrong in the Thing Description. At least one of the two forms should have a video content type but instead one has sse as a subprotocol (which is not useful for a video stream).
This could potentially be a regression from the implementation of the HTTP SSE Profile, or possibly just a bug in the Virtual Things add-on.
The text was updated successfully, but these errors were encountered:
STR:
Expected:
Actual:
I haven't tested this with real video camera hardware recently.
I've noticed that the video property affordance looks wrong in the Thing Description. At least one of the two forms should have a video content type but instead one has
sse
as a subprotocol (which is not useful for a video stream).This could potentially be a regression from the implementation of the HTTP SSE Profile, or possibly just a bug in the Virtual Things add-on.
The text was updated successfully, but these errors were encountered: