MerakiMon 0.1.0

Added

• The backend: Meraki organisations with a read-only API key, one site per network, health checks, history, changes feed, alerts, card and updater on the shared core.
• Installers: a Windows MSI (service or program, tray icon, firewall rule) and a Linux .run (systemd service), with signed in-app updates.
• Choose which networks of an organisation are monitored, when adding its API key and later under Settings > Organisations > Edit. By default every network is monitored, including new ones; once some are unticked, networks that appear later are marked new and wait to be ticked.
• Network Map tab: the network's devices and the links between them (from Meraki's link-layer topology, read every 15 minutes), coloured by device state, with port names; click a device for its details.
• Find Device tab: search every site you may see for a device by name, MAC (any format), IP (LAN or uplink) or serial; each hit links to its site, Devices tab, Network Map or details. Only Meraki's own devices are found: client MACs and IPs are not polled.
• VPN tab: the site-to-site (Auto VPN) status of the network's appliance (hub or spoke, uplinks) and each peer, Meraki or third-party, with whether Meraki reports it reachable. One call for the whole organisation, read every 2 minutes; organisations that don't use site-to-site VPN just show nothing. A peer that stays unreachable raises a warning, and an appliance with no reachable peer at all a critical issue (new health area "VPN", alert kind "VPN peer unreachable"). Latency and loss per peer are not read yet.
• Wi-Fi Clients tab: the wireless clients Meraki saw on a network in the last hour (name, MAC, IP, SSID, access point, VLAN, usage, last seen), with search, sorting and counts by SSID and by access point. Read every 5 minutes, one call per monitored network, kept in memory only (never in the history) and shown only to people who may see that site; the history keeps just a count per site.

Fixed

• Switch ports that are unplugged or switched off are no longer counted as having errors (Meraki lists them under errors).
• The Reports tab now reads the history MerakiMon actually stores: health, the organisation's clients, and latency and loss over all of a site's WAN links.