[BUG] button presses not registering in logging

[marieacg]

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

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

Is this a bug in companion itself or a module?

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

Is there an existing issue for this?

• [x] I have searched the existing issues

Describe the bug

button presses are no longer logged in 4.1.5 - or seems to be

Steps To Reproduce

press any button go to logs, and ensure debug is selected no entries for button press included in log

Expected Behavior

press any button go to logs, and ensure debug is selected entries for button press to be included in log

Environment (please complete the following information)

- OS:W10
- Browser:Chrome
- Companion Version:4.1.5

Additional context

No response

[Julusian]

I am not able to reproduce this on either 4.1.5 or latest beta, these messages are being logged normally for me in both

[marieacg]

hi julian –

thankyou for looking into this for me.

There must be something quirky with my installation.

In this case, I am only using the StreamDeck emulator and not a physical device. I can see emulator button presses on other, older instances of Companion – but could this be a reason why I’m not seeing the button press logs

marie

From: Julian Waller @.> Sent: 07 December 2025 16:34 To: bitfocus/companion @.> Cc: Marie Graham @.>; Author @.> Subject: Re: [bitfocus/companion] [BUG] button presses not registering in logging (Issue #3808)

External: Think before clicking [Image removed by sender.]Julusian left a comment (bitfocus/companion#3808)https://github.com/bitfocus/companion/issues/3808#issuecomment-3622479206

I am not able to reproduce this on either 4.1.5 or latest beta, these messages are being logged normally for me in both

— Reply to this email directly, view it on GitHubhttps://github.com/bitfocus/companion/issues/3808#issuecomment-3622479206, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATGJ7AQVGJZL7766MD5QJS34ARJHVAVCNFSM6AAAAACOEOEEGOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMRSGQ3TSMRQGY. You are receiving this because you authored the thread.Message ID: @.***>

[Julusian]

Yeah I really cant explain how/why this would happen. I am seeing it for the emulator on 4.2.0

I can't think of a reason why they wouldnt show up if the presses are happening