Подключил контроллер к другому аккаунту и через пару дней он ушёл в какую-то ошибку
Добрый день!
Перенёс ваш вопрос в новую ветку обсуждений согласно правилам портала.
Для диагностики проблемы пришлите, пожалуйста, архив с диагностической информацией контроллера. Создание архива описано в документации.
Вот архив
diag_output_A2TGS2AG_2025-08-11-20.44.27.zip (194,7 КБ)
Добрый день!
Я верно понимаю, что проблема сохраняется, но доступ к контроллеру есть?
Да
Добрый день!
Прошу выполнить диагностические команды облачного сервиса и прислать вывод.
Также рекомендую проверить устройства на шине — наблюдаю большое количество ошибок.
Aug 08 13:04:11 wirenboard-A2TGS2AG wb-mqtt-serial[1818]: WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
Aug 08 13:04:16 wirenboard-A2TGS2AG wb-mqtt-serial[1818]: WARNING: </dev/ttyRS485-1 9600 8 N 2>: closed due to repetitive errors
Добрый день, удалось ли решить вопрос?
Пока не было времени. К концу недели займусь
1 лайк
- Вот вывод диагностических команд
root@wirenboard-A2TGS2AG:~# ping 8.8.8.8 -c 4
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=22.7 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=22.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=22.8 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=22.5 ms
root@wirenboard-A2TGS2AG:~# traceroute wirenboard.cloud
traceroute to wirenboard.cloud (5.35.10.8), 30 hops max, 60 byte packets
1 router.msk (192.168.0.1) 0.385 ms 0.326 ms 0.339 ms
2 123.456.789.222 (123.456.789.222) 2.223 ms 2.115 ms 2.016 ms
3 10.149.250.6 (10.149.250.6) 2.242 ms 2.119 ms 1.999 ms
4 as49505.ix.dataix.eu (178.18.224.197) 3.303 ms 3.574 ms 3.478 ms
5 92.53.94.76 (92.53.94.76) 2.838 ms 2.727 ms 2.637 ms
6 5.35.10.8 (5.35.10.8) 2.599 ms 2.859 ms 2.938 ms
7 * * *
8 * * *
27 * * *
28 * *^C
root@wirenboard-A2TGS2AG:~# host agent.wirenboard.cloud
agent.wirenboard.cloud is an alias for wirenboard.cloud.
wirenboard.cloud has address 5.35.10.8
root@wirenboard-A2TGS2AG:~# systemctl status wb-cloud-agent@wirenboard.cloud
● wb-cloud-agent@wirenboard.cloud.service - Wiren Board Cloud Agent (wirenboard.cloud)
Loaded: loaded (/lib/systemd/system/wb-cloud-agent@.service; disabled; vendor preset: enabled)
Active: inactive (dead)```
потом я попробовал запустить wb-cloud-agent, но не помогло
root@wirenboard-A2TGS2AG:~# systemctl enable wb-cloud-agent@wirenboard.cloud
Created symlink /etc/systemd/system/multi-user.target.wants/wb-cloud-agent@wirenboard.cloud.service → /lib/systemd/system/wb-cloud-agent@.service.
root@wirenboard-A2TGS2AG:~# systemctl start wb-cloud-agent@wirenboard.cloud
root@wirenboard-A2TGS2AG:~# systemctl status wb-cloud-agent@wirenboard.cloud
● wb-cloud-agent@wirenboard.cloud.service - Wiren Board Cloud Agent (wirenboard.cloud)
Loaded: loaded (/lib/systemd/system/wb-cloud-agent@.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Condition: start condition failed at Wed 2025-08-20 21:25:48 MSK; 4s ago
└─ ConditionPathExistsGlob=/etc/wb-cloud-agent/providers/wirenboard.cloud/*.conf was not met
Aug 20 21:25:48 wirenboard-A2TGS2AG systemd[1]: Condition check resulted in Wiren Board Cloud Agent (wirenboard.cloud) being skipped.
root@wirenboard-A2TGS2AG:~# curl --connect-timeout 45 --retry 8 --retry-delay 1 --retry-all-errors --cert /var/lib/wb-cloud-agent/device_bundle.crt.pem --engine ateccx08 --key ATECCx08:00:02:C0:00 --key-type ENG -w '|||{"code":"%{response_code}"}' https://agent.wirenboard.cloud/api-agent/v1/agent-start-up/
curl: (58) could not load PEM client certificate, OpenSSL error error:02001002:system library:fopen:No such file or directory, (no key found, wrong pass phrase, or wrong file format?)
Warning: Problem (retrying all errors). Will retry in 1 seconds. 8 retries
Warning: left.
curl: (58) could not load PEM client certificate, OpenSSL error error:02001002:system library:fopen:No such file or directory, (no key found, wrong pass phrase, or wrong file format?)
Warning: Problem (retrying all errors). Will retry in 1 seconds. 7 retries
Warning: left.
curl: (58) could not load PEM client certificate, OpenSSL error error:02001002:system library:fopen:No such file or directory, (no key found, wrong pass phrase, or wrong file format?)
Warning: Problem (retrying all errors). Will retry in 1 seconds. 6 retries
Warning: left.
curl: (58) could not load PEM client certificate, OpenSSL error error:02001002:system library:fopen:No such file or directory, (no key found, wrong pass phrase, or wrong file format?)
Warning: Problem (retrying all errors). Will retry in 1 seconds. 5 retries
Warning: left.
curl: (58) could not load PEM client certificate, OpenSSL error error:02001002:system library:fopen:No such file or directory, (no key found, wrong pass phrase, or wrong file format?)
Warning: Problem (retrying all errors). Will retry in 1 seconds. 4 retries
Warning: left.
curl: (58) could not load PEM client certificate, OpenSSL error error:02001002:system library:fopen:No such file or directory, (no key found, wrong pass phrase, or wrong file format?)
Warning: Problem (retrying all errors). Will retry in 1 seconds. 3 retries
Warning: left.
curl: (58) could not load PEM client certificate, OpenSSL error error:02001002:system library:fopen:No such file or directory, (no key found, wrong pass phrase, or wrong file format?)
Warning: Problem (retrying all errors). Will retry in 1 seconds. 2 retries
Warning: left.
curl: (58) could not load PEM client certificate, OpenSSL error error:02001002:system library:fopen:No such file or directory, (no key found, wrong pass phrase, or wrong file format?)
Warning: Problem (retrying all errors). Will retry in 1 seconds. 1 retries
Warning: left.
curl: (58) could not load PEM client certificate, OpenSSL error error:02001002:system library:fopen:No such file or directory, (no key found, wrong pass phrase, or wrong file format?)
- Что значит проверить устройства на шине? Что делать? Как проверять?
У меня к контроллеру подключено всего 5 устройств: пристыковано 3 модуля в боковой порт и 2 устройства на шине: WB-MAI6 и WBIO-DO-SSR-8 (через WB-MIO-E v.2)
Добрый день!
Благодарю за предоставленную диагностику. Потребуется некоторое время, чтобы подготовить ответ.
Добрый день!
Прошу прислать вывод команды:
ls -lah /var/lib/wb-cloud-agent
Также попробуйте переустановить агент для восстановления его работоспособности.
ls: cannot access '/var/lib/wb-cloud-agent': No such file or directory
Добрый день! Подскажите почему у меня в сообщении “WARNING”?
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: driver loop is started
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: wait for driver to become ready
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: driver is ready
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: [rule info] using file /var/lib/wirenboard/wbrules-persistent.db for persistent DB
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: [wbgo_mqtt] wb-rules-engine-wirenboard-ADAP4RKC-2027: MQTT connection established
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: [engine] Starting main loop
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: the engine is ready
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: [engine] Starting sync loop
Aug 21 15:57:14 wirenboard-ADAP4RKC wb-rules[2027]: WARNING: [rule warning] DAC: no config file
Aug 21 15:57:14 wirenboard-ADAP4RKC wb-rules[2027]: INFO: all rule files are loaded
Добрый день!
Выполните, пожалуйста:
dpkg -s wb-suite
Если пакет отсутствует — потребуется его установка.
Затем выполните:
apt update && apt reinstall wb-cloud-agent
Package: wb-suite
Status: install ok installed
Priority: standard
Section: metapackages
Installed-Size: 8
Maintainer: Wiren Board team info@wirenboard.com
Architecture: all
Source: wb-metapackages
Version: 1.19.8
Depends: wb-essential, wb-knxd-config, wb-update-manager, wb-nm-helper, wb-mqtt-w1, wb-mqtt-gpio, wb-mqtt-adc, wb-mqtt-serial, wb-mqtt-dac, wb-rules, wb-rules-system, wb-mqtt-db, wb-mqtt-db-cli, wb-mqtt-mbgate, wb-mqtt-homeui, wb-mqtt-knx, wb-mcu-fw-flasher, wb-mcu-fw-updater, wb-device-manager, wb-mqtt-confed, wb-mqtt-opcua, wb-mqtt-logs, wb-diag-collect, wb-mqtt-metrics, wb-mqtt-iec104, wb-cloud-agent, wb-scenarios
Recommends: wb-update-notifier, mc, gpiod, modbus-utils-rpc, serial-tool, mmc-utils, python3-serial, wb-modbus-ext-scanner
Breaks: wb-test-suite-deps (<= 1.12.0)
Description: Wirenboard vendor software set
This metapackage pulls in all the packages from Wirenboard vendor
Homepage: GitHub - wirenboard/wb-metapackages: Metapackages to manage Wirenboard software installation
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: wait for driver to become ready
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: driver is ready
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: [rule info] using file /var/lib/wirenboard/wbrules-persistent.db for persistent DB
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: [wbgo_mqtt] wb-rules-engine-wirenboard-ADAP4RKC-2027: MQTT connection established
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: [engine] Starting main loop
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: the engine is ready
Aug 21 15:57:12 wirenboard-ADAP4RKC wb-rules[2027]: INFO: [engine] Starting sync loop
Aug 21 15:57:14 wirenboard-ADAP4RKC wb-rules[2027]: WARNING: [rule warning] DAC: no config file
Aug 21 15:57:14 wirenboard-ADAP4RKC wb-rules[2027]: INFO: all rule files are loaded
Aug 21 15:58:28 wirenboard-ADAP4RKC wb-rules[2027]: INFO: reloading file: /etc/wb-rules/rules.js
Тоже самое
Посовещаюсь с коллегами и вернусь к вам с ответом.
Добрый день!
Можем запланировать подключение через AnyDesk сегодня или в понедельник — уточните, когда будет удобнее.
Добрый день! Можно сегодня, я в принципе готов.
Готов подключиться, пришлите в ЛС номер для подключения.