Issues Getting Hyperion to Install/Run

Creating my own thread rathan than hijacking a "Solved" one.

Trying to get this ambilight working with the following:

WS2812B
Arduino
RPi3

I can get the yellow snake pattern to run, but nothing happens after that. I'm also not able to get my Android App connected to Hyperion (app keeps saying it can't find the server). This all points to Hyperion not running on my RPi. How do I troubleshoot this? Here's the log for when I tried to install straight from HyperCon:

ssh out: cd /tmp && wget -nv -N https://raw.github.com/hyperio…r/bin/install_hyperion.sh && chmod +x install_hyperion.sh && sudo sh ./install_hyperion.sh HyperConInstall ; rm install_hyperion.sh
ssh out: Last-modified header missing -- time-stamps turned off.
ssh out: 2017-03-09 10:01:14 URL:https://raw.githubusercontent.…r/bin/install_hyperion.sh [14539/14539] -> "install_hyperion.sh" [1]
ssh in: *******************************************************************************
ssh in: This script will install/update Hyperion Ambient Light
ssh in: Created by brindosch - hyperion-project.org - the official Hyperion source.
ssh in: *******************************************************************************
ssh in: ---> Stop Hyperion, if necessary
ssh in: ---> Install/Update Hyperion dependencies (This may take a while)
ssh in: Setting up x11-common (1:7.7+7) ...
ssh in: debconf: unable to initialize frontend: Dialog
ssh in: debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
ssh in: debconf: falling back to frontend: Readline
ssh in: debconf: unable to initialize frontend: Readline
ssh in: debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/arm-linux-gnueabihf/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/arm-linux-gnueabihf/perl5/5.20 /usr/share/perl5 /usr/lib/arm-linux-gnueabihf/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
ssh in: debconf: falling back to frontend: Teletype
ssh in: /var/lib/dpkg/info/x11-common.postinst: 697: /var/lib/dpkg/info/x11-common.postinst: update-rc.d: not found
ssh in: dpkg: error processing package x11-common (--configure):
ssh in: subprocess installed post-installation script returned error exit status 127
ssh in: dpkg: dependency problems prevent configuration of libice6:armhf:
ssh in: libice6:armhf depends on x11-common; however:
ssh in: Package x11-common is not configured yet.
ssh in: dpkg: error processing package libice6:armhf (--configure):
ssh in: dependency problems - leaving unconfigured
ssh in: dpkg: dependency problems prevent configuration of libsm6:armhf:
ssh in: libsm6:armhf depends on libice6 (>= 1:1.0.0); however:
ssh in: Package libice6:armhf is not configured yet.
ssh in: dpkg: error processing package libsm6:armhf (--configure):
ssh in: dependency problems - leaving unconfigured
ssh in: dpkg: dependency problems prevent configuration of libxt6:armhf:
ssh in: libxt6:armhf depends on libice6 (>= 1:1.0.0); however:
ssh in: Package libice6:armhf is not configured yet.
ssh in: libxt6:armhf depends on libsm6; however:
ssh in: Package libsm6:armhf is not configured yet.
ssh in: dpkg: error processing package libxt6:armhf (--configure):
ssh in: dependency problems - leaving unconfigured
ssh in: dpkg: dependency problems prevent configuration of libaudio2:armhf:
ssh in: libaudio2:armhf depends on libxt6; however:
ssh in: Package libxt6:armhf is not configured yet.
ssh in: dpkg: error processing package libaudio2:armhf (--configure):
ssh in: dependency problems - leaving unconfigured
ssh in: dpkg: dependency problems prevent configuration of libqtgui4:armhf:
ssh in: libqtgui4:armhf depends on libaudio2; however:
ssh in: Package libaudio2:armhf is not configured yet.
ssh in: libqtgui4:armhf depends on libice6 (>= 1:1.0.0); however:
ssh in: Package libice6:armhf is not configured yet.
ssh in: libqtgui4:armhf depends on libsm6; however:
ssh in: Package libsm6:armhf is not configured yet.
ssh in: dpkg: error processing package libqtgui4:armhf (--configure):
ssh in: dependency problems - leaving unconfigured
ssh in: Errors were encountered while processing:
ssh in: x11-common
ssh in: libice6:armhf
ssh in: libsm6:armhf
ssh in: libxt6:armhf
ssh in: libaudio2:armhf
ssh in: libqtgui4:armhf
ssh out: E: Sub-process /usr/bin/dpkg returned an error code (1)
ssh in: ---> Downloading the appropriate Hyperion release
ssh out: 2017-03-09 10:01:55 URL:https://svwh.dl.sourceforge.ne…hyperion_rpi2_osmc.tar.gz [1637006/1637006] -> "-" [1]
ssh in: ---> Installing systemd script
ssh in: ---> Modify systemd script for OSMC usage
ssh in: ---> Starting Hyperion
ssh in: *******************************************************************************
ssh in: Hyperion Installation/Update finished!
ssh in: Please download the latest HyperCon version to benefit from new features!
ssh in: To create a config, follow the HyperCon Guide at our Wiki (EN/DE)!
ssh in: Wiki: wiki.hyperion-project.org Webpage: www.hyperion-project.org
ssh in: *******************************************************************************

