marc4

I suspected that would be the answer. Unfortunately pushing 2 buttons at the same time works in every other way (turns off both lights at the same time). In terms of supported, I'm not after the ability to program simultaneous taps in any way, I just want it to not trigger programming. Still feels like there's a bug somewhere even if it's unexpected behaviour. It gets my wife all the time when she's turning off the lights in the house. She presses both buttons to be efficient at turning things off, but then activates the double tap programming unintentionally.

@msgreenf any thoughts on the bug report now that my recording has made it clearer? I may have to change all my programming to triple-tap to avoid the bug (since I sometimes press two buttons in close succession, but it's near impossible to push three buttons in close succession).

I don't think I was articulating the problem correctly since we were getting into legacy lighting and brightness levels so I've made a demo. NOTE: This doesn't seem to happen for every keypad configuration. Definitely happens for equal height 3-button configuration. I'm a little worried I'll get a "You're using it wrong" reply with the simultaneous tap, but sometimes I tap both buttons on a keypad at the same time to turn both lights off (and that works if there's no double-tap programming) it also happens if the taps are sequential, but very close together Even simultaneous taps shouldn't trigger a double-tap on any single one of the buttons Here is the programming for the demo, a simple announcement on double-tap: And here is the recording: double tap on the top button announces, as expected double tap on the middle button does nothing, as expected tapping top and middle button announces, UNEXPECTED PXL_20240404_013627273.TS~2.mp4

Have you tried to repro my steps in any of those projects? Does it not happen for you? I can post a video of the repro. I'd happily upgrade to fix but if it's never been reported and isn't listed as a bugfix in the release notes I don't have a lot of confidence that it's been addressed.

I tend to avoid updating unless there's something to gain. Why mess with what's working. I've kept an eye on the changelog since 3.3.3 and saw no indication of any double/triple-tap fixes.

Yes, they are seated well. I believe it's a bug. I have double-tap programming setup on the top button of every one of my keypads to turn off that room and the problem comes up a lot.

Running 3.3.3 I have programming which runs on double-tap of a keypad button. There's a bug where two button taps of different buttons triggers a double-tap event on the last button pushed. For example: I have a 2 button keypad where the top button is "Light" and the bottom button is "Fan". I have programming for double-tap of "Light" which sets the brightness to 50%. No programming for "Fan". I single-tap "Fan" and then quickly single-tap "Light" Unexpected: The "Light" double-tap programming is triggered setting the brightness to 50%, despite only pushing the "Light" button once It seems the logic for the double-tap counts any button tap, rather than accumulating only the button taps of the particular button.

Here's some more details if it helps: This always happens for me with the "Morning Commute" playlist saved as a preset initiated from "Listen" on the navigator. When the bug occurs and playback stops the navigator shows as if it's still playing (see attached navigator photo). When the bug occurs, Spotify keeps counting up if viewed on the app (see attached Spotify app screenshot). So it's as if the song never ends so it never proceeds to the next song.

whoops, mashed submit reply it seems

whoops, mashed submit reply it seems

whoops, mashed submit reply it seems

The source of this is definitely not due to takeover on the same account. It happens when the account is not in use anywhere and my issues match @ramram23's exactly. I have recently resorted to playing from my Spotify app instead of initiating from the "Listen" in the navigator as the problem seems to crop up less in that flow - which is why my log may suggest an initial takeover. But a takeover isn't what's causing the track to stop. When another device uses my Spotify account it closes the session in C4.

No errors in the debug log when the song ends, but here it the log anyway in case it's useful. spotify.log

I am having this issue as well. Can't find a pattern. Usually stops playing after the first song when the listen session is triggered from a saved Spotify preset playlist from a T4 (any navigator really). Pressing skip sometimes sorts things out, sometimes it pauses again at the end of a later song (not always the next song). Initiating the listen from the Spotify app seems to do better, but still sometimes faces the same problem. I'll try to get some logs and share here.