Custom Component: SkyQ Media Player

Yes, also because using the UI flow i am using the same config…

Ok, I’ll take a look tonight/tomorrow.

Very nice touch!

1 Like

Try version 2.4.1. I suspect this is to do with the EPG not being available for some Italian channels. If anyone finds another source for Italian EPG that would be great.

Yes, it works now… If i ffind another italian EPG source i will notify you.
Thanks, great work!

1 Like

This is a great integration from a very responsive developer. Thanks !

1 Like

I’ve noticed I don’t get the images for the apps showing up anymore. I haven’t removed the integration and installed it all again from scratch and copied over the images to /www/community/skyq, I’ve cleared browser cache but they still don’t show up either in a browser or in the app. Has anything changed to stop this working?

Ok, I’ve obviously broken something. Are you on latest version? I’m away from home so won’t look at it before Saturday.

I just tried it on my install, Netflix at least comes up fine. When you look at the entity in developer tools, does it show a value against entity picture and if you add the shown url to the main HA url does it show the picture?

Should be something like:

entity_picture: /api/media_player_proxy/media_player.sky_q?token=e1ec3693030f244f43a3064aba7eb2d9a57c06df96662194a53ba4ceb5bdcb1f&cache=4b69a3b8d83f3eff

Yea so something weird is happening, it looks like pihole is blocking the image, live images work fine but the local images are blocked for some reason.
How does pihole even block stuff on the local network and how do I stop it.
At least you know it’s not your code that’s not working.

I was going to say, if there is something in entity picture, then the integration can see the image, because it only adds a value if it can do a ‘head’ request to it.

Yep it’s there, it seems to show the string in entity picture as it should but for some reason it’s blocked from loading it into a browser.

Try constructing a url with it, and opening it in Chrome with developer tools open, and see if there are any errors showing in the console. It would be cleaner than opening HASS via Chrome.

I stopped using Pihole when they deprecated it, so use Adguard add on now.

Pihole is deprecated? Nothing on the website that I can see to say that. Did not know that. Maybe I’ll check out adguard.

I’m not sure what’s happening now, pihole isn’t blocking the URL but if I go to

http://192.168.1.3:8123/api/media_player_proxy/media_player.skyq_living_room_2?token=d8dd19a2328b18d0aa60ea73c6c58894024cfbb592f9fe9168440af1c84ae21d&cache=4b69a3b8d83f3eff

In chrome I get the pihole landing page, I even get this when I stop the pihole docker.
I also can’t see why live images work in the exact same way but the png’s don’t.

Can you tell me where the images are pulled from and cached to? Maybe I could whitelist that URL?

I should have said the pihole add on is deprecated.

I’ve not looked at HASS image caching to be honest because it has always just worked for me. Should be easy to whitelist it though. Best in mind live images are likely using the external URL. When you look at the entity in developer tools for live view it should show a second URL which I think is what it uses to save you routing via HASS, whilst for a local image it needs to serve it so it is accessible via the Internet.

I run pihole in a docker container, I try to avoid home assistant add-ons for stuff like that, if home assistant dies (or I kill it) I would still want my network to function as it normally would.
I may try adguard to see if it fixes my problem.

To be honest if you are going via IP address pihole doesn’t come into play anyway. So if that URL isn’t accessible then something weird is going on. You can also try yourbaseurl/local/community/skyq/netflix.png, and see if that is accessible. If that works I can look at the code at the weekend to see if I can provide via that url.

That’s what I thought, why would an internal IP go through DNS? It looks like the network thinks that URL is trying to access the pihole admin page.
If I go to those URLs then the images show correctly with both internal IP and duckdns so I know I’ve got the images right.

Does it work if you access HASS externally? Or fail both internal and external? Is your router doing something funny?