Feels like the below is causing Hyperion to fail:

ssh in: Mar 09 14:49:46 osmcAllie hyperiond[7495]: terminate called after throwing an instance of 'std::runtime_error'
ssh in: Mar 09 14:49:46 osmcAllie hyperiond[7495]: what(): V4L2GRABBER ERROR: Cannot identify '/dev/video0' ERROR 2, No such file or directory
ssh in: Mar 09 14:49:46 osmcAllie systemd[1]: hyperion.service: main process exited, code=killed, status=6/ABRT
ssh in: Mar 09 14:49:46 osmcAllie systemd[1]: Unit hyperion.service entered failed state.

Zitat von b1rdhous3

Do you have a v4l2 grabber attached? Seems so that it is not recognized

The obvious next question! Right now I don't since I brought the RPi to work to troubleshoot. About an hour ago I was doing some testing and disabled the Grabberv4L2 option in HyperCon. After doing that, the server appears to start and my Android App can connect.

So it does appear that the v4l2 grabber is causing the issue. What is the best way to test that piece of it when I get home?

I was having issues yesterday well with the grabber. How does the grabber know to put the data here "/dev/video0"? Based on the error message below, there's no file/directory where it's looking.

"Cannot identify '/dev/video0' ERROR 2, No such file or directory"

I bought the grabber below, so appears to have UTV007

https://www.aliexpress.com/ite…=2114.13010608.0.0.RGo4jP

Zitat von b1rdhous3

Which linux do you use and which rpi? Maybe there is not enough power. Do you have an active usb-hub?

I'm using RPI3. No idea what Linux is running on that...how do I find that out?

I'm connecting the grabber straight to the usb ports on the Raspberry Pi (it is the only thing plugged into that tower of usb ports)

Will do, about to go home from work. Will then hook everything up and report back. Thanks so much for your help! I've made some decent progress today so feel like I can get this thing up and working by tonight!

Here's the output you requested. Since I've started this, I've moved from OSMC to OpenElec

