2016-11-29, 08:36
No idea. Boblight doesn't need disk io at all. Its all about gpu. Do you run the daemon on the very same pc?
(2016-10-28, 18:18)RealGsus Wrote:I have exactly the same issue.(2016-10-28, 12:02)RealGsus Wrote: Hi,
I'm running Kodi on Win 10 which recently installed the Anniversary Update. After that, Boblight wasn't working anymore. Tried to uninstall and reinstall the boblight addon, now everytime I start up Kodi the message "This addon needs a binary library. Should the addon try to download it for you." appears. Selecting Yes does nothing.
Maybe you guys can help me figure out what to do, to make it work again. Thanks so much.
Kind regards
Gsus
Here is the Log: http://pastebin.com/uCA7ThQm
Thanks again
Edit: Ok, after checking the log, I found out, that the DLL wasn't downloaded in the addon path, I did that manually, now the startup message is gone and ambilight is back in the menus. BUT it still isn't working while watching a movie. There is just like 1 one the LEDs turned on according to the background. Could it be a config problem? Would be weired since I didn't touch the config.
Here's the new log: http://pastebin.com/htZRwAjH
[global]
interface 127.0.0.1
port 19333
[device]
name ambilight
type popen
output python /home/pi/boblight/ambixi.py
channels 3
interval 500000
[color]
name red
rgb FF0000
[color]
name green
rgb 00FF00
[color]
name blue
rgb 0000FF
[light]
name xi
color red ambilight 1
color green ambilight 2
color blue ambilight 3
hscan 0 100
vscan 0 100
Ambixi.py
from yeelight import *
import sys
bulb = Bulb(IPADDRESS)
bulb.turn_on()
while True:
input = sys.stdin.readline()
inputData=input.split(' ')
print(input)
if(len(inputData)>3):
r = float(inputData[0])
g = float(inputData[1])
b = float(inputData[2])
bulb.set_rgb(r, g, b)
[global]
#timeout 20
interface 0.0.0.0
port 19333
[device]
name ambilight
type momo
output /dev/ttyACM0
rate 115200
channels 150
interval 10000
prefix 41 64 61 00 31 64
delayafteropen 1000000
(2016-12-29, 00:36)Memphiz Wrote: You need to connect the arduino to the windows pc and need to use something like "COM4" (you need to check which one it really is) in the device line i guess...
(InitLog) start of log /home/saber07/.boblight/boblightd.log
(PrintFlags) starting boblightd
(CConfig::LoadConfigFromFile) opening /etc/boblight.conf
(CConfig::CheckConfig) checking config lines
(CConfig::CheckConfig) config lines valid
(CConfig::BuildConfig) building config
(CConfig::BuildConfig) built config successfully
(main) starting devices
(CClientsHandler::Process) opening listening socket on 127.0.0.1:19333
(CDevice::Process) Ambilight: starting with output "/dev/ttyACM0"
(CDevice::Process) Ambilight: setting up
(CClientsHandler::Process) ERROR: bind() 127.0.0.1:19333 Address already in use
(CDeviceRS232::SetupDevice) ERROR: Ambilight: /dev/ttyACM0: write() Resource temporarily unavailable
/dev/ttyACM0 write: 41 64 61 00 18 4d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
(CDevice::Process) ERROR: Ambilight: setting up failed, retrying in 10 seconds
^C(SignalHandler) caught SIGINT
(main) signaling devices to stop
(CClientsHandler::Cleanup) disconnecting clients
(CClientsHandler::Cleanup) closing listening socket
(CClientsHandler::Cleanup) clients handler stopped
(main) waiting for devices to stop
(CDevice::Process) Ambilight: closed
(CDevice::Process) Ambilight: stopped
(main) exiting
(2017-01-22, 13:40)Memphiz Wrote: Pipe the output of boblightd in rc.local to a file and see if the log shows any errors
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6a 00 ff 6c 00 ff 6c 00 ae 9d$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6a 00 ff 6c 00 ff 6c 00 ab 9c$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6b 00 ff 6c 00 ff 6b 00 b1 9c$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6b 00 ff 6c 00 ff 6a 00 b5 9c$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6b 00 ff 6c 00 ff 6a 00 b7 9e$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6b 00 ff 6d 00 ff 6a 00 b5 9f$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6b 00 ff 6d 00 ff 6a 00 b3 9f$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6b 00 ff 6d 00 ff 6c 00 b3 a2$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6b 00 ff 6d 00 ff 6c 00 b3 a3$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6c 00 ff 6d 00 ff 6d 00 b3 a4$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6c 00 ff 6d 00 ff 6d 00 b2 a4$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6c 00 ff 6e 00 ff 6d 00 b3 a3$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6a 00 ff 6b 00 ff 6e 00 ff 6e 00 b1 a2$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6b 00 ff 6b 00 ff 6d 00 ff 6f 00 af a1$
/dev/ttyACM0 write: 41 64 61 00 18 4d ff 6b 00 ff 6b 00 ff 6d 00 ff 6f 00 ae a0$