I’m having some problems setting up Boblight with Openelec on an
Intel NUC – Model D54250WYK (all USB 3.0 ports, no USB 2.0 – I’ve a
feeling this may be my issue).
I have uploaded my Sketch to my Arduino Uno Rev.3 board. I used the
config supplied here: //www.tweaking4all.com/home-theatre/xbmc/xbmc-boblight-openelec-ws2811-ws2812 adjusting for number of LEDs and PIN 13.
I’ve installed both boblightd and Kodi-boblight on my NUC running the
latest version of Openelec. I’ve made sure the baudrates match.
I have used the Boblight config maker and uploaded the config to
When Kodi boots I get the error message that it cannot connect to boblightd.
I have the Pulselight internal HDMI-CEC adapter which Kodi sees on /dev/ttyACM1.
The service.log file in /storage/.kodi/userdata/addon_data/service.multimedia.boblightd shows the following:
line 31 section [device]: wrong value # for key prefix
line 31 section [device]: wrong value PREFIX for key prefix
The Kodi log reads:
### [Kodi Boblight] – connecting to local boblightd
T:140098880403200 DEBUG: ### [Kodi Boblight] – connection to boblightd
failed: SO_ERROR 127.0.0.1:19333 Connection refused
The strange thing is that if I used the sample config that gets
installed on openelec with boblight, it connects to boblightd. The
prefix 41 64 61 00 18 4D
debug off #turn this on to see what it’s doing with the serial port
Whereas my equivalent config reads:
interface 127.0.0.1 # IP Address to bind to
port 19333 # IP Port
name Ambilight # NAME - User readable name for the device
type momo # TYPE - Device type of the LED controller
output /dev/ttyACM0 # OUPUT - Data output device (port) for your LED controller
channels 324 # CHANNELS - Number of channels your configuration has (= 3 x number of LEDs)
interval 20000 # INTERVAL - Refresh rate of your LEDs, 20.000 = 50x per second
rate 460800 # RATE - Communication baufrate to your LED controller
prefix 41 64 61 00 18 4D # PREFIX - Magic code to indicate the START of a full color sequence
threadpriority 10 # THREAD PRIORITY - Boblight process priority
delayafteropen 1000000 # DELAY AFTER OPENING - Time to wait before sending data after opening
debug on # DEBUG - Output debug information (to STDOUT for example)
# colorOrder RGB # NOT NEEDED - HYPERION RGB - Define LED color order (RGB, BRG, etc)
So I’m at a loss, I’ve tried changing the /dev/ttyACM0 to various
others including it’s USB counterparts. Nothing seems to work, all I
have is all the LEDS in white (which is pretty but not the intended
outcome of this weekend’s work!)
If anyone could help me out and point me in the right direction, I’d be very grateful.