Currently, I have to access the Hyperion Web Interface on my cell phone to turn my Hyperion LEDs on. It would be nice to activate LEDs via my Alexa setup.
My typical cable box output goes direct to one HDMI input on my TV. While my gaming device and a ROKU box go through a HDMI switch before the capture/Pi Hyperion combo and, finally, to a TV HDMI input.
Am I doing something wrong?
Is there a better way?
I was surprised that some posts were mentioning that capture devices were no less than $80-100. This one was ~$30 US and seems to do a good job. I found the 1080p capture for lighting lagged a little for this project. But backing it down to 720p works great.
At this price, the added functionality for HDCP devices was a big surprise.
Alles anzeigenYour devices and how they are connected would be interesting.
Do you use 4K, HDR, DV, ARC, CEC and what are the results?
Hyperion Version?
RPI and OS?
Stripes?
regards pclin
My Roku Express box displays at 1080p. I have it hooked to a 3x1 HDMI switch. But, to be certain the switch wasn't stripping the HDCP, I hooked direct to the capture device. I was able to get the same result without the switch. I haven't upgraded our TV service to 4k yet.
I'm a newbie to the 4k/HDR world. I recently upgraded from a 2007 Philips Ambilight plasma TV that died. So I'm finding my way around terms and what settings work best.
TV is an LG UP7070 Series 4k/UHD
Running HyperBian alpha10 on a Pi3 B+
USB
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 Mx
Ch= 1
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev=05.10
S: Manufacturer=Linux 5.10.17-v7+ dwc_otg_hcd
S: Product=DWC OTG Controller
S: SerialNumber=3f980000.usb
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driv
er=hub
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 Mx
Ch= 4
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=02 MxPS=64 #Cfgs= 1
P: Vendor=0424 ProdID=2514 Rev=0b.b3
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=2mA
I: If#=0x0 Alt= 1 #EPs= 1 Cls=09(hub ) Sub=00 Prot=02 Driv
er=hub
T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=480 Mx
Ch= 3
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=02 MxPS=64 #Cfgs= 1
P: Vendor=0424 ProdID=2514 Rev=0b.b3
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=2mA
I: If#=0x0 Alt= 1 #EPs= 1 Cls=09(hub ) Sub=00 Prot=02 Driv
er=hub
T: Bus=01 Lev=03 Prnt=03 Port=00 Cnt=01 Dev#= 5 Spd=480 Mx
Ch= 0
D: Ver= 2.10 Cls=ff(vend.) Sub=00 Prot=ff MxPS=64 #Cfgs= 1
P: Vendor=0424 ProdID=7800 Rev=03.00
C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=2mA
I: If#=0x0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driv
er=lan78xx
T: Bus=01 Lev=03 Prnt=03 Port=01 Cnt=02 Dev#= 4 Spd=480 Mx
Ch= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=148f ProdID=5370 Rev=01.01
S: Manufacturer=Ralink
S: Product=802.11 n WLAN
S: SerialNumber=1.0
C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=450mA
I: If#=0x0 Alt= 0 #EPs= 7 Cls=ff(vend.) Sub=ff Prot=ff Driv
er=rt2800usb
T: Bus=01 Lev=03 Prnt=03 Port=02 Cnt=03 Dev#= 6 Spd=480 Mx
Ch= 0
D: Ver= 2.00 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=eba4 ProdID=7588 Rev=03.28
S: Manufacturer=USB3.0 HD Audio Capture
S: Product=USB3.0 HD Video Capture
S: SerialNumber=HU123450
C: #Ifs= 4 Cfg#= 1 Atr=80 MxPwr=200mA
I: If#=0x0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driv
er=snd-usb-audio
I: If#=0x1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driv
er=snd-usb-audio
I: If#=0x2 Alt= 0 #EPs= 0 Cls=0e(video) Sub=01 Prot=00 Driv
er=uvcvideo
I: If#=0x3 Alt= 1 #EPs= 1 Cls=0e(video) Sub=02 Prot=00 Driv
er=uvcvideo
pi@HyperBian:~ $
Driver Info:
Driver name : uvcvideo
Card type : USB3.0 HD Video Capture: USB3.0
Bus info : usb-3f980000.usb-1.1.3
Driver version : 5.10.17
Capabilities : 0x84a00001
Video Capture
Metadata Capture
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x04200001
Video Capture
Streaming
Extended Pix Format
Media Driver Info:
Driver name : uvcvideo
Model : USB3.0 HD Video Capture: USB3.0
Serial : HU123450
Bus info : usb-3f980000.usb-1.1.3
Media version : 5.10.17
Hardware revision: 0x00000328 (808)
Driver version : 5.10.17
Interface Info:
ID : 0x03000002
Type : V4L Video
Entity Info:
ID : 0x00000001 (1)
Name : USB3.0 HD Video Capture: USB3.0
Function : V4L2 I/O
Flags : default
Pad 0x01000007 : 0: Sink
Link 0x02000010: from remote pad 0x100000a of enti
ty 'Processing 3': Data, Enabled, Immutable
Priority: 2
Video input : 0 (Camera 1: ok)
Format Video Capture:
Width/Height : 960/540
Pixel Format : 'MJPG' (Motion-JPEG)
Field : None
Bytes per Line : 0
Size Image : 518400
Colorspace : sRGB
Transfer Function : Rec. 709
YCbCr/HSV Encoding: ITU-R 601
Quantization : Default (maps to Full Range)
Flags :
Crop Capability Video Capture:
Bounds : Left 0, Top 0, Width 960, Height 540
Default : Left 0, Top 0, Width 960, Height 540
Pixel Aspect: 1/1
Selection: crop_default, Left 0, Top 0, Width 960, Height 54
0, Flags:
Selection: crop_bounds, Left 0, Top 0, Width 960, Height 540
, Flags:
Streaming Parameters Video Capture:
Capabilities : timeperframe
Frames per second: 30.000 (30/1)
Read buffers : 0
pi@HyperBian:~ $
$ v4l2-ctl --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
Type: Video Capture
[0]: 'MJPG' (Motion-JPEG, compressed)
Size: Discrete 1920x1080
Interval: Discrete 0.017s (60.000 fp
s)
Interval: Discrete 0.033s (30.000 fp
s)
Size: Discrete 1280x720
Interval: Discrete 0.017s (60.000 fp
s)
Interval: Discrete 0.033s (30.000 fp
s)
Size: Discrete 960x540
Interval: Discrete 0.017s (60.000 fp
s)
Interval: Discrete 0.033s (30.000 fp
s)
Size: Discrete 800x450
Interval: Discrete 0.017s (60.000 fp
s)
Interval: Discrete 0.033s (30.000 fp
s)
Size: Discrete 640x360
Interval: Discrete 0.017s (60.000 fp
s)
Interval: Discrete 0.033s (30.000 fp
s)
I bought this Zasluke 4K capture device (link below) for my Hyperion setup. It works great with Roku apps (XBox, Netflix, Disney+, Prime, YouTube, Hulu, etc.).
I
occasionally have an issue with the LEDs turn off when activating a device via my HDMI switchbox.
To fix, I go to Hyperion WebUI, turn "Status" off from Dashboard, and the turn back on. This reactivated the lighting system.
Got it sorted out shortly after my question. Thanks.
Running HyperBian alpha 10. Where do you change the setting to ignore black bars on screen? Or, is this feature removed? I notice the lights on the edges with bars are a soft blue, not just off.
SUCCESS! THANKS SO MUCH!
The audio and sudo commands posted worked!
I didn't get a chance to work on it last night. This evening, I hooked up a monitor to my Pi3. I get an occasional "undervoltage" warning. Checking PSU, it's steady at 5v. I tried the "Hyperion Free" colorwheel app and get lights! But, the colors are reversed from what wheel shows. Still no luck with Ambilight setup. I will try the suggested work around. But, I'm confused why one would work and the other does not.
This is easiest if you know how to add the commands in putty via PC, or directly on pi
I'll try that this evening. I seen this post last night when I submitted my OP.
BUT...I believe this post mentions some lights working. So, I considered mine to be a different issue.
Alles anzeigenquestion,
do you see or don't you see the startup effect on the leds?
because if Hyperion is booting up NEVERTHELESS the Hyperion service is running under root, you should always see the startup effect.
mostly the rainbow colours.
so if you are seeing nothing then something else is the matter within your setup
where's your log out of debug section after reboot?
I get no startup effect. Yes, set for rainbow I believe.
I'll post my log this evening. It didn't report any errors, so I didn't add in my OP.
Alles anzeigenHey DIY, for anyone to answer this properly, we need more information
hardware
software
how setting up, what gpio pins are you using etc.
But a shot in the dark, you are using hyperbian alpha 10 on a pi with your LED on ws281X. If so there is a work around to this. Also a rookie error is not grounding your pi gpio and leds together (LED won't work without it)
Yes, I'm using a Pi3 running HyperBian v2_alpha10
https://github.com/hyperion-pr…an/releases/tag/HyperBian
My 5v/15A PSU (not 10A, as I think I typed last night) is powering ws2812B LED strip and Pi using a barrel jack (haven't run power to far end of the LED strip yet). Yes, using GPIO18 for data and GROUND is shared to pin 6 on GPIO header of Pi. Hyperion Web UI is set to ws281x as well.
Could you share the "work around"?
Hi All,
I'm attempting a Hyperion setup. The Phillips plasma TV with Ambilight we bought in 2007 finally went out. So, when we shopped for a replacement, I told my wife I wanted to add a DIY Ambilight. I'm no expert with the Pi. But, I previously had Kodi and MAME/Game system emulation on a Pi2. I am quite comfortable with building electronics projects.
I'm on my second set of ws2812B LEDs for this project. I can't get either set to work.
I bought the second set thinking I got a bad one the first time around. I'll likely try using the first set at a later date on the virtual pinball table I built. (Too many projects - hence my username)
Screen capture appears to be works. I can see it in the Hyperion GUI when accessing through the Wifi xxx:8090 port.
I have a 5v/10A running both Pi3 and LEDs. But, I've tried powering Pi separately as well.
I've added a 25v/1000uf cap at the barrel Jack connector. This was mentioned in a YT video I watched. I figured that it couldn't hurt. I have NOT tried the optional 470 ohm resistor or Logic Level board on the data line (yet). LED Data connected to GPIO18. Barrel Jack negative is linked to GND (Pi pin6).
No errors or warnings shown in log file.
Suggestions please?
