Skip to content
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

Issues updating from check-mk 2.1.0 to 2.2.0 #9

Open
mdweiler4711 opened this issue Jan 25, 2024 · 5 comments
Open

Issues updating from check-mk 2.1.0 to 2.2.0 #9

mdweiler4711 opened this issue Jan 25, 2024 · 5 comments

Comments

@mdweiler4711
Copy link

I am currently in the process of upgrading check-mk from 2.1.0p38 to 2.2.0p20.
Hence I also updated the plugin from 0.5.4 to 0.5.9.

Everything worked fine before the update and I monitored two 7490 Fritzboxes with various smart devices (thermostat, switch, plug, ...).

Now after the update I am getting crashes from the check agent for the discovered services of all my smart-devices, and also upon a service update/rescan:

Invalid check parameter: Humidity: Thresholds for WARN: The datatype must be a tuple, but is list
Variable: checkgroup_parameters:fritzbox_smarthome
Parameters:

{'hkr': {},
 'humidity': {'humidity_crit': [70, 30], 'humidity_warn': [60, 40]},
 'powermeter': {},
 'present': 0,
 'switch': {},
 'temperature': {}}

I have no idea, what's going wrong here or how to tackle it.

I am using a 7490 FritzBox running FRITZ!OS:[7.57] - and the output of the check-agent does not contain any 'humidity' information.

Maybe the update just left some artifacts which need to be removed?

Thanks for any hint and advice

Manfred

@doctore74
Copy link

doctore74 commented Jan 25, 2024

Hallo Manfred,

https://thl-cmk.hopto.org/gitlab/checkmk/various/fritzbox_smarthome

Schau mal hier

Viele Grüße
Christian

@MaximilianClemens
Copy link
Owner

Hi,
can you try:
v0.5.10

@mdweiler4711
Copy link
Author

Unfortunately, only the message changes:

Invalid check parameter: Thermostat (battery settings are also here): Show Batterystate always: Invalid value, must be 'True' but is 'False'
Variable: checkgroup_parameters:fritzbox_smarthome
Parameters:

{'hkr': {'hkr_bat_always': False,
         'hkr_crit': {'hkr_bat_below': 20,
                      'hkr_diff_soll': 8,
                      'hkr_flags': [True, True, False]},
         'hkr_warn': {'hkr_bat_below': 30,
                      'hkr_diff_soll': 5,
                      'hkr_flags': [True, True, False]}},
 'humidity': {'humidity_crit': (70, 30), 'humidity_warn': (60, 40)},
 'powermeter': {},
 'present': 1,
 'switch': {},
 'temperature': {}}

If I add the fritzbox to the check rule under "Service monitoring rules > Applications, Processes & Services > Settings for Fritz!Box Smarthome Devices" - it complains about yet another issue:

Invalid check parameter: Undefined key 'switch' in the dictionary. Allowed are present, hkr, humidity.
Variable: checkgroup_parameters:fritzbox_smarthome
Parameters:

{'hkr': {},
 'humidity': {},
 'powermeter': {},
 'present': 0,
 'switch': {},
 'temperature': {}}

@mdweiler4711
Copy link
Author

Hallo Manfred,

https://thl-cmk.hopto.org/gitlab/checkmk/various/fritzbox_smarthome

Schau mal hier

Viele Grüße Christian

Hallo Christian,

ich habe versucht, mir das anzuschauen, bekomme aber leider gar keine Services erkannt und mit der Doku komme ich auch nicht weiter :-(

Manfred

@ggruber
Copy link

ggruber commented Apr 20, 2024

Hallo Max,

wie schon bei dem anderen issue geschrieben, auch ich habe Probleme mit v0.5.10 auf CMK 2.2p24
Und die Version von Christian läuft zwar, hat aber ein anderes Konzept für die Ausgabe: Jeder Sensor wird ein eigenes Gerät (~Server) im CMK mit Piggyback verfügbar gemachten Daten.
Bei kleinen Installationen mag das nett sein, aber ich wollte jetzt keine eigene CMK Instanz aufsetzen, nur weil ich an vier Fritzboxen 45 Geräte/Sensoren im Blick haben will.
Da finde ich das Konzept der Ergebnisanzeige dieser CheckVersion hier deutlich besser.

Etwas Pflege wäre echt gut.

Gruß

Gerold

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants