Device filters

Added: after 2026-10-R1

The Search or filter box above the device list in the new web UI does two things:

  • Plain words, such as Huawei or Bed Bath and Beyond, search the device list the same way as before.
  • Anything with an operator, quotes, a MAC address, or a sort becomes a filter: a condition on device fields, checked by the Kismet server, which only lists the devices that match.

Filters are written in a short form in the box, and the web UI turns them into a condition in the device rules language. Hovering over the box shows the condition sent to the server. When a filter has an error, it’s shown next to the box, with where in the filter it is.

After 2026-10-R1, the help button next to the box opens a guide to the filter syntax and every field name the device list knows, grouped by phy, with a Find box to look up a name.

The device list filtered to open access points The device list filtered to open access points, dark theme
The device list filtered to open access points

Examples

In the search boxLists
Huawei || DellDevices with either word in any shown field
manuf ~ appleDevices whose manufacturer contains apple, in any case
packets > 1000 && signal > -60Busy devices which are close by
type == "Wi-Fi AP" && crypt == OpenOpen Wi-Fi access points
ssid == ONE || ssid == TWONetworks advertising either SSID
ssid* ~ guestDevices advertising, responding with, or probing for an SSID containing guest
name =~ /^corp-/Devices whose name matches a regular expression
last_time < 5mDevices seen in the last 5 minutes
uptime > 1dAccess points which have been up for more than a day
callsign ~ N1Aircraft and ships whose callsign contains N1
pan_id == 0x1A2B802.15.4 devices on PAN 0x1A2B
first_time < 1h && phy == BTLEBluetooth LE devices first seen in the last hour
related > 1BTLE random addresses sharing their payload with another address (BTLE related devices)
similar > 1BTLE random addresses whose advertisements have the same structure as another address’s
00:11:22Devices with 00:11:22 anywhere in any MAC address field
^00:11:22 || 33:44$MAC addresses starting with 00:11:22, or ending in 33:44
!(phy == IEEE802.11)Everything but Wi-Fi
phy == ADSB sort: signal desc, packetsAircraft, strongest first
sort: last_time descEvery device, most recently seen first

Writing filters

Combining conditions

OperatorMeans
&& or andBoth conditions
|| or orEither condition
! or notNot the condition
( )Grouping

Conditions next to each other without an operator are combined with and. and, or, and not written as words only count as operators in a filter; a box with only words in it, such as Bed Bath and Beyond, is still a plain search.

Comparisons

OperatorMeans
== (or =), !=Equal, not equal
<, <=, >, >=Less than, greater than, for numbers and times
~Contains, in any case, for text; for MAC addresses, contains the octets anywhere
=~ /regex/Matches a regular expression, for text; a / in the expression is written \/

Text with spaces or operator characters goes in double quotes, as in type == "Wi-Fi AP". A word on its own, without a field, matches devices with that word in any of the fields the device list asks for.

Times

Comparing a time field with a duration (30s, 5m, 2h, 1d) compares how long ago it was: last_time < 5m lists devices seen in the last 5 minutes, and first_time > 1d devices first seen more than a day ago.

Fields which hold a length of time, such as uptime (a Wi-Fi access point’s uptime, from its beacons), take a duration the same way: uptime > 1d lists access points up for more than a day. A plain number is in the field’s own units, which for uptime is microseconds.

MAC addresses

A MAC address, or a part of one from 1 to 6 octets (such as 00:11:22, aa:bb, or aa:), separated by : or -, matches anywhere in the address, in every MAC address field the device list knows (the device MAC, BSSIDs, and others). Starting it with ^ only matches the start of the address, and ending it with $ only the end.

With a field, mac == 00:11:22:33:44:55 matches the whole address, and bssid ~ 22:33 part of it.

Field names

