Alarms trigger twice

[mattross]

Does anyone know why alarms would trigger twice? This happens with both the in-built alarm functionality and KDF's AlarmPlugin.

2007-05-20 12:44:02.6819 Alarm Plugin A: Alarm A Has Triggered
2007-05-20 12:44:02.5870 Alarm Plugin A: Playing Current Playlist
2007-05-20 12:44:47.5052 Alarm Plugin A: Alarm A Has Triggered
2007-05-20 12:44:47.7528 Alarm Plugin A: Playing Current Playlist
2007-05-20 12:52:08.7270 Alarm Plugin B: Alarm B Has Triggered
2007-05-20 12:52:09.8549 Alarm Plugin B: Loading Playlist - file:///D:/Filez/Stuff/Music/Playlists/Radio%201.m3u
2007-05-20 12:52:40.0749 Alarm Plugin B: Alarm B Has Triggered
2007-05-20 12:52:40.2020 Alarm Plugin B: Loading Playlist - file:///D:/Filez/Stuff/Music/Playlists/Radio%201.m3u

There is about a 30 second gap between the triggers. That has the tendency for the second trigger to restart the playlist from the beginning.

I have two devices connected to my Slim Server, a Transporter and a Squeezebox3, both wirelessly connected through a Linksys router. Alarm A is on the transporter, Alarm B is on the Squeezebox.

[Ben Sandee]

Alarms trigger twice

On 5/20/07, mattross <mattross.2qvsez1179663301 (AT) no-mx (DOT) forums.slimdevices.com>
wrote:
>
>
> Does anyone know why alarms would trigger twice? This happens with both
> the in-built alarm functionality and KDF's AlarmPlugin.


I had this happen when I was experimenting with automatic, localized time
travel. Needless to say the double alarms were annoying enough that I
ceased all work in that field.

Ben