search

hyperion-project / hyperion.ng

The successor to Hyperion aka Hyperion Next Generation
https://hyperion-project.org/
MIT License
3.04k stars 377 forks source link

Hyperion can't light the amibox (or Prismatik Box) #966

Closed sirpapy closed 4 years ago

sirpapy commented 4 years ago

Bug report

Hello, I bought a USB Ambibox (which is working with the android app Ambilight) but not with Hyperion. I plugged in in my raspberry into the interface ttyUSB0. It is detected but Hyperion can open the light. Can you help me? Thanks

Steps to reproduce

Install the last hyperion using the tutoriel in this repository. Plugged in the Ambibox device into USB. Configure the serial port in hyperion NG. But no lights!

What is expected?

What is actually happening?

System

2020-08-15T13:31:28.115 hyperiond LEDDEVICE : Opening UART: ttyUSB0 2020-08-15T13:31:28.116 hyperiond LEDDEVICE : ProviderRs232.cpp:140:tryOpen() | _rs232Port.open(QIODevice::WriteOnly): ttyUSB0, Baud rate [1000000]bps 2020-08-15T13:31:28.241 hyperiond LEDDEVICE : ProviderRs232.cpp:145:tryOpen() | portName: ttyUSB0 2020-08-15T13:31:28.243 hyperiond LEDDEVICE : ProviderRs232.cpp:146:tryOpen() | systemLocation: /dev/ttyUSB0 2020-08-15T13:31:28.244 hyperiond LEDDEVICE : ProviderRs232.cpp:147:tryOpen() | description: USB Serial 2020-08-15T13:31:28.244 hyperiond LEDDEVICE : ProviderRs232.cpp:148:tryOpen() | manufacturer: 1a86 2020-08-15T13:31:28.245 hyperiond LEDDEVICE : ProviderRs232.cpp:149:tryOpen() | productIdentifier: 0x7523 2020-08-15T13:31:28.246 hyperiond LEDDEVICE : ProviderRs232.cpp:150:tryOpen() | vendorIdentifier: 0x1a86 2020-08-15T13:31:28.247 hyperiond LEDDEVICE : ProviderRs232.cpp:151:tryOpen() | serialNumber: 2020-08-15T13:31:28.252 hyperiond LEDDEVICE : ProviderRs232.cpp:172:tryOpen() | delayAfterConnect for 1500 ms - start 2020-08-15T13:31:29.756 hyperiond LEDDEVICE : ProviderRs232.cpp:179:tryOpen() | delayAfterConnect for 1500 ms - finished 2020-08-15T13:31:29.757 hyperiond COMPONENTREG : ComponentRegister.cpp:36:setNewComponentState() | LED device: enabled

Lord-Grey commented 4 years ago

@sirpapy May I ask you to a) switch on hyperion's Debug Logging -> In the web interface of the Hyperion config go to System > Log. Set the Log-Level = Debug and save settings b) disable the LedDevice via Remote Control c) enable the LedDevice via Remote Control d) share the log output

In addition, please share the details of your system. -> In the web interface of the Hyperion config go to System > About Hyperion and Paste the content of "System info"

sirpapy commented 4 years ago

