- 2.03 Wren1 deviceBeing configured
Viewing as , ,
Vendor access
This part is for Aigna staff
Vendors see their own installation and the device reference they need to build it: device types, setup guides and models. Everything else stays with Aigna.
Go to your installationModule
Assets is switched off
Device types, units, models, setup guides, standards, IT stores and cables. This demo has the Assets module switched off in Organisation settings.
Setup guideVideo barGoogle MeetFirmware CollabOS 1.15+Simulated
MeetUp 2 in a Google Meet hardware room
1 unit doesn't match this setup guide · 1 still to configurechecked just now
Configuring happens in a project's Deploy page
Each device is provisioned, installed, configured in this setup order and commissioned there, ticked off with who and when. This page is the standard it follows.
On the units running it
Checkingon dub-407-vc01
A practice run. A new install, in order. Ticks stay on this browser. The real run is ticked device by device in a project's Deploy page.
0 of 8MeetUp 2 is USB/HDMI hardware, not an all-in-one appliance; it's certified as Google Meet hardware only when paired with a separate ChromeOS compute system, which is what actually runs Google Meet and is enrolled in the Google Admin console. MeetUp 2 itself runs Logitech's CollabOS, so it has its own local web interface (Local Network Access) and is monitored, updated and tuned through Logitech Sync, independently of the compute system.
Google Meet hardware (Google Admin console)Google Admin console > Devices > Google Meet hardware
- SetEnroll a device with a codeDevice name: the hostname (of the paired ChromeOS compute system)Each space uses one Meet hardware licence on its compute system, named the same as everywhere else.source
- SetRoom calendarDevice settings › CalendarThe space's calendar resourceShows the space's meetings and lets people join in one tap.source
- SetTime zoneSettings › Device settingsThe site's time zoneMust match the room and its calendar.source
- SetScheduled rebootSettings › Device settingsDaily, inside the maintenance hoursA fresh start each night when no one is in the space; the documented default isn't stated.source
- SetDefault Camera FramingDevices › Google Meet hardware › Settings › Camera settingsManufacturer framingGoogle's own documentation says RightSight 2 only works when this is set to Manufacturer framing; left at No Preference, the space falls back to manual camera control.source
Camera (Logitech Sync)Logitech Sync App / Sync Portal > Device > Camera
- SetRightSight 2Enabled, Speaker ViewFrames the active speaker with a room-view inset, which is what Aigna wants for its small Google Meet rooms; the documented default isn't stated.source
Security and network (Local Network Access)MeetUp 2's own web interface (Local Network Access, by IP address)
- SetLocal Network AccessSystem › More settingsOnGives Aigna a per-device admin page over the network, rather than needing to reset the device or use only Sync Portal.source
- SetAdmin passwordFrom the password vault, per siteThe default password is the last five digits of the device hostname, printed nowhere obvious; every device needs its own vault password.source
- SetInternet Time (NTP)Local Network Access › System settingsntp1.aigna.exampleUse Aigna's own time server instead of whatever the network offers.source
- VerifyTCP/IP (IPv4 addressing)Local Network Access › NetworkAuto DHCPAigna puts AV devices on the AV VLAN with a DHCP reservation, which is also this device's default.source
FirmwareLogitech Sync Portal
- VerifyFirmware updateInventory › Room › UpdateManually scheduled, after the Lab passes itSync Portal has no automatic-update toggle to turn off; every update is already a manually chosen time window, which matches how Aigna tests firmware in the Lab first.source
What the vendor's documents don't say (4)
- The exact menu names inside the Sync App's Camera and System tabs for RightSight 2, framing speed and NTP aren't laid out step-by-step in the public docs; the paths above are as specific as the sources state.
- Whether RightSound 2 (AI Noise Suppression, AI Echo Suppression) is on by default on MeetUp 2 isn't documented; Aigna's installers should check it during verification rather than assume.
- No PoE standard or power draw is documented for MeetUp 2's own power supply beyond the 19V/2.1A rating (see the device model); the Ethernet port itself carries no PoE.
- It isn't documented in the sources checked whether the ChromeOS compute system this bar is paired with is supplied by Logitech, Google, or a separate vendor (for example a Chromebox); Aigna's procurement should confirm this per site.
Provision is the first step of Deploy: before or as each video bar arrives, every system gets its record, so the device is known the moment it is plugged in. It is ticked in the project's Deploy page; this is what each record needs.
Hostname
<site>-<room>-vcNN
For example dub-407-vc01: the site, the space number without its dot, vc for video bar, and the number in the space. Full name: …aigna.example.
Firmware
CollabOS 1.15+
CollabOS 1.15+ (for RightSight 2 / RightSound 2). Check it before configuring.
Licence and management
No licence named in this setup guide.
Managed in: Logitech Sync (Sync Portal / Sync App), plus the device's own Local Network Access web page.
AssetboxAsset register
assets/<asset tag>.json
Needs
- Asset tag
- Serial
- Model
- Space
- Status
- Hostname
Healthy when status is active; space matches where the device is installed.
InfoDNSAddresses and DNS
zones/aigna.example/<hostname>
Needs
- Hostname
- Mac address
- Ip address
Healthy when address reservation matches the MAC address; forward and reverse DNS records resolve.
Fleet LensDevice management
sites/<site>/devices/<hostname>.yaml
Needs
- Device name
- Serial
- Firmware version
Healthy when online in the vendor's device management service; firmware at the fleet standard for the model; settings match the setup guide for the model.
AppStateRoom booking and signage fleet
rooms/<room id>.yaml
Needs
- Resource name
- Capacity
Healthy when room resource exists and is linked to the device; capacity matches the space.
Monitor DogMonitoring
checks/<hostname>.yml
Needs
- Monitor name
Healthy when reporting; no open critical alerts.
Google Admin console > Devices > Google Meet hardware1 of 1 to set or verify1 settings · CollabOS 1.15+ (for RightSight 2 / RightSound 2)
Google Admin console > Devices > Google Meet hardware › Google Meet hardware (Google Admin console)
- SetEnroll a device with a codeDevice name: the hostname (of the paired ChromeOS compute system)
Device settings1 of 1 to set or verify1 settings · CollabOS 1.15+ (for RightSight 2 / RightSound 2)
Device settings › Calendar
- SetRoom calendarThe space's calendar resource
Settings2 of 2 to set or verify2 settings · CollabOS 1.15+ (for RightSight 2 / RightSound 2)
Settings › Device settings
- SetTime zoneThe site's time zone
- SetScheduled rebootDaily, inside the maintenance hours
Devices1 of 1 to set or verify1 settings · CollabOS 1.15+ (for RightSight 2 / RightSound 2)
Devices › Google Meet hardware › Settings › Camera settings
- SetDefault Camera FramingManufacturer framing
Logitech Sync App / Sync Portal > Device > Camera1 of 1 to set or verify1 settings · CollabOS 1.15+ (for RightSight 2 / RightSound 2)
Logitech Sync App / Sync Portal > Device > Camera › Camera (Logitech Sync)
- SetRightSight 2Enabled, Speaker View
System1 of 1 to set or verify1 settings · CollabOS 1.15+ (for RightSight 2 / RightSound 2)
System › More settings
- SetLocal Network AccessOn
MeetUp 2's own web interface (Local Network Access, by IP address)1 of 1 to set or verify1 settings · CollabOS 1.15+ (for RightSight 2 / RightSound 2)
MeetUp 2's own web interface (Local Network Access, by IP address) › Security and network (Local Network Access)
- SetAdmin passwordFrom the password vault, per site
Local Network Access2 of 2 to set or verify2 settings · CollabOS 1.15+ (for RightSight 2 / RightSound 2)
Local Network Access › System settings
- SetInternet Time (NTP)ntp1.aigna.example
Local Network Access › Network
- VerifyTCP/IP (IPv4 addressing)Auto DHCP
Inventory1 of 1 to set or verify1 settings · CollabOS 1.15+ (for RightSight 2 / RightSound 2)
Inventory › Room › Update
- VerifyFirmware updateManually scheduled, after the Lab passes it
Where dub-407-vc01 (4.07 Goldfinch, Dublin office) is recorded in each system, against what Keia Atlas expects. Simulated values.-found +expected
AssetboxAsset registerIn sync
# assets/AG-000393.json asset_tag: AG-000393 serial: DEMO-DUB-000393 model: Logitech MeetUp 2 location: Dublin office, 4.07 Goldfinch status: In service
InfoDNSAddresses and DNSDrifted
# zones/aigna.example/dub-407-vc01 fqdn: dub-407-vc01.aigna.example-address: 10.20.4.49+address: 10.20.4.48 mac: 02:1c:8d:df:ba:d1 reservation: yes
Fleet LensDevice managementIn sync
# sites/dub/devices/dub-407-vc01.yaml name: dub-407-vc01 firmware: not tracked policy: Dublin office site
AppStateRoom booking and signage fleetIn sync
# rooms/dub-4-07.yaml room: 4.07 Goldfinch resource: dub-4-07@resource.aigna.example device: dub-407-vc01
Monitor DogMonitoringIn sync
# checks/dub-407-vc01.yml host: dub-407-vc01.aigna.example checks: ping, https alerts_to: av-dub
DarkSignSignage playersNot used
No record: video bars are not kept in DarkSign.
Being configured now
In each project's Deploy pageUnits running it
17 in service · 1 drifted · simulated check| Unit | Space | Office | Model | Status | Records |
|---|---|---|---|---|---|
| Goldfinch video bardub-407-vc01 | 4.07 Goldfinch | Dublin office | Logitech MeetUp 2 | In service | InfoDNS record drifted |
| Goldcrest video barchi-1307-vc01 | 13.07 Goldcrest | Chicago office | Logitech MeetUp 2 | In service | In sync |
| Stonechat video barchi-1308-vc01 | 13.08 Stonechat | Chicago office | Logitech MeetUp 2 | In service | In sync |
| Goldfinch video barchi-1309-vc01 | 13.09 Goldfinch | Chicago office | Logitech MeetUp 2 | In service | In sync |
| Robin video barcph-410-vc01 | 4.10 Robin | Copenhagen office | Logitech MeetUp 2 | In service | In sync |
| Goldcrest video barcph-411-vc01 | 4.11 Goldcrest | Copenhagen office | Logitech MeetUp 2 | In service | In sync |
| Chaffinch video bardub-408-vc01 | 4.08 Chaffinch | Dublin office | Logitech MeetUp 2 | In service | In sync |
| Robin video barmel-810-vc01 | 8.10 Robin | Melbourne office | Logitech MeetUp 2 | In service | In sync |
| Stonechat video barnyc-2109-vc01 | 21.09 Stonechat | New York office | Logitech MeetUp 2 | In service | In sync |
| Goldfinch video barnyc-2110-vc01 | 21.10 Goldfinch | New York office | Logitech MeetUp 2 | In service | In sync |
| Chaffinch video barnyc-2111-vc01 | 21.11 Chaffinch | New York office | Logitech MeetUp 2 | In service | In sync |
| Siskin video barnyc-2207-vc01 | 22.07 Siskin | New York office | Logitech MeetUp 2 | In service | In sync |
| Linnet video barnyc-2208-vc01 | 22.08 Linnet | New York office | Logitech MeetUp 2 | In service | In sync |
| Treecreeper video barnyc-2209-vc01 | 22.09 Treecreeper | New York office | Logitech MeetUp 2 | In service | In sync |
| Blue Tit video barnyc-2210-vc01 | 22.10 Blue Tit | New York office | Logitech MeetUp 2 | In service | In sync |
| Goldcrest video bartyo-1510-vc01 | 15.10 Goldcrest | Tokyo office | Logitech MeetUp 2 | In service | In sync |
| Stonechat video bartyo-1511-vc01 | 15.11 Stonechat | Tokyo office | Logitech MeetUp 2 | In service | In sync |
| Wren video barjnu-203-vc01 | 2.03 Wren | Juneau office | Logitech MeetUp 2 | Being installed | Checked when live |