PBJ Omada — Changelog

Every PBJ Omada release, newest first.

September 27, 2026

Current release: 7.20 (October 2026)

7.20 — 15 October 2026

Fixed: webhook messages are no longer lost. A webhook line that could not be saved used to be counted as a duplicate and dropped. Now the error is logged and Omada is asked to send it again; lines already saved are recognised as duplicates on that retry.

Client business and module permissions now narrow private device lists, while existing provider membership and staff access are kept. Needs PBJ CRM 7.82 or newer.

PBJ Omada only connects to public controller addresses, checked again at connection time, with no redirects.

New: “Controller unreachable”. When pbj.tech cannot read a controller through its Open API, an incident opens at the first failed read, one per controller. After the same wait as other problems (60 minutes by default) it becomes a Help Desk ticket for the controller’s client, sent to the controller’s own choice or the default fallback agent, with the staff email. The next good read adds a note and closes it (when auto-close is on); a later outage reopens the same ticket.
Set per controller on its page like the other alerts: Open a ticket (default), Show it, no ticket, or Ignore it. Only controllers with the Open API set up can raise it.
No database change (DB 3).

A failing controller is backed off on the scheduled sync: 5 minutes after the first failed read, doubling to at most an hour; any successful read clears it, and manual reads are never held back. State is kept in pbj_omada_sync_backoff (removed on uninstall).
The Help Desk link switches on only when every Help Desk method it calls exists (code review 2026-09-28, security 15), so an older Help Desk no longer fails in the middle of an incident.
The CRM descriptors load the built .min script. No database change (DB 3).

Devices in the client portal (client_view.webpage.rows, CRM contract 42): one group per Omada site linked to the customer, each device Online / Offline / Status unknown and since when. MAC and IP addresses, firmware and controller details are never included.

New: each controller says who gets its automatic tickets — a person or a Help Desk group (Help Desk’s rota picks the group member) — changed from the controller’s page by owners and managers. Controllers without their own choice use the default fallback agent on Manager › Omada.

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.

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.