You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Request support for a new cable modem model
3
-
labels: ["modem support", "help wanted"]
4
-
body:
5
-
- type: markdown
6
-
attributes:
7
-
value: |
8
-
Thanks for requesting support for a new modem! Before filling out this form, please follow the [Requesting Modem Support](https://github.com/itsDNNS/docsight/wiki/Requesting-Modem-Support) guide to collect the data we need (HAR file, screenshot, firmware version).
description: Full model number (check the label on the device)
24
-
placeholder: e.g., Arris TG3442DE, Netgear CM1000
25
-
validations:
26
-
required: true
27
-
28
-
- type: input
29
-
id: firmware
30
-
attributes:
31
-
label: Firmware Version
32
-
description: Current firmware version (usually shown in the web interface)
33
-
placeholder: e.g., 01.05.063.13.EURO.PC20
34
-
validations:
35
-
required: true
36
-
37
-
- type: input
38
-
id: isp
39
-
attributes:
40
-
label: Internet Provider
41
-
description: Which ISP provides this modem?
42
-
placeholder: e.g., Vodafone Kabel, PYUR, Comcast
43
-
44
-
- type: dropdown
45
-
id: docsis
46
-
attributes:
47
-
label: DOCSIS Version
48
-
description: Which DOCSIS standard does the modem support?
49
-
options:
50
-
- DOCSIS 3.0
51
-
- DOCSIS 3.1
52
-
- Don't know
53
-
validations:
54
-
required: true
55
-
56
-
- type: input
57
-
id: web_url
58
-
attributes:
59
-
label: Modem Web Interface URL
60
-
description: What URL do you use to access the modem settings?
61
-
placeholder: e.g., http://192.168.0.1 or http://192.168.100.1
62
-
validations:
63
-
required: true
64
-
65
-
- type: dropdown
66
-
id: authentication
67
-
attributes:
68
-
label: Authentication
69
-
description: Does the web interface require login?
70
-
options:
71
-
- Yes (username + password)
72
-
- Yes (password only)
73
-
- No authentication required
74
-
validations:
75
-
required: true
76
-
77
-
- type: textarea
78
-
id: screenshot
79
-
attributes:
80
-
label: DOCSIS Status Page Screenshot
81
-
description: |
82
-
Upload a screenshot of the DOCSIS status page showing downstream/upstream channels.
83
-
Redact any sensitive information (MAC address, IP, serial number).
84
-
placeholder: Drag and drop a screenshot here
85
-
validations:
86
-
required: true
87
-
88
-
- type: textarea
89
-
id: har_file
90
-
attributes:
91
-
label: HAR File (Network Capture)
92
-
description: |
93
-
We need a HAR file to understand how your modem's web interface fetches data. Without this, we can't build a driver -- every modem and ISP firmware variant uses different API endpoints and authentication flows.
94
-
95
-
**How to capture:**
96
-
1. Open your modem's web interface in Chrome or Firefox
97
-
2. Open Developer Tools (F12) -> Network tab
98
-
3. Log in and navigate to the DOCSIS status page (the page showing downstream/upstream channels)
99
-
4. Right-click in the Network tab -> "Save all as HAR"
100
-
5. **Important:** Open the HAR file in a text editor and remove any passwords, MAC addresses, or serial numbers before uploading
101
-
6. Upload the .har file here
102
-
placeholder: Drag and drop .har file here
103
-
validations:
104
-
required: true
105
-
106
-
- type: checkboxes
107
-
id: contribution
108
-
attributes:
109
-
label: I am willing to help
110
-
description: Can you help with testing once we have a driver?
111
-
options:
112
-
- label: I can test the driver with my modem
113
-
required: false
114
-
- label: I can provide additional debug logs if needed
115
-
required: false
116
-
117
-
- type: textarea
118
-
id: additional
119
-
attributes:
120
-
label: Additional Information
121
-
description: Any other details that might help (known quirks, alternative access methods, etc.)
122
-
placeholder: This modem also supports SNMP...
2
+
description: Request support for a new cable modem model
3
+
labels: ["modem support", "help wanted"]
4
+
body:
5
+
- type: markdown
6
+
attributes:
7
+
value: |
8
+
Thanks for requesting support for a new modem! Before filling out this form, please follow the [Requesting Modem Support](https://github.com/itsDNNS/docsight/wiki/Requesting-Modem-Support) guide to
9
+
collect the data we need (HAR file, screenshot, firmware version).
10
+
11
+
For modems with login-protected web UIs, the HAR file must include the actual login exchange, not only requests made after you are already logged in.
12
+
13
+
GitHub may block direct `.har` uploads. Please upload the capture as `.har.txt` or `.zip` if needed.
description: Full model number (check the label on the device)
29
+
placeholder: e.g., Arris TG3442DE, Netgear CM1000
30
+
validations:
31
+
required: true
32
+
33
+
- type: input
34
+
id: firmware
35
+
attributes:
36
+
label: Firmware Version
37
+
description: Current firmware version (usually shown in the web interface)
38
+
placeholder: e.g., 01.05.063.13.EURO.PC20
39
+
validations:
40
+
required: true
41
+
42
+
- type: input
43
+
id: isp
44
+
attributes:
45
+
label: Internet Provider
46
+
description: Which ISP provides this modem?
47
+
placeholder: e.g., Vodafone Kabel, PYUR, Comcast
48
+
49
+
- type: dropdown
50
+
id: docsis
51
+
attributes:
52
+
label: DOCSIS Version
53
+
description: Which DOCSIS standard does the modem support?
54
+
options:
55
+
- DOCSIS 3.0
56
+
- DOCSIS 3.1
57
+
- Don't know
58
+
validations:
59
+
required: true
60
+
61
+
- type: input
62
+
id: web_url
63
+
attributes:
64
+
label: Modem Web Interface URL
65
+
description: What URL do you use to access the modem settings?
66
+
placeholder: e.g., http://192.168.0.1 or http://192.168.100.1
67
+
validations:
68
+
required: true
69
+
70
+
- type: dropdown
71
+
id: authentication
72
+
attributes:
73
+
label: Authentication
74
+
description: Does the web interface require login?
75
+
options:
76
+
- Yes (username + password)
77
+
- Yes (password only)
78
+
- No authentication required
79
+
validations:
80
+
required: true
81
+
82
+
- type: textarea
83
+
id: screenshot
84
+
attributes:
85
+
label: DOCSIS Status Page Screenshot
86
+
description: |
87
+
Upload a screenshot of the DOCSIS status page showing downstream/upstream channels.
88
+
Redact any sensitive information (MAC address, IP, serial number).
89
+
placeholder: Drag and drop a screenshot here
90
+
validations:
91
+
required: true
92
+
93
+
- type: textarea
94
+
id: har_file
95
+
attributes:
96
+
We need a HAR file to understand how your modem's web interface fetches data. Without this, we can't build a driver -- every modem and ISP firmware variant uses different API endpoints and
97
+
authentication flows.
98
+
99
+
**How to capture:**
100
+
1. Close any already-open modem web UI tabs first
101
+
2. Open Chrome or Firefox and open Developer Tools (F12) -> Network tab
102
+
3. Start recording **before** opening the modem web interface
103
+
4. Open the modem web interface and log in from a clean browser tab
104
+
5. Navigate to the DOCSIS status page (the page showing downstream/upstream channels)
105
+
6. Right-click in the Network tab -> "Save all as HAR"
106
+
7. **Important:** Verify that the HAR includes the actual login request/response flow, not only post-login data requests
107
+
8. **Important:** Open the HAR file in a text editor and remove any passwords, MAC addresses, or serial numbers before uploading
108
+
9. GitHub may reject raw `.har` uploads. If that happens, rename the file to `.har.txt` or upload it as a `.zip` archive instead
109
+
10. Upload the capture here
110
+
111
+
**Please make sure the capture includes:**
112
+
- The first request to the modem web UI
113
+
- The login request itself (if authentication is required)
114
+
- The first successful requests that load modem/channel data
115
+
placeholder: Drag and drop .har.txt or .zip file here
116
+
validations:
117
+
required: true
118
+
119
+
- type: textarea
120
+
id: session_behavior
121
+
attributes:
122
+
label: Login / Session Behavior
123
+
description: |
124
+
Describe when the problem occurs and whether browser access affects it.
125
+
- Works on first login, fails on second test
126
+
- Only fails after a poll cycle
127
+
- Fails if the modem UI is open in a browser at the same time
128
+
- Browser and DOCSight seem to kick each other out
129
+
130
+
- type: textarea
131
+
id: debug_logs
132
+
attributes:
133
+
label: Debug Logs (if login or polling fails)
134
+
description: |
135
+
If the modem requires authentication or the issue involves failed logins, session expiry, or empty data, please also attach DOCSight debug logs from the same test window as the HAR capture.
136
+
137
+
Example:
138
+
- Docker: `docker run ... -e LOG_LEVEL=DEBUG ...`
139
+
- Docker Compose: set `LOG_LEVEL=DEBUG` in the container environment
140
+
placeholder: Paste relevant debug logs here or attach a .txt file
141
+
142
+
- type: textarea
143
+
id: capture_conditions
144
+
attributes:
145
+
label: Capture Conditions
146
+
description: |
147
+
Tell us how the HAR/logs were captured so we can reason about session state correctly.
148
+
placeholder: |
149
+
Example:
150
+
- Modem was freshly rebooted
151
+
- No browser tabs to the modem UI were open
152
+
- Browser login was done while DOCSight was polling
153
+
- Captured on the first login after reboot
154
+
attributes:
155
+
label: I am willing to help
156
+
description: Can you help with testing once we have a driver?
157
+
options:
158
+
- label: I can test the driver with my modem
159
+
required: false
160
+
- label: I can provide additional debug logs if needed
161
+
required: false
162
+
163
+
- type: textarea
164
+
id: additional
165
+
attributes:
166
+
label: Additional Information
167
+
description: Any other details that might help (known quirks, alternative access methods, etc.)
0 commit comments