mirror of
https://github.com/legop3/MultiRoombaRover.git
synced 2026-11-16 19:52:17 -05:00
roverstate yay yay. future implements for non-roomba rovers...
Container image / image (push) Failing after 54s
Container image / image (push) Failing after 54s
This commit is contained in:
@@ -18,7 +18,7 @@ Select the appropriate architecture binary on a rover. The default object suppli
|
||||
|
||||
## Connections and state
|
||||
|
||||
- `/rover`: existing control commands, acknowledgements, sensors, and operational toggle state. The planned full `roverState` replacement is not implemented yet.
|
||||
- `/rover`: control commands, acknowledgements, sensors, and complete `roverState` snapshots.
|
||||
- `/rover/management`: configuration hello, management commands/acknowledgements, host statistics, and daemon events.
|
||||
- Derive the management address from the configured `ws://host[:port]/rover` or `wss://host[:port]/rover` control URL; there is no second server address to maintain.
|
||||
- Management starts independently of hardware initialization and remains available after serial/peripheral startup failure.
|
||||
@@ -64,7 +64,7 @@ Do this on the intended server/rover, not the development machine:
|
||||
2. With an authenticated admin Socket.IO session, call `roverManagement:list` and `roverManagement:get`. Expect configuration and schema even when the rover's serial device cannot open.
|
||||
3. Change a harmless setting such as description in the returned full object and call `roverManagement:save`. Expect an acknowledgement, disconnect/reconnect, and a new hello containing that setting. Confirm `/etc/roverd.json` matches and survives a service restart.
|
||||
4. Submit an incomplete object. Expect an error, no file replacement, and no restart.
|
||||
5. Confirm host statistics and autocharge/watchdog/daemon notices still reach their existing UI/alert consumers through management. Headlight/laser state must remain on control.
|
||||
5. Confirm host statistics and autocharge/watchdog/daemon notices still reach their existing UI/alert consumers through management. Headlight/laser state must arrive as a complete `roverState` snapshot on control.
|
||||
6. Verify reboot/update requests use management, the normal user reboot restrictions still apply, and non-admin clients cannot read/save configuration or invoke the admin command endpoint.
|
||||
7. Confirm new movement commands cannot execute while a save/reboot/update is stopping the rover, and that control disconnect safety still works independently of management.
|
||||
|
||||
@@ -72,6 +72,8 @@ Record acknowledgement errors, reconnect hello contents, relevant journal/server
|
||||
|
||||
## Pending stages
|
||||
|
||||
Browser/live verification of the configuration page, shared `roverState`, YAML media catalogs/child supervision, universal ALSA routing, standalone bootstrap, and replacement update workflow remain pending. The current updater and systemd media supervisor have moved transport but retain their existing implementations until those stages.
|
||||
Browser/live verification of configuration and operational state, YAML media catalogs/child supervision, universal ALSA routing, standalone bootstrap, and replacement update workflow remain pending. The current updater and systemd media supervisor have moved transport but retain their existing implementations until those stages.
|
||||
|
||||
Apply-field targets the currently management-connected fleet. It clones each rover’s own configuration, replaces an existing field, and sends the complete object for rover-side validation. Inspect individual results for failures. Missing fields and changed connections are reported; offline changes are not queued. Paths traverse object fields, not array elements. Array-valued fields can be replaced as a whole.
|
||||
|
||||
Control state messages have the shape `{ "type": "roverState", "state": { "headlightOn": false, "laserOn": null } }`. Null indicates an unavailable role. Each message replaces the server object; disconnect clears it. The roster exposes `roverState` directly, rather than per-device `state` objects.
|
||||
|
||||
@@ -159,15 +159,15 @@ The order below is a working sequence, not a requirement to leave incompatible i
|
||||
- [x] Rename `pi/` to `rover/` and update references.
|
||||
- [x] Replace machine-specific build targets/tags with architecture-specific artifacts and resolve hardware support split.
|
||||
- [x] Group every native GPIO setting under the disabled-by-default Pi GPIO peripheral switch in the current configuration and samples.
|
||||
- [ ] Expose the grouped Pi GPIO configuration in the new JSON schema/UI.
|
||||
- [x] Expose the grouped Pi GPIO configuration in the new JSON schema/UI.
|
||||
- [x] Register Pi GPIO through the common peripheral provider path, including BRC lifecycle ownership and uniform role-conflict handling.
|
||||
- [ ] Connect peripheral operational state to the new shared `roverState` object.
|
||||
- [x] Connect peripheral operational state to the new shared `roverState` object.
|
||||
- [x] Gate GPIO provider registration, initialization, and BRC startup behind the parent switch; retain saved child settings. Hardware validation remains pending.
|
||||
- [x] Implement complete JSON configuration serialization, schema, validation, atomic saves, and restart flow (live save/reconnect verification pending).
|
||||
- [x] Implement separate management connection and in-memory server management state.
|
||||
- [x] Move reboot, update, media management, host statistics, and daemon status messages to management; update consumers. Preserve the separately authorized user reboot path.
|
||||
- [x] Separate management lifecycle from hardware startup failures (deployment verification pending).
|
||||
- [ ] Implement full-object `roverState` and consolidate server/UI operational-state consumers.
|
||||
- [x] Implement full-object `roverState` and consolidate server/UI operational-state consumers (live verification pending).
|
||||
- [ ] Add bundled YAML catalogs and one custom YAML profile per media category.
|
||||
- [ ] Preserve AIY HAT as an explicit profile and expose ordinary audio-device selection on every architecture, including TTS/horn/mixer paths.
|
||||
- [ ] Generate ALSA routing from shared input/output selections; connect microphone, TTS, horn, forwarded audio, and independent volume controls to the resulting logical devices.
|
||||
@@ -264,3 +264,12 @@ Verification for this stage:
|
||||
- Configuration UI/backend implementation is now present; end-to-end deployment verification remains pending. Profile/status/output controls, unified rover state, audio/media supervision, and bootstrap/update rework are still separate outstanding stages.
|
||||
|
||||
- Placement correction: rover configuration is embedded in the existing fleet management panel alongside the rover roster. Removed the separate administration tab.
|
||||
|
||||
### Unified operational state (2026-11-16)
|
||||
|
||||
- Roverd owns a complete `roverState` object with `headlightOn` and `laserOn`; null indicates an unavailable role. Sends on control connection/reconnection and logical changes. Pending notifications coalesce to the latest complete snapshot.
|
||||
- Server replaces one current object, exposes it in roster snapshots, and clears it on disconnect. Superseded sockets cannot overwrite state or remove a newer connection. Removed per-toggle event handling and separate server state stores.
|
||||
- Desktop/mobile/HUD controls, darkness reward restoration, and learning snapshots read the shared object. Telemetry and daemon management remain separate.
|
||||
- All four architecture binaries rebuilt successfully; focused frontend lint and server syntax checks passed. The two existing roster lifecycle tests passed after updating their state fixture. No new tests added.
|
||||
- Still verify live initial state, toggles through both GPIO/Firmata, reconnect state, disconnect clearing, and darkness restoration. Production UI assets have not been rebuilt.
|
||||
- Next implementation stage: YAML media profiles, command environments and child-process supervision, alongside the planned universal audio routing.
|
||||
|
||||
Reference in New Issue
Block a user