0.107 Warning about community_plugin

Configuration
21

That you still have some place, where you didn’t changed it… :slight_smile:

Take a good Editor (like Notepad++ or SublimeText) and do a “search in files” over your whole config folder. :slight_smile:

22

i edit via the UI

y
y1280×720 160 KB

23

That’s good for you, but doesn’t change a thing… :wink: :wink: :wink:

Either you go through every file “by hand” and search for it, or you will need to do it with an external editor (see the two above) on your config folder… :slight_smile:

I’d advise the following:

24

you mean I need to change every file which contains the word /community_plugin/ to /hacsfiles/ by manually

25

Yep, that’s the bottom line. :slight_smile: You need to find every single line and change it. :wink: I know, that this is not a great task, but unfortunately you have to go one of these ways. :wink:

But really, do yourself a favour and install Samba and use an external editor. It is so much easier! :slight_smile:

1 Like
26

Running this command from homedir of homeassistant

find . -name "*.yaml" -type f | xargs grep "plugin"

returns just:

./custom_components/hacs/services.yaml: example: 'plugin'

And this confirms there are no ‘plugin’ text in my configuration.yaml file:

image
image946×223 15.5 KB

But I get three times this warning in a row in my log

2020-03-28 14:25:05 WARNING (MainThread) [hacs.deprecated] The '/community_plugin/*' is deprecated and will be removed in an upcomming version of HACS, it has been replaced by '/hacsfiles/*', if you use the UI to manage your lovelace configuration, you can update this by going to the settings tab in HACS, if you use YAML to manage your lovelace configuration, you manually need to replace the URL in your resources.

Not sure what’s going on here…

27

If you’re using yaml lovelace it needs to be in the resources section of lovelace in config. If you use GUI for lovelace there is a lovelace resources section in the configuration and you would have the resources in there.

HACS used to use the cmmunity_plugin endpoint but this is replaced by hacsfiles now. This is all in the resources for lovelace - nowhere else.

28

Hi, thanks for the reply.

If you’re using yaml lovelace it needs to be in the resources section of lovelace in config. If you use GUI for lovelace there is a lovelace resources section in the configuration and you would have the resources in there.

When I was asked to “Take control of your Lovelace UI”, I clicked on “Take control”, so is this YAML or GUI? Looking at the “Raw Configuration Editor”, I can’t see any ‘plugin’ there either.

I do use HACS and when I went there, I was told I had one deprecated community plugin (or something like this) and was given a choice to update, which I did. Was it this that caused the log warning?

Thanks again for your help.

29

Take control is not yaml mode. See

https://www.home-assistant.io/lovelace/yaml-mode/
30

So you are in GUI mode. When you installed 107 it moved the resources to the new method. In the side panel in Configuration you will see Lovelace Dashboards and below that is the setting for resources (also a tab if you open up dashboards) I just don’t remember the exact name off the top of my head. That is where you can edit it.

31

Thanks. Went there, paths are already at hacs so I guess that update in HCAS fixed it already. Good thing that came out of this though is now I know I’m in GUI mode :slight_smile:

32

Trying to make sure I understand the process correctly:

  1. Manually edit the configuration.yaml and/or ui-lovelace.yaml for example
    from:
url: /community_plugin/lovelace-home-feed-card/lovelace-home-feed-card.js

to:

url: /hacsfiles/lovelace-home-feed-card/lovelace-home-feed-card.js

  1. Is it needed to rename the actual directory name on the drive from /community_plugin/ to /hacsfiles/ ?

  2. Check configuration

  3. Restart

33

Just change the resources. DO NOT rename the directory. You should not need to do 3 and 4. Perhaps clear cache and refresh view.

34

I’ve replaced it in the ui-lovelace.yaml but am still getting the warning w/HA 108.3 | HassOS 3.12

Log Details (WARNING)
Logger: hacs.deprecated
Source: custom_components/hacs/http.py:35
First occurred: 9:21:16 PM (9 occurrences)
Last logged: 9:21:21 PM

The '/community_plugin/*' is deprecated and will be removed in an upcoming version of HACS, it has been replaced by '/hacsfiles/*', if you use the UI to manage your lovelace configuration, you can update this by going to the settings tab in HACS, if you use YAML to manage your lovelace configuration, you manually need to replace the URL in your resources.
35

From a little above:

:slight_smile:

36

I searched all files for the following and nothing is found, yet I’m still getting the deprecation warning.

lovelace-home-feed-card.js
37

Did you set resources for yaml or storage mode?
Somewhere it has the wrong resource set. I use WinSCP and open all my yaml files and storage files and then search in all open files for the card name. It is there somewhere.