[Bug]: Arris S33v2 crashing when monitor enabled

[mmiller7]

Integration Version

3.12.1

Home Assistant Version

2026.2.1

Modem Model

Arris S33v2

Modem Model Selection in Config

Manually selected my specific model

Bug Description

When the monitor is enabled, the modem crashes/reboots every day/days (resulting in several minutes of outage when the modem reboots). Slowing the polling interval makes it work for longer, but it still crashes.

Unsure if its related, but I also notice the modem logs show "new login" every time the integration polls. It seems like it may not be keeping the cookie and is re-authenticating a new session every polling.

Expected Behavior

I expect it not to crash/reboot the modem frequently

Steps to Reproduce

Set up integration
Enable polling every 2-15 minutes
Wait ~1-2 days

Relevant Log Output

Configuration

URL https://192.168.100.1
Update interval (tried ranging from 120 second to 900 second)

Installation Method

HACS

Diagnostics Download

No response

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)

[kwschulz]

Thanks for the report. I've been investigating and here's my theory on what's happening.

The S33 uses HNAP/SOAP authentication with a challenge-response handshake (HMAC-MD5). Looking at the S33's HAR capture and the Login.js code from the modem's firmware, I can see it has built-in anti-brute-force protection — after too many consecutive failed login attempts, it returns a REBOOT response that forces the device to restart. This matches your symptoms exactly: crashes every 1-2 days, with faster crashes at shorter poll intervals (more failed attempts per hour).

Why logins might be failing every poll:

1. v3.12 auth handling — v3.12 used an auth strategy discovery layer that was fragile and has since been removed in v3.13. It may not have been persisting the HNAP session correctly between polls, forcing a full re-authentication each cycle.

2. S33v2 hardware revision — I've confirmed that the S33v3 uses SHA256 for HMAC instead of the S33's MD5. If the S33v2 also changed the HMAC algorithm, every login attempt from the integration would fail silently, accumulating toward the modem's reboot threshold.

Immediate recommendation: Please upgrade to v3.13.0-beta.11 via HACS (Redownload → "Need a different version?"). This version has overhauled auth handling. If the issue is the v3.12 auth layer, this should resolve it.

If it still crashes on v3.13, the likely cause is an HMAC algorithm mismatch. To confirm, I'd need:

• A HAR capture from your S33v2 using har-capture — this will show us which HMAC algorithm your hardware revision uses. Please use an incognito/private browser window so the login flow is captured.
• HA logs with debug logging enabled for cable_modem_monitor
• A diagnostics download from the integration
• Your modem's firmware version (visible on the modem's status page)

Could you also confirm — did you select "Arris/CommScope S33" as the modem model in the integration config?

[mmiller7]

I'll give this a shot! And yes, I had to manually set Arris/CommScope S33 because "auto" did not work. Firmware version I'm on is TB01.03.001.10_012022_212.S3

I've installed 3.13.0 release (from yesterday) and will try to remember to follow up here in a couple days to see if it is resolved.

[mmiller7]

I am curious, is it normal this shows a new login every time it polls? I would have thought it should keep the same session cookie and be able to keep refreshing until it expires similar to what the web-browser does natively.

I've not had time to try and reverse-engineer the login process for the S33 to BASH scripts but on my old 8200 modem I was scraping it with CURL and able to keep the same login cookie until the modem returned a new login-screen again

[kwschulz]

That's an interesting observation. While some modems only allow a single active session — and for those, the integration is configured to log out after each poll so the user isn't locked out of the web UI — the S33 is not one of those modems. The integration should be holding onto the session cookie and reusing it across polls, which is exactly what you'd expect.

The fact that you're seeing a new login every poll suggests the session isn't persisting between cycles. That lines up with the theory from my previous comment — if the HMAC algorithm on the S33v2 differs from the S33, the modem may be rejecting each session almost immediately, forcing re-authentication on every poll.

Two things that would help us narrow this down:

1. Check your HA logs — they should show timestamps for when the integration is attempting to log into the modem, which will confirm whether it's re-authenticating every cycle.
2. Enable debug logging to capture the full auth flow. Add this to your configuration.yaml and restart HA:

logger:
  logs:
    custom_components.cable_modem_monitor: debug

If it does crash again, the debug logs leading up to the crash would be very valuable.

[mmiller7]

Crashed again this morning. Was working solid for 7 days with the integration disabled, crashed in about 12 hours after enabling.

I may need some help how to capture that har-caprure, I was unable to make it run last night due to errors about missing components at runtime. I opened a ticket on their GitHub about that.

I'll try and add the HA configuration info tonight and look at logs. In the meantime I was able to get the diagnostic page from the integration at least to upload maybe is useful.

config_entry-cable_modem_monitor-01KJE766NJJDGHP29FPM789SWX.json

EDIT: I've just this evening updated the integration to 3.13.1 and set the logging in the configuration.yaml as suggested, I presume it will crash again tomorrow and then may have additional answers to share

[mmiller7]

Here's a sample of the HA logfile with debug turned on showing while things are working nicely this evening, for a reference point - I don't fully understand but it is seeming to log in every time (running 3.13.1 now):

Expand block to show logs

2026-02-27 19:33:50.418 INFO (MainThread) [custom_components.cable_modem_monitor] Cable Modem Monitor version 3.13.1 is starting
2026-02-27 19:33:50.418 DEBUG (SyncWorker_9) [custom_components.cable_modem_monitor.core.parser_registry] Attempting to get parser by name: Arris/CommScope S33
2026-02-27 19:33:50.441 DEBUG (SyncWorker_9) [custom_components.cable_modem_monitor.core.parser_registry] Loaded modem index with 19 entries (19 in name lookup)
2026-02-27 19:33:50.441 DEBUG (SyncWorker_9) [custom_components.cable_modem_monitor.core.parser_registry] Direct loading parser module: custom_components.cable_modem_monitor.modems.arris.s33.parser
2026-02-27 19:33:50.475 DEBUG (SyncWorker_9) [custom_components.cable_modem_monitor.modem_config.loader] Loaded modem index with 19 entries
2026-02-27 19:33:50.477 DEBUG (SyncWorker_9) [custom_components.cable_modem_monitor.modem_config.loader] Loading modem config from /config/custom_components/cable_modem_monitor/modems/arris/s33/modem.yaml
2026-02-27 19:33:50.494 DEBUG (SyncWorker_9) [custom_components.cable_modem_monitor.core.parser_registry] Direct loaded parser: Arris/CommScope S33
2026-02-27 19:33:50.494 DEBUG (SyncWorker_9) [custom_components.cable_modem_monitor.core.parser_registry] Direct loaded parser 'Arris/CommScope S33'
2026-02-27 19:33:50.546 INFO (MainThread) [custom_components.cable_modem_monitor] Loaded parser: Arris/CommScope S33
2026-02-27 19:33:50.626 DEBUG (MainThread) [custom_components.cable_modem_monitor] Using DataOrchestrator for known modem (modem.yaml source of truth)
2026-02-27 19:33:50.626 DEBUG (MainThread) [custom_components.cable_modem_monitor.core.data_orchestrator] Using cached protocol https from working URL: https://192.168.100.1
2026-02-27 19:33:50.626 DEBUG (MainThread) [custom_components.cable_modem_monitor.core.data_orchestrator] SSL certificate verification disabled (common for cable modems with self-signed certificates)
2026-02-27 19:33:50.626 DEBUG (MainThread) [custom_components.cable_modem_monitor.core.data_orchestrator] Scraper initialized with auth strategy: hnap_session, pre-fetched HTML: no
2026-02-27 19:33:50.663 DEBUG (MainThread) [custom_components.cable_modem_monitor.core.health_monitor] Health check: responsive (ping=True, http=True)
2026-02-27 19:33:50.663 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.data_orchestrator] Session has no cookies - will need to authenticate
2026-02-27 19:33:50.663 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.data_orchestrator] Pre-authenticating with strategy hnap_session before data fetch
2026-02-27 19:33:50.663 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.data_orchestrator] Using auth handler with strategy: hnap_session
2026-02-27 19:33:50.663 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.auth.handler] Authenticating with strategy: hnap_session
2026-02-27 19:33:50.667 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.auth.strategies.hnap_json] HNAP JSON auth: endpoint=/HNAP1/, namespace=http://purenetworks.com/HNAP1/
2026-02-27 19:33:50.667 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login attempt: URL=https://192.168.100.1/HNAP1/, Username=admin
2026-02-27 19:33:50.667 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] HNAP challenge request payload: {"Login":{"Action":"request","Username":"admin","LoginPassword":"","Captcha":"","PrivateLogin":"LoginPassword"}}
2026-02-27 19:33:50.779 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP challenge received: Challenge=ir/Z/HGc..., PublicKey=CKH4KRSe...
2026-02-27 19:33:50.779 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP computed credentials, sending login request
2026-02-27 19:33:50.779 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] HNAP login request payload: {"Login":{"Action":"login","Username":"admin","LoginPassword":"[REDACTED]","Captcha":"","PrivateLogin":"LoginPassword"}}
2026-02-27 19:33:50.829 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login response: status=200, response_length=45 bytes
2026-02-27 19:33:50.829 INFO (SyncWorker_6) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login successful! LoginResult=OK
2026-02-27 19:33:50.829 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.auth.strategies.hnap_json] HNAP JSON authentication successful
2026-02-27 19:33:50.829 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.data_orchestrator] Using HTML from pre-authentication (45 bytes)
2026-02-27 19:33:50.829 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.modem_config.adapter] get_url_token_config_for_loader: url_token not in auth.types (available: ['hnap'])
2026-02-27 19:33:50.829 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.loaders.factory] ResourceLoaderFactory: paradigm=hnap, parser_format=json
2026-02-27 19:33:50.829 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.loaders.factory] ResourceLoaderFactory: Creating HNAPLoader
2026-02-27 19:33:50.829 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.data_orchestrator] Created HNAPLoader for Arris/CommScope S33
2026-02-27 19:33:50.829 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.loaders.hnap] HNAPLoader: Calling HNAP actions: ['GetCustomerStatusDownstreamChannelInfo', 'GetCustomerStatusUpstreamChannelInfo', 'GetCustomerStatusStartupSequence', 'GetCustomerStatusConnectionInfo', 'GetArrisDeviceStatus']
2026-02-27 19:33:50.829 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP GetMultipleHNAPs request: actions=['GetCustomerStatusDownstreamChannelInfo', 'GetCustomerStatusUpstreamChannelInfo', 'GetCustomerStatusStartupSequence', 'GetCustomerStatusConnectionInfo', 'GetArrisDeviceStatus'], request_size=219 bytes
2026-02-27 19:33:55.682 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP GetMultipleHNAPs response: status=200, response_size=2774 bytes
2026-02-27 19:33:55.682 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.loaders.hnap] HNAPLoader: Got response with 6 keys
2026-02-27 19:33:55.682 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.data_orchestrator] Fetched 8 resources: ['hnap_response', 'GetCustomerStatusDownstreamChannelInfoResponse', 'GetCustomerStatusUpstreamChannelInfoResponse', 'GetCustomerStatusStartupSequenceResponse', 'GetCustomerStatusConnectionInfoResponse']
2026-02-27 19:33:55.682 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.core.data_orchestrator] Fetched 9 resources via loader
2026-02-27 19:33:55.682 DEBUG (SyncWorker_6) [custom_components.cable_modem_monitor.modems.arris.s33.parser] S33: Parsing pre-fetched HNAP response data
2026-02-27 19:33:55.683 INFO (SyncWorker_6) [custom_components.cable_modem_monitor.modems.arris.s33.parser] S33: Successfully parsed HNAP data (downstream: 26 channels, upstream: 5 channels)
2026-02-27 19:33:55.770 DEBUG (MainThread) [custom_components.cable_modem_monitor] Finished fetching Cable Modem 192.168.100.1 data in 5.130 seconds (success: True)
2026-02-27 19:33:55.770 DEBUG (MainThread) [custom_components.cable_modem_monitor.entity_migration] Skipping entity migration for DOCSIS 3.1 modem (only 3.0 is auto-migratable)
2026-02-27 19:33:55.812 DEBUG (MainThread) [custom_components.cable_modem_monitor.sensor] async_setup_entry called for 01KJE766NJJDGHP29FPM789SWX
2026-02-27 19:33:55.820 DEBUG (MainThread) [custom_components.cable_modem_monitor.sensor] Creating entities for 5 upstream channels
2026-02-27 19:33:55.821 INFO (MainThread) [custom_components.cable_modem_monitor.sensor] Created 149 total sensor entities
2026-02-27 19:33:56.523 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.parser_registry] Attempting to get parser by name: Arris/CommScope S33
2026-02-27 19:33:56.523 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.parser_registry] Found parser 'Arris/CommScope S33' in name cache
2026-02-27 19:33:56.523 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.modem_config.capabilities] Restart supported for Arris/CommScope S33
2026-02-27 19:33:56.785 DEBUG (MainThread) [custom_components.cable_modem_monitor] Updated device registry: name=Cable Modem, manufacturer=Arris/CommScope, model=S33v2
2026-02-27 19:34:56.114 DEBUG (MainThread) [custom_components.cable_modem_monitor.core.health_monitor] Health check: responsive (ping=True, http=True)
2026-02-27 19:34:56.115 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Session has cookies: ['Secure', 'uid', 'PrivateKey']
2026-02-27 19:34:56.115 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Pre-authenticating with strategy hnap_session before data fetch
2026-02-27 19:34:56.115 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Using auth handler with strategy: hnap_session
2026-02-27 19:34:56.115 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.handler] Authenticating with strategy: hnap_session
2026-02-27 19:34:56.115 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.strategies.hnap_json] HNAP JSON auth: endpoint=/HNAP1/, namespace=http://purenetworks.com/HNAP1/
2026-02-27 19:34:56.115 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login attempt: URL=https://192.168.100.1/HNAP1/, Username=admin
2026-02-27 19:34:56.115 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] HNAP challenge request payload: {"Login":{"Action":"request","Username":"admin","LoginPassword":"","Captcha":"","PrivateLogin":"LoginPassword"}}
2026-02-27 19:34:56.256 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP challenge received: Challenge=KawgZS31..., PublicKey=kAx4L7cP...
2026-02-27 19:34:56.256 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP computed credentials, sending login request
2026-02-27 19:34:56.256 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] HNAP login request payload: {"Login":{"Action":"login","Username":"admin","LoginPassword":"[REDACTED]","Captcha":"","PrivateLogin":"LoginPassword"}}
2026-02-27 19:34:56.316 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login response: status=200, response_length=45 bytes
2026-02-27 19:34:56.316 INFO (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login successful! LoginResult=OK
2026-02-27 19:34:56.316 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.strategies.hnap_json] HNAP JSON authentication successful
2026-02-27 19:34:56.316 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Using HTML from pre-authentication (45 bytes)
2026-02-27 19:34:56.317 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.modem_config.adapter] get_url_token_config_for_loader: url_token not in auth.types (available: ['hnap'])
2026-02-27 19:34:56.317 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.loaders.factory] ResourceLoaderFactory: paradigm=hnap, parser_format=json
2026-02-27 19:34:56.317 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.loaders.factory] ResourceLoaderFactory: Creating HNAPLoader
2026-02-27 19:34:56.317 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Created HNAPLoader for Arris/CommScope S33
2026-02-27 19:34:56.317 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.loaders.hnap] HNAPLoader: Calling HNAP actions: ['GetCustomerStatusDownstreamChannelInfo', 'GetCustomerStatusUpstreamChannelInfo', 'GetCustomerStatusStartupSequence', 'GetCustomerStatusConnectionInfo', 'GetArrisDeviceStatus']
2026-02-27 19:34:56.317 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP GetMultipleHNAPs request: actions=['GetCustomerStatusDownstreamChannelInfo', 'GetCustomerStatusUpstreamChannelInfo', 'GetCustomerStatusStartupSequence', 'GetCustomerStatusConnectionInfo', 'GetArrisDeviceStatus'], request_size=219 bytes
2026-02-27 19:35:00.362 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP GetMultipleHNAPs response: status=200, response_size=2774 bytes
2026-02-27 19:35:00.362 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.loaders.hnap] HNAPLoader: Got response with 6 keys
2026-02-27 19:35:00.362 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Fetched 8 resources: ['hnap_response', 'GetCustomerStatusDownstreamChannelInfoResponse', 'GetCustomerStatusUpstreamChannelInfoResponse', 'GetCustomerStatusStartupSequenceResponse', 'GetCustomerStatusConnectionInfoResponse']
2026-02-27 19:35:00.363 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Fetched 9 resources via loader
2026-02-27 19:35:00.363 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.modems.arris.s33.parser] S33: Parsing pre-fetched HNAP response data
2026-02-27 19:35:00.363 INFO (SyncWorker_0) [custom_components.cable_modem_monitor.modems.arris.s33.parser] S33: Successfully parsed HNAP data (downstream: 26 channels, upstream: 5 channels)
2026-02-27 19:35:00.364 DEBUG (MainThread) [custom_components.cable_modem_monitor] Finished fetching Cable Modem 192.168.100.1 data in 4.788 seconds (success: True)
2026-02-27 19:36:00.595 DEBUG (MainThread) [custom_components.cable_modem_monitor.core.health_monitor] Health check: responsive (ping=True, http=True)
2026-02-27 19:36:00.595 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.data_orchestrator] Session has cookies: ['Secure', 'uid', 'PrivateKey']
2026-02-27 19:36:00.595 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.data_orchestrator] Pre-authenticating with strategy hnap_session before data fetch
2026-02-27 19:36:00.595 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.data_orchestrator] Using auth handler with strategy: hnap_session
2026-02-27 19:36:00.596 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.auth.handler] Authenticating with strategy: hnap_session
2026-02-27 19:36:00.596 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.auth.strategies.hnap_json] HNAP JSON auth: endpoint=/HNAP1/, namespace=http://purenetworks.com/HNAP1/
2026-02-27 19:36:00.596 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login attempt: URL=https://192.168.100.1/HNAP1/, Username=admin
2026-02-27 19:36:00.596 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] HNAP challenge request payload: {"Login":{"Action":"request","Username":"admin","LoginPassword":"","Captcha":"","PrivateLogin":"LoginPassword"}}
2026-02-27 19:36:00.854 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP challenge received: Challenge=VPgVsBUy..., PublicKey=Y5tdC1bE...
2026-02-27 19:36:00.854 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP computed credentials, sending login request
2026-02-27 19:36:00.854 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] HNAP login request payload: {"Login":{"Action":"login","Username":"admin","LoginPassword":"[REDACTED]","Captcha":"","PrivateLogin":"LoginPassword"}}
2026-02-27 19:36:00.897 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login response: status=200, response_length=45 bytes
2026-02-27 19:36:00.897 INFO (SyncWorker_7) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login successful! LoginResult=OK
2026-02-27 19:36:00.897 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.auth.strategies.hnap_json] HNAP JSON authentication successful
2026-02-27 19:36:00.897 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.data_orchestrator] Using HTML from pre-authentication (45 bytes)
2026-02-27 19:36:00.898 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.modem_config.adapter] get_url_token_config_for_loader: url_token not in auth.types (available: ['hnap'])
2026-02-27 19:36:00.898 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.loaders.factory] ResourceLoaderFactory: paradigm=hnap, parser_format=json
2026-02-27 19:36:00.898 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.loaders.factory] ResourceLoaderFactory: Creating HNAPLoader
2026-02-27 19:36:00.898 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.data_orchestrator] Created HNAPLoader for Arris/CommScope S33
2026-02-27 19:36:00.898 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.loaders.hnap] HNAPLoader: Calling HNAP actions: ['GetCustomerStatusDownstreamChannelInfo', 'GetCustomerStatusUpstreamChannelInfo', 'GetCustomerStatusStartupSequence', 'GetCustomerStatusConnectionInfo', 'GetArrisDeviceStatus']
2026-02-27 19:36:00.898 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP GetMultipleHNAPs request: actions=['GetCustomerStatusDownstreamChannelInfo', 'GetCustomerStatusUpstreamChannelInfo', 'GetCustomerStatusStartupSequence', 'GetCustomerStatusConnectionInfo', 'GetArrisDeviceStatus'], request_size=219 bytes
2026-02-27 19:36:06.754 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP GetMultipleHNAPs response: status=200, response_size=2774 bytes
2026-02-27 19:36:06.754 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.loaders.hnap] HNAPLoader: Got response with 6 keys
2026-02-27 19:36:06.754 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.data_orchestrator] Fetched 8 resources: ['hnap_response', 'GetCustomerStatusDownstreamChannelInfoResponse', 'GetCustomerStatusUpstreamChannelInfoResponse', 'GetCustomerStatusStartupSequenceResponse', 'GetCustomerStatusConnectionInfoResponse']
2026-02-27 19:36:06.754 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.core.data_orchestrator] Fetched 9 resources via loader
2026-02-27 19:36:06.754 DEBUG (SyncWorker_7) [custom_components.cable_modem_monitor.modems.arris.s33.parser] S33: Parsing pre-fetched HNAP response data
2026-02-27 19:36:06.754 INFO (SyncWorker_7) [custom_components.cable_modem_monitor.modems.arris.s33.parser] S33: Successfully parsed HNAP data (downstream: 26 channels, upstream: 5 channels)
2026-02-27 19:36:06.803 DEBUG (MainThread) [custom_components.cable_modem_monitor] Finished fetching Cable Modem 192.168.100.1 data in 6.228 seconds (success: True)
2026-02-27 19:37:06.583 DEBUG (MainThread) [custom_components.cable_modem_monitor.core.health_monitor] Health check: responsive (ping=True, http=True)
2026-02-27 19:37:06.583 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.data_orchestrator] Session has cookies: ['Secure', 'uid', 'PrivateKey']
2026-02-27 19:37:06.583 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.data_orchestrator] Pre-authenticating with strategy hnap_session before data fetch
2026-02-27 19:37:06.584 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.data_orchestrator] Using auth handler with strategy: hnap_session
2026-02-27 19:37:06.584 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.auth.handler] Authenticating with strategy: hnap_session
2026-02-27 19:37:06.584 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.auth.strategies.hnap_json] HNAP JSON auth: endpoint=/HNAP1/, namespace=http://purenetworks.com/HNAP1/
2026-02-27 19:37:06.584 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login attempt: URL=https://192.168.100.1/HNAP1/, Username=admin
2026-02-27 19:37:06.584 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] HNAP challenge request payload: {"Login":{"Action":"request","Username":"admin","LoginPassword":"","Captcha":"","PrivateLogin":"LoginPassword"}}
2026-02-27 19:37:06.731 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP challenge received: Challenge=Al8vZW6o..., PublicKey=gnpa2ZwO...
2026-02-27 19:37:06.731 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP computed credentials, sending login request
2026-02-27 19:37:06.731 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] HNAP login request payload: {"Login":{"Action":"login","Username":"admin","LoginPassword":"[REDACTED]","Captcha":"","PrivateLogin":"LoginPassword"}}
2026-02-27 19:37:06.814 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login response: status=200, response_length=45 bytes
2026-02-27 19:37:06.814 INFO (SyncWorker_1) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login successful! LoginResult=OK
2026-02-27 19:37:06.814 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.auth.strategies.hnap_json] HNAP JSON authentication successful
2026-02-27 19:37:06.814 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.data_orchestrator] Using HTML from pre-authentication (45 bytes)
2026-02-27 19:37:06.814 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.modem_config.adapter] get_url_token_config_for_loader: url_token not in auth.types (available: ['hnap'])
2026-02-27 19:37:06.814 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.loaders.factory] ResourceLoaderFactory: paradigm=hnap, parser_format=json
2026-02-27 19:37:06.814 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.loaders.factory] ResourceLoaderFactory: Creating HNAPLoader
2026-02-27 19:37:06.814 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.data_orchestrator] Created HNAPLoader for Arris/CommScope S33
2026-02-27 19:37:06.814 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.loaders.hnap] HNAPLoader: Calling HNAP actions: ['GetCustomerStatusDownstreamChannelInfo', 'GetCustomerStatusUpstreamChannelInfo', 'GetCustomerStatusStartupSequence', 'GetCustomerStatusConnectionInfo', 'GetArrisDeviceStatus']
2026-02-27 19:37:06.814 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP GetMultipleHNAPs request: actions=['GetCustomerStatusDownstreamChannelInfo', 'GetCustomerStatusUpstreamChannelInfo', 'GetCustomerStatusStartupSequence', 'GetCustomerStatusConnectionInfo', 'GetArrisDeviceStatus'], request_size=219 bytes
2026-02-27 19:37:12.209 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP GetMultipleHNAPs response: status=200, response_size=2774 bytes
2026-02-27 19:37:12.209 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.loaders.hnap] HNAPLoader: Got response with 6 keys
2026-02-27 19:37:12.209 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.data_orchestrator] Fetched 8 resources: ['hnap_response', 'GetCustomerStatusDownstreamChannelInfoResponse', 'GetCustomerStatusUpstreamChannelInfoResponse', 'GetCustomerStatusStartupSequenceResponse', 'GetCustomerStatusConnectionInfoResponse']
2026-02-27 19:37:12.209 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.core.data_orchestrator] Fetched 9 resources via loader
2026-02-27 19:37:12.209 DEBUG (SyncWorker_1) [custom_components.cable_modem_monitor.modems.arris.s33.parser] S33: Parsing pre-fetched HNAP response data
2026-02-27 19:37:12.209 INFO (SyncWorker_1) [custom_components.cable_modem_monitor.modems.arris.s33.parser] S33: Successfully parsed HNAP data (downstream: 26 channels, upstream: 5 channels)
2026-02-27 19:37:12.260 DEBUG (MainThread) [custom_components.cable_modem_monitor] Finished fetching Cable Modem 192.168.100.1 data in 5.684 seconds (success: True)
2026-02-27 19:38:11.582 DEBUG (MainThread) [custom_components.cable_modem_monitor.core.health_monitor] Health check: responsive (ping=True, http=True)
2026-02-27 19:38:11.583 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Session has cookies: ['Secure', 'uid', 'PrivateKey']
2026-02-27 19:38:11.583 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Pre-authenticating with strategy hnap_session before data fetch
2026-02-27 19:38:11.583 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Using auth handler with strategy: hnap_session
2026-02-27 19:38:11.583 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.handler] Authenticating with strategy: hnap_session
2026-02-27 19:38:11.583 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.strategies.hnap_json] HNAP JSON auth: endpoint=/HNAP1/, namespace=http://purenetworks.com/HNAP1/
2026-02-27 19:38:11.583 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login attempt: URL=https://192.168.100.1/HNAP1/, Username=admin
2026-02-27 19:38:11.583 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] HNAP challenge request payload: {"Login":{"Action":"request","Username":"admin","LoginPassword":"","Captcha":"","PrivateLogin":"LoginPassword"}}
2026-02-27 19:38:11.694 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP challenge received: Challenge=10FNaIwf..., PublicKey=cf/UisZx...
2026-02-27 19:38:11.695 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP computed credentials, sending login request
2026-02-27 19:38:11.695 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] HNAP login request payload: {"Login":{"Action":"login","Username":"admin","LoginPassword":"[REDACTED]","Captcha":"","PrivateLogin":"LoginPassword"}}
2026-02-27 19:38:11.750 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login response: status=200, response_length=45 bytes
2026-02-27 19:38:11.750 INFO (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login successful! LoginResult=OK
2026-02-27 19:38:11.751 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.strategies.hnap_json] HNAP JSON authentication successful
2026-02-27 19:38:11.751 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Using HTML from pre-authentication (45 bytes)
2026-02-27 19:38:11.751 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.modem_config.adapter] get_url_token_config_for_loader: url_token not in auth.types (available: ['hnap'])
2026-02-27 19:38:11.751 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.loaders.factory] ResourceLoaderFactory: paradigm=hnap, parser_format=json
2026-02-27 19:38:11.751 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.loaders.factory] ResourceLoaderFactory: Creating HNAPLoader
2026-02-27 19:38:11.751 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Created HNAPLoader for Arris/CommScope S33
2026-02-27 19:38:11.751 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.loaders.hnap] HNAPLoader: Calling HNAP actions: ['GetCustomerStatusDownstreamChannelInfo', 'GetCustomerStatusUpstreamChannelInfo', 'GetCustomerStatusStartupSequence', 'GetCustomerStatusConnectionInfo', 'GetArrisDeviceStatus']
2026-02-27 19:38:11.751 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP GetMultipleHNAPs request: actions=['GetCustomerStatusDownstreamChannelInfo', 'GetCustomerStatusUpstreamChannelInfo', 'GetCustomerStatusStartupSequence', 'GetCustomerStatusConnectionInfo', 'GetArrisDeviceStatus'], request_size=219 bytes
2026-02-27 19:38:16.059 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP GetMultipleHNAPs response: status=200, response_size=2774 bytes
2026-02-27 19:38:16.059 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.loaders.hnap] HNAPLoader: Got response with 6 keys
2026-02-27 19:38:16.059 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Fetched 8 resources: ['hnap_response', 'GetCustomerStatusDownstreamChannelInfoResponse', 'GetCustomerStatusUpstreamChannelInfoResponse', 'GetCustomerStatusStartupSequenceResponse', 'GetCustomerStatusConnectionInfoResponse']
2026-02-27 19:38:16.059 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Fetched 9 resources via loader
2026-02-27 19:38:16.059 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.modems.arris.s33.parser] S33: Parsing pre-fetched HNAP response data
2026-02-27 19:38:16.059 INFO (SyncWorker_0) [custom_components.cable_modem_monitor.modems.arris.s33.parser] S33: Successfully parsed HNAP data (downstream: 26 channels, upstream: 5 channels)
2026-02-27 19:38:16.106 DEBUG (MainThread) [custom_components.cable_modem_monitor] Finished fetching Cable Modem 192.168.100.1 data in 4.530 seconds (success: True)
2026-02-27 19:39:15.637 DEBUG (MainThread) [custom_components.cable_modem_monitor.core.health_monitor] Health check: responsive (ping=True, http=True)
2026-02-27 19:39:15.637 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Session has cookies: ['Secure', 'uid', 'PrivateKey']
2026-02-27 19:39:15.637 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Pre-authenticating with strategy hnap_session before data fetch
2026-02-27 19:39:15.638 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Using auth handler with strategy: hnap_session
2026-02-27 19:39:15.638 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.handler] Authenticating with strategy: hnap_session
2026-02-27 19:39:15.638 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.strategies.hnap_json] HNAP JSON auth: endpoint=/HNAP1/, namespace=http://purenetworks.com/HNAP1/
2026-02-27 19:39:15.638 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login attempt: URL=https://192.168.100.1/HNAP1/, Username=admin
2026-02-27 19:39:15.638 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] HNAP challenge request payload: {"Login":{"Action":"request","Username":"admin","LoginPassword":"","Captcha":"","PrivateLogin":"LoginPassword"}}
2026-02-27 19:39:15.710 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP challenge received: Challenge=EDU+oSuR..., PublicKey=qxZH8AKe...
2026-02-27 19:39:15.710 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP computed credentials, sending login request
2026-02-27 19:39:15.710 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] HNAP login request payload: {"Login":{"Action":"login","Username":"admin","LoginPassword":"[REDACTED]","Captcha":"","PrivateLogin":"LoginPassword"}}
2026-02-27 19:39:15.755 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login response: status=200, response_length=45 bytes
2026-02-27 19:39:15.755 INFO (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP login successful! LoginResult=OK
2026-02-27 19:39:15.755 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.strategies.hnap_json] HNAP JSON authentication successful
2026-02-27 19:39:15.756 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Using HTML from pre-authentication (45 bytes)
2026-02-27 19:39:15.756 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.modem_config.adapter] get_url_token_config_for_loader: url_token not in auth.types (available: ['hnap'])
2026-02-27 19:39:15.756 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.loaders.factory] ResourceLoaderFactory: paradigm=hnap, parser_format=json
2026-02-27 19:39:15.756 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.loaders.factory] ResourceLoaderFactory: Creating HNAPLoader
2026-02-27 19:39:15.756 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Created HNAPLoader for Arris/CommScope S33
2026-02-27 19:39:15.756 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.loaders.hnap] HNAPLoader: Calling HNAP actions: ['GetCustomerStatusDownstreamChannelInfo', 'GetCustomerStatusUpstreamChannelInfo', 'GetCustomerStatusStartupSequence', 'GetCustomerStatusConnectionInfo', 'GetArrisDeviceStatus']
2026-02-27 19:39:15.756 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP GetMultipleHNAPs request: actions=['GetCustomerStatusDownstreamChannelInfo', 'GetCustomerStatusUpstreamChannelInfo', 'GetCustomerStatusStartupSequence', 'GetCustomerStatusConnectionInfo', 'GetArrisDeviceStatus'], request_size=219 bytes
2026-02-27 19:39:19.884 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.auth.hnap.json_builder] JSON HNAP GetMultipleHNAPs response: status=200, response_size=2774 bytes
2026-02-27 19:39:19.884 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.loaders.hnap] HNAPLoader: Got response with 6 keys
2026-02-27 19:39:19.884 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Fetched 8 resources: ['hnap_response', 'GetCustomerStatusDownstreamChannelInfoResponse', 'GetCustomerStatusUpstreamChannelInfoResponse', 'GetCustomerStatusStartupSequenceResponse', 'GetCustomerStatusConnectionInfoResponse']
2026-02-27 19:39:19.885 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.core.data_orchestrator] Fetched 9 resources via loader
2026-02-27 19:39:19.885 DEBUG (SyncWorker_0) [custom_components.cable_modem_monitor.modems.arris.s33.parser] S33: Parsing pre-fetched HNAP response data
2026-02-27 19:39:19.885 INFO (SyncWorker_0) [custom_components.cable_modem_monitor.modems.arris.s33.parser] S33: Successfully parsed HNAP data (downstream: 26 channels, upstream: 5 channels)
2026-02-27 19:39:19.886 DEBUG (MainThread) [custom_components.cable_modem_monitor] Finished fetching Cable Modem 192.168.100.1 data in 4.264 seconds (success: True)

