Config removed from configuration.yaml? vlc_telnet

Configuration
1

Hello! I recall sometime over last few years that some config will get moved from yaml over to the GUI.

I was using the VLC_Telnet integration, started out with config in configuration.yaml but now its not there. I need to change the ip/pass for the integration but cant find it in the gui for the life of me lol.

2

If you are running the current version of Home Assistant, all integrations should show up on this page:
Open your Home Assistant instance and show your integrations.
If you want to add a new one that is part of core, you also go there and select add.

1 Like
3

I do see it on that page, but I cant find where I can edit the password that was originally in the config yaml.

Maybe i need to delete and re-add it? I hesitated doing this for fear it will give it a new name and Ill have to update my scripts/automations.

I appreciate your reply back!

4

You have 2 options, only one of which is recommended:

  1. Check if your integration has a “Configure” option which should allow you to reconfigure it in-place. If not, then you will unfortunately have to delete and re-add it (make sure you check which automations are using this integration before you do this).
  2. This is absolutely not recommended unless you know what you are doing. You can open the (hidden) storage folder, fine the core.config_entries file, then carefully edit the password. A HA restart should pick up the updated password.
1 Like
5

Thank you! Unfortunately it doesn’t have a config option like many others do.

but I got it!

I added a new device to the integration, which lets me enter IP/password. Resulted in a second entity named. media_player.vlc_telnet_2

So i renamed the old entity to media_player.vlc_telnet_OLD
Renamed the new one back to media_player.vlc_telnet
deleted the old one.

and everything started working! woo hoo

I appreciate the reply! and the tip on core.config_entrie, I’ll explore that later on the side just out or HA curiosity.

1 Like
6

Yep, if your automations are not using Device IDs and are configured to use entity IDs, they should keep working just fine if you fix the entity names in the integration.

1 Like