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

pio run -t monitor always uses first monitor_port even with multiple env's #1841

Closed
blackketter opened this issue Sep 10, 2018 · 2 comments
Closed
Labels
Milestone

Comments

@blackketter
Copy link

Operating system:
macOS

PlatformIO Version (platformio --version):
3.6.0

Description of problem

When trying to do pio run -t monitor -e envname the first monitor_port found in the file is always used, independent of the environment chosen.

Steps to Reproduce

With the below ini file, executing pio run -t monitor -e strip the monitor always connects to the monitor_port listed in env:string

Swapping the order of the environments in the ini file changes to the first one listed.

If problems with PlatformIO Build System:

The content of platformio.ini:

[platformio]
#env_default = string

[common]
libs =
  file://../NTPClient
  file://../Switch
  file://../WiFiThing
  file://../Console
  file://../Clock
  file://../Timezone
  Time
  file://../FastLED
  ESP8266Wifi
  ESP8266mDNS
  ESP8266HTTPClient
  ArduinoOTA

[env:string]
platform = espressif8266
framework = arduino
board = d1_mini
lib_deps = ${common.libs}
upload_port = razzlestring.local
monitor_port = socket://razzlestring.local:23

[env:strip]
platform = espressif8266
framework = arduino
board = d1_mini
lib_deps = ${common.libs}
upload_port = razzlestrip.local
monitor_port = socket://razzlestrip.local:23
@ivankravets ivankravets added this to the 3.6.1 milestone Sep 21, 2018
@ivankravets
Copy link
Member

Thanks, fixed! Please pio upgrade --dev.

@blackketter
Copy link
Author

Working great. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants