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?
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?