On Tab 'SSH' in HyperCon, the topmost drop-down allows to select between 'All Systems (not OE/LE)' and 'OpenELEC / LE'.
When selecting 'OpenELEC / LE', remote access to Hyperion via hyperion-remote works.
Yeah, I know...reading helps.
Though, I really would have appreciated a hint here.
Beiträge von SVLoneStar
-
-
-
Hello,
I am using Hyperion (1.03.4) and HyperCon (v1.03.3) with OpenElec 8.0.4, running on a RasPi 2.
LEDs are working, but colors are off.
I want to calibrate the colors, but I can't get HyperCon to interact with Hyperion using hyperion-remote.
Using HyperCon, I can connect successfully via SSH to the RasPi.
When I try to change the colors using the color wheel on the SSH tab, the log shows:Code
Alles anzeigenSSH Traffic: ssh connected ssh out: hyperion-remote -c ffcea7 ssh out: sh: hyperion-remote: not found ssh out: hyperion-remote -c ffb485 ssh out: sh: hyperion-remote: not found ssh out: hyperion-remote -c ff6d39 ssh out: sh: hyperion-remote: not found ssh out: hyperion-remote -c ff4400 ssh out: sh: hyperion-remote: not found ssh out: hyperion-remote -c ff4300 ssh out: sh: hyperion-remote: not found ssh out: hyperion-remote -c ff550e ssh out: sh: hyperion-remote: not found ssh out: hyperion-remote -c ffbea0 ssh out: sh: hyperion-remote: not found ssh out: hyperion-remote -c 8de1ff ssh out: sh: hyperion-remote: not found ssh out: hyperion-remote -c 8bd9ff ssh out: sh: hyperion-remote: not found ssh out: sudo journalctl -u hyperion.service 2>/dev/null ssh in: There is no working 'sudo'. ssh in: ssh in: On debian/ubuntu/all general purpose linux distributions 'sudo' ssh in: allows a permitted user to execute a command as the superuser ssh in: or another user, as specified by the security policy ssh in: ssh in: With OpenELEC you have root access by default, so you dont need 'sudo'
What do I need to do to get things working? Thanks!!