[RELEASE] Official XBMC boblight Addon

Clumsy Wrote:Is there a quick way to setup a toggle button for the addon? I personally use boblight only maybe 20% of the time I actually use xbmc, mostly when I watch movies and switch to my projector. So at the moment I use lirc with irexec to toggle boblight-X11 on, when I need it. If a toggle feature isn't supported I guess this counts as a feature request - ideally I would have a skin button in the OSD, but a button mapping would wpork as well I guess.

Not possible with the current addon api ... lets talk about that after eden again

...how do I reconnect the addon to boblightd after s3? When entering s3 I'm killing boblightd and later restart it on resume...but the script doesn't reconnect.

Before I also startet boblight-X11 with the script and that still works, but I want to use your addon after resume...

Lunatixz Wrote:My router has a usb... and as far as i know my amblone supports boblightd since the pwm pins are the same... and there is code for the micro controller on boblightd's git...

Look forward to getting it working...thanks for the response...

You can track the ticket i've made to the openwrt guys here:

https://dev.openwrt.org/ticket/10562

snipah Wrote:...how do I reconnect the addon to boblightd after s3? When entering s3 I'm killing boblightd and later restart it on resume...but the script doesn't reconnect.

Before I also startet boblight-X11 with the script and that still works, but I want to use your addon after resume...

Could you post a xbmc.log when resuming please?

Sure! Log is located here as a zip-file: LINK!

boblight-log posts this after resume:

snipah Wrote:Sure! Log is located here as a zip-file: LINK!

boblight-log posts this after resume:

Code:

20:30:08.023513 (InitLog)                        start of log /home/xbmc/.boblight/boblightd.log
20:30:08.023826 (PrintFlags)                     starting /usr/local/bin/boblightd -f
20:30:08.023892 (CConfig::LoadConfigFromFile)    opening /etc/boblight.conf
20:30:08.024477 (CConfig::CheckConfig)           checking config lines
20:30:08.025304 (CConfig::CheckConfig)           config lines valid
20:30:08.025401 (CConfig::BuildConfig)           building config
20:30:08.026640 (CConfig::BuildConfig)           built config successfully
20:30:08.026746 (main)                           starting devices
20:30:08.026909 (CClientsHandler::Process)       opening listening socket on 127.0.0.1:19333
20:30:08.029205 (CDevice::Process)               ambilight: starting with output "/dev/ttyUSB0"
20:30:08.029291 (CDevice::Process)               ambilight: setting up
20:30:08.057270 (CDevice::Process)               ambilight: setup succeeded

Ok i can reproduce the issue ... lets see if i find a fix

snipah Wrote:...how do I reconnect the addon to boblightd after s3? When entering s3 I'm killing boblightd and later restart it on resume...but the script doesn't reconnect.

Before I also startet boblight-X11 with the script and that still works, but I want to use your addon after resume...

This will be fixed in version 1.0.1 (should be there the next days...). Though it can be that after resuming there comes an error message saying "can't connect to boblightd", before it gets a successfull connection ... it depends on how fast the boblightd is up and running after sleep.

...sounds great! Thank you very much!

Btw: Couldn't you implement a switch in addon-config to disable the pop-up-messages?

snipah Wrote:...sounds great! Thank you very much!

Btw: Couldn't you implement a switch in addon-config to disable the pop-up-messages?

yes i could ... so annoying?

Memphiz Wrote:yes i could ... so annoying?

nope... I definitely like the connect-popup and the first sound (I hear a second when the popup disappears), but I think it's always good to have a choice