Good news!! I have now published a beta 2.0 release that features a sensor for each selector in your configuration. Finally you can get rid of all those template sensors in your configuration.
It is now also fully async which improves the overall performance of home assistant.
I’m looking for some testers (select ‘show beta’ in hacs) and will publish a final release after my upcoming holiday when no important issues are reported.
I’m very interested @drogfild but won’t have time to look into it in the coming 2 weeks.
I’m afraid it will be a major job for you to merge this with my latest changes, as they are almost a full rewrite. Hope you will enjoy those new features though.
Is it maybe possible for you to prepare a sample configuration for your change, that logs in into this forum?
Just would like to understand a bit more about the (im)possibilities of your new feature.
Secondly, quick query - after rebooting I see this event in the HA logs;
Logger: custom_components.multiscrape.sensor
Source: custom_components/multiscrape/sensor.py:245
Integration: multiscrape
First occurred: 15:39:23 (3 occurrences)
Last logged: 15:39:36
Sensor State was unable to extract data from HTML
I’m guessing this is probably the website I’m scraping applying some sort of rate control? - Is there any way to know from the logs if this is the case?
I’ve got 6 scraping sensors setup to one site where each sensor has 5 selectors so I wouldn’t be surprised if they weren’t liking that.
Appreciate this is probably more of a question for the original scrape component too
You can add scan_interval to reduce the scrapes (default is 30s)
Also, I think it only does 1 HTTP request per sensor and does the multiple fields separately
This Home Assistant custom component can scrape multiple fields (using CSS selectors) from a single HTTP request (the existing scrape sensor can scrape a single field only).
Thanks, I already had the scan_interval set to hourly (3600). I think it just craps out after a reboot because it does all of them simultaneously.
I might try adjusting the intervals to be sequential instead of asynchronous per scraping sensor - they’ll still conflict and crap out at each reboot, but if they sort themselves out as they refresh at individual intervals (5-10-15 minutes, etc) then that might be fine.
Ignore all that, turns out the stock website sub catagorises 3 of the 6 pages I’m scraping with a different tag for the same field - no idea why, seems to be fund related but that’s why.
Thanks @danieldotnl for this component, I’ve been attempting to use the modified version by @drogfild to scrape tank telemetry data from the LPG supplier, but I’m having real issues getting it past the login page.
The site I’m trying to scrape from is https://my.flogas.co.uk/ - I have a valid login, but using
doesn’t appear to work… I enabled the commented out debug lines in sensor.py and it seems that it just returns the same login page after ‘prelogin’ finishes…
Am I missing something ?
Great component, thanks for that!
I am having trouble using a dynamic select. I want to use something like:
select: >
{% set wn = now().isocalendar()[1] %}
{% set wd = now().weekday() %}
tr[data-weeknumber="{{ wn }}"][data-dayofweek="{{ wd }}"] td:nth-child(2)
But I guess because the select is only a string, it does not support templates. Do you know if something like that is possible or could be made possible?
Support for templates would be a nice feature! I’ll try to find time to look into it.
I also still want to publish the latest pre-release as an official release.
Hi all! Sorry for not being able to update my code lately. I try to find time for this project also.
@swifty For me your config seems valid. Can you test is it possible to login to that page without javascript with your browser? Am I able to create account to that site?
I just released the latest pre-release as an official release and created a new pre-release which supports templates in the select! @Roemer: Please give it a try!
Sorry for the late reply, it was a busy weekend!
I think the site probably needs javascript but got it going in the end.
I use node-red for all my automations so I used a selenium docker container controlled by node-red to scrape the information I needed from the site.
Latest Multi Scape component is working fine for me. It’s logging-in (username/password) and scrape multiple values which are available as attributes on the sensor.
My question is: Is it possible to get the value of ‘totaal:’ as Entity State value? (current Entity State is none)
Hi @majkers! Good question and thanks for giving an example. After @BrianHanifin commit that “prelogin” script also looks for attribute name, id, class or action. So in your case you should be able to use it’s class
preloginform: 'form-horizontal'
or even it’s action
preloginform: '/login'
Unfortunately my script isn’t updated with latest multiscrape improvements and is based on quite old version of it. I haven’t yet got my head around async requests yet
Hi,
I’m trying to get exchange rates as-of-today from national bank link, but seems i don’t write proper syntax.
After someone can illuminate me, then i will want to get with a single request exchage rates for 4 currencies. (tried openexchange, but for free api the result is only for usd and i want base currency to be “ron”
Thank you
That’s weird. Haven’t experienced that error myself. Have you been able to verify if you get that error from the first page load or is it after login attempt?
Most probably doesn’t affect this problem, but I have beta version of my fork new version. It’s quite up to date with original. You can find it from dev branch. Config should be identical.