Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

groupsky/ya-modbus

Sign in to follow View on GitHub

Production-ready Modbus to MQTT bridge with automatic bus collision prevention, adaptive polling, and runtime reconfiguration

Is groupsky/ya-modbus beginner-friendly?

The maintainers of groupsky/ya-modbus usually reply to a pull request within 1 day. 3 beginner-friendly issues are open now.

Stars
3
Forks
0
Open beginner issues
3
Indexed issues
80
Avg merge
1d 1h
Merged PRs (30d)
75
Dominant language
TypeScript
License
GPL-3.0
Last GitHub push
Oct 12, 2026
Latest indexed
Oct 12, 2026
Contributing guide
Code of conduct
Beginner labels
good first issue

How to contribute to groupsky/ya-modbus

  1. Read the contributing guide first: it says how the maintainers want changes proposed, tested and reviewed.
  2. Read its code of conduct: it covers issues and pull requests as well as chat.
  3. Your contributions will be published under the project's GPL-3.0 license.
  4. Pick one of the 3 open beginner-friendly issues below and comment that you want to work on it before you start.
Beginner friendly Everything
Open All

Issues somebody may already be working on are listed last. List everything by date

  • fix: published test helpers import undeclared packages
    Open
    • Is something wrong?
    bug

    Difficulty 3/5 1-2 days Newbie friendliness 66/100

    groupsky/ya-modbus#597 ·

    Maintainers usually reply within 1 day

  • fix(mqtt-bridge): removing a device while its driver is loading leaves the port open
    Open
    • Is something wrong?
    bug scope:mqtt-bridge

    Difficulty 4/5 3-5 days Newbie friendliness 56/100

    groupsky/ya-modbus#594 ·

    Maintainers usually reply within 1 day

  • docs: root README examples use an old mqtt-bridge config shape
    Open
    • Is something wrong?
    documentation

    Difficulty 1/5 Under an hour Newbie friendliness 90/100

    groupsky/ya-modbus#574 ·

    Maintainers usually reply within 1 day

  • docs: fix leftover stale content in examples, CLI README, RELEASE-PROCESS and CONTRIBUTING
    Open
    • Is something wrong?
    documentation priority:low scope:documentation

    Difficulty 3/5 1-2 days Newbie friendliness 72/100

    groupsky/ya-modbus#567 ·

    Maintainers usually reply within 1 day

  • fix(cli): fill modelName in discover results
    Open
    • Is something wrong?
    bug priority:low scope:cli

    Difficulty 2/5 1-3 hours Newbie friendliness 85/100

    groupsky/ya-modbus#563 ·

    Maintainers usually reply within 1 day

  • feat(mqtt-bridge): find serial adapters by USB identity or port location, with remote selection
    Open
    • Is something wrong?
    enhancement scope:mqtt-bridge

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    groupsky/ya-modbus#534 · 2 comments ·

    Maintainers usually reply within 1 day

  • Support Node.js 26 (blocked by serialport native callback bug)
    Open
    • Is something wrong?
    enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 36/100

    groupsky/ya-modbus#507 ·

    Maintainers usually reply within 1 day

  • test(device-profiler): add edge case tests for JSON output
    Open
    • Is something wrong?
    enhancement testing

    Difficulty 2/5 1-3 hours Newbie friendliness 55/100

    groupsky/ya-modbus#376 ·

    Maintainers usually reply within 1 day

  • test(device-profiler): improve JSON formatter integration tests
    Open
    • Is something wrong?
    enhancement testing

    Difficulty 2/5 1-3 hours Newbie friendliness 45/100

    groupsky/ya-modbus#375 ·

    Maintainers usually reply within 1 day

  • Add TCP transport E2E tests for device-profiler
    Open
    • Is something wrong?
    priority:low scope:device-profiler scope:testing testing type:testing

    Difficulty 3/5 1-2 days Newbie friendliness 49/100

    groupsky/ya-modbus#367 ·

    Maintainers usually reply within 1 day

  • Add build validation unit tests for CLI packages
    Open
    • Is something wrong?
    priority:medium reliability scope:cli scope:device-profiler scope:emulator scope:mqtt-bridge type:testing validation

    Difficulty 3/5 1-2 days Newbie friendliness 42/100

    groupsky/ya-modbus#364 ·

    Maintainers usually reply within 1 day

  • Enhance E2E tests to verify bin file executability
    Open
    • Is something wrong?
    enhancement priority:medium scope:cli scope:device-profiler scope:emulator scope:mqtt-bridge testing

    Difficulty 2/5 1-3 hours Newbie friendliness 35/100

    groupsky/ya-modbus#363 ·

    Maintainers usually reply within 1 day

  • Update outdated architecture and phase documentation
    Open
    • Is something wrong?
    documentation priority:medium type:docs

    Difficulty 2/5 1-3 hours Newbie friendliness 35/100

    groupsky/ya-modbus#351 · 1 comment ·

    Maintainers usually reply within 1 day

  • refactor(mqtt-bridge): optional code improvements for device config loading
    Open
    • Is something wrong?
    enhancement priority:low refactor scope:mqtt-bridge

    Difficulty 2/5 1-3 hours Newbie friendliness 28/100

    groupsky/ya-modbus#344 · 1 comment ·

    Maintainers usually reply within 1 day

  • docs(mqtt-bridge): complete device config documentation
    Open
    • Is something wrong?
    documentation priority:high scope:mqtt-bridge type:docs

    Difficulty 2/5 1-3 hours Newbie friendliness 38/100

    groupsky/ya-modbus#343 · 1 comment ·

    Maintainers usually reply within 1 day

  • Add E2E tests for mqtt-bridge error scenarios
    Open
    • Is something wrong?
    enhancement priority:high scope:testing type:testing

    Difficulty 4/5 3-5 days Newbie friendliness 40/100

    groupsky/ya-modbus#340 ·

    Maintainers usually reply within 1 day

  • refactor(cli): align empty part handling across parsers
    Open
    • Is something wrong?
    priority:medium refactor scope:cli technical-debt

    Difficulty 3/5 1-2 days Newbie friendliness 35/100

    groupsky/ya-modbus#334 · 1 comment ·

    Maintainers usually reply within 1 day

  • feat(cli): show filter effectiveness percentage in discover output
    Open
    • Is something wrong?
    developer-experience enhancement priority:low scope:cli

    Difficulty 2/5 1-3 hours Newbie friendliness 48/100

    groupsky/ya-modbus#330 ·

    Maintainers usually reply within 1 day

  • test(cli): add missing edge case tests for discover --id option
    Open
    • Is something wrong?
    enhancement priority:medium scope:cli

    Difficulty 2/5 1-3 hours Newbie friendliness 45/100

    groupsky/ya-modbus#328 ·

    Maintainers usually reply within 1 day

  • Add error scenario coverage to verbose logging E2E tests
    Open
    • Is something wrong?
    enhancement priority:low scope:cli

    Difficulty 3/5 1-2 days Newbie friendliness 48/100

    groupsky/ya-modbus#325 ·

    Maintainers usually reply within 1 day

  • Investigate discover command verbose logging test infrastructure issue
    Open
    • Is something wrong?
    bug priority:medium scope:cli type:research

    Difficulty 4/5 3-5 days Newbie friendliness 35/100

    groupsky/ya-modbus#324 · 2 comments ·

    Maintainers usually reply within 1 day

  • test(e2e): add port access error handling tests
    Open
    • Is something wrong?
    developer-experience enhancement priority:medium type:enhancement

    Difficulty 3/5 1-2 days Newbie friendliness 45/100

    groupsky/ya-modbus#319 ·

    Maintainers usually reply within 1 day

  • test(emulator): add CLI integration tests for verbose flag
    Open
    • Is something wrong?
    developer-experience priority:medium scope:cli type:enhancement

    Difficulty 3/5 1-2 days Newbie friendliness 35/100

    groupsky/ya-modbus#314 · 1 comment ·

    Maintainers usually reply within 1 day

  • test(emulator): add tests for exception response handling in verbose mode
    Open
    • Is something wrong?
    developer-experience priority:medium scope:cli type:enhancement

    Difficulty 4/5 1-2 days Newbie friendliness 35/100

    groupsky/ya-modbus#310 ·

    Maintainers usually reply within 1 day

  • refactor(emulator): extract magic numbers to named constants in protocol helpers
    Open
    • Is something wrong?
    enhancement good first issue priority:low scope:emulator type:refactor

    Difficulty 1/5 1-3 hours Newbie friendliness 55/100

    groupsky/ya-modbus#301 ·

    Maintainers usually reply within 1 day

  • enhancement: Add timeout protection to TCP transport server.close()
    Open
    • Is something wrong?
    enhancement good first issue priority:medium scope:transport type:bug

    Difficulty 2/5 1-3 hours Newbie friendliness 48/100

    groupsky/ya-modbus#298 ·

    Maintainers usually reply within 1 day

  • test(e2e): expand CLI test coverage
    Open
    • Is something wrong?
    enhancement priority:medium scope:cli

    Difficulty 4/5 3-5 days Newbie friendliness 35/100

    groupsky/ya-modbus#291 ·

    Maintainers usually reply within 1 day

  • feat(emulator): add concurrent operation protection to TCP transport
    Open
    • Is something wrong?
    enhancement priority:high scope:emulator

    Difficulty 4/5 3-5 days Newbie friendliness 35/100

    groupsky/ya-modbus#278 · 1 comment ·

    Maintainers usually reply within 1 day

  • enhancement: improve TCP transport error messages with configuration context
    Open
    • Is something wrong?
    developer-experience enhancement priority:medium scope:emulator

    Difficulty 2/5 1-3 hours Newbie friendliness 55/100

    groupsky/ya-modbus#276 ·

    Maintainers usually reply within 1 day

  • docs: document transport lifecycle and event listener management
    Open
    • Is something wrong?
    documentation good first issue scope:emulator

    Difficulty 3/5 1-2 days Newbie friendliness 35/100

    groupsky/ya-modbus#273 · 1 comment ·

    Maintainers usually reply within 1 day

  • feat: add concurrent operation protection to transports
    Open
    • Is something wrong?
    enhancement priority:low scope:emulator

    Difficulty 3/5 1-2 days Newbie friendliness 35/100

    groupsky/ya-modbus#272 · 2 comments ·

    Maintainers usually reply within 1 day

  • feat(emulator): add configurable initialization timeout for transports
    Open
    • Is something wrong?
    enhancement priority:medium scope:emulator

    Difficulty 3/5 1-2 days Newbie friendliness 53/100

    groupsky/ya-modbus#267 ·

    Maintainers usually reply within 1 day

  • feat: Improve EmulatorConfig type safety with discriminated unions
    Open
    • Is something wrong?
    enhancement priority:low scope:emulator type:enhancement

    Difficulty 4/5 3-5 days Newbie friendliness 43/100

    groupsky/ya-modbus#262 ·

    Maintainers usually reply within 1 day

  • feat: Add socket timeouts for TCP connections
    Open
    • Is something wrong?
    enhancement feature priority:medium scope:emulator security

    Difficulty 3/5 1-2 days Newbie friendliness 48/100

    groupsky/ya-modbus#259 ·

    Maintainers usually reply within 1 day

  • feat: Implement maxConnections limit for TCP transport
    Open
    • Is something wrong?
    enhancement feature priority:medium scope:emulator security

    Difficulty 4/5 3-5 days Newbie friendliness 44/100

    groupsky/ya-modbus#258 ·

    Maintainers usually reply within 1 day

  • feat(emulator): add start operation hardening to RTU transport
    Open
    • Is something wrong?
    enhancement error-handling priority:low reliability scope:emulator

    Difficulty 4/5 1-2 days Newbie friendliness 48/100

    groupsky/ya-modbus#250 · 1 comment ·

    Maintainers usually reply within 1 day

  • feat(emulator): add input validation for RTU transport configuration
    Open
    • Is something wrong?
    developer-experience enhancement priority:medium scope:emulator validation

    Difficulty 2/5 1-3 hours Newbie friendliness 52/100

    groupsky/ya-modbus#247 ·

    Maintainers usually reply within 1 day

  • feat(emulator): add handler error handling with Modbus exceptions
    Open
    • Is something wrong?
    enhancement error-handling priority:high scope:emulator

    Difficulty 4/5 3-5 days Newbie friendliness 38/100

    groupsky/ya-modbus#246 ·

    Maintainers usually reply within 1 day

  • feat(emulator): add error event propagation to RTU transport
    Open
    • Is something wrong?
    enhancement error-handling priority:high reliability scope:emulator

    Difficulty 3/5 1-2 days Newbie friendliness 44/100

    groupsky/ya-modbus#245 ·

    Maintainers usually reply within 1 day

  • Add advanced E2E test scenarios
    Open
    • Is something wrong?
    priority:low scope:testing type:enhancement type:testing

    Difficulty 5/5 Over a week Newbie friendliness 25/100

    groupsky/ya-modbus#240 · 1 comment ·

    Maintainers usually reply within 1 day

  • Create regression test for verify-coverage.js itself
    Open
    • Is something wrong?
    priority:medium scope:examples scope:testing type:testing

    Difficulty 3/5 1-2 days Newbie friendliness 45/100

    groupsky/ya-modbus#198 ·

    Maintainers usually reply within 1 day

  • Add package existence check in run-all.sh for local development
    Open
    • Is something wrong?
    developer-experience priority:medium scope:examples type:enhancement

    Difficulty 2/5 1-3 hours Newbie friendliness 64/100

    groupsky/ya-modbus#197 ·

    Maintainers usually reply within 1 day

  • Add npm install error visibility in run-all.sh
    Open
    • Is something wrong?
    developer-experience priority:medium scope:examples type:enhancement

    Difficulty 1/5 Under an hour Newbie friendliness 55/100

    groupsky/ya-modbus#196 ·

    Maintainers usually reply within 1 day

  • Add job summary output to GitHub Actions compatibility job
    Open
    • Is something wrong?
    developer-experience github-actions priority:low type:enhancement

    Difficulty 2/5 1-3 hours Newbie friendliness 56/100

    groupsky/ya-modbus#194 ·

    Maintainers usually reply within 1 day

  • Make test file path mapping more flexible in verify-coverage.js
    Open
    • Is something wrong?
    developer-experience priority:low refactor scope:examples

    Difficulty 2/5 1-3 hours Newbie friendliness 35/100

    groupsky/ya-modbus#193 · 1 comment ·

    Maintainers usually reply within 1 day

  • Improve verify-coverage.js error messages with remediation steps
    Open
    • Is something wrong?
    developer-experience priority:low scope:examples type:enhancement

    Difficulty 2/5 1-3 hours Newbie friendliness 55/100

    groupsky/ya-modbus#191 ·

    Maintainers usually reply within 1 day

  • Add explicit .default anti-pattern test to compatibility examples
    Open
    • Is something wrong?
    developer-experience priority:low scope:examples type:enhancement

    Difficulty 2/5 1-3 hours Newbie friendliness 54/100

    groupsky/ya-modbus#189 ·

    Maintainers usually reply within 1 day

  • refactor: consolidate duplicate error detection logic from CLI into shared utility
    Open
    • Is something wrong?
    developer-experience priority:medium refactor

    Difficulty 4/5 3-5 days Newbie friendliness 35/100

    groupsky/ya-modbus#179 · 1 comment ·

    Maintainers usually reply within 1 day

  • feat(device-profiler): enhance error classifier to check modbusCode and errno
    Open
    • Is something wrong?
    feature priority:low type:enhancement

    Difficulty 2/5 1-3 hours Newbie friendliness 38/100

    groupsky/ya-modbus#178 · 1 comment ·

    Maintainers usually reply within 1 day

  • Add CLI tests to @ya-modbus/emulator package
    Open
    • Is something wrong?
    enhancement good first issue priority:low

    Difficulty 2/5 1-3 hours Newbie friendliness 49/100

    groupsky/ya-modbus#176 · 1 comment ·

    Maintainers usually reply within 1 day

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.