lsusb: (note grabber and arduino are not hooked up right now)
Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ls /dev:
autofs nbd8 tty16 tty54
block nbd9 tty17 tty55
btrfs-control net tty18 tty56
bus network_latency tty19 tty57
char network_throughput tty2 tty58
console null tty20 tty59
cpu_dma_latency ppp tty21 tty6
disk ptmx tty22 tty60
fb0 pts tty23 tty61
fd ram0 tty24 tty62
full ram1 tty25 tty63
fuse ram10 tty26 tty7
gpiomem ram11 tty27 tty8
hidraw0 ram12 tty28 tty9
hidraw1 ram13 tty29 ttyAMA0
hwrng ram14 tty3 ttyS0
initctl ram15 tty30 uhid
input ram2 tty31 uinput
kmsg ram3 tty32 urandom
log ram4 tty33 usb
loop-control ram5 tty34 vc-cma
loop0 ram6 tty35 vc-mem
mem ram7 tty36 vchiq
memory_bandwidth ram8 tty37 vcio
mmcblk0 ram9 tty38 vcs
mmcblk0p1 random tty39 vcs1
mmcblk0p2 shm tty4 vcs2
mqueue snd tty40 vcs3
nbd0 spidev0.0 tty41 vcs4
nbd1 spidev0.1 tty42 vcs5
nbd10 stderr tty43 vcs6
nbd11 stdin tty44 vcsa
nbd12 stdout tty45 vcsa1
nbd13 tty tty46 vcsa2
nbd14 tty0 tty47 vcsa3
nbd15 tty1 tty48 vcsa4
nbd2 tty10 tty49 vcsa5
nbd3 tty11 tty5 vcsa6
nbd4 tty12 tty50 vcsm
nbd5 tty13 tty51 zero
nbd6 tty14 tty52
nbd7 tty15 tty53

Made massive progress by taking someone else Arduino sketch and using that as opposed to what I was using before. Why that helped, I have no idea. So now I can get the LEDs to light up, and it appears they are lighting up based on the internal frame grabber (i.e. kodi). Now to get the external grabber working. I took apart the device to see which chipset is inside. I thought I bought UTV007, but it turns out to be MBA22N. Do you think this might be why I keep getting the error below:

ssh in: INFO: Frame grabber created and started
ssh in: terminate called after throwing an instance of 'std::runtime_error'
ssh in: what(): V4L2GRABBER ERROR: Cannot identify '/dev/video0' ERROR 2, No such file or directory
ssh in: Aborted

For whatever reason, the grabber isn't creating that folder/file. I'm not sure if it's something I need to setup on my end, or if it's due to the device itself.

Will be picking up another one of these devices locally tomorrow. Feels like hit or miss with these things, they say one chipset and it ends up being another. From what I've heard, as long as it's the UTV or STK one I should be fine. Fingers crossed...

Still looking for the UTV one, but in the meantime I've located a STK113 one and using that now. The device now recognizes the grabber, so another step in the right direction. I can get the screenshot to work through SSH, but this appears to not use the v4l2 grabber, but just the standard rpi screenshot. However, if I trigger a screenshot through HyperCon, it freezes up and doesn't work. What could be causing this?

My setup is as follows:

RPi3
Arduino Uno
STK113 Grabber (plugged into a powered USB hub)

The only thing I can think of is that the STK113 is causing the issue, but no idea how to confirm this. Here's what my log says about the triggered screenshot through HyperCon. I'm using a 6ft cable connecting the HDMI-->AV to the grabber. I read somewhere that using a shorter cable can help. I'll be trying this when I get home today.

killall hyperiond 2>/dev/null ; /storage/hyperion/bin/hyperion-v4l2.sh --device /dev/video0 --video-standard NTSC --input 0 --width 240 --height 192 --crop-left 0 --crop-right 0 --crop-top 0 --crop-bottom 0 --size-decimator 1 --frame-decimator 2 --red-threshold 0.0 --green-threshold 0.0 --blue-threshold 0.0 --screenshot
ssh in: hyperion-v4l2:
ssh in: version : V1.03.2 (brindosch-99d9396/d3713a8-1469452981
ssh in: build time: Jul 25 2016 06:54:40
ssh in: V4L2GRABBER INFO: width=240 height=160
ssh in: V4L2GRABBER INFO: pixel format=UYVY
ssh in: V4L2GRABBER INFO: signal threshold set to: {0,0,0}
ssh in: V4L2GRABBER INFO: started

Tried it with the STK113...and while the RPi would recognize it, HyperCon would freeze up whenever I tried to grab a screenshot. Got my hands on a UTV007 this morning, and can confirm that it worked on the first try.

Working, thanks for everyone's help! Biggest issue was finding the UTV007 chipset.