-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Manually specify OTA ports in arduino Ide ? #2480
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
Comments
+1 vote to add OTA port(s) into arduino IDE manually. |
+1 vote |
@penfold42 is this issue still valid? I understand that ArduinoOTA advertises using mDNS, and that you can specify which port to use. This is done in your code. |
Yes, still an issue. A way to fake / manually add the entries would be great |
I guess this is more of an IDE issue than ESP8266 then? I.e. it applies to
any board which uses mDNS for OTA, not just the ESP8266.
…On Fri, Oct 13, 2017, 17:12 penfold42 ***@***.***> wrote:
Yes, still an issue.
A way to fake / manually add the entries would be great
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2480 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEJcejXB34_if2RBV-D6ToV6hBjCmNbEks5sr9JUgaJpZM4J0bTi>
.
|
Yes - I didn't realise the OTA subsystem is a base arduino IDE capability. |
Actually I don't think opening the 5353 port does solve the issue (I've tried adding a rule and it still fails the uploading process). I tried using the CLI command: It would be great to be able to specify one port to listen onto, maybe in a config file |
SOLVED! In file ".arduino15/packages/esp8266/hardware/esp8266/2.3.0/platform.txt" change line: to: this way the LISTENING port on your development pc is fixed to 8266 (of course you can change it) and you can write a rule on your firewall |
better yet! in "preferences.txt" add ota.hostport=8266 and in file ".arduino15/packages/esp8266/hardware/esp8266/2.3.0/platform.txt" change the line in: tools.esptool.upload.network_pattern="{network_cmd}" "{runtime.platform.path}/tools/espota.py" -i "{serial.port}" -p "{network.port}" -P "{ota.hostport}" "--auth={network.password}" -f "{build.path}/{build.project_name}.bin" |
This issue is in a closed state -- could you please re-open it so it does not get forgotten, and gets documented |
of course, you can change the config to any port you want :) |
actually, let me say that 5353 should NOT be used since it's dedicated to mdns service, while the upload of the new sketch via network is another service altogether, i.e. we should use an "unused" port mdns is a discovery service, it's needed to find the device, the following communication is another story |
understood, but there is 'legacy' backward compatibility to match existing documentation -- a clean break at a major release epoch makes sense, though I'd be thrilled on a small IoT friendly avahi daemon and hand-off for OTA purposes. I have not looked -- do you know of a less 'weighty' suite (the current Avahi tarball is 1.2 meg big) |
The subject could be misleading. This relies on mDNS advertisements making it past the firewall on port 5353. |
Sorry for "bumping", did you think about my proposal? |
@atrent, there's a slight misunderstanding here I think. @penfold42 was looking for a way to manually specify a TARGET destination for an OTA upload in the Arduino GUI. As a good example of this, on Windows machines, it can be difficult to get mDNS working properly which means that even though I have an ESP OTA service running (I can see it using my mDNS browser on my iPhone) I'm unable to see the "Network Port" in the Arduino GUI. However, I can still manually connect to the ESP using it's IP address, and since the IP doesn't change very often on my home network it would be very helpful to be able to manually setup a network port in the Arduino UI in order to be able to deploy an OTA update to my ESP from the UI. @penfold42 - I still think this is a reasonable issue to be open. Could you re-open this bug so that we can at least have something tracking this and maintain a bit of the historical discussion? |
For anybody interested in a useful workaround, if you're using VSCode you can create a custom task to execute the Example {
// See https://go.microsoft.com/fwlink/?LinkId=733558
// for the documentation about the tasks.json format
"version": "2.0.0",
"tasks": [
{
"label": "OTA Upload",
"type": "shell",
"command": "py",
"args": [
"%LOCALAPPDATA%\\Arduino15\\packages\\esp8266\\hardware\\esp8266\\2.5.0\\tools\\espota.py",
"-i",
"192.168.29.243",
"-p",
"8266",
"-f",
"${workspaceFolder}\\..\\build\\${fileBasename}.bin",
],
"options": {
"shell": {
"executable": "cmd.exe",
"args": [ "/c" ]
}
}
}
]
} This task assumes that you have specified that the build output go into |
Is there still no solution to this? The network port for OTA only rarely appears in Tools > Ports so I cannot upload OTA. I am running on Windows 10. If I could specify the device IP address manually then that would (I think) solve my problem. |
You can
|
Thanks. I looked for that script earlier but couldn't find it. Will have another look. |
@MaBi6411 Thanks I fixed my comment. |
if espota were installed as an IDE tool, one could configure it as programmer (and it would be part of referred package problem solution too). examples for the arduinoOTA tool: programmer.txt:
platform.local.txt
|
@d-a-v |
Where do I have to do it? Could you explain to me please? I'm totally new in GitHub. |
Just want to add another vote for manual specification of an OTA target. I have found the automated method to be hit-and-miss when it comes to showing the target in the target ports list. |
I would like to add another vote in favour of being able to manually specify the OTA target. Like others I have found the automated solution to be rather hit-and-miss when it comes to detecting and showing the OTA target. If I am to use this seriously then I need a reliable method of OTA updating my devices. My dev machine is running Linux so its not a Windows 10 issue. |
I'm voting for manual specification of an OTA target too. |
I'm voting for manual specification of an OTA target too. ( IP Adress and Port ) |
I can' t believe, guys... this issue was opened in 2016 and still has not been resolved by 2025... :( My development board is in a separate LAN from the computer with IDE, so I know it won't be "magically" discovered via mDNS. I also know the IP/port where it's listening at, and that my firewall is configured to allow necessary communication between the networks. I am on IDE 2.3.6/Win11 and don't see any way to add the OTA IP/port manually. Please, implement. |
My laptop has a firewall I can't administer and it blocks UDP 5353 inbound.
This stops AirTunes but also stops the OTA advertisements making it it.
How can I manually fake the existence of the ESP devices so they show up in the ide ?
Thanks !
The text was updated successfully, but these errors were encountered: