chenjintao/lucky-cat
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix(config): migrate device API URLs to kikivok domain

Browse Source
This commit is contained in:
chenjintao
2026-10-23 14:30:30 +08:00
parent efd7aac623
commit 6d103938ab
10 changed files with 19 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/device-fortune-controller-api.md
+5 -5
View File
@@ -14,7 +14,7 @@
The complete path through the gateway is normally:
```text
POST https://gz.api.talkingq.com/token/api/device/fortune/daily-wealth
POST https://gz.api.kikivok.com/token/api/device/fortune/daily-wealth
```
When connecting directly to the token service, use its deployed port, for example:
@@ -91,7 +91,7 @@ The response field names are part of the current server contract and are intenti
### Windows PowerShell
```powershell
curl.exe -X POST "https://gz.api.talkingq.com/token/api/device/fortune/daily-wealth" `
curl.exe -X POST "https://gz.api.kikivok.com/token/api/device/fortune/daily-wealth" `
-H "Content-Type: application/json" `
-d "{\"deviceId\":\"test-device\",\"birthYear\":1998,\"birthMonth\":5,\"birthDay\":21,\"birthHour\":14,\"birthMinute\":30,\"birthPlace\":\"广东省广州市\",\"currentResidence\":\"广东省深圳市\",\"mbti\":\"INFJ\",\"timezone\":\"Asia/Shanghai\",\"targetDate\":\"2026-06-08\"}"
```
@@ -99,7 +99,7 @@ curl.exe -X POST "https://gz.api.talkingq.com/token/api/device/fortune/daily-wea
### Linux and macOS
```bash
curl -X POST "https://gz.api.talkingq.com/token/api/device/fortune/daily-wealth" \
curl -X POST "https://gz.api.kikivok.com/token/api/device/fortune/daily-wealth" \
-H "Content-Type: application/json" \
-d '{
"deviceId": "test-device",
@@ -118,11 +118,11 @@ curl -X POST "https://gz.api.talkingq.com/token/api/device/fortune/daily-wealth"
### HTTP
Send this HTTP/1.1 request over TLS to `gz.api.talkingq.com`:
Send this HTTP/1.1 request over TLS to `gz.api.kikivok.com`:
```http
POST /token/api/device/fortune/daily-wealth HTTP/1.1
Host: gz.api.talkingq.com
Host: gz.api.kikivok.com
Content-Type: application/json
{
docs/knowledge vault/device-auth-v2-flow.zh-CN.md
+1 -1
View File
@@ -695,7 +695,7 @@ control_plane_multimodal_auth_fetch();
再请求：
```text
POST https://gz.api.talkingq.com/token/api/device/token
POST https://gz.api.kikivok.com/token/api/device/token
```
请求头：
docs/knowledge vault/runtime-diagnostics-and-network-recovery-config.md
+1 -1
View File
@@ -121,7 +121,7 @@ The 2026-08-12 device log captured the complete failure and recovery chain:
1. Downstream TTS audio stopped arriving and the three-second playback watchdog
retired the unresponsive WebSocket after its bounded Stop acknowledgement
also timed out.
2. The token HTTPS preflight failed to resolve `gz.api.talkingq.com`. The STA
2. The token HTTPS preflight failed to resolve `gz.api.kikivok.com`. The STA
still reported an IP address, DHCP state, strong RSSI (`-38` to `-41 dBm`),
and configured DNS servers.
3. The gateway and fallback-DNS probes received no reply. More importantly, a
docs/knowledge vault/websocket-and-audio-flow.md
+1 -1
View File
@@ -91,7 +91,7 @@ sequenceDiagram
| `CONFIG_MULTIMODAL_USE_STATIC_CREDENTIALS` | 未启用 | 不直接使用静态 API Key |
| `CONFIG_MULTIMODAL_AUTH_BYPASS_TOKEN_SERVICE` | 未启用 | 不绕过设备 Token 服务 |
| `CONFIG_AUTH_V2_ENABLE` | `y` | 获取业务 Token 时使用设备 JWT 鉴权 |
| `CONFIG_MULTIMODAL_DEVICE_TOKEN_URL` | `https://gz.api.talkingq.com/token/api/device/token` | 设备业务 Token 接口 |
| `CONFIG_MULTIMODAL_DEVICE_TOKEN_URL` | `https://gz.api.kikivok.com/token/api/device/token` | 设备业务 Token 接口 |
| `CONFIG_MULTIMODAL_WS_URI` | `wss://dashscope.aliyuncs.com/api-ws/v1/inference` | 多模态 WebSocket 地址 |
| `CONFIG_MULTIMODAL_CONNECT_TIMEOUT_MS` | `10000` | 建连网络超时，10 秒 |
| `CONFIG_MULTIMODAL_RECONNECT_DELAY_MS` | `2000` | WebSocket 自动重连间隔，2 秒 |