> I think what it does is forward the signal as a GCM event which is then played in your browser. RPi itself doesn't play the sound in this case. Yup. I usuall

> I think what it does is forward the signal as a GCM event which is then played in your browser. RPi itself doesn't play the sound in this case. Yup. I usually have headphones on, so I wanted it to play the sound where I'll actually hear it. GCM was so I wouldn't have to bother with disconnection/reconnection logic with individial browsers (especially phones...) myself. Then again, the GCM API seems so incredibly unreliable that that might actually have been a net improvement.