Skip to content

Stream Deck Studio button feedback (colour) not updating when the same key triggers its own action; only updates after unrelated redraw event #4358

Description

@JanuszCzujko

Make sure you're on the latest stable or beta build

  • I have tested this on the latest stable or beta release

Is this a bug in companion itself or a module?

  • I believe this to be a bug in companion and not a specific module

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

When a Stream Deck Studio button triggers an action that changes a device's state (PDU socket toggle via HTTP), the feedback (background colour) correctly updates when the same button is triggered remotely (e.g. via Companion's web buttons page), but does not update when the button is pressed directly on the Stream Deck Studio itself — even though the control command is sent correctly in both cases.

The feedback does eventually catch up: if I press a different button on the same Stream Deck Studio page afterward, the previous button's colour then updates to reflect the correct state. This suggests the feedback is being recalculated correctly, but the repaint is not being pushed to the key that originated its own press — only to the surface as a whole on a subsequent, unrelated redraw event.

Steps To Reproduce

  1. Set up a button with an action (PDU socket toggle via HTTP) and a feedback that changes background colour based on socket state.
  2. Assign this button to a Stream Deck Studio page.
  3. Also access the same button via Companion's web buttons interface.
  4. Press the button via the web buttons page — action fires, and the SDS key's colour updates correctly.
  5. Press the same button directly on the Stream Deck Studio — action fires (PDU state changes correctly), but the key's own colour does not update.
  6. Press a different button on the same SDS page — the previous button's colour now updates to the correct state.

Expected Behavior

Pressing a button directly on the Stream Deck Studio should repaint that same key with its recalculated feedback state immediately, the same way it does when triggered remotely.

Environment (please complete the following information)

- Companion Version:5.0.2
- OS: Win 11
- Browser: Edge

Connection tested: both USB and network (PoE) — same behaviour on both
Module: standard tcp commands from repository PDU control (Lindy IPower Switch Classic 8, p4456) standard tcp commands from repository

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    BUGSomething isn't working

    Type

    No type

    Projects

    Status
    No status

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions