TikMan v2.2.0

📬 Scheduled update check (new)

Settings → Auto-check: once a day, at a time you pick, TikMan asks every RouterOS device with a
login whether it has an update, and e-mails you what it found.

It only checks — nothing is installed, and that's the design rather than a first step. A check
can't strand you: if it fails at 03:00, the worst case is a mail that doesn't arrive. Installing is
what reboots devices, and that stays a decision you make while you're watching.

• Daily at HH:mm, with catch-up. TikMan is a desktop app, so the schedule only runs while it's
  open — a slot missed because the app was closed is run at the next opportunity rather than skipped.
• Several recipients, comma-separated, and a choice between a mail after every run or only when
  there's an update or a failure.
• A test button that sends with the settings as they are on screen. Find the typo now, not at
  03:00 in a mail that never arrives and can't report its own absence.
• The SMTP password is DPAPI-encrypted, like every other password TikMan stores. An empty user
  means an unauthenticated relay.
• Port 587 (STARTTLS). Port 465 (implicit TLS) isn't supported and says so up front rather than
  failing later as an unreadable timeout.

🔓 The update check falls back to SSH

A broken RouterOS HTTPS handshake is the whole reason TikMan's SSH read path exists — monitoring,
topology, Wi-Fi names, logs and the config export all fall back to it. The update check was the one
that didn't, so on exactly the devices that need the fallback most it failed at the first step and
took the whole run down with it. Setting the channel and checking now go HTTPS REST → SSH CLI,
like everything else. Not via the plain-HTTP fallback, even when you've allowed it: this writes a
setting with your password attached.

🧭 Backup and updates: only what can actually happen

• Pick what to save — configuration (.rsc) and/or binary backup (.backup). Each device gets
  the intersection of what you asked for and what it can produce, and Start is only offered when
  that isn't empty.
• The lists hold what qualifies. The update list used to contain every device TikMan knows,
  printers and IoT plugs included. Devices that can't be backed up grey out and say why on hover.
• The runs count honestly. "2 updated" for a run that installed one update and skipped the other
  is now "1 updated, 1 skipped". A backup where the config saved but the binary didn't is partial.
• The binary backup is no longer silent — it was fetched and never mentioned.
• The folder is asked for every time, rather than silently reusing an hour-old choice.
• The channel dropdown reads 2026-06-02 7.23.1 (stable): version and release date where you
  choose, so the separate "Latest" column is gone. It's a read from MikroTik's public server and
  touches no device; your device's channel is still only written when you install.

🚀 A calmer app

• The update check runs first on startup, before anything touches the network, and the download
  gets a real progress window instead of a status line that looked like a hang.
• "No scan at startup" now means it. Restored devices stay grey ("not checked yet") instead
  of a green dot nobody verified.
• The bottom bar is a banner that wraps; the detail pane folds away with a chevron.
• A PC running Spotify is not a speaker. mDNS was trusted ahead of everything, so a workstation
  advertising _spotify-connect._tcp was filed as a speaker, ahead of the RDP/WMI+SMB signature that
  exists to say "this is a PC".

The bulk-update warning claimed edge-devices-first as if it were a law. It's a rule of thumb, and
CAPsMAN inverts it when the controller carries its CAPs along (upgrade-policy).

Downloads

File	Platform	Runtime
TikMan-2.2.0-win-x64.exe	Intel/AMD 64-bit	none (self-contained, ~68 MB)
TikMan-2.2.0-win-x64-fdd.exe	Intel/AMD 64-bit	.NET 10 Desktop Runtime (~12 MB)
TikMan-2.2.0-win-arm64.exe	ARM64	none (self-contained, ~65 MB)
TikMan-2.2.0-win-arm64-fdd.exe	ARM64	.NET 10 Desktop Runtime (~12 MB)

When in doubt, take the self-contained build (-x64 or -arm64). The exes are unsigned, so Windows
SmartScreen shows an "unknown publisher" notice on first run — More info → Run anyway.