-
Notifications
You must be signed in to change notification settings - Fork 118
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
QoS other than default not supported #110
Comments
Thanks for reporting the issue. We will investigate and get back to you. |
This issue has been marked stale because it has been open for 14 days with no activity. Please remove the stale label or comment on this issue, or the issue will be automatically closed in the next 14 days. |
This issue has been marked stale for 14 days and will now be closed. If this issue is still valid, please ping a maintainer. |
Hi, I'm getting exactly the same problem. Did you get this solved by any chance? |
No, didn't adapt the code. So still open. |
Describe the bug
I can't subscribe to topics which have QoS profile other than the default one.
For example if I publish a topic with QoS Sensor Data, the endpoint subscriber says it can't receive any data as the qos profiles are not compatible.
To Reproduce
Publish data with QoS Sensor Data
Try to receive data with endpoint
Console logs / stack traces
offering incompatible QoS. No messages will be received from it. Last incompatible policy: RELIABILITY
Expected behavior
Data is received and sent to unity.
Environment (please complete the following information, where applicable):
The text was updated successfully, but these errors were encountered: