Implementation would be easy, but could you explain a little why?
If you start the intall via HyperCon a reboot is already forced - in case spi is added to config.txt -
On a Hyperion update no reboot is required.
If you use the command line install no reboot is forced, but you get a notice to do once.
Nope, updated the jschd lib to: jsch-0.1.53.jar
/confirmed
/fixed
New release online
A 4 channel chip, sounds interesting. You could mix up a white led with the rgb.
Result maybe a better color?
Puh, but how.
Maybe @tvdzwan have an idea 
Hello Zac Morris,
device config is is a known problem
https://hyperion-project.org/threads/known-bugs.17/
Load: Oh, yes this is a UI bug, which was already fixed but plops up again now. :eek:
Will have look.
A workaround for you:
1 load your .dat
2 close hypercon
3. start hypercon again
now you should see it.
Thank you for your report
One question, did you tried again with LibreELEC? I am really interested, if they just pushed a RPi build.
Thank you
Yeah, great that it solves this for you, on the other hand sad that you need that strange workaround and the log indicates nothing here.
Thank you for your help, we will note it.
thank you!
This is strange, the log says nothing about the amlogic grabber that is working for you now. hm
You are 100% sure that the duplicated entry changed it?
could you post both hyperion logs with this config? one with the old hyperiond and one with my hyperiond? I really want to know what is going on now.
This is no problem, We still had no real feedback to the wetek devices or any other amlogic device, so no idea what is working here or not.
hm, framebuffer grabber. I will compile one just with amlogic enabled. we will see what happen then
Edit: new bin attached, replace hyperiond with your current
Could you provide a hyperion log? just to check that.
Thank you.
yes, i consider to use this location, because it is accessible from samba. So in case easy to grab even if you don´t use HyperCon to get it.
OpenELEC is in many terms a compromise. The read-only filesystem is one of them. Due to the point OpenELEC uses systemd i should not need a hyperion.log, because systemd writes everything to a database. On other systemd systems (OSMC/Raspbian jessie(Debain 8, etc)) you could easy grab a log with the following command: journalctl -u hyperion.service
@Rick164
maybe we should consider to split this up to a another thread "Use Arduino via USB to connect your leds" or something. This should also bring a better overview.
Hello Remus, great to have a first feedback from a wetek user.
I am sure their installer just install a raspberrypi compatible build?
We provide no builds for them, they compiled their own build - which may be just a rpi compatible build (?!)
There are several problems with LibreELEC and their install flow. I wrote down a list for myself. I will report this soon.
1. no dtparam=spi=on is added to config.txt (for RPis)
2. the folder hyperion.service is not created at install (this will be created automatically if you open the settings dialog - which they don´t use)
3. due to the missing folder i can´t upload a config to it with hypercon
4. minor - no samba access to the config file (if you want to place it via network)
5. start/stop work now
6. No hyperion.log available - need a solution for this (no journalctl access?)
7. i can´t get a v4l2 screenshot. the output looks gut, but no image is created
8. but v4l2 grabbing is working
(Cause you will run in some of them)
So to push the config file is a little bit uncomfortable.
I would really appreciate if you could try it with OpenELEC first and follow our install instruction that we know it is really working. And no source code problem.
If this is working for you, you need to request a wetek compatible build from them.
We also thought to add LibreELEC support to our install script, but they released now their own binarys so we may not need it. If they found no good solution for hyperion and the libreelec platforms we may get here many issues and we can´t do anything, just to say - don´t use the libreelec hyperion installer
yeah, good to know! Should be done now
Thank you for your fast response
So if you access your openelec via samba there is no "Logfiles" dir that you could enter?
hm, no logfiles directory? interesting. at least on OE7 there is one. Thank you, i will add it to the script
yeah, the logs says: no startup entry added o_O. Don´t get it why that happend
I tried it right now, something went wrong on your install.
Could you push the install button again? The log button should work right now after install
You are the first poster! 
HyperCon V1.02.0
Link zur neuen Farbkalibrierung: [wiki]Farbkalibrierung[/wiki]
Hyperion V1.02.0
Die neue Version könnt ihr ganz einfach installieren, entweder über HyperCon
[wiki]Installation-auf-allen-Systemen[/wiki]
oder die Kommandozeile
[wiki]Installation-über-Kommandozeile[/wiki]
For our advanced users we provide beta versions for testing purposes and ensure to sort out problems.
[COLOR=rgb(0, 0, 0)]Current version:[/COLOR]
none
Install with the following command:
wget -nv -N https://raw.github.com/hyperion-project/hyperion/Beta/bin/install_hyperion.sh && chmod +x install_hyperion.sh && sudo sh ./install_hyperion.sh BETA
On OpenELEC / LibreELEC / RasPlex:
curl -# -k -L --output install_hyperion.sh --get https://raw.github.com/hyperion-project/hyperion/Beta/bin/install_hyperion.sh && sh ./install_hyperion.sh BETAChangelog:
none