Getting Started Cameras & Video Detection & Recording Automation & Events Actions Integration & Connectivity Network & Discovery AI & Remote Control MQTT Modbus Pi4J & Raspberry Pi GPIO ZeroMQ System & Administration Comparisons Use Cases Troubleshooting About & Legal
Home / Documentation / Banalytics 2.0.0 Architecture
Release 2.0.0

Banalytics 2.0.0 architecture

Version 2.0.0 moves component user-interface ownership from the portal to agent modules. The portal becomes a generic management shell, while every module ships its backend and matching browser resources together.

// At a glance

What changed

MOD

Module-owned UI

JavaScript, CSS, icons, translations, and event views are packaged beside each Thing, Task, or Action.

SYNC

Hashed synchronization

The browser downloads only missing or changed resources over the authenticated WebRTC environment channel.

ENV

Per-agent scope

UI classes are registered by environment UUID, so different module versions can coexist in one browser session.

// Console startup

Connection flow

01

Authenticate and connect

The user opens an environment through the portal and establishes the existing WebRTC connection.

02

Compare resource hashes

EnvironmentRegistry compares the agent resource catalogue with its IndexedDB path@hash cache.

03

Load changed resources

The browser registers translations and event renderers, scopes CSS, exposes icons, and compiles component classes for that environment.

04

Open the console

The portal loads hierarchy, configuration descriptors, events, and Remote API data through the normal channel.

// 1.1.0 versus 2.0.0

Main architectural differences

Area1.1.02.0.0
Component UI
Static catalogue in the portalDelivered by each agent module
Class scope
Global browser classesPer environment UUID
Cache invalidation
Portal deploymentResource SHA-256
Dashboards
Stored and implemented by portalStored on agent; provider UI supplied by modules
Event presentation
Portal must know event typeModule may contribute an event UI extension
Connection code
Mostly callbacksPromise / async flows
// Upgrade

Compatibility and operations

Component configuration is preserved. Existing Things, Tasks, Actions, rules, and connection settings need no reconfiguration after the upgrade.
Upgrade portal and agents together. The 2.0.0 portal requires the UI-resource protocol and has no 1.1.0 fallback component catalogue. Until an agent is upgraded, it cannot be operated through the 2.0.0 web console.
Dashboard migration is manual. The portal schema removes the legacy dashboard table without transferring its rows to agents. Back up and recreate required dashboards on DashboardHierarchyThing.

Agent-supplied JavaScript executes in the browser for owned and shared environments. Treat modules as trusted executable software and install them only from trusted release sources.