How do I find "tag" on existing Scrape sensor?

I have nine Scrape sensors in use, and I need to add a tenth. The problem is when I try to configure the ressource. On the second page of the configuration there’s a field called “tag”, and I have no idea what to put there. It is supposed to be the same as the other ones, but where do I find that?

When I open “configure ressource” on the excisting sensors the second page just doesn’t show at all. Is there anywhere to find that field?

I have tags in the actual sensors too, those I can see when I open the sensor to “configure sensor”. But the ressource I just can’t see anywhere.

I do not know the scrape sensor, but usually there is an option to edit the configuration in YAML.
It might be in the three dots in the upper right corner or if there are three dots elsewhere then there.

Thanks for the attempt, but no. There is nothing like that on the Scrape sensor, as far as I can see. The only way is to edit the ressource, and that does not show the second page with the info I need.

What ‘resource’ are you talking about? What sensors? What scraper? What web browser? Are you having code issues because of spelling mistakes? Is ChatGPT or any other LLM/AI involved?

You have not given us much to go by. Any code, error logs, example, specific integration?

[Please post any code with appropriate </> forum formatting for readability purposes]

Thank you for answering! But I’m a bit unsure if you are familiar with the integration, based on your question. Because there is not much code when configuring the Scrape entries, and there are no error logs before the entry is made.

As for AI I have never used it and I probably never will, it’s the first thing I disable on any new device. I am a translator by profession and I think it will take my job in a couple of years, which incidentally is the same time that I can retire. And I will retire, but still don’t use any AI.

  1. There is as far as I know only one official integration that creates scrape sensors. There are multiscrape and maybe others on HACS, but I assumed (I may assume too much, like Qui-Gon Jinn) that writing about Scrape sensors would lead the thoughts of the reader to the integration called Scrape.

  2. I should have written entry, not sensor where the resource is mentioned, so that’s on me. But there is only one “Resource” per entry in the Scrape integration that can be configured, see screenshot (as I wrote, all the excisting entries are identical):

When clicking on that menu, I get this box:

The problem is that this is only half of the configuration. When configuring a new entry, I first have the same box, and when clicking “Submit” on that box, I get a second box, this:

The second field in that box is:
“Select Defines what tag to search for. Check Beautifulsoup CSS selectors for details.”

And nothing from that second box is shown when I open an excisting resource to configure it, so maybe three or four years after I created the other ones I have no idea what to put in that field for it to work as the existing ones do. That’s my problem.

This is the exact reason why I hate GUI only set ups.
The devs need to make sure an element can be fully set up and fully reconfigured, and the latter often fails.

I fully agree. Luckily it’s not often a problem, but when it is, it can be unsurmountable.