Werk #20250: Cisco Meraki: handle unmapped device status
| Component | Checks & agents | ||||
| Title | Cisco Meraki: handle unmapped device status | ||||
| Date | Jul 31, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
The "Device Status" service for Cisco Meraki devices could crash with a
KeyError if the device reported a status value that the configured "Map
device status to monitoring state" rule did not cover (for example, a rule
saved before all four status values became mandatory in the rule editor).
The check now falls back to the plugin's built-in default monitoring state for that status instead of crashing, and only shows UNKNOWN if the status is not one of the four known device statuses at all.