-
Notifications
You must be signed in to change notification settings - Fork 6
FAQs
If the server is on the Internet, are you connected to the Internet? If the server is on a local Wifi, are you connected to that local Wifi? If you are running your own server on your computer, is it still running? Perhaps restart it.
Still nothing? Check this: OOCSI uses a communication protocol on port 4444 (default, can be changed on the server). It might be that your Wifi network or Internet Provider blocks this port. Probably it is best to ask an administrator about this.
Probably you just reconnected after an earlier connection was ended abruptly. It could be that the server still remembers that connection and your client handle. Just wait for 2 minutes before reconnecting or choose a different handle for the time being. The newest server versions will resolve this case automatically, so this issue will disappear in the future.
Yes, please do.
Please check the following points:
- Did you actually send the message in your code?
- Are both clients connected to the same OOCSI server?
- Is the receiving client actually subscribed to the channel that the message went to?
- Does the receiving client have a function registered to handle the incoming message?
If all points are checked, you can try to insert logging statements (for instance, "println(...); in Processing") to check where the sending or receiving fails.
Usually, the problem is that you receive the single message once, but you process it many times inside your own code, often because you are running the processing function in a loop (for instance, "draw" in Processing or "loop" in ESP).
Probably you are doing something like this:
oocsi.data("key1", 3).send();
oocsi.data("key2", 43.21).send();
oocsi.data("key3", "cucumber").send();`
Always send the data that belongs together in a single message, like so:
oocsi.data("key1", 3).data("key2", 43.21).data("key3", "cucumber").send();