[CAaronL]

I'm using nightly builds of XBMC, updating daily 95% of the time, and this issue started a few weeks back, after I updated one day.

For some reason, Sick Beard (alpha build 497, and build 496 before it) can no longer successfully send notifications to XBMC via the default web interface. I've double- and triple-checked the settings (port#, username, password), and everything is configured correctly, but Sick Beard reports an error when trying to send a notification ("Unable to contact XBMC host"). Likewise, XBMC never receives the notification.

I use the official iOS XBMC remote app almost exclusively as my remote control, and it continues to connect to the web interface in order to control XBMC without any problems, using the same settings Sick Beard is trying to use. I can also connect to the web interface without a problem using any web browser on my LAN.

Sick Beard was interacting with my XBMC perfectly for months, until a nightly build sometime in the past month or so broke it. I can always do a manual library update, but I miss the pop-ups which tell me when a new show has downloaded, etc.

Is there a subtle change in the way the web interface is set up in the current pre-Frodo builds that is limiting Sick Beard's interaction with it? Is there anything I can do on the XBMC end to re-establish communication between the two programs?

[artrafael]

Sickbeard uses httpapi, which has no longer supported in XBMC Frodo. See here: http://sickbeard.com/forums/viewtopic.php?t=5348

[nutski]

I think the relevant changes have been pulled from the development branch, download 499 from http://code.google.com/p/sickbeard/downloads/list and it should be fine, i run my from source and everything works well

[CAaronL]

I think the relevant changes have been pulled from the development branch, download 499 from http://code.google.com/p/sickbeard/downloads/list and it should be fine, i run my from source and everything works well

I got excited when I saw your reply, but upon investigating further, I've been using build 499 for as long as it's been released, and the notification in XBMC no longer work. I'm just anxiously awaiting the next build release, I guess. :-)

[saitoh183]

I think the relevant changes have been pulled from the development branch, download 499 from http://code.google.com/p/sickbeard/downloads/list and it should be fine, i run my from source and everything works well

I got excited when I saw your reply, but upon investigating further, I've been using build 499 for as long as it's been released, and the notification in XBMC no longer work. I'm just anxiously awaiting the next build release, I guess. :-)

This is already fixed

[Michaehm]

I've been using