A field can be named in several ways:

  • The short names from the device rules language: mac, name, phy, type, simple_type, manuf, crypt, channel, frequency, packets, datasize, first_time, last_time, mod_time, num_alerts, signal, min_signal, and max_signal. In the web UI, type matches both the device’s type, such as Wi-Fi AP or Apple Watch, and its simple type, such as Wi-Fi or BTLE, so type == "Wi-Fi AP" and type == "Wi-Fi" both work; simple_type matches only the simple type. Sorting by type sorts by the device’s type.
  • Device list columns, by their name or title, in lowercase with spaces as _, and without a group name: ssid, bssid, clients, encryption, last_seen, and so on.
  • Search groups, such as adsb, ais, uav, cell, base, or rule_tags, which match when any of their fields do.
  • Full Kismet field paths, such as kismet.device.base.manuf or dot11.device/dot11.device.last_bssid.

Some names have a wider form, written with *:

NameFields
ssid*Advertised, responded, and probed SSIDs
bssid*The last BSSID and the BSSIDs probed for
mac*Every MAC address field

Names for device details

After 2026-10-R1, many of the details shown in the device panel can be filtered on by name, even when they aren’t columns in the list. A name is only known when the server has the phy it belongs to.

PhyNames
Anyaltitude / alt (reported altitude, in meters), speed (reported speed, in km/h)
ADS-Bicao, callsign, registration / reg, model, operator, aircraft_type
AISmmsi, imo, ship_name / vessel, callsign, ship_type, destination, flag / country, nav_status, sog / knots
UAV / dronesserial, drone_manufacturer, model, registration / reg, operator / operator_id, altitude / alt, height
Celloperator, mcc, mnc, plmn, tac, cell_id / cellid, pci, arfcn, band, rsrp, rsrq, sinr, cqi
802.15.4pan_id / pan, short_addr, ext_pan_id, network_name, role, thread_version, joining / thread_joining (joining > 1 finds open Thread networks), router_id, child_id, children, polls, poll_interval (a duration, such as poll_interval > 30s)
Meshtasticnode_id / nodeid, node_name (long or short name), long_name, short_name, battery, voltage, channel_use, uptime
MeshCorenode_name, pubkey / public_key, hops
Metersmeter_id, meter_type, consumption
Sensorsmodel, sensor_id, battery, temperature / temp (°C), tire_temperature, moisture, wind_speed / wind
Z-Wavehome_id, zwave_id
Bluetooth LEcompany_id, bt_version, chip / chip_maker, related / related_count (addresses in the device’s related group), similar / similar_count (addresses in its similar group)
Location trackerstracker / tracker_network, battery, separated
Bluetoothservices
Wi-Fiwps_manuf, wps_model, wps_device, serial / wps_serial, country, mesh_id

A name used by more than one phy, such as callsign, model, battery, or uptime, matches the field of every phy which has it: callsign ~ N1 finds aircraft and ships. Durations convert to each field’s own units, so uptime > 1d works for Wi-Fi access points and Meshtastic nodes alike.

Numbers can be written in hex, as in pan_id == 0x1A2B.

More names for columns

Some columns answer to more than one name: the Wi-Fi QBSS usage column also to qbss, utilization, and usage, and QBSS clients to stations. A name used by more than one column or search group matches any of their fields; the short names above always keep their meaning.

A comparison on a field skips devices which don’t have data for it. uptime > 1d doesn’t list clients, or access points which never sent a beacon timestamp, and usage > 50 only lists access points which report QBSS. A device without data for a field matches neither a comparison on it nor its negation: !(usage > 50) lists access points reporting QBSS usage of 50% or less, not every device without QBSS.

Numbers and times can only be compared with ==, !=, <, <=, >, and >=; text and MAC addresses with ==, !=, ~, and (for text) =~.

Sorting

sort: followed by fields orders the list, each with asc or desc; later fields break ties in earlier ones. A sort can follow a filter or be used on its own:

phy == BTLE sort: signal desc, packets desc

A sort in the box replaces sorting by a column header.

Filters in the REST API

The web UI sends filters to the server as the filter and filter_sort parameters of device views, and other tools can do the same. These take a condition, and sort keys, in the full device rules language, rather than the short form of the search box; for instance:

filter=packets > 100 and manuf icontains "apple"
filter_sort=kismet.device.base.signal/kismet.common.signal.last_signal desc

In a filter, text("<s>") matches devices where any text field the request asks for contains s, in any case.