Hello 2020-08-15T17:17:30.245 hyperiond COMPONENTREG : ComponentRegister.cpp:36:setNewComponentState() | LED device: disabled 2020-08-15T17:17:30.275 hyperiond LEDDEVICE : ProviderRs232.cpp:195:writeBytes() | _inClosing [1], enabled [0], _deviceReady [1], _frameDropCounter [0] 2020-08-15T17:17:30.276 hyperiond LEDDEVICE : ProviderRs232.cpp:208:writeBytes() | [41:64:61:00:9b:ce:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00] 2020-08-15T17:17:30.276 hyperiond LEDDEVICE : ProviderRs232.cpp:247:writeBytes() | In Closing: bytesWritten [474], _rs232Port.error() [0], (null) 2020-08-15T17:17:30.277 hyperiond LEDDEVICE : ProviderRs232.cpp:251:writeBytes() | [0], _inClosing[1], enabled [0], _deviceReady [1] 2020-08-15T17:17:30.308 hyperiond LEDDEVICE : ProviderRs232.cpp:195:writeBytes() | _inClosing [1], enabled [0], _deviceReady [1], _frameDropCounter [0] 2020-08-15T17:17:30.309 hyperiond LEDDEVICE : ProviderRs232.cpp:208:writeBytes() | [41:64:61:00:9b:ce:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00] 2020-08-15T17:17:30.309 hyperiond LEDDEVICE : ProviderRs232.cpp:247:writeBytes() | In Closing: bytesWritten [474], _rs232Port.error() [0], (null) 2020-08-15T17:17:30.310 hyperiond LEDDEVICE : ProviderRs232.cpp:251:writeBytes() | [0], _inClosing[1], enabled [0], _deviceReady [1] 2020-08-15T17:17:30.311 hyperiond LEDDEVICE : ProviderRs232.cpp:92:close() | Flush was successful 2020-08-15T17:17:30.311 hyperiond LEDDEVICE : ProviderRs232.cpp:94:close() | Close UART: ttyUSB0 2020-08-15T17:17:32.673 hyperiond LEDDEVICE : Opening UART: ttyUSB0 2020-08-15T17:17:32.673 hyperiond LEDDEVICE : ProviderRs232.cpp:140:tryOpen() | _rs232Port.open(QIODevice::WriteOnly): ttyUSB0, Baud rate [1000000]bps 2020-08-15T17:17:32.802 hyperiond LEDDEVICE : ProviderRs232.cpp:145:tryOpen() | portName: ttyUSB0 2020-08-15T17:17:32.803 hyperiond LEDDEVICE : ProviderRs232.cpp:146:tryOpen() | systemLocation: /dev/ttyUSB0 2020-08-15T17:17:32.803 hyperiond LEDDEVICE : ProviderRs232.cpp:147:tryOpen() | description: USB Serial 2020-08-15T17:17:32.803 hyperiond LEDDEVICE : ProviderRs232.cpp:148:tryOpen() | manufacturer: 1a86 2020-08-15T17:17:32.803 hyperiond LEDDEVICE : ProviderRs232.cpp:149:tryOpen() | productIdentifier: 0x7523 2020-08-15T17:17:32.804 hyperiond LEDDEVICE : ProviderRs232.cpp:150:tryOpen() | vendorIdentifier: 0x1a86 2020-08-15T17:17:32.804 hyperiond LEDDEVICE : ProviderRs232.cpp:151:tryOpen() | serialNumber:
2020-08-15T17:17:32.809 hyperiond LEDDEVICE : ProviderRs232.cpp:172:tryOpen() | delayAfterConnect for 1500 ms - start 2020-08-15T17:17:34.311 hyperiond LEDDEVICE : ProviderRs232.cpp:179:tryOpen() | delayAfterConnect for 1500 ms - finished 2020-08-15T17:17:34.311 hyperiond COMPONENTREG : ComponentRegister.cpp:36:setNewComponentState() | LED device: enabled

And for the informations: Hyperion Server:

Hyperion Server OS:

Thanks

tpmodding commented 4 years ago

This should be a arduino....did you try adalight?

sirpapy commented 4 years ago

Yes, I choose Adalight in the ttyUSB0 port

image
Lord-Grey commented 4 years ago

@sirpapy Just to verify... Did it work before? or is this a new installation? I am just wondering, if I search for amibox, I get references to Lightpack (which is a device in hyperion too) and HID devices, not serial ones that you try to configure. I am not familiar with ambibox, therefore please bear with me on "silly" questions I might have. The log files do not indicate any error....

In an old forum thread https://hyperion-project.org/threads/ambibox-problem.3444/ I found that the baud rate needs to be "115200". You might want trying this too.

Additional question: On the preview you see the expected picture and mapping to LEDs? Please confirm.

sirpapy commented 4 years ago

hello I tried to put 115200 for Baud rate and It is working now. I think you can put a little tooltips text or something like that for other persons that might have the same problem. Thanks a lot

sirpapy commented 4 years ago

I can provide you other informations for documenting the solution if you want. Feel free to tell me. But really thanks!!!!!