-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Connection Issue #12
Comments
As I don't own a WiFly, I'm not going to make any immediate progress in debugging this myself. If it is in anyway related to that previous bug, it would suggest the client.available() call of the WiFly library behaves differently. Can you point me at exactly which WiFly library you are using? |
Did you make any progress on this? |
Adapted the Pusher lib instead: https://github.com/jonmarkgo/ArduinoPusherClient |
okay - I'll close this issue then. If you do happen to try again, let me know how you get on. |
I'm using the latest git pull of this library, with the only modification being that I changed instances of Ethernet to WiFly. I also tried it with https://github.com/dpslwk/pubsubclient
It connects successfully to my mosquitto server but then it starts having issues and cannot publish or subscribe:
Jul 25 22:02:46 localhost mosquitto[4096]: New connection from 50.74.0.42.
Jul 25 22:02:46 localhost mosquitto[4096]: New client connected from 50.74.0.42 as twiliopower.
Jul 25 22:02:46 localhost mosquitto[4096]: Sending CONNACK to twiliopower (0)
Jul 25 22:02:46 localhost mosquitto[4096]: Socket read error on client twiliopower, disconnecting.
Jul 25 22:02:55 localhost mosquitto[4096]: New connection from 50.74.0.42.
Jul 25 22:02:56 localhost mosquitto[4096]: Socket read error on client (null), disconnecting.
Jul 25 22:03:15 localhost mosquitto[4096]: New connection from 50.74.0.42.
Jul 25 22:03:16 localhost mosquitto[4096]: Socket read error on client (null), disconnecting.
Looks very similar to this bug: https://bugs.launchpad.net/mosquitto/+bug/528663
The text was updated successfully, but these errors were encountered: