HTTP/1.1 405 Method Not Allowed when trying to call SUBSCRIBE /AlarmClock/Event HTTP/1.1

[opes]

Excellent app! After configuring the firewall as per the comments in #9, everything has been working great. The only issue is that I've been receiving the following error repeatedly in the console when calling noson-app --debug. Since I don't use the Alarm Clock functionality, it hasn't been a big deal, but still wanted to report it just in-case others are experiencing it.

Here's the relevant bit from the debug log:

(SONOS)__connectAddr: connected to socket(0x7f4449ffacd8)
(SONOS)__connectAddr: connected to socket(0x7f4438000b38)
(SONOS)SendRequest: SUBSCRIBE /AlarmClock/Event HTTP/1.1
Host: 192.168.50.73:1400
User-Agent: libnoson/1.0
Connection: close
Accept-Charset: utf-8
Accept-Encoding: gzip, deflate
Callback: <http://192.168.50.76:1400>
NT: upnp:event
TIMEOUT: Second-300
(SONOS)GetResponse: HTTP/1.1 405 Method Not Allowed
(SONOS)GetResponse: Allow: GET, HEAD
(SONOS)GetResponse: Content-type: text/html
(SONOS)GetResponse: Server: Linux UPnP/1.0 Sonos/46.3-57250 (BR200)
(SONOS)GetResponse: Connection: close
(SONOS)GetResponse: 
(SONOS)WSResponse: bad request (405)

Thanks again for the excellent app!

[janbar]

Thanks reporting the issue.
I guess your Sonos device doesn't support the alarm clock service. It could cause this issue. Until now I thought all devices support it. Probably I should check capabilities of connected devices. For instance that won't cause bug other than log a failure.

[opes]

Thanks for following up and apologies for the delay, @janbar. My Sonos device does indeed support the alarm clock service, but perhaps there is something else at play, here. I will try to isolate it on my end and see if I can get any ideas what might be causing it.