Thank you for all your work and support on hyperion. This is a great application.
I didn't realize there was a command line option for exporting. Now that i do, i just did a quick hyperiond -h and got it figured out. My config is now backed up just in case.
I did notice that it would not backup my config with hyperion already running. I had to stop it then run the export command. Maybe it's related to the GUI export error, maybe it's not.
Posts by syntaxintact
-
-
Thank you for the info and looking into this.
I did try the config exporter when I first discovered this issue, and it gives an error of invalid params when i try it.
On the console it outputs JSON parse errors.Code2024-10-11T10:15:30.806 |__| WEBSOCKET : <ERROR> JSON parse error @(JsonRpc@::1) - [root].instanceFilter: no schema definition 2024-10-11T10:15:30.806 |__| WEBSOCKET : <ERROR> JSON parse error @(JsonRpc@::1) - [root].configFilter: No check function defined for attribute global 2024-10-11T10:15:30.806 |__| WEBSOCKET : <ERROR> JSON parse error @(JsonRpc@::1) - [root].configFilter: No check function defined for attribute instances
However, disabling the effects does allow me to stop/start hyperiond as root.
-
I followed the steps for troubleshooting a coredump. It wasn't clear how to obtain a debug version of hyperion from the instructions. I ran it with the nightly i have installed anyway. It's probably not useful, but here is what it output.
Code
Display More(No debugging symbols found in /usr/share/hyperion/bin/hyperiond) (gdb) run Starting program: /usr/share/hyperion/bin/hyperiond warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/libQt6Gui.so.6 warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/libQt6Network.so.6 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/libglib-2.0.so.0 warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/libbrotlidec.so.1 warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/libproxy.so.1 warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/libbrotlicommon.so.1 warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/libgobject-2.0.so.0 warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/libcap.so.2 warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/liblber.so.2 warning: could not find '.gnu_debugaltlink' file for /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 [New Thread 0x7ffff0c006c0 (LWP 46549)] [New Thread 0x7fffebe006c0 (LWP 46550)] [New Thread 0x7fffeb4006c0 (LWP 46551)] [Detaching after fork from child process 46552] warning: could not find '.gnu_debugaltlink' file for /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so warning: could not find '.gnu_debugaltlink' file for /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so [New Thread 0x7fffeaa006c0 (LWP 46553)] [New Thread 0x7fffea0006c0 (LWP 46554)] [New Thread 0x7fffe96006c0 (LWP 46555)] [New Thread 0x7fffe8c006c0 (LWP 46556)] [New Thread 0x7fffe3e006c0 (LWP 46557)] [New Thread 0x7fffe34006c0 (LWP 46558)] [New Thread 0x7fffe2a006c0 (LWP 46559)] [New Thread 0x7fffe20006c0 (LWP 46560)] [New Thread 0x7fffe16006c0 (LWP 46561)] [New Thread 0x7fffe0c006c0 (LWP 46562)] [New Thread 0x7fffd7e006c0 (LWP 46563)] warning: could not find '.gnu_debugaltlink' file for /usr/lib/x86_64-linux-gnu/qt6/plugins/tls/libqcertonlybackend.so [New Thread 0x7fffd74006c0 (LWP 46564)] warning: could not find '.gnu_debugaltlink' file for /usr/lib/x86_64-linux-gnu/qt6/plugins/tls/libqopensslbackend.so [New Thread 0x7fffd6a006c0 (LWP 46565)] [New Thread 0x7fffd60006c0 (LWP 46566)] [New Thread 0x7fffd56006c0 (LWP 46567)] [New Thread 0x7fffd4c006c0 (LWP 46568)] [New Thread 0x7fffcbe006c0 (LWP 46569)] [Thread 0x7fffe3e006c0 (LWP 46557) exited] Thread 11 "Effect" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe2a006c0 (LWP 46559)] 0x00007ffff6d25b3f in PyObject_GC_UnTrack () from /lib/x86_64-linux-gnu/libpython3.12.so.1.0
-
I've run into a consistent repeatable problem where hyperion core dumps.
My LED strips require i run hyperion as root.
When I intiially run hyperion as root it's fine. I can configure it, my LED strips work great.
After i stop hyperion, either a ctrl-c or a reboot of the system. I go to start hyperion again as root, it boots and runs the lights through the initial patterns then core dumps every time.
To get it to run again I have to rm /root/.hyperion/db/hyperion.db Then re-configre everything.
This core dump does not occur running as normal user.Code
Display More2024-10-10T10:53:08.893 |I1| IMAGETOLED : <DEBUG> ImageToLedsMap.cpp:112:ImageToLedsMap() | Total index number is: 1096 (memory: 1096). Reduced pixel set factor: 0, Accuracy level: 0, Image size: 88 x 64, LED areas: 72 2024-10-10T10:53:08.893 |I1| IMAGETOLED : <DEBUG> ImageToLedsMap.cpp:112:ImageToLedsMap() | Previous line repeats 1 times 2024-10-10T10:53:08.893 |I1| HYPERION : <DEBUG> Hyperion.cpp:658:handleSourceAvailability() | new source available -> Resume output processing and switch LED-Device on 2024-10-10T10:53:08.893 |I1| LEDDEVICE : <DEBUG> LedDevice.cpp:392:switchOn() | Device adalight is already on. Skipping. 2024-10-10T10:53:08.899 |__| GRABBER-X11 : <INFO> XRandR=[available] XRender=[available] XShm=[available] XPixmap=[unavailable] 2024-10-10T10:53:08.899 |__| GRABBER-X11 : <INFO> Update of screen resolution: [0x0] to [3840x2160] 2024-10-10T10:53:08.899 |__| GRABBER-X11 : <INFO> Using XRender for grabbing 2024-10-10T10:53:08.899 |__| GRABBER-X11 : <INFO> Update output image resolution to [480x270] 2024-10-10T10:53:08.899 |__| GRABBER-X11 : <INFO> Capture interface is now enabled 2024-10-10T10:53:08.918 |I1| MUXER : <DEBUG> PriorityMuxer.cpp:183:registerInput() | Register new input 'System/GRABBER' (X11) with priority 250 as inactive 2024-10-10T10:53:08.918 |I1| MUXER : <DEBUG> PriorityMuxer.cpp:298:setInputImage() | Priority 250 is now active 2024-10-10T10:53:08.918 |I0| MUXER : <DEBUG> PriorityMuxer.cpp:183:registerInput() | Register new input 'System/GRABBER' (X11) with priority 250 as inactive 2024-10-10T10:53:08.918 |I0| MUXER : <DEBUG> PriorityMuxer.cpp:298:setInputImage() | Priority 250 is now active 2024-10-10T10:53:11.901 |I0| EFFECTENGINE : <INFO> Effect [Rainbow swirl fast] finished Hyperion caught signal :SIGSEGV 2024-10-10T10:53:11.926 |__| CORE : <ERROR> /lib/x86_64-linux-gnu/libc.so.6(+0x45320) [0x70c8cca45320] 2024-10-10T10:53:11.926 |__| CORE : <ERROR> /lib/x86_64-linux-gnu/libpython3.12.so.1.0(PyObject_GC_UnTrack+0x1f) [0x70c8ce525b3f] 2024-10-10T10:53:11.926 |__| CORE : <ERROR> /lib/x86_64-linux-gnu/libpython3.12.so.1.0(+0x1dc5f6) [0x70c8ce3dc5f6] 2024-10-10T10:53:11.926 |__| CORE : <ERROR> /lib/x86_64-linux-gnu/libpython3.12.so.1.0(+0x1ce648) [0x70c8ce3ce648] 2024-10-10T10:53:11.926 |__| CORE : <ERROR> /lib/x86_64-linux-gnu/libpython3.12.so.1.0(_PyModule_ClearDict+0x242) [0x70c8ce3de692] 2024-10-10T10:53:11.926 |__| CORE : <ERROR> /lib/x86_64-linux-gnu/libpython3.12.so.1.0(+0x2ef1e0) [0x70c8ce4ef1e0] 2024-10-10T10:53:11.926 |__| CORE : <ERROR> /lib/x86_64-linux-gnu/libpython3.12.so.1.0(Py_EndInterpreter+0x8e) [0x70c8ce4f2fee] 2024-10-10T10:53:11.926 |__| CORE : <ERROR> hyperiond(+0x189915) [0x57382c0fa915] 2024-10-10T10:53:11.926 |__| CORE : <ERROR> hyperiond(+0x178d8f) [0x57382c0e9d8f] 2024-10-10T10:53:11.926 |__| CORE : <ERROR> /lib/x86_64-linux-gnu/libQt6Core.so.6(+0x27c48d) [0x70c8cd47c48d] 2024-10-10T10:53:11.926 |__| CORE : <ERROR> /lib/x86_64-linux-gnu/libc.so.6(+0x9ca94) [0x70c8cca9ca94] 2024-10-10T10:53:11.926 |__| CORE : <ERROR> /lib/x86_64-linux-gnu/libc.so.6(+0x129c3c) [0x70c8ccb29c3c] Segmentation fault (core dumped)
Anyone run into this before?
I'm running Ubuntu 24.04
HyperionVersion 2.0.17-beta.2+nightly20241001ecceb4e7ae96af69dc6f7a3a12805386b447f35b -
It took too long for me to figure out that there was just no way to adjust the default layout/starting position in the basic settings, and had to switch to advanced settings and manually set the layout in the JSON. That was a pain in the ass.
For anyone else using two Skydimo 34" strips in a top half/bottom half configuration with the starting point of each string on the left side of the tv. Here is the json configs.
skydimo_34inch_top_half.txt
skydimo_34inch_bottom_half.txt -
I was able to get the LED strip to work. I noticed a small note, That some led strips needed root access to function. I attempted to use the escalation command provided, but that didn't work. I ended up having to stop hyperion and start it on the command line with sudo.
After re-setting up the controller, the Strip lit up. However I still have an issue with the LED order. The default ordering is all wrong, and i have no idea how to change it. The little documentation i can find doesn't seem to address this topic.
I'd appreciate any instructions or simply documentation links on this topic. I'm just finding it. -
I'm running a nightly install, which is supposed to support the skydimo lights.
I do see it as an option under adalight usb lights. I'm having issues with getting them to work.
I've got the 34" screen version. All the LEDs work, the initial boot tri-color flash confirms that.It's unclear to me if this is an issue due to support still being worked on, or if I've got a configuration problem.
One of the potential issues I see is the default selection of the input position. I cannot find a way to set this. This LED string is a continuous run starting at the bottom left.
Meant to post this as well. Logs show permission denied.
Code
Display More2024-10-02T04:27:35.559Z [LEDDEVICE|Skydimo Livingroom] (INFO) Start 2. attempt of 6 to enable the device in 15 seconds 2024-10-02T04:27:50.574Z [LEDDEVICE|Skydimo Livingroom] (DEBUG) (LedDevice.cpp:140:enable()) Enable device adalight' 2024-10-02T04:27:50.574Z [LEDDEVICE|Skydimo Livingroom] (INFO) Opening UART: ttyUSB0 2024-10-02T04:27:50.574Z [LEDDEVICE|Skydimo Livingroom] (DEBUG) (ProviderRs232.cpp:167:tryOpen()) _rs232Port.open(QIODevice::ReadWrite): ttyUSB0, Baud rate [115200]bps 2024-10-02T04:27:50.610Z [LEDDEVICE|Skydimo Livingroom] (DEBUG) (ProviderRs232.cpp:172:tryOpen()) portName: ttyUSB0 2024-10-02T04:27:50.610Z [LEDDEVICE|Skydimo Livingroom] (DEBUG) (ProviderRs232.cpp:173:tryOpen()) systemLocation: /dev/ttyUSB0 2024-10-02T04:27:50.610Z [LEDDEVICE|Skydimo Livingroom] (DEBUG) (ProviderRs232.cpp:174:tryOpen()) description: USB Serial 2024-10-02T04:27:50.610Z [LEDDEVICE|Skydimo Livingroom] (DEBUG) (ProviderRs232.cpp:175:tryOpen()) manufacturer: 1a86 2024-10-02T04:27:50.610Z [LEDDEVICE|Skydimo Livingroom] (DEBUG) (ProviderRs232.cpp:176:tryOpen()) vendorIdentifier: 0x1a86 2024-10-02T04:27:50.610Z [LEDDEVICE|Skydimo Livingroom] (DEBUG) (ProviderRs232.cpp:177:tryOpen()) productIdentifier: 0x7523 2024-10-02T04:27:50.610Z [LEDDEVICE|Skydimo Livingroom] (DEBUG) (ProviderRs232.cpp:178:tryOpen()) serialNumber: 2024-10-02T04:27:50.610Z [LEDDEVICE|Skydimo Livingroom] (ERROR) Device disabled, device 'adalight' signals error: 'Permission denied' 2024-10-02T04:27:50.610Z [LEDDEVICE|Skydimo Livingroom] (DEBUG) (LedDevice.cpp:181:enable()) Device's enablement failed - Start retry timer. Retried already done [2], isEnabled:
-
Thanks for the response.
Looks like this was resolved. I was able to install this evening. -
Good afternoon all,
I just recently started playing around with Hyperion. I had one of the nightly builds up and running on an Ubuntu 22.04 system. Unfortunately I had to wipe that system for unrelated reasons, and installed 24.04. I just tried to re-install from the nightly builds and i'm getting an error i didn't see on my last install.
Code
Display Moresudo apt install hyperion Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: hyperion : Depends: libqt6sql6-sqlitet64 but it is not installable E: Unable to correct problems, you have held broken packages.
As far as i can tell there is no package available in Ubuntu 24.04 named libqt6sql6-sqlitet64, then again i wasn't able to find a package by that name for Ubuntu 22.04 either.
I was able to find libqt6sql6-sqlite and libqt6sql6sqlt64. I've installed both and neither resolved this.
Anyone run into this or have suggestions?