Welcome to docsight Discussions!

[itsDNNS]

Welcome to DOCSight Discussions!

This is the place to connect with other users and discuss everything around DOCSight.

What is this space for?

• Support & Setup: Questions about running the Docker container, configuring your modem driver, or getting integrations to work? Ask here!
• Feature Requests: Missing support for a specific modem model or want a new metric visualized? Let us know.
• Bug Reports: Something not working as expected? Open a discussion or file an issue.
• Show & Tell: Share your dashboards, success stories in debugging ISP issues, or how DOCSight helped you.

Signal interpretation & cable issues

We built DOCSight as users who wanted to keep an eye on their own connection. We are not cable technicians and cannot reliably assess whether your signal levels justify a complaint or indicate a specific wiring problem.

If you need help interpreting your DOCSIS values (power levels, SNR, modulation changes, etc.), we recommend asking in one of these specialized communities where experienced technicians and power users can help:

• kabeluser.de (very active, German)
• Vodafone Kabelforum (German)

We are happy to help with anything DOCSight-related though!

Community Guidelines

We are all here to improve our internet connection reliability. Please keep the conversation constructive, even when discussing frustrating ISP experiences.

[le-mon]

dont know how i landed here, but in 10 min. i went from "Huh, i got errors on my modem" to "WOW, i just installed for the 1st time WSL, Docker and a fckn beautiful web tool which tells me more information about my internet connection than i never knew i would be interested in".

All without any hazzle, so smooooooth. Just a THANK YOU for your effort, i like it!

[itsDNNS]

Damn, this made my day 😄
Love that DOCSight took you from modem errors to a full WSL plus Docker setup in like 10 minutes.

Massive respect for jumping in and just doing it.

More good stuff is coming for sure.
We just need to make sure it does not evolve into an absurdly expensive homelab addiction 😅

[Tobik17]

Hello,
I am trying to connect to a CH7465 modem managed by Play (formerly UPC) in Poland. When I log in via a browser, only a password is required; I don't even know the username. Therefore, I cannot go through the DOCSIght setup, which requires full credentials. What should I do?
Best regards.

[itsDNNS]

Hey @Tobik17, welcome!

The CH7465 Connect Box is sold under different names depending on the ISP (Unitymedia, Vodafone, UPC/Play, Ziggo, etc.). The Play/UPC firmware variant only shows a password field in the browser UI, but the underlying API still accepts the same login call.

Try this:

1. In the DOCSight setup wizard, select Unitymedia Connect Box (CH7465)
2. Enter your modem IP (usually 192.168.0.1)
3. Leave the username field empty -- the Compal default is blank
4. Enter the password printed on your modem (or the one you use in the browser)
5. Hit Test Connection

If that does not work, please open an issue with your firmware version (you can find it on the modem status page) and we will look into it.

[itsDNNS]

Quick update @Tobik17: We just shipped a change that makes this smoother.

The modem type dropdown now auto-fills sensible defaults (IP, username) when you switch types. For the CH7465, the username field stays editable and you can simply leave it blank if your firmware does not require one.

Also renamed the entry to Compal CH7465 (Connect Box) so it is easier to find regardless of ISP branding.

Let us know if you run into anything!

[Tobik17]

Hi guys,

Thank you very much for your quick response and for working on the problem. I followed your instructions, but nothing worked. I still get the message: RuntimeError: Modem authentication failed. Also tried to pass the credentials via the .env file, but the result was the same. So, I will open an issue as requested.

See you!

[Tobik17]

@itsDNNS - I'm afraid it's time for the .har file.
But that's enough for today, right?
Thank you very much for your commitment.

[itsDNNS]

@itsDNNS - I'm afraid it's time for the .har file.
But that's enough for today, right?
Thank you very much for your commitment.

The build should be ready any minute now. Let's continue with your feedback in #149

[ypsilonkah]

Hi,
thank you for this really interesting project. I tried it our but faced some issues/questions with configuring it correctly. I use a Commscope TG6442VF (aka Vodafone Station) in Bridge-Mode. The router is a OpnSense machine. I am wondering what I should setup and how: IP address of the router? The modem in bridge mode has no ip, i can connect to IMHO.
Login, then are the router / OpnSense credentials?

[itsDNNS]

Hey @ypsilonkah, welcome!

The TG6442VF (Commscope/Vodafone Station) is not explicitly tested yet, but it shares the same Arris/Commscope hardware family as the TG3442DE which we do support. There is a good chance the existing Vodafone Station driver will work.

Bridge mode & network setup:

In bridge mode the modem still has a web interface, but on a dedicated management IP — typically 192.168.100.1 or 192.168.0.1 (not the OPNsense IP). Quick check: try opening one of those IPs in your browser. If you see the modem login page, that is the IP to use in DOCSight.

If you cannot reach the modem from your browser either, you first need to set up a route on your client machine (or on OPNsense for the whole LAN) into the modem management subnet. The management network (e.g. 192.168.100.0/24) is typically only visible on the OPNsense WAN interface, so:

• Add a static route on OPNsense so your LAN (and the Docker subnet where DOCSight runs) can reach the modem management network
• Or run the DOCSight container with network_mode: host
• Or add a secondary IP on the WAN interface in the modem subnet

Both your browser and the DOCSight container need to be able to reach the modem IP — so getting browser access working first is a good test before configuring DOCSight.

DOCSight setup:

1. Select Vodafone Station as modem type
2. Enter the modem management IP (not the OPNsense IP)
3. Use the modem credentials (the password printed on the modem or set via the modem web UI) — not the OPNsense login
4. Username: try admin or leave empty
5. Hit Test Connection

The driver auto-detects the hardware variant (CGA vs TG), so it will try both auth flows automatically.

If it does not work, please open an issue with:

• Your firmware version (visible on the modem status page)
• The error message from Test Connection

That way we can check if the TG6442VF needs any adjustments to the driver.

[ypsilonkah]

Thank you for the detailed write up! I will test the coming days.