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

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
@@ -35,7 +35,7 @@
#endif #endif
#ifndef CONFIG_MULTIMODAL_DEVICE_TOKEN_URL #ifndef CONFIG_MULTIMODAL_DEVICE_TOKEN_URL
#define CONFIG_MULTIMODAL_DEVICE_TOKEN_URL "https://gz.api.talkingq.com/token/api/device/token" #define CONFIG_MULTIMODAL_DEVICE_TOKEN_URL "https://gz.api.kikivok.com/token/api/device/token"
#endif #endif
#ifndef CONFIG_MULTIMODAL_USE_STATIC_CREDENTIALS #ifndef CONFIG_MULTIMODAL_USE_STATIC_CREDENTIALS
@@ -42,7 +42,7 @@
#include "soc/soc_caps.h" #include "soc/soc_caps.h"
#ifndef CONFIG_AUTH_REGISTER_BASE_URL #ifndef CONFIG_AUTH_REGISTER_BASE_URL
#define CONFIG_AUTH_REGISTER_BASE_URL "https://gz.api.talkingq.com/register" #define CONFIG_AUTH_REGISTER_BASE_URL "https://gz.api.kikivok.com/register"
#endif #endif
#ifndef CONFIG_AUTH_CHALLENGE_PATH #ifndef CONFIG_AUTH_CHALLENGE_PATH
@@ -27,7 +27,7 @@
#include "soc/soc_caps.h" #include "soc/soc_caps.h"
#ifndef CONFIG_FORTUNE_API_URL #ifndef CONFIG_FORTUNE_API_URL
#define CONFIG_FORTUNE_API_URL "https://gz.api.talkingq.com/token/api/device/fortune/daily-wealth" #define CONFIG_FORTUNE_API_URL "https://gz.api.kikivok.com/token/api/device/fortune/daily-wealth"
#endif #endif
#ifndef CONFIG_FORTUNE_TIMEZONE #ifndef CONFIG_FORTUNE_TIMEZONE
@@ -32,7 +32,7 @@
#define CONFIG_TQ_OTA_ENABLE 0 #define CONFIG_TQ_OTA_ENABLE 0
#endif #endif
#ifndef CONFIG_TQ_OTA_REPORT_URL #ifndef CONFIG_TQ_OTA_REPORT_URL
#define CONFIG_TQ_OTA_REPORT_URL "https://gz.api.talkingq.com/ota/api/ota/versionInfoReport" #define CONFIG_TQ_OTA_REPORT_URL "https://gz.api.kikivok.com/ota/api/ota/versionInfoReport"
#endif #endif
#ifndef CONFIG_TQ_OTA_INTERNAL_AUTH_SECRET #ifndef CONFIG_TQ_OTA_INTERNAL_AUTH_SECRET
#define CONFIG_TQ_OTA_INTERNAL_AUTH_SECRET "" #define CONFIG_TQ_OTA_INTERNAL_AUTH_SECRET ""
+5 -5
View File
@@ -14,7 +14,7 @@
The complete path through the gateway is normally: The complete path through the gateway is normally:
```text ```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: 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 ### Windows PowerShell
```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" ` -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\"}" -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 ### Linux and macOS
```bash ```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" \ -H "Content-Type: application/json" \
-d '{ -d '{
"deviceId": "test-device", "deviceId": "test-device",
@@ -118,11 +118,11 @@ curl -X POST "https://gz.api.talkingq.com/token/api/device/fortune/daily-wealth"
### HTTP ### 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 ```http
POST /token/api/device/fortune/daily-wealth HTTP/1.1 POST /token/api/device/fortune/daily-wealth HTTP/1.1
Host: gz.api.talkingq.com Host: gz.api.kikivok.com
Content-Type: application/json Content-Type: application/json
{ {
@@ -695,7 +695,7 @@ control_plane_multimodal_auth_fetch();
再请求: 再请求:
```text ```text
POST https://gz.api.talkingq.com/token/api/device/token POST https://gz.api.kikivok.com/token/api/device/token
``` ```
请求头: 请求头:
@@ -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 1. Downstream TTS audio stopped arriving and the three-second playback watchdog
retired the unresponsive WebSocket after its bounded Stop acknowledgement retired the unresponsive WebSocket after its bounded Stop acknowledgement
also timed out. 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`), still reported an IP address, DHCP state, strong RSSI (`-38` to `-41 dBm`),
and configured DNS servers. and configured DNS servers.
3. The gateway and fallback-DNS probes received no reply. More importantly, a 3. The gateway and fallback-DNS probes received no reply. More importantly, a
@@ -91,7 +91,7 @@ sequenceDiagram
| `CONFIG_MULTIMODAL_USE_STATIC_CREDENTIALS` | 未启用 | 不直接使用静态 API Key | | `CONFIG_MULTIMODAL_USE_STATIC_CREDENTIALS` | 未启用 | 不直接使用静态 API Key |
| `CONFIG_MULTIMODAL_AUTH_BYPASS_TOKEN_SERVICE` | 未启用 | 不绕过设备 Token 服务 | | `CONFIG_MULTIMODAL_AUTH_BYPASS_TOKEN_SERVICE` | 未启用 | 不绕过设备 Token 服务 |
| `CONFIG_AUTH_V2_ENABLE` | `y` | 获取业务 Token 时使用设备 JWT 鉴权 | | `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_WS_URI` | `wss://dashscope.aliyuncs.com/api-ws/v1/inference` | 多模态 WebSocket 地址 |
| `CONFIG_MULTIMODAL_CONNECT_TIMEOUT_MS` | `10000` | 建连网络超时,10 秒 | | `CONFIG_MULTIMODAL_CONNECT_TIMEOUT_MS` | `10000` | 建连网络超时,10 秒 |
| `CONFIG_MULTIMODAL_RECONNECT_DELAY_MS` | `2000` | WebSocket 自动重连间隔,2 秒 | | `CONFIG_MULTIMODAL_RECONNECT_DELAY_MS` | `2000` | WebSocket 自动重连间隔,2 秒 |
+4 -4
View File
@@ -73,7 +73,7 @@ menu "TQ Cat Configuration"
config TQ_OTA_REPORT_URL config TQ_OTA_REPORT_URL
string "OTA version report URL" string "OTA version report URL"
default "https://gz.api.talkingq.com/ota/api/ota/versionInfoReport" default "https://gz.api.kikivok.com/ota/api/ota/versionInfoReport"
depends on TQ_OTA_ENABLE depends on TQ_OTA_ENABLE
config TQ_OTA_INTERNAL_AUTH_SECRET config TQ_OTA_INTERNAL_AUTH_SECRET
@@ -1160,7 +1160,7 @@ menu "TQ Cat Configuration"
config FORTUNE_API_URL config FORTUNE_API_URL
string "Daily fortune API URL" string "Daily fortune API URL"
depends on FORTUNE_ENABLE depends on FORTUNE_ENABLE
default "https://gz.api.talkingq.com/token/api/device/fortune/daily-wealth" default "https://gz.api.kikivok.com/token/api/device/fortune/daily-wealth"
help help
HTTPS endpoint used for the daily fortune POST request. HTTPS endpoint used for the daily fortune POST request.
@@ -1267,7 +1267,7 @@ menu "TQ Cat Configuration"
config MULTIMODAL_DEVICE_TOKEN_URL config MULTIMODAL_DEVICE_TOKEN_URL
string "Device token URL" string "Device token URL"
default "https://gz.api.talkingq.com/token/api/device/token" default "https://gz.api.kikivok.com/token/api/device/token"
help help
URL to request a temporary device token. Request body contains URL to request a temporary device token. Request body contains
deviceId / serialNumber in JSON. deviceId / serialNumber in JSON.
@@ -1310,7 +1310,7 @@ menu "TQ Cat Configuration"
config AUTH_REGISTER_BASE_URL config AUTH_REGISTER_BASE_URL
string "Auth V2 registration base URL" string "Auth V2 registration base URL"
depends on AUTH_V2_ENABLE depends on AUTH_V2_ENABLE
default "https://gz.api.talkingq.com/register" default "https://gz.api.kikivok.com/register"
help help
HTTPS base URL of the device registration / challenge-response HTTPS base URL of the device registration / challenge-response
backend. The engine appends /api/auth/challenge, backend. The engine appends /api/auth/challenge,
+3 -3
View File
@@ -97,7 +97,7 @@ CONFIG_TQ_SPEECH_ENDPOINT_MIN_SPEECH_MS=200
CONFIG_TQ_SPEECH_ENDPOINT_SILENCE_MS=900 CONFIG_TQ_SPEECH_ENDPOINT_SILENCE_MS=900
CONFIG_TQ_LOCAL_WAKE_ENABLE=y CONFIG_TQ_LOCAL_WAKE_ENABLE=y
CONFIG_TQ_OTA_ENABLE=y CONFIG_TQ_OTA_ENABLE=y
CONFIG_TQ_OTA_REPORT_URL="https://gz.api.talkingq.com/ota/api/ota/versionInfoReport" CONFIG_TQ_OTA_REPORT_URL="https://gz.api.kikivok.com/ota/api/ota/versionInfoReport"
CONFIG_TQ_OTA_POLL_INTERVAL_MS=21600000 CONFIG_TQ_OTA_POLL_INTERVAL_MS=21600000
CONFIG_TQ_OTA_CONFIRMATION_POLL_MS=21600000 CONFIG_TQ_OTA_CONFIRMATION_POLL_MS=21600000
CONFIG_TQ_OTA_HTTP_TIMEOUT_MS=15000 CONFIG_TQ_OTA_HTTP_TIMEOUT_MS=15000
@@ -176,9 +176,9 @@ CONFIG_MULTIMODAL_WIFI_SSID=""
CONFIG_MULTIMODAL_WIFI_PASSWORD="" CONFIG_MULTIMODAL_WIFI_PASSWORD=""
CONFIG_ESPTOOLPY_MONITOR_BAUD=115200 CONFIG_ESPTOOLPY_MONITOR_BAUD=115200
CONFIG_ESP_CONSOLE_UART_BAUDRATE=115200 CONFIG_ESP_CONSOLE_UART_BAUDRATE=115200
CONFIG_MULTIMODAL_DEVICE_TOKEN_URL="https://gz.api.talkingq.com/token/api/device/token" CONFIG_MULTIMODAL_DEVICE_TOKEN_URL="https://gz.api.kikivok.com/token/api/device/token"
CONFIG_FORTUNE_ENABLE=y CONFIG_FORTUNE_ENABLE=y
CONFIG_FORTUNE_API_URL="https://gz.api.talkingq.com/token/api/device/fortune/daily-wealth" CONFIG_FORTUNE_API_URL="https://gz.api.kikivok.com/token/api/device/fortune/daily-wealth"
CONFIG_FORTUNE_TIMEZONE="Asia/Shanghai" CONFIG_FORTUNE_TIMEZONE="Asia/Shanghai"
CONFIG_FORTUNE_CONNECT_TIMEOUT_MS=10000 CONFIG_FORTUNE_CONNECT_TIMEOUT_MS=10000
CONFIG_FORTUNE_USER_CONFIG_HTTP_PORT=80 CONFIG_FORTUNE_USER_CONFIG_HTTP_PORT=80