Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
MQTT Node doesn't allow for port to be edited.
See original GitHub issueHi,
The MQTT Input node does not seem to allow you to edit the server port but instead has it locked to 1883.
Note: We were participating in a hackathon over the weekend where several different groups were trying to use MQTT input nodes and all ran into the same issue with their own installations.
What are the steps to reproduce?
Add a MQTT Input node to your flow graph. Double click on node to edit. Click pencil icon to edit server
What happens?
The Port field is not editable.
What do you expect to happen?
The Port field should be editable for servers that don’t use the default port of 1883.
Please tell us about your environment:
- Node-RED version: 1.0.3: Maintenance Release
- Node.js version: v13.6.0
- npm version: 6.13.4
- Platform/OS: macOS Catalina
- Browser: Chrome
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ah yes, that’s the expected behaviour. If you specify a fully qualified URL then you don’t set a port separately - otherwise we have to deal with deciding if the user wants us to use the port from the URL or from the input.
Thanks for the confirmation. It makes sense now that we’ve had this conversation but it might be a good idea to add that to the “Node Help” section as well.