Thanks cinzas. Its the custom_compent folder that I can not locate.
My HA is using a Portainer/Docker via Open Media Vault 5.
Hi
I’m having problems with the name of the enigma 2 in the card.
This is my enigma2.yaml
- platform: enigma2
host: 192.168.1.33
name: Lounge
mac_address: **:**:**:**:**:**
username: ******
password: ********
port: *****
Each time I put the name, the card show me that error: La entidad no está disponible: media_player.enigma2_media_player_3
When I delete the name, the card show me the default name Enigma2 Media Player.
When you change the default name, changes the entity mame also, so your name will be media_player.lounge in your example.
1 Like
Thank u!!!
we need fix to version 0.110.0? 
Really?
What’s the error? Can you share debug?
I will probably update tomorrow.
Rgds
sorry, my mistake, after disable enigma component, restart, enable enigma all works fine.
before was no module enigma
after restarts works
New version released.
Only changing from MEdiaPlayerDevvice (to be deprecated) to MEdiaPlayerEntity
damn bro, works like a charm with my zgemma h9. Thanks a lot! Google assistant is now able to switch channels on my enigma2 box by using IFTTT.
For people who are interested:
- Home assistant automation
- id: ifttt_google_home_dreambox
alias: Kanaal veranderen dreambox
trigger:
- event_data:
action: call_service
event_type: ifttt_webhook_received
platform: event
action:
- data_template:
entity_id: '{{ trigger.event.data.entity_id }}'
media_content_id: '{{ trigger.event.data.media_content_id }}'
media_content_type: '{{ trigger.event.data.media_content_type }}'
service_template: '{{ trigger.event.data.service }}'
- IFTTT setup
phrase: Switch to channel #
Request method: POST
Request URL: <your external home assistant url + token>
Request body:
{
"action": "call_service",
"service": "media_player.play_media",
"entity_id": "media_player.dreambox",
"media_content_id": {{NumberField}},
"media_content_type": "channel"
}
1 Like
Awesome.
I will give it a try.
I think I can update the README to include that example.
Thanks
Great. Btw I noticed some lag spikes while watching tv on my zgemma box. Looks like the enigma plugin was the cause of the issue. How many times is your plugin requesting the endpoints to get enigma’s status? When I disabled openwebif on my box the spikes disappeared.
hi,
I also have the lags because of grabbing screenshots on Zgemma H9s. How can I disable screenshot function in media_player component?
picon:picon
In the configuration, it will disable the screenshots, and probably also the lag issues.
Can you try ?
Hi,
there’s an error:
Invalid config for [media_player.enigma2]: [picon] is an invalid option for [media_player.enigma2]. Check: media_player.enigma2->picon. (See ?, line ?).
I tried: use_channel_icon: true
but it stills grabs full screenshots.
Probably my receiver is too slow, but I don’t want to resign from whole media control functionality 
hi,
same case here. Every 10s I get lags, I cannot disable screenshots from media_player in HA. Have you solved this already?
Hi
It still occurs when you set picon: picon ?
This is my current configuration, and below a screenshot.
First box is showing picon instead of screenshot.
devices:
- host: 192.168.1.20
port: 80
name: Gigablue
picon: picon
username: root
password: !secret enigma_password
- host: 192.168.1.21
port: 80
name: Dreambox Room
picon: screenshot
username: root
password: !secret enigma_password
bouquet: '1:7:1:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.dbe03.tv" ORDER BY bouquet'
- host: 192.168.1.22
port: 80
name: Dreambox Kitchen
picon: screenshot
username: root
password: !secret enigma_password
enigma2 integration is broken after 0.117 Home Assistant upgrade, even newest it doenst work, at least notify.
restart gives error:
Invalid config
The following integrations and platforms could not be set up:
* enigma
* enigma.notify
Unable to prepare setup for platform enigma.notify: Unable to set up component.
7:48:22 PM – setup.py (ERROR)
Error during setup of component enigma
7:48:22 PM – custom_components/enigma/__init__.py (ERROR)
You are using a custom integration for enigma which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant.
7:48:22 PM – loader.py (WARNING)
Hi
Can you provide more info ? Enable debug…
Currently running 0.117.5 and enigma is working.
I will have a look in the notify.
Thanks
I have also 0.117.5
I did remove all files custom_component/enigma folder, and custom_components.json and copied newest again. same errors
I am not sure how to debug but I got now more info:
Logger: homeassistant.components.notify
Source: components/notify/__init__.py:255
Integration: Notifications (documentation, issues)
First occurred: 8:00:40 AM (1 occurrences)
Last logged: 8:00:40 AM
Unknown notification service specified
Logger: homeassistant.components.notify
Source: components/notify/__init__.py:255
Integration: Notifications (documentation, issues)
First occurred: 8:00:40 AM (1 occurrences)
Last logged: 8:00:40 AM
Unknown notification service specified
Logger: homeassistant.setup
Source: setup.py:280
First occurred: 8:00:40 AM (1 occurrences)
Last logged: 8:00:40 AM
Unable to prepare setup for platform enigma.notify: Unable to set up component.
Logger: homeassistant.setup
Source: custom_components/enigma/__init__.py:94
First occurred: 8:00:40 AM (1 occurrences)
Last logged: 8:00:40 AM
Error during setup of component enigma
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 213, in _async_setup_component
result = await task
File "/config/custom_components/enigma/__init__.py", line 94, in async_setup
configured_devices = config[DOMAIN].get(CONF_DEVICES)
KeyError: 'enigma'
Thanks for the reply.
I will do the same and check what happens.
Give me till the weekend to check it 
1 Like