Fritzbox mit Grafana visualisieren [Version 2022]
-
Moin,
warum bist Du nicht nach dem offiziellen Installations Doku vorgegangen fritzinfluxdb?
Benutzt DuinfluxDB V. 1.8oderinfluxDB V.2.x?
Welche Version setzt Du vonfritzinfluxdbein (Aktuell ist 1.2.1)
IstinfluxDBauch der korrekte Name der Datenbank, Zeig mal die zufitzinfluxdbpassende Konfiguration/opt/fritzinfluxdb/fritzinfluxdb.ini
!!!Achtung!!! da können User und Passwort im Klartext stehenInstallations Beispiel für Ubuntu, sieh obigen link
sudo apt-get install python3-virtualenv cd /opt git clone https://github.com/bb-Ricardo/fritzinfluxdb.git cd fritzinfluxdb virtualenv -p python3 .venv . .venv/bin/activate pip3 install -r requirements.txtmodify your configuration and test it ./fritzinfluxdb.pyWenn Du das ganze über
systemdstartest, was sagt dir# systemctl status fritzinfluxdb.serviceBei mir sieht das so aus:
[dp20eic@loki fritzinfluxdb]$ systemctl status fritzinfluxdb.service * fritzinfluxdb.service - Fritz to InfluxDB daemon Loaded: loaded (/usr/lib/systemd/system/fritzinfluxdb.service; enabled; preset: disabled) Active: active (running) since Wed 2023-02-01 17:11:39 CET; 3min 5s ago Main PID: 187969 (python) Tasks: 1 (limit: 38366) Memory: 34.4M CGroup: /system.slice/fritzinfluxdb.service `-187969 /opt/fritzinfluxdb/.venv/bin/python /opt/fritzinfluxdb/fritzinfluxdb.py -d Feb 01 17:11:40 loki fritzinfluxdb[187969]: INFO: Connection to InfluxDB 2.5.1 established and bucket is present Feb 01 17:11:45 loki fritzinfluxdb[187969]: INFO: Unknown FritzBox link type 'Ethernet'. Please report this link type as issue to the gi> Feb 01 17:11:45 loki fritzinfluxdb[187969]: INFO: Successfully established FritzBox TR-069 session Feb 01 17:11:46 loki fritzinfluxdb[187969]: INFO: Successfully established FritzBox Lua session Feb 01 17:11:46 loki fritzinfluxdb[187969]: INFO: Successfully connected to FritzBox '192.168.178.1' (fritz.box) Model: FRITZ!Box 7590 (> Feb 01 17:11:46 loki fritzinfluxdb[187969]: /opt/fritzinfluxdb/fritzinfluxdb.py:141: DeprecationWarning: There is no current event loop Feb 01 17:11:46 loki fritzinfluxdb[187969]: loop = asyncio.get_event_loop() Feb 01 17:11:46 loki fritzinfluxdb[187969]: INFO: Starting main loop Feb 01 17:11:48 loki fritzinfluxdb[187969]: INFO: Service 'DSL Info (Fritz!OS 7.29 - latest)' not applicable for this FritzBox Model Lin> Feb 01 17:11:48 loki fritzinfluxdb[187969]: INFO: Service 'Cable Info (Fritz!OS 7.29 - latest)' not applicable for this FritzBox Model L> [dp20eic@loki fritzinfluxdb]$Die original Dashboards liegen, wenn Du alles richtig gemacht hast unter den jeweiligen Ordnern für
influx1/influx2[dp20eic@loki ~]$ ls -la /opt/fritzinfluxdb/grafana/ total 555 drwxr-xr-x 4 root root 6 Jan 25 14:00 . drwxr-xr-x 7 root root 18 Jan 25 14:03 .. -rw-r--r-- 1 root root 356744 Jan 25 14:00 grafana_dashboard.png -rw-r--r-- 1 root root 164338 Jan 25 14:00 grafana_home-automation_dashboard.png drwxr-xr-x 2 root root 5 Jan 25 14:00 influx1_dashboards drwxr-xr-x 2 root root 6 Jan 25 14:00 influx2_dashboards!!!Achtung!!!
fritzinfluxdb fürinfluxDb V. 1.8wird vom Developer nicht mehr weiter entwickelt.VG
Bernd -
@iobrojb sagte in Fritzbox mit Grafana visualisieren [Version 2022]:
Leider zeigt Grafana keine Werte an, obwohl ich die vorhandene influxdb zugewiesen habe
Sind denn auch Daten in der Datenbank?
Ich hatte das wie weiter oben geschrieben, per upnp Adapter laufen, der die Daten holte und die query's im Dashboard entsprechend angepasst.
Nutze das allerdings seit rund 3 Jahren nicht mehr
-
@dp20eic
hi, ist ein alter Thread aber ich versuch es trotzdem.Ich habe jetzt schon Proxmox LXC Container mit Debian 11 + 12, Ubuntu 22.04 + 23.04 versucht das Teil ans Laufen zu bringen.
Auch mit nem Docker auf dem Synology NAS hab ich es versucht. Was soll ich sagen? Es klappt einfach nicht. Kann das an meiner Fritte liegen. Das ist die 7590 AX. Wäre super, wenn mir jemand noch n Tipp geben könnte. Hier die Logs dazu.(.venv) stefan@helper:/opt/fritzinfluxdb$ ./fritzinfluxdb.py 2023-10-31 18:15:40,918 - INFO: Starting fritzinfluxdb v1.2.1 (2023-01-26) 2023-10-31 18:15:40,918 - INFO: Done reading config files 2023-10-31 18:15:40,938 - INFO: Successfully parsed config 2023-10-31 18:15:40,940 - INFO: Connection to InfluxDB 2 established 2023-10-31 18:15:46,412 - INFO: Successfully established FritzBox TR-069 session 2023-10-31 18:15:47,135 - INFO: Successfully established FritzBox Lua session 2023-10-31 18:15:47,136 - INFO: Successfully connected to FritzBox '192.168.178.1' (fritz.box) Model: FRITZ!Box 7590 AX (DSL) - FW: 7. 57 2023-10-31 18:15:47,136 - INFO: Starting main loop 2023-10-31 18:15:59,125 - INFO: Service 'Cable Info (Fritz!OS 7.29 - latest)' not applicable for this FritzBox Model Link type 'DSL' 2023-10-31 18:16:00,134 - ERROR: Unable to convert FritzBox Lua value '0-673710080' for 'ha_alert' to '<class 'int'>': invalid literal for int() with base 10: '0-673710080' 2023-10-31 18:16:00,134 - ERROR: Unable to convert FritzBox Lua value '0-1865154560' for 'ha_alert' to '<class 'int'>': invalid litera l for int() with base 10: '0-1865154560' 2023-10-31 18:16:24,525 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:16:30,738 - ERROR: Unable to convert FritzBox Lua value '0-673710080' for 'ha_alert' to '<class 'int'>': invalid literal for int() with base 10: '0-673710080' 2023-10-31 18:16:30,738 - ERROR: Unable to convert FritzBox Lua value '0-1865154560' for 'ha_alert' to '<class 'int'>': invalid litera l for int() with base 10: '0-1865154560' 2023-10-31 18:16:30,767 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:16:35,802 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:16:40,870 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:16:45,920 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:16:50,991 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:16:56,016 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:17:02,085 - ERROR: Unable to convert FritzBox Lua value '0-673710080' for 'ha_alert' to '<class 'int'>': invalid literal for int() with base 10: '0-673710080' 2023-10-31 18:17:02,085 - ERROR: Unable to convert FritzBox Lua value '0-1865154560' for 'ha_alert' to '<class 'int'>': invalid litera l for int() with base 10: '0-1865154560' 2023-10-31 18:17:03,083 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:17:08,623 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:17:14,134 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:17:19,203 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:17:24,889 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:17:30,976 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:17:33,338 - ERROR: Unable to convert FritzBox Lua value '0-673710080' for 'ha_alert' to '<class 'int'>': invalid literal for int() with base 10: '0-673710080' 2023-10-31 18:17:33,339 - ERROR: Unable to convert FritzBox Lua value '0-1865154560' for 'ha_alert' to '<class 'int'>': invalid litera l for int() with base 10: '0-1865154560' 2023-10-31 18:17:36,381 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:17:41,420 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:17:46,463 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:17:51,571 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:17:56,971 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:18:02,262 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:18:05,602 - ERROR: Unable to convert FritzBox Lua value '0-673710080' for 'ha_alert' to '<class 'int'>': invalid literal for int() with base 10: '0-673710080' 2023-10-31 18:18:05,602 - ERROR: Unable to convert FritzBox Lua value '0-1865154560' for 'ha_alert' to '<class 'int'>': invalid litera l for int() with base 10: '0-1865154560' 2023-10-31 18:18:07,437 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:18:17,150 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:18:22,474 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:18:29,000 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:18:35,006 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:18:36,383 - ERROR: Unable to convert FritzBox Lua value '0-673710080' for 'ha_alert' to '<class 'int'>': invalid literal for int() with base 10: '0-673710080' 2023-10-31 18:18:36,383 - ERROR: Unable to convert FritzBox Lua value '0-1865154560' for 'ha_alert' to '<class 'int'>': invalid litera l for int() with base 10: '0-1865154560' 2023-10-31 18:18:40,422 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:18:45,471 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:18:51,073 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 2023-10-31 18:18:56,581 - ERROR: Failed to write to InfluxDB '192.168.178.139': 422: failure writing points to database: partial write : field type conflict: input field "ha_alert" on measurement "fritzbox" is type string, already exists as type integer dropped=2 ^C2023-10-31 18:19:01,953 - INFO: Received exit signal SIGINT... 2023-10-31 18:19:01,954 - INFO: Cancelling 4 outstanding tasks 2023-10-31 18:19:01,955 - INFO: Closed FritzBox TR-069 connection 2023-10-31 18:19:01,955 - INFO: Closed FritzBox Lua connection 2023-10-31 18:19:01,955 - INFO: Closed InfluxDB session 2023-10-31 18:19:01,955 - INFO: Successfully shutdown fritzinfluxdb (.venv) stefan@helper:/opt/fritzinfluxdb$Die Datenbank wird kurz mit Daten gefüttert, die ich auch mit Grafana darstellen sehe, aber nach ca. einer Minute sind die Daten wieder weg, N/A.
-
@maxtor62 sagte in Fritzbox mit Grafana visualisieren [Version 2022]:
Es klappt einfach nicht.
Moin,
wie ist die FritzBox eingerichtet, welchen User nutzt Du zum Login?
Die Einrichtung im LX Container hast Du nach Vorgabe wie auf der Github Seite gemacht, also auchfritzconnectionund alle Python Module installiert?Zeig mal die
fritzinfluxdb.iniaber nimm vorher den User und das Passwort raus, oder x es ausVG
Bernd -
@dp20eic
hi sorry für meine Ungeduld. Hab halt schon so viel probiert.
Auf der Fritte hab ich extra ein User eingerichtet den ich dafür nehme. Hat alle Rechte.
Die Einrichtung habe ich jedes Mal genau so wie Du oder auf Github beschrieben, gemacht.
Fritzconnection und alle Python Module installiert.Hier die fritzinfluxdb.ini
[influxdb] # requires a hostname or IP which points to your InfluxDB instance hostname = 192.168.178.139 # define the port your InfluxDB instance is listening on port = 8086 # weather TLS encryption is enabled or disabled #tls_enabled = false # set this to 'true' to enforces TLS certificate validation #verify_tls = false # set a measurement name which is used to write the data to InfluxDB # If this is changed from the default then it also has to be changed # from the default value during the Grafana dashboard installation measurement_name = fritzbox # The amount of days the data should be stored in InfluxDB. # Older data will be deleted. # Attention: THIS IS ONLY CONFIGURED ON NEW DB/BUCKET CREATION! data_retention_days = 365 # define which InfluxDB version you are using version = 2 ##### InfluxDB version 1.x options # username and password to use to write data to InfluxDB username = password = # defines the InfluxDB database to write the data to # if the credentials permit to create databases then this # will be created automatically database = ##### InfluxDB version 2.x options # requires an InfluxDB API token with permissions to write to the desired bucket token = RRoG5NJBBUqnql1OKaHuxo3d2xqz0YpA-2AOO-fviu1Ft5mpafJizebVkpiQdGxwdtQvDv3AUJvXWLMreSQ1NA== # a valid InfluxDB organisation needs to be defined which is used during login organisation = home # defines the InfluxDB bucket to write the data to # if the credentials permit to create buckets then this # will be created automatically bucket = fritzbox ### ### [fritzbox] ### ### Controls the parameters for connecting to your InfluxDB instance. ### [fritzbox] # changes the default FritzBox IP hostname = 192.168.178.1 # username and password to connect to the FritzBox username = XXXX password = XXXX # Define the port the FritzBox is listening on # change to 49443 if you use ssl port = 49000 # weather TLS encryption is enabled or disabled (will set port to 49443 if port is undefined) #tls_enabled = false # set this to 'true' to enforces TLS certificate validation (only affects Lua sessions) #verify_tls = false # defines the InfluxDB measurement tag which is used # to tag data from this FritzBox #box_tag = fritz.box # Define the FritzBox time zone. Used to convert dates/times from FritzBox to correct UTC Timestamp timezone = Europe/Berlin # the maximum of time in seconds which a connection to the FritzBox is allowed to take connect_timeout = 30 # interval to request data from FritzBox in seconds # the value CAN'T be lower then 10 seconds request_interval = 30 # EOFDanke und Grüße
-
@maxtor62 sagte in Fritzbox mit Grafana visualisieren [Version 2022]:
Hier die fritzinfluxdb.ini
Moin,
also da sehe ich erst einmal keine Klinke.
Ich habe mal nach dem im Log aufgeführten Fehlerha_alertim Source auf Github gesucht, das kommt wohl aus dem Bereichhomeauto.py, jetzt kann ich damit aber auch nicht mehr anfangen, ob das jetzt an der FritzBox liegt, oder ob die Version 7.57 da für die AX eine Macke hat oder ob Du da vielleicht Geräte inSamrt Homeeingerichtet hast und deswegen der Fehler kommt.Warte einfach mal ab, was
bb-Ricardozu dem Fehler sagt.VG
Bernd -
@dp20eic
ok, danke für Deine Mühe. Im SmatHome hab ich nur Fritz Geräte über DECT eingerichtet, außer die drei Rollladen Motoren. Die sind von BoxControl, was auch über DECT läuft. Da sollte die Fritte ja kein Problem haben.
Ich werde mich in Geduld üben.Grüße
Stefan -
@maxtor62 sagte in Fritzbox mit Grafana visualisieren [Version 2022]:
ok, danke für Deine Mühe. Im SmatHome hab ich nur Fritz Geräte über DECT eingerichtet, außer die drei Rollladen Motoren. Die sind von BoxControl, was auch über DECT läuft. Da sollte die Fritte ja kein Problem haben.
Moin,
na dann kann es ja doch sein, dass da etwas nicht korrekt eingerichtet oder installiert ist. Du solltest mal gleich dein
issuseauf Github mit allen Informationen erweitern, damitbb-Ricardonicht erst noch nachfragen muss, verzögert dann ja nur zusätzlich.VG
Bernd -
@dp20eic
es ist unglaublich.
FritzBox boot tut gut.
Jetzt funktioniert alles.
Danke Dir noch mal.
Grüße
Stefan -
@maxtor62 sagte in Fritzbox mit Grafana visualisieren [Version 2022]:
Danke Dir noch mal.
Moin,
bidde schön, ist aber nicht meine Verdienst, Du kannst Dich bei
bb-Ricardobedanken.Und ja, mach mal, tut ein Boot gut
VG
Bernd -
@crunchip Hallo hab mal mitgelesen, bei der Anleitung die Du empfohlen hast, scheitere ich schon bei sudo pip install fritzcollectd mit folgender Meldung:
error: externally-managed-environment × This environment is externally managed ╰─> To install Python packages system-wide, try apt install python3-xyz, where xyz is the package you are trying to install. If you wish to install a non-Debian-packaged Python package, create a virtual environment using python3 -m venv path/to/venv. Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make sure you have python3-full installed. For more information visit http://rptl.io/venv note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages. hint: See PEP 668 for the detailed specification.Hast du ne Ahnung was ich tun muss?
Michael -
@michihorn hast du das befolgt?
https://forum.iobroker.net/post/793557 -
@crunchip Ja habe ich, selbst mit "neu" aufgesetzter Maschine klappt es nicht
habe es jetzt mal so versucht:pip install fritzcollectd --break-system-packagesIst durch gelaufen, brachte am Ende aber folgende Meldung:
note: This error originates from a subprocess, and is likely not a problem with pip. error: legacy-install-failure × Encountered error while trying to install package. ╰─> lxml note: This is an issue with the package mentioned above, not pip. hint: See above for output from the failure.EDIT: So hat es geklappt:
Quelle
Eine TOP Anleitung zur Installation der Fritzbox Visualisierung findet man unter:
AnleitungKeine Panik die Anleitung trägt den Titel "Fritz!Box Monitoring mit Raspberry Pi Zero W" funktioniert aber auch top bei neueren Versionen. Kleiner Tip, sollte mal die Installation von collectd schiefgehen, kann die Installation komplett mit "sudo apt-get purge --auto-remove collectd" gelöscht werden.
-
@michihorn kann dir da aktuell nicht weiterhelfen, hab das schon lange nicht mehr laufen.
