Skip to content

Verification Request: homebridge-polestar-c3 #1375

Closed

Description

@jeroendbr-web

Plugin Name

homebridge-polestar-c3

Link To GitHub Repo

https://github.com/jeroendbr-web/homebridge-polestar-c3

Plugin Icon (Optional)

No response

Verification Requirements

General

The plugin does not offer the same nor less functionality than that of any existing verified plugin.

🟢 Yes

Environment

The plugin successfully installs and does not start unless it is configured.

🟢 Yes

The plugin does not require the user to run Homebridge in a TTY or with non-standard startup parameters, even for initial configuration.

🟢 Yes

Codebase

The plugin does not contain any analytics or calls that enable you to track the user.

🟢 Yes

If the plugin needs to write files to disk (cache, keys, etc.), it stores them inside the Homebridge storage directory.

🟢 Yes

The plugin does not throw unhandled exceptions, the plugin must catch and log its own errors.

🟢 Yes

More Information

Dynamic platform plugin for Polestar 2/3/4 vehicles. It uses the same cloud backend (C3, gRPC) as the official Polestar app, via the GPL-3.0 client from the Homey Polestar app (kaohlive/Polestar), bundled unmodified in lib/polestar-c3/. There is currently no verified Polestar plugin.

  • Accessories: lock + battery/charging, climate (switch or thermostat), charger connected, door/window/tailgate sensors, optional tyre pressure/service warnings, charging override and find-my-car.
  • Settings GUI via config.schema.json. Without email/password the plugin logs an error and does not start.
  • The only file written is the login session (refresh token) in api.user.storagePath()/polestar-c3/.
  • Login failures retry with backoff; polling and command errors are caught and logged; unreachable state is reported with HapStatusError(SERVICE_COMMUNICATION_FAILURE).
  • No dependencies on homebridge/hap-nodejs at runtime; only axios and qs.
  • CI runs the smoke test on Node 22, 24 and 26 against Homebridge 2. engines: node ^22.12.0 || ^24.0.0 || ^26.0.0, homebridge ^1.8.0 || ^2.0.0.
  • Every version has a GitHub release with release notes.
  • In daily use with a Polestar 3.

