Discussion in 'Software Support' started by Tyler983, 8 September 2020.
and attached the complete dmesg
@TylersSavage Is there an option to install Hyperion.NG on your windows PC and test, if the Lighberry Box works in general with Hyperion.NG?
It seems that you are using a new Rpi4B and there might be additional considerations and configurations to be taken care of, we (I) are not yet aware of.
Well I'm just using the lightberry led system, the rest is all new (ezcap269 and rpi4). Anyway I also own a rpi3 if could be better to use...
rpi3 may also be good. I just want ruling out that with rpi4 we get additional factors in, which are new.
It is to ring-fence the area where the problem might reside....
Guys, you are and where so gentle and kind. If you need an hep' to understand how hyperion ng act in the rpi4 ambient, i can wait and help you testing on my own with your indications
I tested hyperbian with the rpi4 yesterday. see post: https://hyperion-project.org/threads/hyperbian-hyperion-ng-ezcap-269.10746/page-3#post-27807
I remember good, but what i can't understand is why i have no led response...
Suggest you read the following article and the linked readme.
I assume that is the problem that you face. A conflict between Bluetooth and the Serial device:
@Lord-Grey I start to study the article...
Meanwhile I started a debug and it seems no error but continue to make it in loop:
2020-09-16T20:37:53.223 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:238:setInputImage() | Priority 250 is now active
2020-09-16T20:37:58.683 hyperiond HYPERION : <DEBUG> PriorityMuxer.cpp:238:setInputImage() | Priority 250 is now inactive
following the debug txt
As I have understood from the article I should deactivate Bluetooth.
is this the command? sudo systemctl disable hciuart
Trying to disable bluetooth...
this is my rfkill list:
[email protected]:~ $ rfkill list
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
I don't understand if it's disabled or not
Sorry what is difficult in looking for ERROR messages in the log, like the one that clearly states the reason why the LEDs are off?
2020-09-16T20:34:10.371 hyperiond LEDDEVICE : <ERROR> Device disabled, device 'adalight' signals error: 'Timeout writing data to ttyACM0'
There is a problem writing data to the ttyACM0 device. If you resolve that issue your lights will work.
(and that might save you and us some time guessing....)
@Lord-Grey I know I'm bothering you and I'm so sorry about it.
As I read around, many peoples didn't had problem with ezcap269 and started led just plugging in the usb. So decided to buy it too...
I know, there's a problem with writing data to the ttyACM0 but I don't know how to solve it, because of it I opened this post.
I hope to solve it as soon as possible cause I'm getting crazy, and I think also you because of your patience.
Really thx for support
Fingers crossed that you get it sorted
(and other might benefit too)
thx a lot
I would still suggest that you try hyperion.ng on rpi3 and/or Windows with your Lightberry Setup.
Just to rule out that it is a general, but rpi4 specific problem. Key is getting to the root cause of the issue in a structured fashion.
Sure, tomorrow I'll try with my rpi3 and I'll post here the result. Thx
Still nothing, I transferred the sd to the rpi3 and still nothing happened, Still problems...
If someone wants help me, following there's the dmesg I obtained.
Thx a lot
Do you have a hyperion debug log, too?
Just to see, if the Error is the same?
Here we are...
<ERROR> Device disabled, device 'adalight' signals error: 'Invalid serial device name: [ttyUSB0]!'
Correct that port setting (to ttyACM0) in configuration.
And disable eventually that bluetooth, otherwise we go in circles without clue.
Separate names with a comma.