Skip to content
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

GET_NOTIFIES #16

Open
hacker1024 opened this issue Feb 3, 2019 · 1 comment
Open

GET_NOTIFIES #16

hacker1024 opened this issue Feb 3, 2019 · 1 comment

Comments

@hacker1024
Copy link

This issue isn't with the library; rather it's with the documentation in this file.
I'm having trouble using the GET_NOTIFIES operation to listen to node updates. The documentation says "This is a special Command: The device does not close the HTTP-Request.", but that's not the case for me. After making the request, the device will either immediately return a list of all the changed nodes since the last request, and close the connection (if nodes had been changed since the last request) or keep the connection open and respond and close immediately after a node changes (if no nodes had been changed since the last request).

How, then, can I constantly listen for changes?

The documentation also says, "With this command you can use the connection like a normal socket, where the device sends you updates about changed nodes.". What kind of socket?

@flammy
Copy link
Owner

flammy commented Jul 3, 2019

@hacker1024 you are right, that is the same behavior I also noticed.

I will update the documentation about this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants