📝 docs: Modbus endpoint group (devices.md) #124
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/modbus-group"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Consolidate the Modbus endpoint group into one section of
devices.md(roadmap §2.4, issue #69):Closes #69.
Evidence
Live probe 2026-10-11 (END_USER session, reads only):
GET /api/gateways/modbus-configurations→200, 4 entries, keys exactly{id, name, label, port, slave, device_kinds}— matches the issue's field list; sample entry (vendor catalogue) included.GET /api/connectedobjects/{id}/modbus-expert/state-history→404, content-typeapplication/json, body = bare Spring array"No Modbus configuration associated with ConnectedObject id: {id}"— refines "404 on AZUREIOT": the trigger is no Modbus configuration, and the body is the #68 format with an extrafieldkey.scan-modbus-ip/POSTendpoints: documented from the 2026-08-15 recon (scan + writes not re-probed — avoids mutating the live install).Docs-only change, no code touched. Test suite: 139 passed (unchanged baseline).
Merge Danger
Door: two-way (docs-only, trivially revertible)
Blast Radius: none — documentation only.
WIP: 📝 docs: Modbus endpoint group (devices.md)to 📝 docs: Modbus endpoint group (devices.md)