Add inline search inputs for filter panels with >= 10 items, "Most popular"
grouping for use cases with >= 11 items, scrollable filter items containers
with hover-visible scrollbar, and totalItems filtering. Convert *ngFor/*ngIf
to new Angular @for/@if flow syntax in the filter panel.
Replace hardcoded category/use-case/subtype enums and translation maps
with dynamic FilterParamInfo data from /api/item-listing/filterInfo/{itemType}.
Add inline search input for filter panels with >= 10 items, "Most popular"
grouping for use cases and vendors with >= 11 items, scrollable filter
items container with hover-visible scrollbar, and multi-vendor support
in MpItemVersionQuery. Remove redundant enums, maps, and locale translations.
Update dashboard widget select filter panel to use dynamic data.
When a device is already installed, show an "Install one more" button
next to the Remove button. Clicking it opens the install wizard to
provision another instance of the same device package.
Always fetch ZIP and open the device install review dialog (tabs with
instructions, forms, provisioning) — never fall back to the generic
detail dialog. The review dialog handles missing installState gracefully
(shows empty forms but instructions still render from ZIP).
Show the guide icon on device cards for ALL installed items, not just
those with installState. If installState is available, opens the
read-only review dialog. If not (items installed before the feature),
falls back to the item detail dialog — same pattern as the installed
items page info button.
When the browse component is used on /iot-hub/devices (via items page
component), the parent sets config in its own ngOnInit, so the child's
@Input setter fires AFTER the child's ngOnInit. The DEVICE-specific
loading (vendors + installed items) in ngOnInit never executed because
activeType was still the default WIDGET at that point.
Fix: trigger loading directly in the activeType setter when the value
changes to DEVICE.
The device card's "Installed" chip, guide button, and delete/update
buttons need the installed item data. Added installedDevices loading
when DEVICE tab is active, included in getInstalledItem() lookup
and reloadInstalledItems() refresh.
Without this, getInstalledItem() returned undefined for DEVICE type,
so cards showed "Install" instead of "Installed" and the guide button
was never visible.
Show a document icon button (📄) next to the "Installed" chip on
device cards that have stored install state. Clicking opens the
read-only review dialog with tabs (same as from Installed Items).
Visible in both "same version" and "update available" card states.
Tooltip: "View setup guide". Only shown for DEVICE items with
installState in their descriptor.
Hardware Types: update to 15 values (was 19):
Actuator, AI Accelerator, Analyzer, Camera, Controller, Data Logger,
Development Board, Display, Gateway, Meter, PLC, Relay, Sensor,
Single Board Computer, Tracker
Use Cases: flatten to 22 values (was 27 grouped into 8 industries):
Air Quality Monitoring, Asset Tracking, Cold Chain, Drones, ...
No more group headers — simple flat checkbox list.
Fetch distinct vendor list from IoT Hub API (GET /versions/published/vendors)
when DEVICE tab is activated. Render as checkboxes (same pattern as
Hardware Type filter). Vendor is the first filter section for devices.
Replaces the debounced text input approach with dynamic checkbox list.
Add Vendor as the first filter for DEVICE type in browse page:
- Text input with debounced search (400ms)
- Clear button when filter is active
- Passes vendor param to IoT Hub API query
- Included in filter count and clearAllFilters
- Positioned above Hardware Type and Connectivity filters
- Use Cases: add 27 grouped values (8 industry groups) with sub-headers
in the filter panel. Applied to all item types.
- Device filters: replace Category with Connectivity (55 values, 3 groups)
and Hardware Type (19 values) filters. Category hidden for DEVICE type.
- Query model: add hardwareTypes, connectivity, vendor params to
MpItemVersionQuery (IoT Hub API already supports these).
- Detail dialog: DEVICE type shows Hardware Type + Connectivity + Use Cases
instead of Category + Use Cases.
- Filter chips updated for new filter types.
Replace mat-stepper with mat-tab-group in review mode for a cleaner
read-only experience. All tabs are freely clickable without linear
progression.
- Extract step content into shared ng-template (used by both stepper
and tabs to avoid duplication)
- Pre-activate all step content on init in review mode (tabs render
lazily)
- Add onTabChanged handler for tab selection
- Footer shows Close + Open Dashboard buttons
- Install mode stepper unchanged
The provisioning step content (entity list) was empty because
onStepActivated() was only called for the initial step. When the
user clicked on the Provisioning step directly, nothing triggered
the content initialization.
Fix: listen to mat-stepper selectionChange event to call
onStepActivated() whenever the user navigates between steps.
Also disable linear mode in review mode so all steps are freely
clickable.
The review mode check ran after the single-connectivity auto-start,
so the wizard was already built with empty state before review mode
could restore form values and entity outputs.
Fix: move connectivity selection logic after the review mode check.
Review mode sets its own connectivity from stored state; normal mode
falls through to the existing single/multi connectivity logic.
- Remove stale iotHubApiService from dialog data (now directly injected)
- Fall back to regular detail dialog for items without installState
(installed before the review mode feature)
Search component:
- New TbIotHubSearchComponent in home/components/iot-hub/ with search toolbar,
pagination, grouped results, sort, loading/empty states
- Inputs: searchText (two-way), creatorId, showCreator; ng-content for title
- Custom search input (320x40px, border, search icon, clear button)
- Sort icon-only button on lt-sm, mobile results count in title row
- Divider before categories section
Search page:
- Renamed to TbIotHubSearchPageComponent, embeds TbIotHubSearchComponent
- Title projected via ng-content, responsive inset padding per breakpoint
- Full-height layout with flex
Creator profile:
- Two-column layout: creator info (360px) + vertical divider + published items
- Uses TbIotHubSearchComponent with creatorId and showCreator=false
- 140px avatar, 28px name, description, link rows with hover styles
- Responsive: column layout on lt-lg, adjustable padding per breakpoint
- Back button inside creator info column
Item detail dialog:
- showCreator parameter (default true), hides author section when false
- openItemDetail service method accepts showCreator argument
Item card:
- Respects showCreator input, hides author in both compact and big layouts
Template syntax:
${note(This is an informational note.)}
${warn(All code examples require ThingsBoard Library version **0.10.2**.)}
${error(This device is not compatible with ThingsBoard CE.)}
Renders as styled callout boxes with Material Icons:
- note: blue background, info icon
- warn: amber background, warning icon
- error: red/pink background, error icon
Track which resolution was used per entity step (created, use-existing,
overwrite, create-copy). Store in installState for review mode.
Provisioning step now shows green resolution label on the right:
"Created", "Used existing", "Overwritten", or "Created copy".
Visible in both live install and read-only review dialog.
When an entity with the same name already exists, show amber conflict
UI with resolution options instead of a red error:
- Device Profile / Rule Chain / Device / Gateway:
"Use existing" (reuse as-is) or "Overwrite" (update with template)
- Dashboard: "Overwrite" or "Create copy" (duplicate names allowed)
Pre-checks by name before each entity creation. If conflict found,
pauses provisioning and shows resolution buttons. After user chooses,
resumes with remaining steps.
New status: 'conflict' with amber styling, warning icon, and action
buttons on the progress row.
Store install state (form values, entity outputs, selected connectivity)
in DeviceInstalledItemDescriptor during registration. Installed Items
info icon for DEVICE type re-fetches the ZIP and opens the wizard in
read-only review mode:
- All stepper steps clickable (jump to any step)
- Form fields populated with stored values and disabled
- Entity progress shows all items as completed
- Markdown instructions rendered with resolved variables
- Download buttons and image galleries still work
- Single "Close" button in footer
Backend: add selectedConnectivity and installState fields to descriptor
Test: verify installState deserialization round-trip
Replace Done button on the last step with:
- Close (text button) — closes dialog
- Open Dashboard / Open Device / Open Gateway (primary button) —
closes dialog and navigates to the entity
Priority: dashboard > device > gateway > integration.
If no entity was created, only Close is shown.
Add ${images.gallery(path1,path2,path3)} template syntax that renders
multiple ZIP images as a side-by-side gallery in instruction steps.
Images are resolved from zipImages (base64 data URIs). Click to expand
individual images. Styled as a flex row with thumbnails.
The helpImage field in form definitions was rendered with the raw path
from the ZIP. Now resolved through zipImages map to get the base64 data
URI, same as markdown images.
Add optional 'dockerCompose' field to GATEWAY step definition pointing
to a YAML template in the ZIP. Variables (${mqtt.host}, ${gateway.token},
form values) are resolved after gateway creation. The download button
serves the custom template as a Blob download instead of calling the
standard backend endpoint.
Falls back to the standard API-generated docker-compose.yml when no
custom template is provided.
Add optional 'credentials' field to DeviceInstallStep pointing to a
JSON file in the ZIP. After device creation, fetches existing credentials,
applies overrides (credentialsType, credentialsValue, credentialsId),
and saves. Supports MQTT_BASIC with clientId/userName/password.
Example credentials.json:
{
"credentialsType": "MQTT_BASIC",
"credentialsValue": {
"clientId": "${deviceName}",
"userName": "${mqttUsername}",
"password": "${mqttPassword}"
}
}
Load image files (png, jpg, gif, svg) from ZIP as base64 data URIs
during parsing. Resolve markdown image references  to
inline data URIs before rendering, so images bundled in the device
package display in instruction steps without a server endpoint.
Instead of a fixed download bar above markdown, the creator writes
${gateway.downloadButton} anywhere in their markdown. It resolves to
an HTML button with data-action attribute. After markdown renders,
onMarkdownReady() attaches a click handler that calls the authenticated
DeviceService.downloadGatewayDockerComposeFile().
Usage in post-install.md:
${gateway.downloadButton}
Markdown links can't pass JWT auth headers, so instead of relying on
${gateway.dockerComposeUrl} in markdown, add a download bar above the
instruction content when a gateway was created. Uses the existing
DeviceService.downloadGatewayDockerComposeFile() which handles
authenticated download via ResourcesService (JWT injected by interceptor,
Blob created, browser download triggered).
Each entity output now includes a url field:
- deviceProfile: /profiles/deviceProfiles/{id}
- device: /entities/devices/{id}
- gateway: /entities/gateways (generic, no ID)
- dashboard: /dashboards/{id}
- ruleChain: /ruleChains/{id}
Available in templates as ${device.url}, ${dashboard.url}, etc.
- Add GATEWAY step: creates gateway device, outputs dockerComposeUrl
- Add GATEWAY_CONNECTOR step: saves connector config as shared attributes,
appends to active_connectors array on the gateway
- Add optional serverAttributes/sharedAttributes fields to all entity steps
(DEVICE, GATEWAY, DEVICE_PROFILE, DASHBOARD, RULE_CHAIN)
- Attribute files are read from ZIP, variable-resolved, and saved via
AttributeService after entity creation
The admin settings endpoint requires SYS_ADMIN authority but the device
install wizard runs as TENANT_ADMIN.
Fix: add getConnectivityInfo(baseUrl) to DeviceConnectivityService which
resolves host/port with baseUrl fallback (reusing existing getHost/getPort
logic). Expose via new TENANT_ADMIN endpoint GET /api/iot-hub/connectivity.
Remove AdminService dependency from the dialog component.
Fetch connectivity settings from admin API on wizard init and make
transport variables available in all templates and instructions:
${http.host}, ${mqtt.port}, ${coap.host}, etc.
Resolution priority: form values > transport vars > entity outputs.
Drop ${step1.id}, ${step2.name} etc. positional variable resolution.
Only named entity outputs (${device.id}, ${dashboard.name}) are supported.
Updated spec to reflect the simplified resolution priority.
- Extract filter panel content into ng-template for reuse
- Desktop sidebar (tb-iot-hub-filters-desktop): hidden on lt-lg
- Filter toggle button: shown on lt-lg with active filter count
- mat-drawer (right-side overlay): 60% width on lt-lg, 100% on lt-md
- Drawer has header with close button, active filter chips, and filter body
- mat-drawer-container wraps content area for proper drawer integration
- Add activeFilterCount getter and filterDrawerOpened property
- New addItem(itemType, options?) method opens add item dialog via service
- Options: optional itemSubType and entityId
- Refactored dashboards, rule chains, devices, widget types, calculated fields
to use iotHubActions.addItem() instead of opening dialog directly
- Removed direct TbIotHubAddItemDialogComponent imports from all table configs
- All table configs now inject IotHubActionsService
- New iot-hub-components.models.ts with shared ITEM_TYPE_TO_ENTITY_TYPE
mapping and resolveEntityDetailsUrl function
- Remove duplicated ITEM_TYPE_TO_ENTITY_TYPE from install and update dialogs
- Remove duplicated resolveEntityDetailsUrl from install and update dialogs
- Both dialogs now use shared function from models file
Igor Kulikov
Andrii Shvaika