Perhaps its me but my original multiscrape still functions I believe. I dont have any automations or whatsoever but purely for display. I still get updates about dhl packages
Normally, when you can authenticate using your saved X-AUTH-TOKEN cookie, you can still fetch the data and the form_submit function of multiscrape isnât used.
My problem was, as I just started using this integration, the initial login doesnât work so the token canât be fetched.
Your response brings me hope the X-AUTH-TOKEN doesnât expire (soon) so this solution is a good workaround until someone finds a quicker way.
@Milenco1 when I login step 1 result is I logged in without token.
how do I get the X-AUTH-TOKEN ?
Once you have logged in, can get visit the page in your browser to see the JSON data? Then the cookie is stored in your browser and need to retrieve it via Developer Tools.
See: View, add, edit, and delete cookies | Chrome DevTools | Chrome for Developers
Are you sure you are looking correctly? Maybe this helps: https://www.youtube.com/watch?v=E-j-vlDuYtA
thank you, now I managed to get the sensor but strggling with my already existing sensor in command_line.
dumb question: do you know how I get this right ?
Itâs probably a yaml/indentation error. See the docs (Command line - Home Assistant), youâll probably need to use:
# Example configuration.yaml entry
command_line:
- sensor:
command: SENSOR_COMMAND
- sensor:
command: SENSOR_COMMAND_2
Try it directly from configuration.yaml first and then include.
remove the âsensor:â from line 8
both solutions unfortunately didnât work
The command line works for me so far. Hopefully the token is for a long time :-). Thanks a lot.