One last thing that I should have checked first: the power.
I usually don't need more than 2.5 amps for my Raspberry 3B+
But it seems Hyperion needs more...
I have used 10 amps and the problem is gone !
My settings remain as they should and there is no noticeable problem in my logs.
The only point now is to get the Ambilight effect. But again I will need more power, at least 3 amps for tests I think.
I have just tried v4l2-ctl --list-devices and I can see that my device is recognised and returns
/dev/video0 and
/dev/video1
which is not that bad...
Yes I did... And I also set dtparam=audio=off
Do you think my device is faulty? How can I be sure?
The leaflet that comes with it specifies a CPU at least i5-3400 and a graphic card NVIDIA GT630 or above.
Oh didn't see you'r using au camera.
This is not a camera but a 'capture device with loop'. Don't ask me why it comes to specifying camera1. This is apparently needed in the settings to have this stuff deliver what is expected.
BTW if anyone has other settings that work for this kind of device, please feel free.
unplug / plug the camera then restart hyperion
For sure, there is a response from the device that says to the software 'yes I'm here'. When I unplug the device, I never can get the options offered 'USB video' and 'camera1'. But pluggi.g it back does not really help.
I am not sure I understand what you want to do with detecting the camera first then starting hyperion.
Most of times device to select is camera1 in WebUI
That's what I am ( desperately) trying to do. The only way for me to have the option 'camera1' offered is to select 'USB video: USB video' when it is possible. And it is possible only under the circumstances above.
I could agree if any setting would be useless.
What is a webcam grabber?
After some difficulties, I realise that I am offered the USB capture options I expected, in certain circumstances.
Now when I save them and restart the system, these settings are ignored. Everything comes back to 'automatic' and I am no longer offered these options.
How come?
The circumstances I am refering to are setting the device to custom > /dev/video14 then saving, then restarting, then again here are the right options offered. Useless.
As I said, I can't enter Camera 1 under 'input'. And I wonder if it's a harware problem, because the capture device is supposed to return some value to hyperion?
When I click on input > automatic , I have -1 for default, which I can replace with a figure but no letters.
I'd like to find another usb cable before I come to the conclusion the capture device is faulty. What do you think?
So now I have this video capture device with loop and it is not easy.
First I had to run Hyperion as root. Then my device was not found by the system until I called it /dev/video14
Then I'd like to follow your advice, but I can't enter Camera1 under input. Only figures fit in.
I have 15 fps, but what device resolution do you advise for a start?
Setting a colour effect via the remote control led to nothing. So I tried with setting the USB device, which is now fine on /dev/video14. I don't have errors in my logs any more.
But still, no colour effects via the remote control. I can see it in the led vizualisation screen in Hyperion but not with the real leds.
The boot effect is fine. My leds light up 1 sec or 2. Then nothing.
My logs show an error
2021-05-03T09:32:31.798Z [hyperiond V4L2:AUTO] (ERROR) Throws error nr: VIDIOC_DQBUF error code 19, No such device 2021-05-03T09:32:32.571Z [hyperiond V4L2:AUTO] (ERROR) VIDIOC_STREAMOFF error code 19, No such device 2021-05-03T09:33:17.696Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:204:sendClose()) send close: 1000 2021-05-03T09:33:21.390Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.1.98 2021-05-03T09:33:21.391Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:81:handleInstanceSwitch()) Client '::ffff:192.168.1.98' switch to Hyperion instance 0 2021-05-03T09:33:25.864Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.1.98I finally found my way to start hyperiond as root in
/etc/systemd/system/hyperion@.service
Now I have the LED status in green on the dashboard, which should be a good sign. But things have not improved, I have no effect yet.
I my json file has been modified, here it is...
Hyperion-2.0.0-alpha.9-Backup (My Hyperion Config) 2021.05.03.txt
The only place I can think of is /boot/config.txt but there is nothing in this file about hyperion.
Please help!
Great. Let's try that... But how can I do it?
Hyperion runs as a daemon and it is launched on system start up. So I need to find the command and modify it. Where?
Here are some logs on debug mode:
2021-04-29T12:50:27.082Z [hyperiond LEDDEVICE] (ERROR) Device disabled, device 'ws281x' signals error: 'Failed to open. Error message: mmap() failed' 2021-04-30T05:56:18.328Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:204:sendClose()) send close: 1000 2021-04-30T05:56:21.435Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.1.98 2021-04-30T05:56:21.436Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:81:handleInstanceSwitch()) Client '::ffff:192.168.1.98' switch to Hyperion instance 0 2021-04-30T05:56:22.896Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.1.98 2021-04-30T05:56:23.228Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1063:handleLoggingCommand()) log streaming deactivated for client ::ffff:192.168.1.98 2021-04-30T05:59:53.583Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:204:sendClose()) send close: 1000 2021-04-30T05:59:57.793Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.1.98 2021-04-30T05:59:57.803Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:81:handleInstanceSwitch()) Client '::ffff:192.168.1.98' switch to Hyperion instance 0 2021-04-30T06:00:03.478Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.1.98 2021-04-30T06:00:03.995Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1063:handleLoggingCommand()) log streaming deactivated for client ::ffff:192.168.1.98 2021-04-30T06:02:33.345Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:204:sendClose()) send close: 1000 2021-04-30T06:02:37.793Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.1.98 2021-04-30T06:02:37.806Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:81:handleInstanceSwitch()) Client '::ffff:192.168.1.98' switch to Hyperion instance 0 2021-04-30T06:02:39.976Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.1.98 2021-04-30T06:02:40.290Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1063:handleLoggingCommand()) log streaming deactivated for client ::ffff:192.168.1.98 2021-04-30T06:05:03.754Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:204:sendClose()) send close: 1000 2021-04-30T06:05:10.734Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.1.98 2021-04-30T06:05:10.740Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:81:handleInstanceSwitch()) Client '::ffff:192.168.1.98' switch to Hyperion instance 0 2021-04-30T06:05:12.668Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.1.98 2021-04-30T06:05:13.055Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1063:handleLoggingCommand()) log streaming deactivated for client ::ffff:192.168.1.98 2021-04-30T06:07:06.522Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:204:sendClose()) send close: 1000 2021-04-30T06:07:11.634Z [hyperiond WEBSOCKET] (DEBUG) (WebSocketClient.cpp:30:WebSocketClient()) New connection from ::ffff:192.168.1.98 2021-04-30T06:07:11.640Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:81:handleInstanceSwitch()) Client '::ffff:192.168.1.98' switch to Hyperion instance 0 2021-04-30T06:07:13.835Z [hyperiond WEBSOCKET] (DEBUG) (JsonAPI.cpp:1054:handleLoggingCommand()) log streaming activated for client ::ffff:192.168.1.98Device is disabled??? Why?
I can add pictures if you want.
I started some tests a month ago without any splitter or grabber. Now I start again with a capture device with loop and a splitter.
What am I doing wrong ? Only one led is flashing on the raspy boot. When I unplug the usb connection between the rapi and the capture device, all the leds are flickering. And when I plug the usb back in, all the leds get brighter (?)
But this is not the expected effect.
Hyperion-2.0.0-alpha.9-Backup (My Hyperion Config) 2021.04.29.txt
Yes I read afterwards your latest topic which answers some of my questions here 
Thanks.
I should have started with this forum instead of viewing all these videos, with some outdated ones. I could figure out that RCA grabbers are not an up-to-date solution, but some people seemed to insist on this.
Anyway, I will go for an HDMI capture device 'with a loop' now... Still wandering why my test does not work 
Yes I've checked in /boot/config.txt for dtparam=spi=on
I've doubled checked the GPIO connection.
What else?
I have Hyperion version 2.0.0-alpha.9 running on top of Raspbian Buster, a led strip attached to pin 12 (GPIO 18) and source effect "warm mood blobs" selected in the remote control section, with priority 254. Nothing happens...
My led strip is ok, tested with another device.
You should be able to get some light from the kit without a source though - for testing the different Hyperion light effects for example.
Did you try that without your grabber? For me the result is negative.
So you also have a splitter I presume, with one HDMI connection to your capture device and the other one to your TV?
