Repository navigation
Modem PYUR FAST3896 15
PŸUR (Germany) ships a FAST3896-15 firmware with its own /api/v1 web interface. It is a separate protocol from the Sagemcom XMO /cgi/json-req firmware handled by the sagemcom driver and from the Liberty Global /rest/v1 firmware handled by the f3896lg driver. Select the PYUR entry for this firmware.
| Property | Value |
|---|---|
| Driver Key | pyur_fast3896 |
| Auth Method |
/api/v1 session with a SHA512-crypt challenge; password only (user admin) |
| DOCSIS Version | 3.1 |
| Default IP | 192.168.100.1 |
| Channels | SC-QAM + OFDM (downstream), SC-QAM (upstream) |
- Select PYUR FAST3896-15 (experimental) in the setup wizard or in Settings > Connection; search for "PYUR" in the modem list, it is grouped under Sagemcom.
- Use
http://192.168.100.1, or your modem's configured address. - Enter the modem UI password. The modem UI is password-only; the driver uses the user name
admin.
Support was developed from an examined capture of FAST3896-15_PYUR-RDK_83.2.4 and automated tests. With image sha-208d8b4, the reporter confirmed successful login and data collection, followed by nominal operation after one day.
Login uses a portable SHA512-crypt implementation checked against independent vectors. The captured frontend references a helper that was not available in the capture; the reported login provides hardware evidence for this implementation on the tested modem. Automated tests alone do not establish universal firmware compatibility.
Not individually confirmed by the reporter: reboot recovery, session expiry, channel accuracy, and the device uptime and firmware fields.
- Upstream
QAMchannels report no known modulation order, and the OFDM channel has no known profile modulation. - Counters and connection rates that the firmware does not report stay unknown instead of being shown as zero.
- Subscriber network parameters (
/docsis-info/network_parameters) are not requested, because they include subscriber addresses and are not needed.
The login flow, transport limits, and the parsing contract are described in Architecture. The test fixture used for parser tests is described in Developer Testing.
If you run this firmware, please report your results in #865.
Home | Quick Start | Configuration | API Reference | GitHub
- Quick Start
- Installation
- Windows Quick Start
- Windows Desktop Preview
- Running without Docker
- Podman Quadlet
- Configuration
- Reverse Proxy
- Example Compose Stacks
- Dashboard (Home)
- Connection Monitor
- Signal Trends
- Before/After Comparison
- Channels: Status, Timeline & Compare
- Event Log
- Smart Capture
- Gaming Quality Index
- Modulation Performance
- Cable Segment Utilization
- In-App Glossary
- Incident Journal
- Correlation Analysis
- Evidence Journey
- German TKG Compensation
- Filing a Complaint
- LLM Export
- Speedtest Tracker
- BNetzA Breitbandmessung
- ThinkBroadband BQM
- Smokeping
- Weather
- Netzbremse (Peering)
- Notifications
- Home Assistant (MQTT)
- Prometheus Metrics