[mmiller7]

Figured out how to do the har-capture of my S33-v2 with Firefox instead of that utility and then sanitized it with that har-capture github utility. Please see attached capture.

I fully expect some time tomorrow it will restart the modem again and I'll provide updated HA logs when that happens.

192.168.100.1_Archive [26-02-27 20-54-16].sanitized.har.zip

[mmiller7]

As expected the modem restarted a short time ago (9:54:51 AM offline, 9:58:59 AM online)

Here is the log data from Home Assistant logs, 60 sec polling interval, spanning 9:50AM (4 min prior to reboot) thru 10:13AM (15 min after reboot):
debug-modem-reboot.txt

Integration download-diagnostics (around 10:30 after I got done looking at the log):
config_entry-cable_modem_monitor-01KJE766NJJDGHP29FPM789SWX.json

If you need a larger chunk of log data let me know I can pull the whole night worth - I didn't want to spam with a bunch of irrelevant logs (I know I have an unrelated MQTT sensor that spams logs when a device is offline which I tried to filter that out for your convenience)

(EDIT: I believe the other SNMP, device tracker, etc sensor errors are related to when the modem went down my router reinitialized stuff restarting services as it fails over, which causes connections to be dropped for a moment during failover and fail-back to primary WAN, that is unrelated and normal)

For now I'm going to disable the integration until I hear back on additional troubleshooting guidance

[kwschulz]

Thank you for the debug logs, diagnostics, and HAR capture — all three were extremely useful.

The logs confirm every poll performs a full HNAP challenge-response login, even when a valid session already exists. At over a thousand logins/day, this is the most likely explanation for the reboots — the S33's Login.js has anti-brute-force code that can force a device restart after repeated login attempts.

v3.13.2 will reuse existing HNAP sessions instead of re-authenticating on every poll. If a session goes stale, it should detect the failure and does a single fresh login.

Also, your HAR capture validates the S33v2 uses the same HNAP/HMAC-MD5 flow and endpoints as the S33 — no parser changes needed. Added S33v2 model aliases so it'll be recognized by name.

You'll be the first live test when v3.13.2 ships.

[mmiller7]

That's great to hear! I'll be on the lookout for the updated version and give it a try!

Thank you so much!