Welcome to the Tweaking4All community forums!
When participating, please keep the Forum Rules in mind!
Topics for particular software or systems: Start your topic link with the name of the application or system.
For example “MacOS X – Your question“, or “MS Word – Your Tip or Trick“.
Please note that switching to another language when reading a post will not bring you to the same post, in Dutch, as there is no translation for that post!
[Solved] boblight configmaker 2 beta config file isn´t working
(@azrael_84)
Active Member
Joined: 9 years ago
Posts: 17
Topic starter
July 30, 2016 7:28 AM
Hi,
i face servere problems regarding a boblight config file created with the version 2 of your boblightconfigmaker program. With version 1 my ambilight is working. As attachment my config files and aduino sketch. What is wrong with my settings in configmaker version 2 ? I need a version 2 file because i have to set an alternative beginning of my stripe.
//www.tweaking4all.com/home-theatre/xbmc/xbmc-boblight-openelec-ws2811-ws2812/#comment-184970
(@hans)
Famed Member Admin
Joined: 12 years ago
Posts: 2861
July 30, 2016 11:25 PM
Welcome to the forum Azrael_84, and thanks for posting config files here with a return link to the original comment. Nice!
What I noticed, when comparing the 2 files, is that the config file v1.4 uses a period as a decimal separator, where as v2.0 is using a komma.
In v2 you can set this in "Preferences" under "Config File Decimal Separator" to "Period".
That will most likely solve the issue.
(@azrael_84)
Active Member
Joined: 9 years ago
Posts: 17
Topic starter
July 31, 2016 2:00 AM
Dear Hans,
thank you for your reply, but the period and komma change couldn´t solve the problem. When i start up my libreelec computer there is written "no connection to boblight" when i use the config file created by your newest config maker program.
Configuration Screen Boblight configmaker vers.2
[url url=
]
[/url]
(@hans)
Famed Member Admin
Joined: 12 years ago
Posts: 2861
July 31, 2016 2:05 AM
I'd also disable the comments as well. Set under "Preferences" the "Config File Comments" to "No Comments".
Just to make sure that does not interfere.
You could also try to copy and pasting the [global], [device] and [color] from v1 -> v2.
(@azrael_84)
Active Member
Joined: 9 years ago
Posts: 17
Topic starter
July 31, 2016 2:31 AM
here are the logs of my libre system
... and a setting screen from configmaker v. 2
[url url=
]
[/url]
(@azrael_84)
Active Member
Joined: 9 years ago
Posts: 17
Topic starter
July 31, 2016 2:39 AM
(@hans)
Famed Member Admin
Joined: 12 years ago
Posts: 2861
July 31, 2016 2:40 AM
I can't see much in the log files, except that the connection is refused ...
Did you try copy/paste the [global], [device] and [color] sections from the v1.4 config, overwriting the v2.0 config sections?
The only real differences I see are "delayafteropen 100000" (in v2 this is set to 0) and "colorOrder RGB" (does not exist in v1.4).
Did you also try removing all comments?
(@azrael_84)
Active Member
Joined: 9 years ago
Posts: 17
Topic starter
July 31, 2016 5:23 AM
copying the settings doesn´t work, all comments are removed.
(@hans)
Famed Member Admin
Joined: 12 years ago
Posts: 2861
July 31, 2016 10:55 PM
That's weird ... the [global] and [device] sections determine communication - if wrong, this would cause the "could not connect" message.
Can you post the log and the config file after you made those changes?
(@azrael_84)
Active Member
Joined: 9 years ago
Posts: 17
Topic starter
August 3, 2016 6:32 AM
sorry Hans for the delay. Here is my kodi log file and the modified configmaker file 1.4 and 2.0. When i use this modified file, there is an error message: not connected to boblight.
I was also trying to use hyperion but this is a great failure, till now i didn´t get my led´s shining. the only thing that is working is your arduino sketch with boblight configmaker file 1.4 nothing else worked. Only that the start point isn´t right and the colors seem to be a little intense.
(@hans)
Famed Member Admin
Joined: 12 years ago
Posts: 2861
August 3, 2016 11:35 PM
I see in your modified config file that still komma's are being used, where as the working config file used a period.
Open the config file in a text editor and do a search and replace, replacing all komma's (,) with a period (.) and try again.
The connection settings are identical, and in the log I see the error messages concerning the komma:
(CConfig::CheckLightConfig) ERROR: /storage/.kodi/userdata/addon_data/service.multimedia.boblightd/boblight.conf line 669 section [light]: wrong value 1,5 6,2 for key vscan
--> komma makes it fail
(@azrael_84)
Active Member
Joined: 9 years ago
Posts: 17
Topic starter
August 4, 2016 4:32 AM
Hi Hans i removed the comma and replaced them with points ., still no working ambilight, the error message not connected to boblight.
(@hans)
Famed Member Admin
Joined: 12 years ago
Posts: 2861
August 4, 2016 5:45 AM
Ah crap, we're not very lucky in getting this to wrok, are we? But I'm not giving up just yet ...
I removed all comments, see attached file, try that one ...
(@azrael_84)
Active Member
Joined: 9 years ago
Posts: 17
Topic starter
August 4, 2016 9:35 PM
sorry Hans, it´s the same: failed to connect to boblightd. I am running out of ideas
(@hans)
Famed Member Admin
Joined: 12 years ago
Posts: 2861
August 4, 2016 11:47 PM
Hi Azrael_84,
Well, that's a bummer.
So according to the log file; it cannot connect. This usually means that the [device] and [global] section are not set right (or: serial speed and prefix are not matching with the sketch values). Or ... you're connecting to the wrong USB port (or in other words: setting the value for "output" is wrong).
You said that the v1.4 config worked ... right?
For the last file I posted here and you working v1.4, the [device] and [config] are identical. So that should not be the issue.
The komma and period issue has been addressed my file as well, and all comments have been removed as well to make sure.
There must be something else going wrong.
You're using the exact same USB port for the working v1.4 and the one I editted, right?
Can you send me the log for when you're trying the working v1.4?
You're not changing anything on the Arduino right?