| Author | ![[]](/git/avatar/c50933ca2aa61e0fe2c43d46bb6b59cb_avatar){kind=avatar} Andy Green <andy@warmcat.com> 2026-09-21 05:51 UTC |
| Committer | Andy Green <andy@warmcat.com> 2026-09-21 07:08 UTC |
| Tree | 784aa1d7e78d9216cb76c864ed67605dc3bf99e3 |
etc-sai-EXAMPLE: point the sai-power and sai-virt server urls at /sai/power Both examples told the daemons to connect to wss://.../sai/builder, but sai-power and sai-virt speak the /power endpoint's message family (stay info, pcon linkstate, pending task lists) and are only classified as power peers by the /power path; a deployment following the examples gets its power messages routed into the builder rx path and ignored. Real deployments use /sai/power for both, so make the examples match. | |
diff --git a/etc-sai-EXAMPLE/power/conf b/etc-sai-EXAMPLE/power/conf index 157508f..b9525b7 100644 --- a/etc-sai-EXAMPLE/power/conf +++ b/etc-sai-EXAMPLE/power/conf @@ -9,7 +9,7 @@ "servers": [ { - "url" : "wss://libwebsockets.org:4444/sai/builder", + "url" : "wss://libwebsockets.org:4444/sai/power", "power_controllers": [ { diff --git a/etc-sai-EXAMPLE/virt/conf b/etc-sai-EXAMPLE/virt/conf index 975df3f..ecb576b 100644 --- a/etc-sai-EXAMPLE/virt/conf +++ b/etc-sai-EXAMPLE/virt/conf @@ -11,7 +11,7 @@ "servers": [ { - "url": "wss://libwebsockets.org:4444/sai/builder" + "url": "wss://libwebsockets.org:4444/sai/power" } ],