u/fildline

Fieldwatch 1.1.23 just got more useful on your map. 🛰️

https://preview.redd.it/61srk8hbuxuh1.png?width=1690&format=png&auto=webp&s=421f5faa27aa2ee08cf1a5b722b95ea87719a3d2

Fieldwatch already detects drones, decodes their Remote ID, and plots the drone track and pilot location in TAK. Now it also watches your phone's own GPS for possible jamming and spoofing. When it hits, your marker in TAK gets flagged so your whole team sees it right away.

Runs on the same Android device as ATAK. Free, open source, receive-only, and fully offline. The only official release is on the GitHub releases page.

github.com/OffGridPete/Fieldwatch

I'm trying to work out the advertisement format of Goodyear's BLE tire sensors. These are the tire-mounted "intelligent tire" sensors, not the 315/433 MHz valve-stem TPMS most cars use. I couldn't find a public decode anywhere: rtl_433, Theengs/OpenMQTTGateway, Home Assistant and ESPHome projects, and GitHub code search all came up empty. If you've seen this format or have any info, I'd love to compare notes.

What the radio looks like

- BLE advertiser, LE 1M PHY, non-connectable (broadcast only), no name, no service UUIDs

- Public, stable MAC in Goodyear's OUI `7C:E1:52` (for example `7C:E1:52:02:E1:D8`, `…:03:FF:8D`, `…:04:28:96`, `…:04:44:E6`)

- Manufacturer data (AD type `0xFF`) with company ID `0x0B99` (The Goodyear Tire & Rubber Company)

- Full AD example: `11 FF 99 0B 01 05 5B CA FF 22 04 30 02 A0 DA 43 B4 01`

- The manufacturer payload is always 14 bytes (positions counted from 0):

```

pos:  0  1  2  3  4  5  6  7  8  9 10 11 12 13

01 05 TT PP xx xx 04 30 SS rr rr 43 cc 01

```

Sample payloads

```

01 05 5B CA FF 22 04 30 02 A0 DA 43 B4 01   tire A, Aug 16, parked

01 05 5C C9 FF 22 04 30 02 40 F3 43 B4 01   tire A, Aug 26, start of drive

01 05 61 C9 FF 22 04 30 03 96 F3 43 C0 01   tire A, Aug 26, ~8 min into drive

01 05 5E C8 09 32 04 30 04 38 5B 43 B7 01   tire C, Sep 28 evening

01 05 59 CA ED 34 04 30 02 0E C1 43 4B 01   different vehicle

```

Four of these sensors are always heard together (one car's set), across sightings weeks apart.

What looks solid

- Bytes 0, 1, 6, 7, 11 and 13 (`01 05 … 04 30 … 43 … 01`) never change, so they're framing or type bytes.

- Bytes 9–10 are a 16-bit little-endian sequence counter. It goes up by exactly 1 per advertisement, rolls over (`DAFF` then `DB00`), and keeps climbing across days as a lifetime counter. So there doesn't seem to be a checksum, integrity code or encryption.

- Byte 8 is a transmit mode or rate, taking values `02`, `03` and `04`. At `02` it sends about once a second, and at `03`/`04` it slows to about once every 10–60 seconds. It backs off from `02` to `03` to `04` over time while parked.

Hypotheses (not confirmed, please poke holes)

- Byte 2 may be temperature. It ranges from `58` to `64` (88–100), climbs from `5C` to `61` over an 8-minute drive, and reads higher on hot Florida afternoons. Maybe raw °F, or °C with an offset.

- Byte 12 also rises with heat and driving (`B4` to `C0`). It could be a second, finer temperature, or bytes 11–12 (`43 Bx`) could form one 16-bit value.

- Byte 3 sits at `C8` to `CA` (200–202) and drifts down slightly over weeks. It could be pressure (200 kPa is about 29 psi), but it flickers by 1 between packets and didn't rise as the tire warmed on a drive, so it might be battery or something else.

- Bytes 4–5 are constant per sensor: `09 32` on three tires of one car and on an unrelated sensor, `FF 22` on the fourth tire, and `ED 34` on another vehicle. `09 32` read big-endian is 2354, or 235.4 kPa (34.1 psi), a typical placard pressure, so this might be a target or configured pressure. `FF 22` might mean "not set."

What would help

- Any Goodyear, SightLine or TDK documentation, or a known decode for company ID `0x0B99`

- Captures from anyone with these tires, ideally with a gauge reading and a tire-temperature reading at the same moment

- Ideas on bytes 3, 4–5 and 12

Thank you.

https://preview.redd.it/bnvx9a3pw0gh1.jpg?width=4284&format=pjpg&auto=webp&s=7667e7a88d350c9709673ddd0f6191f40a32559f

I just upgraded my home setup from the UDM Pro to the Pro Max. I had this space in the wall made 25 years ago when the house was built. I haven’t kept it the neatest, but it’s constantly evolving. I’d love to find a nice rack door that I can somehow attach to the front and maybe add some lighting. It’s currently running a USG Pro Max with two 8TB drives, two 24-port PoE switches, three Access Points, a Synology DS1821+ NAS with 80TB, one AI Key, 10 cameras, two relays, a bunch of sensors, two UPS units, and a 5G backup. There’s also a legacy NVR with three remaining cameras that will soon be gone.