-
Suriya released this
2026-09-19 10:42:45 +00:00 | 43 commits to main since this releasedemo build: TeNext Coimbatore, both office cameras
Demo build. Needs the unlock code that travels separately. Supersedes v0.4.7-demo — same app; the shop it joins is now set up completely.
- Joins TeNext Coimbatore at head office. Both office cameras —
entrance(192.168.1.122) andcam2(192.168.1.121), sub-streams, passwords stored at head office — arrive on the first sync and connect. - Everything from v0.4.7-demo: honest tray, setup refuses to run under a live app, credentials reload on a re-claim, Loya, Loyaly branding.
Installing
Quit any running Behavision (tray → Quit). Unzip, run
behavision-setup.exe, type the unlock code, open Behavision, sign in as the TeNext owner. Both cameras show Connected within a minute or two. One PC per package.Downloads
- Joins TeNext Coimbatore at head office. Both office cameras —
-
2026-09-19 10:22:57 +00:00 | 44 commits to main since this releasedemo build: the tray tells the truth, and setup protects itself
Demo build. Needs the unlock code that travels separately. Supersedes v0.4.6-demo. Quit any running Behavision from the tray before running setup — setup now refuses otherwise.
Found on the v0.4.6-demo install, all fixed here:
- Tray Start/Stop looked dead. A second engine already held port 8010, so the app's own engine failed and the tray said nothing. It now says "Not running — port 8010 is already in use — another Behavision or its engine is still running" (and the other known causes), and the buttons cannot freeze the menu.
- Setup refuses to run while Behavision is open. Running it underneath the app started a second engine and re-claimed the shop while the open app still held the old credentials.
- The app reloads its credentials when setup or a claim rewrites them, instead of leaving camera sync silently refused.
Carries everything from v0.4.6-demo: a claimed PC forgets old logins and old cameras; Loya; Loyaly branding.
Installing
Quit any running Behavision (tray → Quit). Unzip, run
behavision-setup.exe, type the unlock code, open Behavision, sign in as the TeNext owner. One PC per package.Downloads
-
2026-09-19 09:59:22 +00:00 | 45 commits to main since this releasedemo build: a claimed PC starts clean
Demo build. Needs the unlock code that travels separately. Supersedes v0.4.5-demo.
Found on the first v0.4.5-demo install, all fixed here:
- Leftover login. The PC was still signed in to the previous demo's head office, so every screen and Loya said "session expired". Claiming a shop now clears any old login, and a login the server rejects sends the app back to Sign in by itself.
- Three cameras for a shop with two. Cameras left from the earlier demo were offered up to head office without their passwords, duplicating the entrance camera. Setup now removes cameras from an earlier install before joining the shop — head office is the source of truth.
- Loya tells you to sign in again instead of showing an error.
Installing
Unzip, run
behavision-setup.exe, type the unlock code, open Behavision, sign in as the TeNext owner. One PC per package.Downloads
-
v0.4.5-demo — demo build: joins TeNext Chennai, with Loya (fixes the v0.4.4-demo launch error) Pre-Release
2026-09-19 09:43:52 +00:00 | 47 commits to main since this releasedemo build: joins TeNext Chennai, with Loya (fixes the v0.4.4-demo launch error)
Demo build. Needs the unlock code that travels separately from this zip. Supersedes v0.4.4-demo, whose Behavision.exe showed a "build tags" error on launch; carries every fix from v0.4.2 and v0.4.3.
What this demo does differently
The first demo sealed the office cameras into the package and ran on its own. This one joins a real shop at head office — TeNext Chennai — exactly as a customer install would:
behavision-setup.exeasks for the unlock code, links the PC, and the office entrance camera arrives from head office on the first sync. Sign in with the TeNext owner account and you see the real product end to end: the camera connected, arrivals, Loya.What's new since v0.4.3
- Loya — the Behavision buddy, top-right of every screen. Asks and answers about your shop in plain words; knows how setup works.
- Cameras and Customers screens rebuilt — picture-led camera cards, "connected" and "proven" as separate claims, forms at proper width.
- Loyaly branding throughout.
Installing
Unzip, run
behavision-setup.exe(needs Python 3.10+), type the unlock code when asked, then open Behavision and sign in. The installation code inside is single-use: one PC per package.Downloads
-
2026-09-19 08:21:52 +00:00 | 48 commits to main since this releasedemo build: joins TeNext Chennai, with Loya
Demo build. Needs the unlock code that travels separately from this zip. Supersedes v0.4.1-demo; carries every fix from v0.4.2 and v0.4.3.
What this demo does differently
The first demo sealed the office cameras into the package and ran on its own. This one joins a real shop at head office — TeNext Chennai — exactly as a customer install would:
behavision-setup.exeasks for the unlock code, links the PC, and the office entrance camera arrives from head office on the first sync. Sign in with the TeNext owner account and you see the real product end to end: the camera connected, arrivals, Loya.What's new since v0.4.3
- Loya — the Behavision buddy, top-right of every screen. Asks and answers about your shop in plain words; knows how setup works.
- Cameras and Customers screens rebuilt — picture-led camera cards, "connected" and "proven" as separate claims, forms at proper width.
- Loyaly branding throughout.
Installing
Unzip, run
behavision-setup.exe(needs Python 3.10+), type the unlock code when asked, then open Behavision and sign in. The installation code inside is single-use: one PC per package.Downloads
-
2026-09-19 07:25:16 +00:00 | 52 commits to main since this releasethe Loyaly mark, and the engine dashboard ships complete
Standard build. Supersedes v0.4.2 — same fixes, plus the two below. If you have not yet updated from v0.3.x / v0.4.1-demo, read the v0.4.2 notes: those builds could not deliver visits to head office and must be re-claimed once after updating.
What changed since v0.4.2
- Loyaly branding. The app, the tray icon (the mark with a green/amber/red/grey state dot),
Behavision.exeandbehavision-agent.exein Explorer, the installer, head office and the engine dashboard all carry the Loyaly mark. - The engine's own dashboard at
http://localhost:8010works on a source install. The Python wheel in earlier packages did not include the dashboard page, so opening that address on a Windows PC failed with a missing file. The desktop app was unaffected — it does not use that page.
Installing
Unzip, run
behavision-setup.exe(needs Python 3.10+ on the PC), then open Behavision and enter the installation code from head office. SeeINSTALL.txt.Downloads
- Loyaly branding. The app, the tray icon (the mark with a green/amber/red/grey state dot),
-
2026-09-19 07:14:58 +00:00 | 53 commits to main since this releaseshop PCs can publish, Quit really quits, shops open themselves
Standard build (no sealed demo cameras). Supersedes v0.3.2 and v0.4.1-demo. Every shop PC should update — the first fix below means no earlier build could deliver a visit to head office.
Fixes on the shop PC
- Claiming a PC now keeps the broker's certificate. The server has always sent it at enrolment; the app and the agent dropped it, so every claimed PC failed TLS to
mcp.loyaly.ai:8883and reported "the broker did not accept this PC". No visit from any real site could ever have arrived. Re-claim once with a new installation code after updating; nothing else changes. - Quit from the tray stops the engine. On Windows the engine is started through a Python redirector that spawns the real interpreter; Quit killed the redirector and left recognition running with no icon and no way to stop it. The engine now runs in a job object that dies with the app — even if the app crashes.
- One tray icon. A second launch (the usual reflex after closing the window to the tray) started a second full copy of the app. It now brings the existing window to the front.
- The engine no longer opens a black console window behind the app.
- The Live screen shows arrivals only; the camera picture lives on the Cameras screen.
Head office
- Owners open shops themselves — Shops → Open a new shop, or
POST /api/sites. The broker login is registered in the same request; the next step is the installation code on the new card. No support ticket per branch. - Platform admin can suspend/reinstate a company (all its sessions end immediately), reset an owner's password, and delete a suspended company.
mcp.loyaly.aiis current with this release.
Installing
Unzip, run
behavision-setup.exe(needs Python 3.10+ on the PC), then open Behavision and enter the installation code from head office. SeeINSTALL.txt.Downloads
- Claiming a PC now keeps the broker's certificate. The server has always sent it at enrolment; the app and the agent dropped it, so every claimed PC failed TLS to
-
v0.4.1-demo — live picture fixed Pre-Release
2026-09-11 10:59:06 +00:00 | 65 commits to main since this releaseDemo build with the office cameras sealed inside. Supersedes v0.4.0-demo. Same unlock code as v0.4.0-demo.
Fixes the lagging camera feed
Reported from the first Windows install. The live picture was served from the frame the recognition pipeline had most recently finished, so on a modest PC it advanced a few times a second and every frame was already as old as the processing. Now the picture runs at the camera's own rate off the capture thread, with recognition boxes drawn over it from the last processed frame; frames are encoded only while somebody is watching; and ffmpeg runs with low-latency flags instead of its default RTSP buffer.
Measured on the same machine, ten seconds each: 9.8 → 14.0 new pictures per second against a 15 fps camera, with engine CPU down from 90% to 62% even with a viewer attached.
Engine 1.1.0. Re-run
behavision-setup.exeon a PC that already has an earlier build — it upgrades the engine in place; nothing else needs redoing.SHA-256:
f79ccc31b82695fbbc6fb1a1419e66ddc1c98de8e24bbade18c26f6bb2db766bDownloads
-
v0.3.2 — live picture fixed Pre-Release
2026-09-11 10:59:01 +00:00 | 65 commits to main since this releaseStandard build. Supersedes v0.3.1.
Fixes the lagging camera feed
Reported from the first Windows install. The live picture was served from the frame the recognition pipeline had most recently finished, so on a modest PC it advanced a few times a second and every frame was already as old as the processing. Now the picture runs at the camera's own rate off the capture thread, with recognition boxes drawn over it from the last processed frame; frames are encoded only while somebody is watching; and ffmpeg runs with low-latency flags instead of its default RTSP buffer.
Measured on the same machine, ten seconds each: 9.8 → 14.0 new pictures per second against a 15 fps camera, with engine CPU down from 90% to 62% even with a viewer attached.
Engine 1.1.0. Re-run
behavision-setup.exeon a PC that already has an earlier build — it upgrades the engine in place; nothing else needs redoing.SHA-256:
98cb04c1eb9df8c73d3b0110776fd9bbe312936346a99fcca12db6ccd8002aecDownloads
-
v0.4.0-demo — superseded by v0.4.1-demo Pre-Release
2026-09-11 10:41:33 +00:00 | 66 commits to main since this releaseUse v0.4.1-demo. This build's live camera picture lags on a modest PC; fixed in v0.4.1-demo.
Downloads