Panel Watch  ·  what it is 01 / 05

Bosch B / G-series intrusion

Panel Watch. Read the panel from a desk — Knight Watch

See what the panel is reporting, without standing in front of it.

Panel Watch · Bosch B9512G · firmware 3.10AUTO-POLLHEALTHAC power fail · Battery low · Phone line failurePOINTNAMESTATE01Front doorNormal02Rear fire exitNormal03Stockroom doorOpen04Roof hatchNormal05Compressor roomTrouble06Office motionNormal07Safe tamperNormal08Loading dockNormalthe panel’s own point text — exported as CSVThe panel is holding the answer. This is what it says when you ask it.Not battery fault — battery low, and battery missing, reported separately. Not just that the bus is faulted — SDI bus or point bus. Every condition the panel currently has set, in the protocol’s own words.
It runs unattended and holds the current state of every panel — and it tells nobody. No alerting, no notification, no escalation, and it receives no alarms. docs.knightwatch.net/panel-watch
Panel Watch  ·  the problem 02 / 05

a zone number, and a decision to make

You are told which zone. Not whether it is still faulted.

The signal says what happened at 02:14. By eight, somebody has to decide whether to send a van — and nothing at their desk has told them what the panel looks like now.

WHAT YOU ARE TOLDSITE 0412TROUBLE · ZONE 0502:14A zone number, at a moment.Is it still true? What is zone 05 actuallycalled? What is the rest of the panel doing?one event, hours agoAND IF SOMEBODY WALKS TO THE KEYPADCOMPRESSOR RM05 · TROUBLEThe name is there — on the wall.The keypad does show the panel’s own text for the point.What it will not do is travel.a person in the building, at that keypadWHAT IT SAYS WHEN YOU ASK ITPoint 05 — Compressor room — TroublePoint 03 — Stockroom door — OpenAC power failBattery lowPhone line failureFirmware 3.10 · B9512Gas of right now — not as of 02:14The system is the source of truth, and it is telling the truth to an empty room.The signal is one event. The keypad is live — when the trouble clears, it clears there — but it is on a wall in the building. What is missing is that same live answer at the desk that decides.
Panel Watch changes what a person can find out on demand. It replaces nothing your central station does, and it is not a second receiver.
Panel Watch  ·  how it works 03 / 05

one machine, one protocol

Read directly over Bosch’s own Mode 2 automation protocol.

Nothing on the panel is internet-facing, and no inbound rule is opened at the site.

B9512Gpoints · areas · status wordThe Bosch panelB- or G-series on firmware3.03.014 or later, with theautomation device set to Mode2 in RPS.MODE 2 · TLS · 7700a framed byte stream, asked and answeredWindows machinerunning the Panel Watch gatewayHOLDS THE STATEOne machine, not one per buildingIt needs only IP reach to the panel on 7700.It runs unattended, holding a connection anda cached state for each panel, so where thepanel networks reach a central site this onemachine covers the estate.WHAT IT FOUNDHEALTHAC power fail · Battery lowPOINTNAMESTATE01Front doorNormal02Rear fire exitNormal03Stockroom doorOpen04Roof hatchNormalThe panel viewOne system: every configured point withthe panel’s own name for it, its areas,and every condition that panel currentlyhas set — or all normal. The dashboardcarries the status of every panel.The gateway holds the state. The dashboard is a client of it.It polls each panel and caches what it finds, so a client reads the current state without waiting on a panel — and every client reads the same answer.
Needs the automation device set to Mode 2 in RPS with an automation passcode, on firmware 3.03.014 or later. TLS with certificate pinning; the passcode is never logged.
Panel Watch  ·  what it does 04 / 05

and what it does not

Everything it can see, and everything it cannot.

Every configured point

Read from the panel, named by the panel.

Normal Open Trouble
Trouble means short or missing — the protocol tells those apart and Panel Watch shows both as Trouble. Supervised resistor states read as Normal. The panel can also be asked for just the points that are not normal.

The condition, not the category

Every fault currently set, worst first — or all normal.

AC power fail Battery missing Battery low Communication fail
Phone line failure, SDI bus fail, point bus fail, user code tamper and parameter CRC fail are reported the same way. Battery missing and battery low are different problems, and it says which.

What is actually installed

Identity from the same status response.

Firmware version and revision Panel model
So a fleet answer to what is at that site, on what firmware, does not depend on the asset register being right.

On demand, or on an interval

Refresh when you want it, or leave it polling.

Manual refresh Auto-poll CSV export of the point list
It polls: refresh on demand, or leave auto-poll running on a set interval while you watch. The point list on screen saves out as CSV.

It watches, and it never tells

The most important line on this board.

No alerting No notification No escalation Receives no alarms
It runs unattended and keeps a current state for every panel, so the answer is already there when somebody asks. What it never does is reach outward: nobody is paged, nothing is emailed, no ticket is raised. Your central station keeps doing exactly what it does.

What it cannot tell you

Named here rather than found later.

What happened last night Which area is in alarm Which module on the bus Cellular signal and diagnostics
Mode 2 exposes the panel's event log; this does not read it today, and that is the next thing we would add. A dedicated alarm summary is not built either, and a bus fault says there is one, not which.
Not built today: alerting of any kind, the panel event log, push updates, per-module bus detail, the RPS-API endpoint routes, and any manufacturer other than Bosch.
Panel Watch  ·  where it fits 05 / 05

the panel, the machine, the limits

Bosch B- and G-series, on firmware 3.03.014 or later.

Firmware 3.03.014
or later, automation device in Mode 2

The gate everything else on this board sits behind. A panel that meets it can be read; a panel that does not, cannot. What it takes, end to end:

  • Bosch B-series and G-series — no other manufacturer
  • Automation device set to Mode 2 in RPS, with an automation passcode
  • IP reach to each panel on port 7700
  • TLS with certificate pinning, and nothing port-forwarded
  • One Windows machine with the .NET 8 desktop runtime
  • That one machine covers the estate wherever the panel networks are reachable from a central site
  • A machine at the site only where its network is an island
These are preconditions, not preferences. The automation passcode is set in RPS alongside the Mode 2 setting, and Panel Watch never writes it to a log. A panel below 3.03.014 cannot be read at all.
Fits
Estates running Bosch intrusion panels across more than one building, where whoever is responsible for them is not in the building with them.
Many panels, not one at a time
A panel view is one system — its points by the panel’s own name for them, its areas, and every condition it has set. The dashboard is every panel: each one’s current state on one screen, faulted and unreachable called out, so an estate is something you look at rather than a sequence of site visits.
Where it earns its place
At one panel, or ten, opening them one at a time is fine. Somewhere past fifty or a hundred it stops being a way to run an estate: the question becomes which sites are faulted right now, and which cannot be reached at all. A screen carrying every panel's current state answers that in one look. Opening four hundred panels one by one does not.
Support
Business hours as standard, with an optional premium tier. Coverage is set by the executed support addendum.
In one line
Panel Watch runs unattended, polling Bosch B- and G-series intrusion panels over their own Mode 2 automation protocol and holding the current state of each — every configured point by the panel's own name for it, and every condition it has set. The dashboard reads that state and shows every panel at once. It alerts nobody.
The collector runs on one machine on a schedule. Remote access to it is an outbound ConnectWise ScreenConnect session, so no site router needs an inbound rule and port 7700 is never forwarded. docs.knightwatch.net/panel-watch