engima2 component use_channel_icon not working

[ageurtse]

Hello,

i'm using the last ha version 0.90.1

enabled enigma2 component in configuration.yaml

media_player:
  - platform: enigma2
    host: UNO4K
    port: 80
    name: UNO4K
    username: root
    use_channel_icon: true

the problem is that it isn't displaying the picon, instate it is grabbing a screenshot

[tjorim]

Hi @ageurtse, please fill out the issue template next time, it's provided to make things easier for everyone. Is there anything in the HA logs?

[ObiKaiKenobi]

Same here:

Home Assistant release with the issue:

0.90.1 

Last working Home Assistant release (if known):

Never. moved from custom component to this one.

Operating environment (Hass.io/Docker/Windows/etc.):

Home Assistant: Docker on Synology NAS
Enigma2 receiver: VU Solo2, VTi 14.0.2

Component/platform:

https://www.home-assistant.io/components/enigma2/

Description of problem:

Option "use_channel_icon" is set to "true" but component is still showing sreenshot

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

media_player.yaml

- platform: enigma2
  host: "MyEnigmaIP"
  use_channel_icon: true
  username: root
  password: !secret enigma_password
  name: Vu Solo2

Traceback (if applicable):

None

[cgtobi]

Did you check the logs and did you try setting the log level for enigma2 to debug?

[robbiet480]

@fbradyirl Assigning this one to you 😄

[fbradyirl]

It will only display the picons if you have picons installed on the box. Else, fallback to screen grab.

[fbradyirl]

E.g. I have this pack installed:

root@vuduo2:~# opkg list-installed | grep picon

enigma2-plugin-picons-snp-full.400x240-400x240.light.on.transparent

[ObiKaiKenobi]

Picons are installed and im also able to open them via webbrowser. (E.g. http://vusolo2/picon/1_0_19_2887_40F_1_C00000_0_0_0.png)

/api/statusinfo is showing correct service reference: "currservice_station": "tagesschau24 HD", "currservice_serviceref": "1:0:19:2887:40F:1:C00000:0:0:0:"

But debug log is showing that the picon could not be found:

2019-03-23 10:43:02 DEBUG (SyncWorker_8) [openwebif.api] url: http://192.168.178.21:80/api/statusinfo
2019-03-23 10:43:02 DEBUG (SyncWorker_8) [openwebif.api] _call_api : http://192.168.178.21:80/api/statusinfo
2019-03-23 10:43:02 DEBUG (SyncWorker_8) [openwebif.api] Getting Picon URL for : tagesschau24 HD
2019-03-23 10:43:02 DEBUG (SyncWorker_8) [openwebif.api] Going to look for non HD picon for: tagesschau24
2019-03-23 10:43:02 DEBUG (SyncWorker_8) [openwebif.api] Getting Picon URL for : tagesschau24
2019-03-23 10:43:02 DEBUG (SyncWorker_8) [openwebif.api] Could not find picon for: tagesschau24
2019-03-23 10:43:02 DEBUG (SyncWorker_8) [openwebif.api] cached_urls_which_exist: ['http://192.168.178.21:80/grab?format=jpg&r=720&mode=all&T=1252639981', 'http://192.168.178.21:80/grab?format=jpg&r=720&mode=all&T=2230777847', 'http://192.168.178.21:80/grab?format=jpg&r=720&mode=all&T=9612903815']
2019-03-23 10:43:02 DEBUG (SyncWorker_8) [openwebif.api] Instead of picon, returning screen grab url: http://192.168.178.21:80/grab?format=jpg&r=720&mode=all&T=9612903815

Mybe a problem because we are using the service reference as picon filename and noch the channel name?

[fbradyirl]

Correct, newer picon packs in the past 3-4 years use the channel name instead of service ref for the picon file name. It makes maintaining them so much easier because the channel name rarely changes but service ref commonly does.

[ObiKaiKenobi]

Hmm, OK. Good to know. Maybe i´ll give that chanel name thing a try. ;-) It is still not that hard because I am using a PlugIn (PiconManager(mod)) to manage the picons.

Thank you for the clarification and for your contribution!!

Btw: A note about picon nameing on the component page would be superb.

[cgtobi]

So, this isn't an issue with the component or has been sorted?

[fbradyirl]

I think the component is ok but I’ll make a note to update the docs around this.

[cgtobi]

Closing this. Please reopen if this is still an issue or not completely resolved.

[adrianmihalko]

I have a custom logo pack, which is not available as opkg package and it's using service name as reference filename. Is there any chance to continue use this format or is there any tool to convert?

[fbradyirl]

@adrianmihalko wait for #22393 to be released. It should work with service ref picon packs.

[gianky69]

I have picons in my box (external USB pen), these are not displayed in Enigma2 component under Home Assistant 0.92.2 (nor screen grab).

2019-05-16 11:28:08 DEBUG (SyncWorker_2) [openwebif.api] url: http://192.168.1.60:80/api/statusinfo
2019-05-16 11:28:08 DEBUG (SyncWorker_2) [openwebif.api] _call_api : http://192.168.1.60:80/api/statusinfo
2019-05-16 11:28:08 DEBUG (SyncWorker_2) [openwebif.api] Getting Picon URL for Rai 1 HD
2019-05-16 11:28:08 DEBUG (SyncWorker_2) [openwebif.api] trying picon url (by channel name): http://192.168.1.60:80/picon/rai1hd.png
2019-05-16 11:28:08 DEBUG (SyncWorker_2) [openwebif.api] url at http://192.168.1.60:80/picon/rai1hd.png does not exist.
2019-05-16 11:28:08 DEBUG (SyncWorker_2) [openwebif.api] Going to look for non HD picon for: Rai 1 
2019-05-16 11:28:08 DEBUG (SyncWorker_2) [openwebif.api] Getting Picon URL for Rai1
2019-05-16 11:28:08 DEBUG (SyncWorker_2) [openwebif.api] trying picon url (by channel name): http://192.168.1.60:80/picon/rai1.png
2019-05-16 11:28:08 DEBUG (SyncWorker_2) [openwebif.api] url at http://192.168.1.60:80/picon/rai1.png does not exist.
2019-05-16 11:28:08 DEBUG (SyncWorker_2) [openwebif.api] trying picon url (with sref): http://192.168.1.60:80/picon/1_0_1_D49_1450_13E_820000_0_0_0.png
2019-05-16 11:28:08 DEBUG (SyncWorker_2) [openwebif.api] picon url (already tested): http://192.168.1.60:80/picon/1_0_1_D49_1450_13E_820000_0_0_0.png

[robbiet480]

@gianky69 Please open a new issue, thanks!