OSMC and Hyperion

The “no carrier” spam is a long standing tradition with no explanation I’ve ever found.

O.K., thanks a lot!
The TV Screen Icon shows me the actual file playing, so i think grabbing is o.k.
Colours and effects not working, must be a problem with the forwarding i think.

I must have missed something or have a port missmatch, dont think so but double check it.

Never tried forwarding myself, but it’s not a stretch to say a mix of NG and Classic might not be helping. I’d suggest getting NG on the Zero.

I can give it a try,
Can i just install Debian on Zero and use your installer?

No it’s specific for the Vero4K. Although its reason for existing was that all guides and build instructions were for the RPi, so there should be plenty of guides/advice how. It may even be available pre-compiled.

So, if it install Hyperion NG on the Zero i also have to use the forwarder, right?
How do You connect your Ambilght to the Vero ?

Most users have employed an Arduino to drive the LEDs when around a TV. An RPi is overkill, but as that’s what you have to work with already then that’s what we’re doing. The Arduino just has a simple “sketch” on it rather than full Hyperion. The Vero then controls and usually powers the Arduino via a USB cable. We use USB device “adalight” in the Hyperion configuration.

I assume there’s a reason you were connecting you’re original device to the RPi via WiFi, so we’re attempting to recreate that for here.

I like that i can control hyperion with my homebridge (homebridge-hyperion plugin) so i can switch between ambilight mode or just a normal lighting mode from my phone.

The Hyperion Kodi addon works find with my Hyperion “claasic” on Zero. Even when ist installed on the Vero4k but only with SD. Maybe someone had a clue why the Vero crashes when playing HD with the Kodi addon is active…

I’ve followed the instructions on the Hyperion.ng GitHub page to build it on the RPi Zero W. It works on each device - grabbing their local screen output, but no amount of fiddling with network settings is letting me send grabbed data from the Vero to be displayed by the Zero. I’m going to ask the Hyperion Devs about it as it is still in alpha after all.

In the meantime, if by Homebridge you mean some sort of Phillips Hue setup then further up the thread you’ll see @Anthrax has been using the experimental version with Hue support. This might be the modern way of achieving what you want. Have a search/read above.

So you are also unable to send grabbed data to the Zero, right?

Regarding Homebridge. i meant i have the homebridge server ( GitHub - homebridge/homebridge: HomeKit support for the impatient. ) running on another Zero an control several lights ( no Hue´s), power outlet´s and so on…

So, I’d like to work on my Vero4K + Hyperion ambilight setup again because I never got it working well again after switching from pi3+osmc to the Vero4k.
I almost forgot I actually started this topic :slight_smile: .
The last things I tried (like 2 years ago) is to connect the WS2801 leds to a teensy 2.0 and then with usb to the vero4k.

The main problem I had was that I couldn’t get the whitelevel (and other colors as well) correct. Note that I want my leds pretty dim because I want them to be present but not taking to much attention.
It seems that with low brightness the leds have trouble showing the accurate colors.
So I never used the ambilight anymore :frowning: .

If I want to start all over again and get it right this time.
Should I buy new (better) leds? If so, which ones?
Is connecting to a teensy 2.0 still ok and (fast) enough? Or is a pi zero for instance better?
Or what is the very best way (type of leds and controller) to get accurate colors with low brightness lights.

Get a HDfury Diva. Spendy, but it’s the only way to get truly accurate colours from any source. Brightness is also fully adjustable. I just got myself one last week … :wink:

Setup should be much easier these days. The hard part was getting the Hyperion software built and that’s taken care of now.
You’ve already got the gear so I’d suggest trying again with what you have for free.
Colour issues can be power related, in which case make sure the power lines of the LED tape are connected in a common ring to avoid voltage drop.
Calibration is the other main thing to help. That may have improved with NG.
Also, the colour reproduction will likely vary with brightness, so aiming for those levels when you calibrate would be helpful in your case.

Does Hyperion make sense with only bulbs? I have an array of milight bulbs connected via diyHue + esp8266_milight_hub, but no space for LEDs due to my giant projector screen.

Hue lamps alone have been done and ok, as per Anthrax’s video further up. But a quick peruse of the Hyperion GitHub suggests Milight aren’t supported? Shame as they are a lot cheaper. I see now there are a few competitors to Hue bulbs.

Thanks, will take a look at it. Milights arent (yet) genuine supported, but my “Fake Hue” approach works pretty well atm. Compatible with most hue apps and services (afaik as long as they support IP discovery and doesnt work on upnp or sth. like this) I tried. I built the esp8266-milight-hub for 20 Euros with support of unlimited groups to control. Instead of a hue bridge I use diyHue as a software solution.

As I own cheap esp8266 based plugs (Teckin SP21) I flashed them with Tasmota firmware via tuya-convert, so I can use my old on/off-lamps also as Hue devices. Same counts for some other tuya/esp bulbs (Teckin SB50), but they are outsorted due to pretty lame lumen.

All I did was buying an array of different milight bulbs for about 100 Euro, and now I have a highly configurable “surround” lighting system that can be voice controlled via mycroft.ai.

But building an Ambient-like system on top with DIY means seems difficult. Approaches like the existing kodi-ambilight integrations doesnt really work, so I am hung now between a more proprietary solution (hue sync box etc.) and something like Hyperion.

As I am running also an Intel NUC (OMV, plex.tv) as powerful media server, I am also wondering if I could bypass the external videograbber by internal transcoding the video via the NUC.

But first I have to build the more fundamental infrastructure to get all of this running. As you can imagine I have a variety of construction sites within this complex environment.

@hissingshark
Two more things before I give it a try.

  1. I try to utilize the second HDMI Out of my AVR as “grabber”. What would be a fitting “HDMI-to-USB” adapter?
  2. Do I have any advantages when using my more powerful NUC instead of the Vero? Not sure on what device I should run Hyperion.
    Thanks
    Kelvin
  1. I have not found any nice HDMI-to-USB adapter unless you go for an all-in-one solution like Lightpack; it might have changed in the last year so you’ll have to look. I have a HDMI-splitter connected to a HDMI-to-analogue convertor. Don’t got for the cheap mini ones ($15) as most of them give out a blue screen when nothing is playing which results in a blue Ambilight… Next is a Fushicai USBTV007 Video Grabber which connects to the Vero. It’s a bit messy but it does the trick.
  2. Hyperion was designed with low-power devices in mind; NUC would add no advantage as far as I can tell

Hello,
any news on how to forward captured information from Vero 4k + (running hyperion-ng) to another Hyperion instance over Network?

Thanks

I’ve taken Moode Audio off my Zero so I can test. As I reported I’ve successfully built and tested Hyperion.ng itself on there, but have been unsuccessful forwarding to it from the Vero. I’ve opened a thread regarding it on the Hyperion forum to see if we are doing something wrong, but no one has responded yet.