Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enigma2 does not support custom source bouquet after migration to the UI setup #117152

Open
iliessens opened this issue May 9, 2024 · 2 comments

Comments

@iliessens
Copy link
Contributor

The problem

As I am using my Enigma2 box (with OpenWebif) mainly as a radio receiver, I changed the "source_bouquet" to show radio stations instead of the default TV-stations bouquet.

It seems that this option is lost when migrating away from the YAML configuration, and can not be added again through the UI?
UI configuration was introduced in 2024.5.1 it seems, and deprecating YAML for this integration in the process.

Old YAML config is attached.

What version of Home Assistant Core has the issue?

core-2024.5.2

What was the last working version of Home Assistant Core?

core-2024.4.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Enigma2

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

- platform: enigma2
    host: 192.168.0.13
    name: Radio decoder
    use_channel_icon: True
    source_bouquet: >-
        1:7:2:0:0:0:0:0:0:0:FROM BOUQUET "userbouquet.dbe01.radio" ORDER BY bouquet

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented May 9, 2024

Hey there @autinerd, mind taking a look at this issue as it has been labeled with an integration (enigma2) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of enigma2 can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign enigma2 Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


enigma2 documentation
enigma2 source
(message by IssueLinks)

@autinerd
Copy link
Contributor

autinerd commented May 9, 2024

Hi, the PR for the options flow is already waiting for review in #115795.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants