Ahh fair enough. Don’t worry, a personal workaround that might not work is probably not worth your time.
We are long overdue a contract renewal with SKY anyway. 
Thanks for looking into this though!
I’ve just released version 2.4.4. This comes with two enhancements.
Firstly is support for Germany. Unfortunately I haven’t found a location for a lookup between the Sky IDs for channels, and the published EPG, so this is maintained on my skyq_remote GitHub with the help of @bluenazgul.
Secondly is an option around how many channel EPGs to cache in support of the Media Browser function. The more you have the slower it will be on first load. Also it will consume more memory, so watch out for this issue.
1 Like
Since latest release, during the night, i get two or three of these errors never seen before…
2020-10-28 01:00:05 ERROR (MainThread) [custom_components.skyq.media_player] E0010M - Device is not available: Sky Q
I don’t believe I’ve changed anything in that area. This error will happen when it polls the device and it isn’t available. This always happens for me around 2.45am when the Sky box goes into deep sleep.
Ok, so no problem… 
Hi
Just noticed my sky q component is no longer working. On my sky q media player its showing unavailable and in developer states skyq is showing unavailable. I can see this in the error log?
what have i missed?
Logger: homeassistant.components.media_player
Source: custom_components/skyq/classes/volumeentity.py:54
Integration: Media Player (documentation, issues)
First occurred: 19:54:20 (1 occurrences)
Last logged: 19:54:20
skyq: Error on device update!
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 346, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 469, in async_device_update
await self.async_update() # type: ignore
File "/config/custom_components/skyq/media_player.py", line 353, in async_update
await self._volume_entity.async_update_volume_state(self.hass)
File "/config/custom_components/skyq/classes/volumeentity.py", line 54, in async_update_volume_state
f"W0030M - Volume entity does not exist: {self.name} - {self._entity_name}"
AttributeError: 'Volume_Entity' object has no attribute 'name'
hmm its the volume control. commented that out and it works. Can a skyq media card not control volume of a tv anymore then, sorry maybe its in the docs
I would restart you HA instance and make sure you TV (or whatever) is available.
ps sorry the browse media function is amazing?
click it and see what’s playing on several different channels! Is there a way of having that button more reachable than having to click into a mini media card? not sure if that’s a skyq thing or a media card thing?
Not down to the integration. But use the standard Lovelace card and it is visible.
After latest release not anymore showing the image of the running broadcast as the screenshot shows.
What happened?
EDIT: Sorry, my fault… all is working as before… It happened as i pressed a button to enter inside a special menu (the green button to enter the infos about the play).
Hi,
Newbie here and trying to get this to install. I have it setup via HACS, and is visible on the integrations tab in there, but I am struggling on the:
"On the Integrations page, click to add a new Integration and search for Sky Q. Sky Q will only be visible if you have previously installed via one of the methods above and have restarted Home Assistant.
You will be asked to enter a host (which must be contactable on your network and name). The name defaults to Sky Q. Assuming the Sky Q box is switched on and the details are correct a device and entity will be created and be useable. You can then configure other items by clicking on Options on the Sky Q Integration card. Details are below."
Whilst installing it via HACS I was never asked this, have tried searching the in built integrations tab of HA after a restart but nothing comes up so a bit stuck?
Apologies if this is really obvious!
Thanks
When you have the component installed via HACS (which I think you have) then after a restart you go to the Integrations page and add SkyQ in there (click + in bottom right).
At this stage you’ll be asked for the info you mentioned in your post.
Have a go and post back here if any issues 
Thanks for your reply, that’s what I thought… This is the correct page just to check?
When I search nothing comes up…
Thanks again
This shows that I think it has been installed correctly (sorry not used HACS before so a learning curve for me!)
Both the above look correct…
coupe of things…you may already have done this but just in case
- have you restarted Home Assistant after installing the component in HACS
- (and sorry for asking) have you searched for Sky on the screen your showing in the Integrations page (and yes you are on the right page there)
@Gav_in is exactly right, it should appear in that dialogue. If it doesn’t then it isn’t installed correctly. You may also be able to see if it is installed by looking (assuming you have FTP or have installed File Editor) in your ‘custom_components’ folder where there should be a SkyQ folder with code the same as in my GitHub as below. If not, then uninstall and re-install using HACS, then restart your HA instance.
Many thanks to both of you for replying. Turns out it was because I was connected remotely via Nabu Casa at work. When I connected via local IP came up straight away when I searched.
Not sure why?
Thanks again
1 Like
After finding this custom component last night, I was keen to get it installed and configured.
I installed through HACS and for some reason, it put the component data that should have been in /custom_components/skyq in /www/community/Home_Assistant_SkyQ_MediaPlayer/. I restarted my HA server anyway and went to integrations and SkyQ wasn’t there. I restarted again (just in case) and it still didn’t show.
I uninstalled from HACS and tried reinstalling, but chose an earlier version 2.4.3 (just in case there was an issue). Again it created the Home_Assistant_SkyQ_MediaPlayer folder in the wrong directory and inserted the code and didn’t create a skyq folder.
I do not understand why this is happening. There is nothing showing in the HA logs.
I ended up downloading the code from Github, manually created the skyq folder in custom_components, pasted the code and rebooted HA. I was then able to add through integrations and configure my 3 Sky Q boxes.
I would prefer to use HACS rather than the manual install.
I am running HA 0.117.6, HassOS 4.16 and Supervisor 2020.11.0
Has anybody had this issue or know what I am doing wrong, please?
That’s a new one on me. What did you add as the custom repository name. It should be:-
Have you installed any other HACS integrations? What version of HACS are you using? Unfortunately I don’t have a test environment (other than my Dev) that can try a test install to see if there is a problem with the latest version of HACS.
There is a www in the Github, but that isn’t included in the install zip.