SECUREXSECURITY ENGINEERINGNVR 文档

MQTT

MQTT 用于 Securex NVR 与 Home Assistant、自动化服务和其他系统交换事件。

配置示例

mqtt:
  enabled: true
  host: 192.168.1.210
  port: 1883
  user: securex
  password: "YOUR_PASSWORD"
  topic_prefix: securex

MQTT disconnected

  1. 确认 Broker 地址和端口可达。
  2. 检查账号密码与 ACL。
  3. 确认 Broker 未要求 TLS 而客户端使用明文。
  4. 查看 Broker 与 Securex NVR 两侧日志。

MQTT

MQTT connects Securex NVR events and state to Home Assistant, automation systems, and external consumers. A stable broker connection is required for reliable event delivery.

Configuration

mqtt:
  enabled: true
  host: 192.168.1.210
  port: 1883
  user: securex
  password: ${MQTT_PASSWORD}
  topic_prefix: frigate

Connectivity

  • Use the broker IP/hostname reachable from the Securex host.
  • Verify port 1883 for plain MQTT or the TLS port chosen by your broker.
  • Use a dedicated account and keep the password in an environment variable.

Topics and automations

topic_prefix defines the root namespace. Existing Home Assistant automations may depend on this value, so changing it can make old subscriptions appear offline.

Troubleshooting

  • Disconnected/reconnect loop: verify broker, credentials, ACLs, and network.
  • Connected but no events: verify subscriptions and that the relevant event/object is actually produced.
  • Home Assistant entity missing: verify the integration configuration and topic prefix.

MQTT

MQTT conecta eventos y estado de Securex NVR con Home Assistant, automatizaciones y otros consumidores. Se necesita una conexión estable con el broker.

Configuración

mqtt:
  enabled: true
  host: 192.168.1.210
  port: 1883
  user: securex
  password: ${MQTT_PASSWORD}
  topic_prefix: frigate

Conectividad

  • Use una IP/host accesible desde Securex.
  • Compruebe el puerto del broker.
  • Use una cuenta dedicada y guarde la contraseña en una variable de entorno.

Topics y automatización

topic_prefix define el espacio de nombres. Cambiarlo puede romper suscripciones existentes.

Diagnóstico

  • Bucles de desconexión: broker, credenciales, ACL y red.
  • Conectado sin eventos: revise suscripciones y que el evento exista.
  • Entidad HA ausente: revise integración y topic prefix.
输入关键词开始搜索