Enigma2 receivers integration

@cinzas ,

Config is okay, it is like what you are saying.
Like i did say, with “picon: screenshot” it is working. But with “picon:picon” it’s not working. And I think it’s because the addon asking for 1_0_19_xxxxxx file. And has to be the 1_0_1_xxxxxx file in the picon directory.

But the strange thing is that it’s showing the right picon in “openwebif” and on the screen/guide/lcd on the VU+.

Also see my error in the HA log, we’re the addon searching voor the 1_0_19 file instead of the 1_0_1 file

That is ineed strange.
What is the image you are using on the enigma box ?
And what OpenWebIf version ?

Probably the image can read picons in distinct formats, however my plugin is expecting to have the picon by grabbing the url with that reference.

Please share the channel reference (you can see it on the channel information). Try to open it via browser .
If Openwebif is showing the right icon, copy the image url and share it.
I need to understand how OpenWebIf is gathering the picon.

Hey @cinzas ,

Using OpenPLi 8.3
OpenWebIf version: 1.5.2

As example again channel name “RTL 4”.

Using channel reference: “1_0_19_4C05_835_600_FFFF0000_0_0_0”.
If i use http://xxx.xxx.xxx.xxx/picon/1_0_19_4C05_835_600_FFFF0000_0_0_0.png it is not showing.
If i use http://xxx.xxx.xxx.xxx/picon/1_0_1_4C05_835_600_FFFF0000_0_0_0.png it’s showing picon RTL4

If i copy the icon from OpenWebIf url: http://xxx.xxx.xxx.xxx//picon/1_0_1_4C05_835_600_FFFF0000_0_0_0.png

So somewere OpenWebIf is making in the service reference the 3th digit smaller from 2 digits to 1. It’s on all the other channels also.

example channel “Nickelodeon”
Service refrence: 1_0_16_5274_C99_3_EB0000_0_0_0
Icon name used: 1_0_1_5274_C99_3_EB0000_0_0_0

I hope, you can find a sollution for this.
If i need some more testing or other things to do, let me know.
If needed by DM.

i have the same issue like @Todzjoe , only the Card with Pause and Shutdown button.
and on click i have the options.
Any ideas how to fix it ?
btw. is there any way to make picons work for newnigma2 devices ? (or is there anything the developers of these image can do ?)
oh, and, is it possible to make more bouquets added to the card ?
thank you

Integration stops working after update to 2023.6 with “AttributeError: module ‘asyncio’ has no attribute ‘coroutine’” error.
To fix this problem some changes should be made in media_player.py file.
Deleted “@asyncio.coroutine” phrases in 14 places and integration works again.

@Szaman : Still on 2023.5. I will update over the weekend, do some tests and upgrade github.

Thanks for the hint

1 Like

Did you all ready had some time to look at this @cinzas ?

Deleting that should work.
Although I think I need to use async before the definition.

I will check it. Stay tuned :slight_smile:

Deleting works but shows some warning:

/usr/local/lib/python3.11/site-packages/bs4/builder/__init__.py:545: XMLParsedAsHTMLWarning: It looks like you're parsing an XML document using an HTML parser. If this really is an HTML document (maybe it's XHTML?), you can ignore or filter this warning. If it's XML, you should know that using an XML parser will be more reliable. To parse this document as XML, make sure you have the lxml package installed, and pass the keyword argument `features="xml"` into the BeautifulSoup constructor. warnings.warn(

I’m still too weak in python to investigate this but boxes works again and it’s enough for me :wink:

Integration has stopped working with 2023.6.0. Suspect it’s the new python update.

I will release a update tomorrow

Thanks for the feedback

1 Like

Appreciate the work you do on the integration. Use it most days.

Hi guys.
Thanks for the feedback, really appreciated.

I have published version 1.6.
If you added the repo to HACS you can easily update. If not, please donwload and copy to the right folder.

Screenshot from 2023-06-08 10-53-40

Screenshot from 2023-06-08 10-54-09

5 Likes

Back working again. Thank you.

1 Like

Hi everyone

Version 1.7 released.

The only change is that it won’t show anymore the XML warning message on boot.

Thanks

image

2 Likes

Thank you very much for all the work you put into this integration.
Would it be possible to fix the annoying problem with enigma entities “unavailable” if HA was restarted previously during receiver in “deep sleep” ?
Would be much better if entities would be available with state “off” so after I start the receiver state changes to “on” and related automations could work.
Now I must everytime restart the whole HA manually when receiver is online, otherwise enigma-related entities never recover from “unavailable” state.

image

1 Like

Seems that some new error appears in the HA log when receiver in deepsleep (4200 occurences in 24 hours).

This error originated from a custom integration.

Logger: homeassistant.helpers.entity
Source: custom_components/enigma/media_player.py:187
Integration: Enigma2 addon (documentation, issues)
First occurred: June 12, 2023 at 10:23:56 AM (4283 occurrences)
Last logged: 8:11:22 AM

Update for media_player.vuplus fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/aiohttp/connector.py", line 980, in _wrap_create_connection
    return await self._loop.create_connection(*args, **kwargs)  # type: ignore[return-value]  # noqa
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1085, in create_connection
    raise exceptions[0]
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 1069, in create_connection
    sock = await self._connect_sock(
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/base_events.py", line 973, in _connect_sock
    await self.sock_connect(sock, address)
  File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 634, in sock_connect
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/selector_events.py", line 674, in _sock_connect_cb
    raise OSError(err, f'Connect call failed {address}')
OSError: [Errno 113] Connect call failed ('192.168.1.17', 80)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 559, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 784, in async_device_update
    await self.async_update()
  File "/config/custom_components/enigma/media_player.py", line 203, in async_update
    powerstate_xml = await self.request_call('/web/powerstate')
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/enigma/media_player.py", line 187, in request_call
    async with self._opener.get(uri, auth=aiohttp.BasicAuth(self._username, self._password)) as resp:
  File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 1141, in __aenter__
    self._resp = await self._coro
                 ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 536, in _request
    conn = await self._connector.connect(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/connector.py", line 540, in connect
    proto = await self._create_connection(req, traces, timeout)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/connector.py", line 901, in _create_connection
    _, proto = await self._create_direct_connection(req, traces, timeout)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/connector.py", line 1206, in _create_direct_connection
    raise last_exc
  File "/usr/local/lib/python3.11/site-packages/aiohttp/connector.py", line 1175, in _create_direct_connection
    transp, proto = await self._wrap_create_connection(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/connector.py", line 988, in _wrap_create_connection
    raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.1.17:80 ssl:default [Connect call failed ('192.168.1.17', 80)]

+1 for that. I would really love it!

+1 on this one

Hi folks,

I discovered thin integration and just want to know if it is possible to use reboot and restart enigma function as a service.

thanks for help
BJ70