### Vehicle/setup
- 2018 Nissan Leaf ZE1 40 kWh (Netherlands)
- Ficosa 2016–2019 TCU, firmware `TCU033`
- Lebara NL prepaid SIM
- OpenCARWINGS public instance
- GatewayAPI.com binary SMS provider
- TCU Configurator v1.0.11
### Configuration
- APN data connection works
- OBS/TSP: `http://biz-tcu.viaaq.eu:80`
- TCU activation enabled
- VIN, TCU ID and SIM ID are accepted by OpenCARWINGS
### Problem
The car connects successfully and its location updates. OpenCARWINGS shows a green status and a recent “Last Connection”, so the TCU → server connection works.
However:
- “Refresh data” remains pending/spinning
- SOC, range, odometer and other EV values remain zero or blank
- GatewayAPI accepts the binary SMS requests, but every message remains `ENROUTE`
- The exported messages are one 74-byte segment and share the header `820300320402010002202030`
- Starting the car produces data usage and server connections, but no complete EV-status update
Re-adding the car did not change the result.
### Question
Does this indicate that the binary wake SMS is not reaching the TCU, or could OpenCARWINGS be receiving only a location/navigation report and failing to request or process the full ZE1 status packet?
It would also be useful if the GatewayAPI integration exposed the final delivery status instead of treating the initial HTTP 200 response as successful.
