#confusing multiscrape installation instructions

23 messages · Page 1 of 1 (latest)

shut meadow
#

oioi rather new to HA and HACS. seems like the default integration of "multiscrape" (not scrape) returns an error, i.e. unsupported install message. seems like their installation doc is entirely depecrated in terms of supported/automatic hacs-integration installation

in their docs the instruction reads as follows:
Install via HACS (default store) or install manually by copying the files in a new 'custom_components/multiscrape' directory.

then there's a "configuration" YAML example.
however it basically looks like an actual parsing/template example.

some (older?) usage videos reference /config/custom_components/multiscrape which seems completely deprecated.

does anyone know how to actually "install" this integration?
or which "configuration" to actually edit? that instruction seems very much unclear to a newcomer.

it doesn't look like one is supposed to use/extend homeassistant/configuration.yaml
the /homeassistant/custom_components/multiscrape/ which was downloaded on my end apparently, does not any sort of configuration file either.

those old videos seem to use /config/multiscrape.yaml (manually created?)
so is the idea to now use homeassistant/multiscrape.yaml?

outer cove
#

It's not clear if you have HACS installed and went that route to install the integration?

shut meadow
#
  • yea I'm sort of getting some sort of data or at least sensor now after some search, trial and error. thank you for your response
#
  • also saw some module/include examples. which are probably better than constantly rechecking yaml config in devtools or potentially bricking the main config
#
  • when new for full integrations the gui/comfort way is to integrate via hacs and gui. and also via settings/device/card/entity gui and the gui based YAML editor. which gets confusing in light of the instruction and docs - as that more lowlevel process via yaml config files is simply entirely new to more regular/standard GUI examples/integrations. for HA newcomers
#
  • then the doc mention of "Example configuration (YAML)" in docs imho is somewhat ambiguous. especially in imho this newcomer pov and context and situation. even just "configuration.yaml" would already be way clearer. or even better: /homeassistant/configuration.yaml - so that aspect of GUI vs. filesystem location is made clear.
#
  • still getting used to more difficult non-gui YAML "checks" and config reloads etc. still sometimes confused in terms of settings devices vs. devtools devices/entities. especially with such filesystem-based integration. but that will surely become clearer as well. thank you very much for your response. yes: I was using the current docs/github. that's exactly what lead to some confusion.
shut meadow
#

correct @outer cove - both questions yes. following github in a single configuration file, no module imports. and running a HAOS installation. retested recently and don't seem to get any results

#

wether from regular "scrape", nor "multiscrape". tested some curl tests from terminal. seemed to work for some attempts at least

#
  • any other suggestions? got a multiparse example incl static/working url to paste? or a scrape example? either I'm missing something entirely. something is possibly messed up. or yea. no clue
outer cove
#

You should share what you're trying

#

Both the configuration and the result

shut meadow
#

wow. you've got to be kidding me

#

I often used "quick-restart" in devtools as...

#

that sounded like the intended way to reload said yaml files.

#
  • certainly used full HAOS restarts once in a while
#

now I finally see an actual scrape as well as multiscrape test

#

result

#
  • after performing a full HAOS restart in devtools gui
#

thank you for time and input/support eitherway 😉

#

extremely misleading. guess that "loads NEW yaml confuguration etc..." is meant extremely literally then. is that really the only way to update config.yaml script content and edits?