Activity

  1. bwp91 commented on Nov 18, 2026

    @bwp91
    Contributor

    /check

  2. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor

    🟢 Passed Checks

    • Installation: successfully installed
    • Package JSON: homepage exists
    • Package JSON: bugs.url exists and seems a valid URL
    • Package JSON: keywords exist and contain 'homebridge-plugin'
    • Package JSON: keywords declare the supported transports ('supports-hap' and/or 'supports-matter')
    • Package JSON: 'preinstall' in scripts is not present
    • Package JSON: 'install' in scripts is not present
    • Package JSON: 'postinstall' in scripts is not present
    • Package JSON: engines.node property is compatible with Node 22
    • Package JSON: engines.node property is compatible with Node 24
    • Package JSON: engines.homebridge property is compatible with Homebridge 2.5.0
    • Package JSON: initializer function found
    • NPM Package: has not been deprecated
    • GitHub Repo: version in package.json (v0.2.2) matches NPM version (v0.2.2)
    • Config Schema JSON: exists and is valid JSON
    • Config Schema JSON: contains valid JSON Schema
    • Config Schema JSON: schema has valid type property
    • Config Schema JSON: schema has valid properties for object type
    • Config Schema JSON: contains a valid pluginAlias
    • Config Schema JSON: pluginAlias matches the platform/accessory registered in code
    • Config Schema JSON: the pluginType is set to 'platform'
    • Config Schema JSON: contains a name schema property
    • Dependencies: homebridge is not declared as a runtime/peer/bundled dependency
    • Dependencies: hap-nodejs is not declared as a runtime/peer/bundled dependency
    • Security: no known vulnerabilities in dependencies
    • Security: code patterns flagged for manual review
    • Security: no privilege escalation attempts detected
    • Runtime: homebridge installed successfully
    • Runtime: no config - homebridge should start without plugin configuration and plugin should not load
    • Runtime: platform only - plugin should start with just platform property
    • Runtime: minimal required - plugin should start with minimal required configuration
    • Runtime: full config - plugin should start with comprehensive configuration
    • Runtime: network resilience - plugin should handle network failures without crashing
    • Runtime: plugin shuts down cleanly within 12s of SIGTERM
    • Runtime: plugin restarts cleanly without port conflicts
    • GitHub Repo: repository is public
    • GitHub Repo: repository is not archived
    • GitHub Repo: issues are enabled
    • GitHub Repo: contains releases

    🔍 For Manual Review

    The following items were detected and require manual review. We understand that these items may be false positives.

    • Security: accesses environment files in lib/polestar-c3/client.js

    ℹ️ Check Details

    • These checks were run against v0.2.2 of the plugin.
    • Link to the run workflow: visit →.
    • External HTTP requests detected:
      • 📡 https://polestarid.eu.polestar.com/.well-known/openid-configuration
        Methods: GET | Count: 5 | Scenarios: full config, minimal required, network resilience
      • 📡 https://polestarid.eu.polestar.com/as/X3pLbxjxiY/resume/as/authorization.ping
        Methods: GET, POST | Count: 2 | Scenarios: minimal required
      • 📡 https://polestarid.eu.polestar.com/as/authorization.oauth2
        Methods: GET | Count: 4 | Scenarios: full config, minimal required
      • 📡 https://polestarid.eu.polestar.com/as/gAMnWXRfwb/resume/as/authorization.ping
        Methods: GET, POST | Count: 2 | Scenarios: full config

    📋 Next Steps

    All checks passed successfully, nice work! Your plugin and/or icon will now be manually reviewed by the Homebridge team.

  3. added a commit that references this issue on Nov 18, 2026
  4. added
    verifieduse when a plugin meets the criteria - adds the verified badge text
    on Nov 18, 2026
  5. github-actions commented on Nov 18, 2026

    @github-actions
    Contributor

    Congratulations! Your plugin has been verified!

    You can now add one of the Verified by Homebridge badges to your plugin's README:

    verified-by-homebridge

    [![verified-by-homebridge](https://img.shields.io/badge/_-verified-blueviolet?color=%23491F59&style=flat&logoColor=%23FFFFFF&logo=homebridge)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)
    

    verified-by-homebridge

    [![verified-by-homebridge](https://img.shields.io/badge/homebridge-verified-blueviolet?color=%23491F59&style=flat)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)
    

    verified-by-homebridge

    [![verified-by-homebridge](https://img.shields.io/badge/homebridge-verified-blueviolet?color=%23491F59&style=for-the-badge&logoColor=%23FFFFFF&logo=homebridge)](https://github.com/homebridge/homebridge/wiki/Verified-Plugins)
    

    Your plugin is now also eligible to display a ❤️ Donate button on its tile in the Homebridge UI. See https://github.com/homebridge/homebridge/wiki/Donation-Links for instructions.

    Interested in getting a @homebridge-plugins/ scope for your plugin? See our Homebridge Scoped Plugins program.

    If for any reason in the future you can no longer maintain your plugin, please consider transferring it to our Homebridge Plugins organization.

    Don't forget to join the official Homebridge Discord server, where plugin developers can get tips and advice from other developers and the Homebridge project team in the #plugin-development channel!

    As a verified plugin, you can request a channel in the Discord server to discuss your plugin with users and other developers. Just ask in the #plugin-development channel.

    Thank you for your contribution to the Homebridge community.

    • The Homebridge Team
  6. bwp91 commented on Nov 18, 2026

    @bwp91
    Contributor

    Hi @jeroendbr-web, thanks for contributing to Homebridge, and nice to see the first Polestar plugin on the list!

    Your request was missing the labels from the template, so it never reached our checks. I've added them, and everything passed.

    A few optional suggestions from reading the code, nothing that held this up:

    • The client tells Polestar's server it accepts compressed replies (grpc.js), but if one ever arrives, parseFrames throws inside the stream's end handler, where nothing catches it, and that would take Homebridge down. Asking only for uncompressed replies (identity) would close that off.
    • A few messages in client.js use console.warn rather than the Homebridge logger, so they show up without the plugin's name in front.
    • GPL-3.0 in package.json is an older licence name; GPL-3.0-only or GPL-3.0-or-later is the current form.

    If you'd like a custom icon to show for your plugin in the Homebridge UI, you can request one with the icon form.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    request-verificationverifieduse when a plugin meets the criteria - adds the verified badge text

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions