[Bug]: SB6190 parser error

[Winesnob]

Integration Version

3.10.2

Home Assistant Version

2025.12.4

Modem Model

Arris SB6190

Modem Model Selection in Config

Manually selected my specific model

Bug Description

CAble modem status shows 'parser error'
Can see latency values, but no other data from modem status page.
Modem status page is accessible via web browser.

Expected Behavior

All values should display and update in HA.

Steps to Reproduce

Load the integration and choose SB6190

Relevant Log Output

Configuration

Installation Method

HACS

Diagnostics Download

config_entry-cable_modem_monitor-01KD60XS438MTGCVC1ERGHRF40.json

Additional Context

No response

Pre-submission Checklist

• I have searched for similar issues and found none
• I have reviewed the troubleshooting guide
• I have provided all requested information
• I have removed any sensitive information (passwords, IP addresses if private)

[sfennell]

I attempted to reproduce the issue with my SB6190 and I'm not seeing any problems. I did notice your diag shows credentials are used, tested with that, even though my modem doesn't require credentials and I'm still not getting the Parse errors as you and the status page is parsed.

[Winesnob]

Not sure if this provides any additional insight:

Standard Specification Compliant	ARRIS DOCSIS 3.0 Cable Modem / Retail
Hardware Version	3
Software Version	9.1.103AA72

[kwschulz]

Thanks to both of you for digging into this. This might be our first case of the same modem model behaving differently across firmware versions, so I want to get enough data to understand what's happening and build something that handles this cleanly going forward.

Where We're At

@Winesnob, thanks for sharing your firmware version (9.1.103AA72).

@sfennell, thanks for the original SB6190 contribution and for jumping in to help troubleshoot. A HAR capture from your modem would give us your firmware version plus the HTML structure that's working.

When the SB6190 parser was contributed (PR #22), our fixture data was light with just one HTML file. Fixture data is used to run tests against real modem HTML, catch regressions, and (in v3.12) enable mock modem logic for development. Without complete fixtures, we're flying a bit blind when issues like this come up.

What Would Help

I need fixture data from both modems so I can compare the structure.

The integration has an HTML capture feature, but recently we found a gap in how it discovers pages - that's getting patched in v3.12. So for now, a HAR capture is the most reliable way to get everything we need in one shot:

👉 HAR Capture Instructions

Individual page saves can work, but there's more risk of inconsistencies or accidentally including PII.

Next Steps

Once I can compare both, I'll update the parser to handle both variants and set up proper fixture coverage. Targeting v3.12.0 (first week of January) for the fix.

Thanks for helping build the modem database - getting this right now means we'll have a solid template for handling firmware variants as more pop up.

[Winesnob]

192.168.100.1.har.gz

[kwschulz]

Thanks for the quick turnaround on the HAR capture. I tested the parser against your HTML and it works - parsed 32 downstream and 4 upstream channels correctly.

The HTML structure matches our existing fixture exactly, so this isn't a firmware variant issue. Something else caused the 0 channels in your original diagnostics.

A few things I noticed that might help narrow this down:

1. Credentials configured - The SB6190 doesn't require authentication, but your diagnostics show credentials were entered. Could you try without them?

2. High ping latency - Your diagnostics show 418ms ping to the modem, which is unusually high for a local device. Is the modem directly connected to your network, or behind another router/gateway?

v3.11.0 releases tomorrow. Once it's available, could you try a clean reinstall?

1. Update to v3.11.0
2. Go to the modem device → "Cleanup Entities"
3. Remove and re-add the integration (leave username/password blank)
4. Let it run for one poll cycle

If you still see "parser_issue" with 0 channels, grab fresh diagnostics with HTML capture:

1. Go to your modem device page
2. Click "Capture HTML" button, wait for confirmation
3. Click ⋮ → Download diagnostics
4. Attach the JSON file here

That will show me what Home Assistant is actually receiving - the HAR showed what your browser sees, but we need to see what the integration sees.

[Winesnob]

I tried to remove modem login credentials, however am not able to remove the password or set a null password. This may be a function of the different firmware version.

Latency looks like a one-off as typically much lower (40-50ms). Modem is connected to the main router, which has a single MESH node (ethernet backhual) where HAOS (QNAP virtualized) is connected by ethernet.

Latest diagnostic file attached.

config_entry-cable_modem_monitor-01KDRVD5M8MXH8Z76RBW93JKVK.json