So, I pulled my little MQTT experiment apart and did things with the parts for the last couple of weeks. I removed all of the feeds and dashboard from my account at that time as well.
Today I pulled everything together again and recreated my feeds and dashboard. What used to be an intermittent connection failure is now a complete one. I can not connect with any sketch I try now, only get 'Failed to subscribe' over and over - even with your test sketch.
Can you, please, look into my account and see if it has the same issue that the others had? I would really like to be able to participate in this BETA, but with so many failures on this end, it's kinda hard.
Still No AIO Connection
Moderators: adafruit_support_bill, adafruit
Forum rules
If you're posting code, please make sure your code does not include your Adafruit IO Active Key or WiFi network credentials.
If you're posting code, please make sure your code does not include your Adafruit IO Active Key or WiFi network credentials.
- jwcooper
- Posts: 1004
- Joined: Tue May 01, 2012 9:08 pm
Re: Still No AIO Connection
As far as I can tell your account is setup just fine. IO is running fine as well.
Try sending data from one of our python/ruby/node libraries from your computer to see if it works. If that works, then we know something is wrong with the device you're trying to use.
Try sending data from one of our python/ruby/node libraries from your computer to see if it works. If that works, then we know something is wrong with the device you're trying to use.
- pyremage
- Posts: 18
- Joined: Mon Aug 27, 2012 10:05 am
Re: Still No AIO Connection
I tried your suggestion of using another client and MQTT.fx will interact with my dashboard okay. So I tore apart my circuit, again, and re-built it, again, to only receive the same error "Failed to subscribe." This is with a sketch that used to work and has not been altered,.
So I figured I would try renaming my feeds to something else, then recreate my AIO key. Neither worked, but I noticed something on my serial port: it showed immediately when i changed the key, because now the sketch won't authenticate with the old key. I expect this behavior if it couldn't find the correct key,
But it is talking to AIO and not finding the subscriptions even after being deleted, recreated, and then renamed. I'm at a loss as to where to look for the problem now.
So I figured I would try renaming my feeds to something else, then recreate my AIO key. Neither worked, but I noticed something on my serial port: it showed immediately when i changed the key, because now the sketch won't authenticate with the old key. I expect this behavior if it couldn't find the correct key,
Code: Select all
Retrying AIO connection in 5 seconds...
Failed to subscribe
Retrying AIO connection in 5 seconds...
Failed to subscribe
Retrying AIO connection in 5 seconds...
Failed to subscribe
Retrying AIO connection in 5 seconds...
Failed to subscribe
Retrying AIO connection in 5 seconds...
Failed to subscribe
Retrying AIO connection in 5 seconds...
Failed to subscribe
Retrying AIO connection in 5 seconds...
Not authed
Retrying AIO connection in 5 seconds...
Not authed
Retrying AIO connection in 5 seconds...
Not authed
Retrying AIO connection in 5 seconds...
Not authed
Retrying AIO connection in 5 seconds...
Not authed
- pyremage
- Posts: 18
- Joined: Mon Aug 27, 2012 10:05 am
Re: Still No AIO Connection
I moved my sketch over to a Mega2560 running a W5200 Ethernet shield and get the exact same response from AIO as I did with the UNO/CC3k: "Failed to subscribe." I am not having an issue connecting to any other service but this one and do not believe the problem to be on my end.
One really cool thing that has come of this adventure anyway, is that I've now learned that using most MQTT 'services' is really not very reliable at all. You have to depend on so many other people to keep your MCU available. Unless you, and your broker, have a perfect network connection too many things can get in between you and your MCU. So I tried several other ways of accessing my relays over the Internet, such as aREST and HTML, and have found that hosting a webpage from the device and accessing it directly through the router is the most reliable way of accomplishing my project. Then all I have to worry about is keeping my 'net bill paid - and no longer depend on an MQTT broker to keep my relays available.
Anyway, thanks for the great learning experience...
So long and thanks for all the fish!!
One really cool thing that has come of this adventure anyway, is that I've now learned that using most MQTT 'services' is really not very reliable at all. You have to depend on so many other people to keep your MCU available. Unless you, and your broker, have a perfect network connection too many things can get in between you and your MCU. So I tried several other ways of accessing my relays over the Internet, such as aREST and HTML, and have found that hosting a webpage from the device and accessing it directly through the router is the most reliable way of accomplishing my project. Then all I have to worry about is keeping my 'net bill paid - and no longer depend on an MQTT broker to keep my relays available.
Anyway, thanks for the great learning experience...
So long and thanks for all the fish!!
Forum rules
If you're posting code, please make sure your code does not include your Adafruit IO Active Key or WiFi network credentials.
If you're posting code, please make sure your code does not include your Adafruit IO Active Key or WiFi network credentials.