-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FritzBox Cable - Channel Information / Modulation #100
Comments
Hi, This could be added. I would need the output of the json response. If you use the browser dev tools you should be able to retrieve them. Also the params which are used to query this data. |
Hi, nice and thanks for the fast reply :) I have a litte JS at the moment to extract the upload modulation, if that helps you. Also added the JSON. Let me know if u need anything else :) Thanks |
well, exactly what I needed! how familiar are you with python? You could add the data to request here: https://github.com/bb-Ricardo/fritzinfluxdb/blob/main/fritzinfluxdb/classes/fritzbox/service_definitions/connection_info.py |
That's a good start. I probably have aome time next week to look into it. Which values would be good to monitor? Or just all of them and add them to a dashboard? |
Hi @leex279, I added the parsing of the data to the "next-release" branch. Can you check out this branch and see if the parsing of the data works? If it works then only the addition to the system dashboard would be needed. |
Hi @bb-Ricardo, yeah, mega cool. Vielen Dank :) Excactly what I need :) |
Sorry for not working on this. It is currently blocked by this issue #114. I need to find a good way forward with influxDB as I don't like to repeat everything once again. Any ideas from your side? |
As I see now there are no information about the channels/modulation indexed. Would be nice to add this too.
Its very useful if you have problems with bad internet quality and can see what is changing and provide information to your provider (currently have this problem).
The text was updated successfully, but these errors were encountered: