Skip to main content

PBJ Omada — Changelog

Every PBJ Omada release, newest first.

September 27, 2026

Current release: 7.13 (September 2026)

7.13 — 27 September 2026

The first release offered to customers. Needs PBJ CRM 7.61 or newer. No database change.

  • The controller list shows the full address. Manager › Omada now shows a controller’s address with its port (for example 203.0.113.10:2087), as the controller’s own page already did.
  • A controller that answers the Open API counts as heard from. Before its first webhook, a controller pbj.tech has read shows All up (or N down) with Last read … instead of Not heard from yet. Not heard from yet now means neither a webhook nor a read; a controller whose reads fail says Reads failing. The controller page, the Network card and the Omada settings panel say the same.

7.00 – 7.12 — 25–27 September 2026

Built and field-tested on pbj.tech before the first customer release; everything below ships in 7.13.

  • Omada alerts on your client records. A webhook receiver for TP-Link Omada controllers (its own address plus the controller’s Shared Secret, retries stored once), device status read through the Omada Open API, and a Network card and Network events on the business and person profiles.
  • Help Desk tickets for problems that last. Devices that go down, WAN links that drop, isolated access points and failed Cloud Access can open a ticket, close it on reconnect and reopen it on a repeat — each alert kind set per controller to ticket, show only, or ignore. Every automatic ticket goes to a fallback agent picked on Manager › Omada; nothing is ticketed until one is chosen.
  • Manager › Omada. Every controller in one list for managers and owners: who it is for, its address, sites, status and when it was last heard from. Owners add a controller with the CRM’s own form and business finder; the webhook address is shown once, with Copy.
  • Three ways to connect. Webhooks only, a TP-Link Cloud-Based Controller (by region), or port forwarding to a controller on the client’s own network — with step-by-step instructions for each, a connection line that says connected only after a read worked, and a check that says which side is blocking when a controller does not answer.
  • One controller, one client — or several. A controller is filed under one client business, or marked Several clients with each site filed under its own business.

Every PBJ plugin is on the WordPress Plugins page.

Latest Articles