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

BasicOTA.ino does not seem to work #1447

Closed
probonopd opened this issue Jan 16, 2016 · 8 comments
Closed

BasicOTA.ino does not seem to work #1447

probonopd opened this issue Jan 16, 2016 · 8 comments

Comments

@probonopd
Copy link
Contributor

The way I understand it, running BasicOTA.ino should make the device available as a port in the Arduino IDE so that sketches can be uploaded over the air.

Running the BasicOTA.ino sketch with staging and the hourly Arduino IDE build, the sketch does not seem to advertise itself using dns-sd, at least it never shows up in the IDE as a port and using avahi-browse -a I also never see the device.

@celsworth added on gitter.im:

for what its worth I don't seem to get any MDNS announcements from ArduinoOTA.begin() either, just never noticed before cos I don't use the MDNS part of it
a bit of error checking might not go amiss: https://github.com/esp8266/Arduino/blob/master/libraries/ArduinoOTA/ArduinoOTA.cpp#L108
there's no check whether MDNS actually worked

@WereCatf
Copy link
Contributor

The mDNS-responder doesn't understand mDNS-queries for all services. You have to do 'avahi-browse _arduino._tcp' to see the device, ie. query for a specific service. Also, dns-sd != mDNS.

@WereCatf
Copy link
Contributor

Oh, and I, at least, have to restart the IDE for it to see the device. After that it works fine, though.

@probonopd
Copy link
Contributor Author

The mDNS-responder doesn't understand mDNS-queries for all services.

Here is a patch written my @me-no-dev that solves this:
patch.txt

Also, @me-no-dev pointed out that when using the latest hourly Arduino IDE builds, one does NOT have to select "OTA" but "Serial" when doing OTA (yes!).

With the patch linked above the port does appear in the IDE (without having to restart it) and OTA works in the latest hourly build of the IDE.

Sent PR #1451

@me-no-dev
Copy link
Collaborator

Actually on any build 1.6.7 or above, you do not need to select OTA in upload method options.
As a matter of fact, if you do and you are running on a different port or have password enabled, it will fail to upload the new firmware.
Maybe option should be removed all together now that we have it supported officially and that to be noted in the OTA instructions.

@WereCatf
Copy link
Contributor

@me-no-dev: That's a good bit of information to know! I've been wondering why I can't get password-enabled OTA to work. I do heartily support the idea of better documentation -- both regarding this and in general ;)

@probonopd
Copy link
Contributor Author

So:

@probonopd
Copy link
Contributor Author

Looks like the only thing left to do in order to close this is "Remove OTA option from the menu since it is now misleading"

@igrr
Copy link
Member

igrr commented Feb 29, 2016

Created #1702 to track the remaining task, closing this one.

@igrr igrr closed this as completed Feb 29, 2016
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

4 participants