Skip to content

Instantly share code, notes, and snippets.

View heumn's full-sized avatar

Nikolai Heum heumn

View GitHub Profile
@heumn
heumn / driveaway-illustration.html
Created April 25, 2026 09:22
Drive-away detection illustration for enode/api#11388
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Drive-Away Detection Change</title>
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500&family=JetBrains+Mono:wght@400;500&display=swap" rel="stylesheet">
<style>
@heumn
heumn / enode_production_access_consensus.md
Last active August 27, 2025 08:41
Enode Production Access for Personal/Home Assistant Use - Support Consensus Analysis

Enode Production Access for Personal/Home Assistant Use - Support Consensus

Overview

Based on analysis of 50+ historical support tickets from 2023-2025, there is a clear pattern of personal users and hobbyists requesting production access for their own vehicles to integrate with Home Assistant. Production access requires manual approval from Enode support staff.

Key Statistics

  • Volume: ~15-20% of production access requests are for personal/hobbyist use
  • Primary Brands: Xpeng (35%), BYD (10%), Tesla (15%), Others (40%)
  • Common Use Case: Home Assistant integration (80% of personal requests)
  • Resolution Pattern: Manual approval required (100% of cases)