iSponsorBlockTV triggers unmute event without prior mute event (false positive ad detection) for chromecasts

[FrankTub]

Describe the Bug

iSponsorBlockTV triggers an "unmute" action for an ad event without a prior "mute" action, leading to unexpected muting/unmuting behavior during normal video playback. Content that is not an ad is treated as an ad boundary, and an Unmuting... command is sent to the device even though Muting... was never executed for that segment.

In the provided logs, an unmute event (Unmuting...) is logged and sent to the target device without any preceding mute event for that category or segment.

Reproduction Steps

1. Launch iSponsorBlockTV and connect it to a YouTube client on a Chromecast.
2. Begin playing content where SponsorBlock segments or ad detection triggers occur.
3. Observe playback and console/container logs when non-ad content is playing.
4. Notice that iSponsorBlockTV issues an Unmuting... command without ever having issued a Muting... command beforehand.

Expected Behavior

iSponsorBlockTV should maintain and verify the current mute state, only sending an unmute command if a mute command was actually triggered previously during an active ad segment.

Actual Behavior

An unmute action is issued independently without a prior mute event:

2026-08-18 20:15:02,935 - iSponsorBlockTV-<screen-id> - INFO - Playing video 7cSXnbRzl2o with 0 segments
2026-08-18 20:15:06,592 - iSponsorBlockTV-<screen-id> - INFO - Getting segments for next video: pWIW1peY9jE
2026-08-18 20:15:06,756 - iSponsorBlockTV-<screen-id> - INFO - Ad has ended, unmuting
2026-08-18 20:15:06,766 - iSponsorBlockTV-<screen-id> - INFO - Playing video 7cSXnbRzl2o with 0 segments
2026-08-18 20:15:06,767 - iSponsorBlockTV-<screen-id> - INFO - Playing video 7cSXnbRzl2o with 0 segments
2026-08-18 20:16:24,585 - iSponsorBlockTV-<screen-id> - INFO - Ad has ended, unmuting