Newer
■
■
■
■
■
■
■
■
■
■
Older
57 lines
|
1.544kb
| 1 |
# floriandotorg/um24c |
|
| 2 | ||
| 3 |
Repository: |
|
| 4 | ||
| 5 |
- https://github.com/floriandotorg/um24c |
|
| 6 | ||
| 7 |
## Why it matters |
|
| 8 | ||
| 9 |
This appears to be a contemporary external project focused on the same family of Bluetooth USB power meters. |
|
| 10 | ||
| 11 |
It is relevant because it covers: |
|
| 12 | ||
| 13 |
- `UM24C` |
|
| 14 |
- `UM25C` |
|
| 15 |
- `UM34C` |
|
| 16 | ||
| 17 |
These overlap substantially with the devices targeted by this project. |
|
| 18 | ||
| 19 |
## Quick Notes |
|
| 20 | ||
| 21 |
From a quick inspection, the project appears to be a web UI built around Web Bluetooth and live plotting. |
|
| 22 | ||
| 23 |
Potentially useful areas: |
|
| 24 | ||
| 25 |
- model naming conventions |
|
| 26 |
- field naming choices |
|
| 27 |
- unit scaling assumptions |
|
| 28 |
- decoded status values |
|
| 29 |
- command / payload interpretation hints |
|
| 30 |
- UI ideas for live data presentation |
|
| 31 | ||
| 32 |
## Observations From Initial Review |
|
| 33 | ||
| 34 |
- The repository describes itself as a web UI for `UM24C/UM25C/UM34C` power meters. |
|
| 35 |
- It uses a JavaScript frontend rather than native iOS code. |
|
| 36 |
- It includes explicit model mappings such as: |
|
| 37 |
- `0x0963 -> UM24C` |
|
| 38 |
- `0x09c9 -> UM25C` |
|
| 39 |
- `0x0d4c -> UM34C` |
|
| 40 |
- It also includes a charging mode map with values such as `QC2`, `QC3`, `DCP1.5A`, and `SAMSUNG`. |
|
| 41 | ||
| 42 |
## Limits |
|
| 43 | ||
| 44 |
- It does not appear to target `TC-66C`. |
|
| 45 |
- It should be treated as a secondary reference, not as ground truth. |
|
| 46 |
- Any payload interpretation borrowed from it should be validated against our own code and captures. |
|
| 47 | ||
| 48 |
## Suggested Use |
|
| 49 | ||
| 50 |
Use this project mainly for: |
|
| 51 | ||
| 52 |
- terminology alignment |
|
| 53 |
- comparison of decoded fields |
|
| 54 |
- cross-checking known model identifiers |
|
| 55 |
- identifying gaps in our current understanding |
|
| 56 | ||
| 57 |
Avoid assuming protocol equivalence without validation. |