[Feature]: Include sensors for binary status indicators

[sgofferj]

Feature Type

New sensor/entity

Problem Statement

As mentioned in #75 , the CGA2121 has a row of binary/check-X indicators for the provisioning status which would probably be useful to monitor so one can tell the ISPs support that's a fault is their fault and why 😄 .

Those status indicatore are on top of the Docsis status page.

Older discussion:
#75 (comment)

Proposed Solution

Create binary sensors in HA for those status indicators

Alternatives Considered

I can watch them through the modem status page but that isn't really in the spirit of this integration 😆

Modem Information (if applicable)

Technicolor CGA2121

Use Case

Showing the ISP tech support why a fault is their fault.

Additional Context

No response

Contribution

Yes, I can provide modem HTML samples

Pre-submission Checklist

• I have searched for similar feature requests and found none
• This feature aligns with the integration's purpose (cable modem monitoring)
• I have provided a clear description of the feature and its benefits

[kwschulz]

Hi Stefan! v3.14 is a ground-up rewrite — one of the reasons I did it was to eliminate the kind of regressions you hit during v3.12/v3.13. The provisioning status indicators you asked about are now supported through a dynamic field system, so any modem can pick up additional fields without code changes. I'm alpha testing now and will need your help testing the CGA2121 again once beta is ready. I'll tag you here when there's a build to try.

[kwschulz]

Hi Stefan! v3.14.0-alpha.14 is ready for your CGA2121 — ground-up rewrite, so the auth and parsing are completely new. The provisioning status indicators you asked about in #96 (DS Scanning, US Ranging, DHCP, TFTP, Registration) are in there as system_info fields.

Install via HACS Developer Tools using the feature/v3.14.0 branch — instructions here. Restart HA after installing and add the integration fresh.

I caught one thing during review: the login form sends a language_selector=en field that wasn't in the config. Already fixed for alpha.15 but it's likely optional — shouldn't stop you from authenticating. If you do hit auth failures, that's the probable cause.

Please attach the diagnostics JSON either way (Settings → Devices → Cable Modem Monitor → three dots → Download diagnostics). It shows auth state, resource timings, and parse results — useful whether things work or not.

The issues you hit in v3.11–v3.13 (auth not wired, parser getting the login page instead of data, case sensitivity on form fields) are all structurally gone in this version. Appreciate you sticking with it.

[sgofferj]

Put to my list. I'm super busy atm, though. Still can fire up some kind of tunnel for you if you wanna play with the modem directly. It's in bridge mode and wifi is off, so no critical data there.

[kwschulz]

Appreciate your help and thank you for the offer. Still trying to do this without accessing your network but I might set up a Discord channel for quicker back-and-forth if we need to debug something live. No rush on your end — whenever you get a window to install and pull diagnostics, that's the most useful next step. The alpha is stable and the branch isn't going anywhere.