Skip to content

"Send notifications on button press or IR" does not work when using "JSON remote" #4519

Closed

Description

@V-R-E

What happened?

When "Send notifications on button press or IR" is enabled and "JSON remote" is selected for the IR remote WLED does not send UDP sync notifications for IR events, notifications are only sent on button presses.

To Reproduce Bug

Enable "Send notifications on button press or IR"
Enable "IR GPIO" with "JSON remote"
Upload custom "ir.json" remote file
Use IR remote to trigger IR event

Expected Behavior

UDP sync notification should be sent on IR events when using JSON remote

Install Method

Binary from WLED.me

What version of WLED?

WLED 0.15.0 (build 2412100)

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

Anything else?

Tested on ESP32/ WT32-ETH01 with ethernet connection
UDP sync notification are sent on IR events when using "24-key RGB" remote
Custom ir.json file used shown below

"0xD242628C": { "label": "Playlist 3", "pos": "1x2", "cmd": "&PL=3" }, "0xCC19A35B": { "label": "Playlist 4", "pos": "1x2", "cmd": "&PL=4" }

Code of Conduct

  • I agree to follow this project's Code of Conduct

Activity

  1. blazoncek commented on Jan 25, 2025

    @blazoncek
    Contributor

    Please use JSON API in the cmd key.

  2. V-R-E commented on Jan 25, 2025

    @V-R-E
    Author

    Thank you!
    Just confirmed using the JSON API commands sends UDP sync notifications on IR events.
    I will submit a pull request with an added note to the Infrared documentation page.

    EDIT: Pull request submitted

  3. blazoncek commented on Jan 25, 2025

    @blazoncek
    Contributor

    Actually I consider this a bug in implementation as button should trigger correct notification regardless of API used.

  4. V-R-E commented on Jan 25, 2025

    @V-R-E
    Author

    Okay I also tested in v0.14.4 with the same results so it predates the v0.15.0 release.

  5. added
    confirmedThe bug is reproducable and confirmed
    workaroundThe issue contains a workaround
    on Jan 25, 2025
  6. blazoncek commented on Jan 27, 2025

    @blazoncek
    Contributor

    I have a possible fix ready. @V-R-E are you willing to test? If so, which binary do you need?
    PM me on Discord.

  7. V-R-E commented on Jan 27, 2025

    @V-R-E
    Author

    Yes, just sent you a message.

  8. added 2 commits that reference this issue on Jan 27, 2025
  9. added a commit that references this issue on Feb 9, 2025
  10. added this to the 0.15.2 milestone on Mar 13, 2025
  11. added 2 commits that reference this issue on Aug 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugconfirmedThe bug is reproducable and confirmedworkaroundThe issue contains a workaround

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions