Dec 15 00:33:10 wirenboard-AHDPBCQU mosquitto[22359]: 1702589590: Client <unknown> disconnected due to protocol error.
Dec 15 00:33:14 wirenboard-AHDPBCQU mosquitto[22359]: 1702589593: Client <unknown> closed its connection.
Dec 15 00:33:14 wirenboard-AHDPBCQU mosquitto[22359]: 1702589594: New connection from 172.233.58.223:50778 on port 1883.
Dec 15 00:33:14 wirenboard-AHDPBCQU mosquitto[22359]: 1702589594: Client <unknown> disconnected due to protocol error.
Dec 15 05:08:16 wirenboard-AHDPBCQU mosquitto[22359]: 1702606096: New connection from 167.248.133.185:48228 on port 1883.
Dec 15 05:08:16 wirenboard-AHDPBCQU mosquitto[22359]: 1702606096: Client <unknown> disconnected, not authorised.
Dec 15 07:26:59 wirenboard-AHDPBCQU mosquitto[22359]: 1702614419: New client connected from ::ffff:10.8.1.98:62767 as wb-mqtt-homeui-DTHrRxQRgd (p2, c1, k60, u’root’).
Dec 15 07:26:59 wirenboard-AHDPBCQU mosquitto[22359]: 1702614419: New client connected from ::ffff:10.8.1.98:62774 as wb-mqtt-homeui-hKyg4WE1Tq (p2, c1, k60, u’root’).
Dec 15 07:30:22 wirenboard-AHDPBCQU mosquitto[22359]: 1702614622: New connection from 10.8.1.98:63095 on port 1883.
Dec 15 07:30:22 wirenboard-AHDPBCQU mosquitto[22359]: 1702614622: New client connected from 10.8.1.98:63095 as mqtt-explorer-bdeb35f1 (p2, c1, k60, u’root’).
systemctl status wb-mqtt-logs
root@wirenboard-AHDPBCQU:~# systemctl status wb-mqtt-logs
● wb-mqtt-logs.service - Wiren Board journald to MQTT gateway
Loaded: loaded (/lib/systemd/system/wb-mqtt-logs.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2023-12-14 11:37:28 MSK; 19h ago
Main PID: 24163 (wb-logs main)
Tasks: 5 (limit: 1146)
Memory: 1.6M
CPU: 1.000s
CGroup: /system.slice/wb-mqtt-logs.service
└─24163 /usr/bin/wb-mqtt-logs
Dec 14 11:37:28 wirenboard-AHDPBCQU systemd[1]: Started Wiren Board journald to MQTT gateway.
Dec 14 11:37:28 wirenboard-AHDPBCQU wb-mqtt-logs[24163]: MQTT broker localhost:1883
Dec 14 11:37:28 wirenboard-AHDPBCQU wb-mqtt-logs[24163]: INFO: [mqtt] Default host and port detected, checking if UNIX socket exists on /var/run/mosquitto/mosquitto.sock
Dec 14 11:37:28 wirenboard-AHDPBCQU wb-mqtt-logs[24163]: INFO: [mqtt] UNIX socket exists, using it for connection
Dec 14 11:37:28 wirenboard-AHDPBCQU wb-mqtt-logs[24163]: INFO: [mqtt] connection estabilished with code “0” <success>
Dec 14 11:37:28 wirenboard-AHDPBCQU wb-mqtt-logs[24163]: INFO: [mqtt] subscription succeeded (message id 1)
Dec 14 11:37:28 wirenboard-AHDPBCQU wb-mqtt-logs[24163]: INFO: [mqtt] subscription succeeded (message id 2)
Dec 14 11:37:28 wirenboard-AHDPBCQU wb-mqtt-logs[24163]: INFO: [mqtt] subscription succeeded (message id 3)
systemctl status wb-mqtt-serial
root@wirenboard-AHDPBCQU:~# systemctl status wb-mqtt-serial
● wb-mqtt-serial.service - MQTT Driver for serial devices
Loaded: loaded (/lib/systemd/system/wb-mqtt-serial.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2023-12-14 09:25:24 MSK; 22h ago
Main PID: 28014 (wb-mqtt-serial)
Tasks: 10 (limit: 1146)
Memory: 9.9M
CPU: 3h 2min 20.626s
CGroup: /system.slice/wb-mqtt-serial.service
└─28014 /usr/bin/wb-mqtt-serial
Dec 14 11:57:55 wirenboard-AHDPBCQU wb-mqtt-serial[28014]: WARNING: [modbus] failed to read 6 discrete(s) @ 0 of device modbus:79: Serial protocol error: malformed response: invalid crc
Dec 14 11:57:55 wirenboard-AHDPBCQU wb-mqtt-serial[28014]: WARNING: [modbus] failed to read 1 input(s) @ 283 of device modbus:73: Serial protocol error: malformed response: invalid crc
Dec 14 13:17:55 wirenboard-AHDPBCQU wb-mqtt-serial[28014]: WARNING: [modbus] failed to read 1 input(s) @ 280 of device modbus:111: Serial protocol error: malformed response: invalid crc
Dec 14 15:47:55 wirenboard-AHDPBCQU wb-mqtt-serial[28014]: WARNING: [modbus] failed to read 1 input(s) @ 14013 of device modbus:1: Serial protocol error: malformed response: invalid data size
Dec 14 18:17:55 wirenboard-AHDPBCQU wb-mqtt-serial[28014]: WARNING: [modbus] failed to read 2 input(s) @ 270 of device modbus:41: Serial protocol error: malformed response: invalid crc
Dec 14 20:37:55 wirenboard-AHDPBCQU wb-mqtt-serial[28014]: WARNING: [modbus] failed to read 1 input(s) @ 32 of device modbus:41: Serial protocol error: malformed response: invalid crc
Dec 15 00:47:40 wirenboard-AHDPBCQU wb-mqtt-serial[28014]: WARNING: [serial client] </dev/ttyRS485-2 9600 8 N 2> Register read rate limit is exceeded
Dec 15 03:07:56 wirenboard-AHDPBCQU wb-mqtt-serial[28014]: WARNING: [modbus] failed to read 1 input(s) @ 280 of device modbus:65: Serial protocol error: malformed response: invalid crc
Dec 15 03:27:56 wirenboard-AHDPBCQU wb-mqtt-serial[28014]: WARNING: [modbus] failed to read 2 input(s) @ 9 of device modbus:65: Serial protocol error: malformed response: invalid crc
Dec 15 05:17:56 wirenboard-AHDPBCQU wb-mqtt-serial[28014]: WARNING: [modbus] failed to read 1 discrete(s) @ 0 of device modbus:41: Serial protocol error: malformed response: invalid crc
Пока не вносил никаких исправлений со вчерашнего дня
Утренний диагностический архив
приложен диагностический архив, доступен только сотрудникам поддержки
(222,5 КБ)
Какие посоветуете произвести первичные действия для выявления причин пропадания топиков?
Dec 14 09:25:23 wirenboard-AHDPBCQU wb-mqtt-serial[1861]: ERROR: [driver] Failed to accept 'on' value for control "Buzzer" of device "wb-msw-v3_73": Control "Buzzer" of device "wb-msw-v3_73" was deleted @ wblib/control.cpp:171
То есть топик устройства был создан в процессе запуска wb-mqtt-serial и затем штатно удален при завершении сервиса,
Я вижу топики всех устройств, причем с meta. Эти топики видно в “настройки - Каналы MQTT?”
Ну и, традициоонно - используя другой компьютер или телефон?
Обновлялось все fit’om через WebUI
Теперь обновил apt’ом еще три файла, в том числе и wb-mqtt-homeui
На всякий случай забэкапил wb-webui.conf и подставил чистый из обновления.
Перезагрузил
Завтра снова проверю
