platformio / platformio/platformio-core
Remote Upload and Monitor not using environment config
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9.5k
- Forks
- 905
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 2
Description
I want 2 different environments, for local and remote.
I have this in my platformio.ini :
[env:remote]
upload_port = /dev/ttyUSB1
monitor_port = /dev/ttyUSB1
[env:local]
upload_port = COM4
monitor_port = COM4
By using the remote monitor (or upload, but it behaves the same), the port used will be the first specified (in this case, /dev/ttyUSB1).
It seems that upload_port and monitor_port aren't taken into account properly when using remote actions.
It works when using monitor on the current machine however : the right port is used.
Can you please fix the remote actions so that it uses the ports I specify in the environments ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the remote upload or monitor action with the two environments shown in platformio.ini, then compare its selected port with the local monitor behavior. Done means each remote action uses the upload_port or monitor_port configured for the selected environment, including the differing local and remote values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100