App 2.19.0: EVHardware updated from upstream (malys/EVHardware e4e1158)

Three-way merge from b595ccb, the commit Fatih copied, to upstream's
current state; Fatih's vendor reads (tyres, mileage, charge status,
SWI69) stay. LICENSE.md records the base for the next update.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QLJfZQZeAKAwSqViTmLzki
This commit is contained in:
2026-10-19 09:44:00 +02:00
co-authored by Claude Opus 5.5
parent c6e6b3e88e
commit f0f4f57fee
71 changed files with 4646 additions and 191 deletions
+8
View File
@@ -25,6 +25,14 @@ software. `LICENSE` names all of them; keep every line.
[`EVHardware/LICENSE.md`](EVHardware/LICENSE.md). Commercial use is not permitted, and its
`Required Notice: Copyright (c) 2026 EVHardware contributors` must go with any copy.
It is a copy, not a submodule: [malys/EVHardware](https://github.com/malys/EVHardware) at
`e4e1158` (2026-10-18, after 1.18.0), merged on 2026-10-19 with the changes this fork carries on
top. Those are Fatih's reads the car needs and upstream does not have — the vendor tyre-pressure
ids `0x21401553`–`56`, the vendor mileage `0x21401566` for the odometer, the charging status
from `0x2140F409`, SoC, range, power, pack voltage and current on SWI69 as on SWI68, and SWI69
speed already in km/h — plus translated comments. To take upstream again, merge three ways with
`e4e1158` as the base.
The car app links EVHardware into its APK, so the **built app** may only be used and passed on
non-commercially, whatever the MIT parts would allow on their own. The server, the Kubernetes
manifests and the docs do not contain EVHardware and are plain MIT.