npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-red-contrib-volkswagen-we

v0.0.5

Published

Simple Node-RED nodes for interacting with Volkswagen We.

Downloads

29

Readme

node-red-contrib-volkswagen-we

Simple Node-RED nodes for interacting with Volkswagen We.

Node we-connect-login

Node that logs in to the WE Connect Portal and outputs properties needed for subsequent calls for information or actions.

Outputs

After successful login to VW We Connect, the 'we-connect-login' node sets a few outputs.

msg.vw_base_url: The base URL as string, to be used when calling for data/actions.

"https://www.portal.volkswagen-we.com/portal/delegate/dashboard/[MY_VIN_NUMBER]"

msg.headers: Headers set during login, should be used in HTTP calls for data/actions. Can be directly feed in to standard 'http request' node.

{
  "Accept":"application/json, text/plain, */*",
  "Content-Type":"application/json;charset=UTF-8",
  "User-Agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0",
  "Referer":"https://www.portal.volkswagen-we.com/portal/delegate/dashboard/[MY_VIN_NUMBER]",
  "X-CSRF-Token":"[SOME_CSRF]",
  ...
}

msg.cookies: Cookies set during login, should be used in HTTP calls for data/actions. Can be directly feed in to standard 'http request' node.

{
  "JSESSIONID":{
    "key":"JSESSIONID",
    "value":"BB86626BEE0D744FEC7851065158E065.blue-1",
    "domain":"www.portal.volkswagen-we.com",
    ...
  },
  "COOKIE_SUPPORT":{
    "key":"COOKIE_SUPPORT",
    "value":"true",
    "expires":"2021-01-06T09:56:05.000Z",
    "domain":"www.portal.volkswagen-we.com",
    ...
  },
  ...
}

msg.we_connect: A JSON object containing all of the above.

{
  "headers":{
    ...
  },
  "cookies":{
    ...
  },
  "url":"THE_BASE_URL"
}

Credits

Credits should go to wez3 for his volkswagen-carnet-client scripts. The Volkswagen communication for these nodes are heavily based on that implementation.

Buy me a coffee

Find it useful? Please consider buying me or other contributors a coffee.