Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / stephenhouser/node-red-contrib-flexradio issues and pull requests
#40 - Radio connection problems when radio nickname is all numbers, e.g. "8600"
Issue -
State: closed - Opened by stephenhouser 24 days ago
#39 - Fix Node-RED instances to have proper spelling and caps
Issue -
State: open - Opened by stephenhouser over 1 year ago
#38 - flexradio-messages not emitting status packets for Global and TX profile changes
Issue -
State: closed - Opened by stephenhouser about 2 years ago
- 2 comments
Labels: bug
#37 - Catch errors on failed connections to radio
Issue -
State: closed - Opened by stephenhouser about 2 years ago
- 4 comments
Labels: enhancement
#36 - Add filter to discovery node
Issue -
State: open - Opened by stephenhouser over 2 years ago
Labels: enhancement
#35 - Update nodes to allow radio creation and selection
Issue -
State: closed - Opened by njungels almost 3 years ago
- 3 comments
Labels: enhancement
#34 - No way to "disconnect"
Issue -
State: closed - Opened by stephenhouser almost 3 years ago
- 1 comment
Labels: enhancement
#33 - Unnamed meter errors, meters not correctly identified.
Issue -
State: closed - Opened by stephenhouser almost 3 years ago
- 1 comment
Labels: bug
#32 - A way to tie commands to responses with request node
Issue -
State: closed - Opened by stephenhouser almost 3 years ago
- 2 comments
Labels: enhancement
#31 - Does not pad hex numbers properly
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 1 comment
#30 - Silently drops requests if radio is not connected
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 1 comment
#29 - Discovery node reporting decimal handle for connected GUI client. Should be hex.
Issue -
State: closed - Opened by stephenhouser about 3 years ago
Labels: bug
#28 - Decode panadapter, waterfall, and audio data from VITA-49 streams
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 4 comments
Labels: enhancement
#27 - Give an option to automatically bind to a client with the configuration node
Issue -
State: open - Opened by stephenhouser about 3 years ago
- 2 comments
Labels: enhancement
#26 - Auto-configuration if there is only one radio
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 2 comments
Labels: enhancement
#25 - Parsing of error messages is broken
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 1 comment
Labels: bug
#24 - Make RECONNECT_TIMEOUT a configuration parameter for the node
Issue -
State: closed - Opened by stephenhouser about 3 years ago
Labels: enhancement
#23 - Make numbers be numbers in JSON data
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 3 comments
Labels: enhancement
#22 - A different `meter list` response with named meter topics
Issue -
State: open - Opened by stephenhouser about 3 years ago
Labels: enhancement
#21 - Add a 'request' field to `flexradio-request` node to simplify sending requests
Issue -
State: open - Opened by stephenhouser about 3 years ago
Labels: enhancement
#20 - Ensure nodes unsubscribing to events when redeployed
Issue -
State: closed - Opened by stephenhouser about 3 years ago
Labels: bug
#19 - Move `Name` field to bottom of node config screens
Issue -
State: closed - Opened by stephenhouser about 3 years ago
Labels: enhancement
#18 - Change default 'host' for flexradio-radio from `localhost` to something else
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 1 comment
Labels: enhancement
#17 - Discovery listener takes over UDP port
Issue -
State: closed - Opened by stephenhouser about 3 years ago
#16 - Make meters auto-subscribe to the topic they are monitoring
Issue -
State: open - Opened by stephenhouser about 3 years ago
- 1 comment
Labels: enhancement
#15 - Use regex to specify topic patterns in addition to MQTT topic syntax
Issue -
State: closed - Opened by stephenhouser about 3 years ago
Labels: enhancement
#14 - Possible memory leak in Radio.js -- keeping all old requests and never releasing the memory
Issue -
State: closed - Opened by stephenhouser about 3 years ago
Labels: bug
#13 - Incinsistency when not specifying a topic for subscription
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 1 comment
Labels: bug
#12 - Subscribe to meters by name in addition to number
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 3 comments
Labels: enhancement
#11 - Fix typo in help message.
Pull Request -
State: closed - Opened by KD4Z about 3 years ago
- 2 comments
#10 - Connection to the radio times out after a period of inactivity
Issue -
State: open - Opened by stephenhouser about 3 years ago
- 2 comments
Labels: enhancement
#9 - Update meter list when meters are added/removed
Issue -
State: closed - Opened by stephenhouser about 3 years ago
Labels: enhancement
#8 - Move meter and topic subscription filter into config node rather than -meter and -message nodes
Issue -
State: open - Opened by stephenhouser about 3 years ago
- 1 comment
Labels: enhancement
#7 - payloads from requets with empty text response is inconsistent with other responses
Issue -
State: closed - Opened by stephenhouser about 3 years ago
Labels: bug
#6 - Parse `profile` messages that contain a `list` of `^` delimited profiles.
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 3 comments
Labels: bug
#5 - Test cases to make sure the nodes continue to work across changes and firmware
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 3 comments
Labels: enhancement
#4 - Merge flexradio-meter and flexradio-message nodes into one
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 1 comment
Labels: enhancement
#3 - Add a _raw_ mode to the request and message nodes
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 1 comment
Labels: enhancement
#2 - Dynamic radio configuration (from discovery node output)
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 3 comments
Labels: enhancement
#1 - Discovery node "Error: bind EADDRINUSE 0.0.0.0:4992" on Restart Flows
Issue -
State: closed - Opened by stephenhouser about 3 years ago
- 1 comment