Removal of Index from the config broke my sensors

Version of the custom_component

6.2.0

Configuration

multiscrape:
  - resource: https://meteoregionelazio.it/rete/stazione.php?id=RM-139
    scan_interval: 600
    sensor:
      - unique_id: infernetto_hum
        name: Umidità Infernetto
        select: ".dato_grande"
        index: 1
        value_template: '{{ (value.split("%")[0]) }}'
        device_class: "humidity"
        state_class: "measurement"
        unit_of_measurement: "%"

Describe the bug

Removal of Index from the config broke all my sensors. It was a useful feature… now how can I get the same result?

Also, the readme.md still lists Index as a parameter.

[SirUli]

Taking the example from above:

select: ".dato_grande"
index: 1

Then reading the link of Daniel leads to:

select: "tr > td[width="243.3"]:nth-of-type(4) > .dato_grande"

The issue on that webpage is that there is no specific indicator for the field that @namadori wanted to have. So this wasn’t the best example 😉

Generally the solution is :nth-of-type(<number>) where number is the previous index number + 1 (since it doesn’t start with zero). Theoretically the solution would have been

select: ".dato_grande:nth-of-type(2)"

But in the case of the website that doesn’t work 😉

You can easily find the solutions by using the developer tools (e.g. in Chrome via F12 and then change to the “Elements” tab and hit CTRL+F to open the bar where you can enter the Xpath selectors.

[danieldotnl]

This works: .textFCK > p:nth-of-type(1) (even without the nth-of-type)

Check this for more info on CSS selectors: https://www.w3schools.com/cssref/css_selectors.asp