search

fetzerch / fritzcollectd

A collectd plugin for monitoring AVM FRITZ!Box routers
MIT License
130 stars 30 forks source link

Status stays on disconect after Box reboot #55

Open LeoEckert opened 3 years ago

LeoEckert commented 3 years ago

Hi guys, I know that it is getting a bit quite here but I would appreciate if anyone could help me. My issue is that my Graphana DB shows still disconnected after reboot of fritzbox while I am actually connected. My database and colledtd is running on raspberry pi 4b

Here is what I have tried: Reboot pi systemctl restart collectd systemctl restart influxdb /bin/systemctl daemon-reload

So for some reason it looks like I receive data now. Bildschirmfoto von 2021-03-18 17-08-34

I would apreciate if someone has an idea.

LeoEckert commented 3 years ago

For some reasons it works now. I rebooted the Fritzbox and the pi again. Than I did

sudo systemctl restart collectd sudo systemctl restart influxdb

I still dont get temp values but as far as I understand is that only available for dect Devices and not the Fritzbox.

framps commented 1 year ago

I faced the same issue. The connect takes some time (for me > 6 seconds) and unfortunately there is no retry loop. I created a PR and you can download the fixed __init__.py from my fork.

Jan 28 23:53:22 raspberrypi-bullseye-docker-64 collectd[547]: fritzcollectd: Connecting to FRITZ Box ...
Jan 28 23:53:22 raspberrypi-bullseye-docker-64 collectd[547]: fritzcollectd: Retrying in 3 seconds ...
Jan 28 23:53:25 raspberrypi-bullseye-docker-64 collectd[547]: fritzcollectd: Connecting to FRITZ Box ...
Jan 28 23:53:25 raspberrypi-bullseye-docker-64 collectd[547]: fritzcollectd: Retrying in 3 seconds ...
Jan 28 23:53:28 raspberrypi-bullseye-docker-64 collectd[547]: fritzcollectd: Connecting to FRITZ Box ...
Jan 28 23:53:33 raspberrypi-bullseye-docker-64 collectd[547]: Initialization complete, entering read-loop.