2 Lightpack (devices maybe) with boblight possible bug ??? about boblight-lightpack

[Speedy1985]

Hi Timsat, We have make progress in the lightpack code to connect more then one lp device.
We no now that if there is one LP device connected and in boblight.conf is one configured then alll is ok. But when we add a 2e LP then the problem begins.

We have
Amibilight_1st
Serial 1234567890

Ambilight_2st
Serial 0987654321

Now devicelightpack.cpp see the serialnumbers and make a connection with the first device, this is ok.
Then it will connect to the 2e device but it use the first serial. So it will result in a error and try to reconnect, now we are in some loop of connected / disconnected.

ambilight_1st: found Lightpack at bus 3 address 2, serial is A4830363935351708161
ambilight_1st: Lightpack is initialized, bus 3 device address 2
ambilight_1st: found Lightpack at bus 4 address 2, serial is A4830363935351B022F0 << this belongs to ambilight_2st

You see that one devicename Amibilight_1st use two serialnumbers.
I hope you understand the problem.
I wil try to find a solution. But hope you see the solution faster then me :)

I think we need some list with serialnumbers and devicenames. if the serialnumber is used then delete it from the list so there will be only left a serialnumber whats not used. or something
Or check if serialnumber belongs the devicename.

If we are in debugmode we see this error apears:
libusb release interface error error=22

Thanks!

Kind regards Speedy1985 (boblightenigma2.net)

[timsat]

Hi @Speedy1985, i've just tried to reproduce problem and it seems everything is ok except these confusing log messages.

(CDevice::Process)              Lightpack_1: starting
(CDevice::Process)              Lightpack_1: setting up
(CDevice::Process)              Lightpack_2: starting
(CDevice::Process)              Lightpack_2: setting up
(CDeviceLightpack::SetupDevice) Lightpack_1: found Lightpack at bus 1 address 5, serial is 74136353933351809170
(CDeviceLightpack::SetupDevice) Lightpack_1: Lightpack is initialized, bus 1 device address 5
(CDeviceLightpack::SetupDevice) Lightpack_2: found Lightpack at bus 1 address 5, serial is 74136353933351809170
(CDeviceLightpack::SetupDevice) Lightpack_1: found Lightpack at bus 1 address 6, serial is 85234333237351E0D1C1
(CDevice::Process)              Lightpack_1: setup succeeded
(CDeviceLightpack::SetupDevice) Lightpack_2: found Lightpack at bus 1 address 6, serial is 85234333237351E0D1C1
(CDeviceLightpack::SetupDevice) Lightpack_2: Lightpack is initialized, bus 1 device address 6
(CDevice::Process)              Lightpack_2: setup succeeded
(CClientsHandler::Process)      127.0.0.1:35177 connected
(CClientsHandler::ParseMessage) 127.0.0.1:35177 said hello
(CClientsHandler::ParseSet)     127.0.0.1:35177 priority set to 128

the messages saying that it founds lightpack is not final, and really means it is probing that lightpack, look at "Lightpack is initialized..." messages instead, i'll fix the text. Btw, what Boblight version do you use? I have been trying to patch you repo with related fix for half a year .)

[silelis]

Hi Timsat,

Even if the Lightpack is initialised well it gives disconnections during boblightd <==> boblight-enigma2 (boblight-X11 replacement) comunication.

Maybe it is possible that We (Timsat, Speedy1985, SileliS) will meet on TeamView and solve this problem togother? - Last week We spend a lot of hours on that. :/

[timsat]

i suggest to make sure we use the same code first, if it doesn't help us then i'm ready to the remote session.

[silelis]

1. Can You point (paste url) to correct version so in our wortk We will have 100% certainty that We use right one?
2. Can You paste You config for 2 Lightpacks so I will compare it with mine?

[timsat]

@silelis

1. now i see the verison is up to date.
2. https://gist.github.com/timsat/83b68bab4c9ad096fc9b

[silelis]

@timsat,

I made config based on Yours, the boblightd version is Speedy 0.87 (up to dated).
And I still have this error (see picture below).

When I execute boblightd -c /etc/boblight.conf the Lightpacks are initializing (end it is correct). This state is stable and may stay as long as I want.
But when I execute boblight-enigma2 -m 2 (boblight-enigma2 == boblight-X11' -m 2 oprion means dynamic mode) it starting to disconnect and connect (infinitive error loop marked on picture with red).

It would be great If You and Speedy connect skills and fix this bug.
From my site I can help as a "in the flow" tester (both Debian PC and Enigma2 set-top sat receiver).

I have to admit that with 1 Lightpack boblight works 100% correct.

[silelis]

@timsat
Is it possible to help in this issue solveing?

[timsat]

@silelis Sorry for late response. Sure, i'm working on it.

[timsat]

@silelis try to build this: https://github.com/timsat/boblight-for-enigma2
i've increased timeout and increased number of IO retries for Lightpack, it might fix the problem.

[wohali]

I have this same problem with boblightd as installed in openelec 3.2.4. I see the same "infinite loop" scrolling and boblightd will only control 1 of the lightpacks attached. If I disconnect the working one and reboot, it will see the other lightpack and control it - but sometimes there is a "strobe" effect.

Do you have a patch not for enigma2 that I can try on standard boblightd source code?

My boblightd.conf is here: https://gist.github.com/wohali/10522168 . I am using 2x serial numbers to identify the devices. They are both firmware 7.5. My machine is an Intel x86-64 i5 MSI motherboard.

[wohali]

FYI I applied https://github.com/timsat/boblight-for-enigma2/commit/96c2f70d93f4b96bfd133541e4899ca7bfc6eb0c.patch to http://boblight.googlecode.com/svn/trunk/ and it fixed the problem.

Thank you so much for your patch! Please contribute it upstream to boblight 😺

[wohali]

Update: This patch does not seem to be sufficient. I have to disconnect then reconnect one of the devices to get both recognized. Also, it seems sometimes the two devices are reversed, even though I am specifying serial numbers in my boblight.conf file.