Перестали работать аналоговые входы

Здравствуйте уважаемые.
Помогите пожалуйста решить проблему (сабж).

В UI всё красное:

В логах ошибки:


15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage3_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage1_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage2_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage4_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage5_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage8_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage3_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage1_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage2_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage4_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage5_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage8_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage3_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage1_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage2_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage4_raw
15-08-2025 13:00:26.702 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage5_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage8_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage3_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage1_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage2_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage4_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage5_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage8_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage3_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage1_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage2_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage4_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage5_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage8_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage3_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage1_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage2_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage4_raw
15-08-2025 13:00:26.658 [wb-mqtt-adc]	ERROR: [wb-adc] Can't open file:/sys/bus/iio/devices/iio:device0/in_voltage5_raw

О системе:

Спасибо!

Добрый день!

Для диагностики проблемы пришлите, пожалуйста, архив с диагностической информацией контроллера. Создание архива описано в документации.

root@wirenboard-A7IOITQU:~/diag# wb-diag-collect diag
Traceback (most recent call last):
File “/usr/bin/wb-diag-collect”, line 8, in
from wb.diag.diag_collect import main # pylint:disable=wrong-import-position
File “/usr/share/wb-diag-collect/wb/diag/diag_collect.py”, line 7, in
import yaml
ModuleNotFoundError: No module named ‘yaml’

Для решения проблемы с отсутствием модуля yaml следуйте следующим шагам:

Установите модуль yaml:
Откройте командную строку на контроллере и выполните команду:

apt update
apt install python3-yaml

Проверьте наличие других зависимостей:
Убедитесь, что все остальные зависимости пакета wb-diag-collect установлены корректно.

Перезапустите службу:
После установки модуля, перезапустите службу wb-mqtt-adc:

systemctl restart wb-mqtt-adc

Если после этого проблема сохраняется, попробуйте еще раз создать диагностический архив и проверить логи на наличие других ошибок.

проблема с зависимостями остаётся

root@wirenboard-A7IOITQU:~/diag# apt install python3-mqttrpc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
python3-mqttrpc is already the newest version (1.3.2).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
root@wirenboard-A7IOITQU:~/diag# wb-diag-collect diag
Traceback (most recent call last):
  File "/usr/bin/wb-diag-collect", line 8, in <module>
    from wb.diag.diag_collect import main  # pylint:disable=wrong-import-position
  File "/usr/share/wb-diag-collect/wb/diag/diag_collect.py", line 10, in <module>
    from wb.diag import collector, rpc_server
  File "/usr/share/wb-diag-collect/wb/diag/rpc_server.py", line 10, in <module>
    from mqttrpc import dispatcher
ModuleNotFoundError: No module named 'mqttrpc'

с обновлением тоже не всё гладко:

root@wirenboard-A7IOITQU:~/diag# apt update
Hit:1 https://debian-mirror.wirenboard.com/debian bullseye InRelease                                          
Hit:4 https://deb.wirenboard.com/wb6/bullseye stable InRelease                                                
Hit:2 https://debian-mirror.wirenboard.com/debian bullseye-updates InRelease
Get:3 https://debian-mirror.wirenboard.com/debian-security bullseye-security InRelease [27.2 kB]
Err:1 https://debian-mirror.wirenboard.com/debian bullseye InRelease
  Splitting up /var/lib/apt/lists/debian-mirror.wirenboard.com_debian_dists_bullseye_InRelease into data and signature failed
Err:4 https://deb.wirenboard.com/wb6/bullseye stable InRelease
  Splitting up /var/lib/apt/lists/deb.wirenboard.com_wb6_bullseye_dists_stable_InRelease into data and signature failed
Err:2 https://debian-mirror.wirenboard.com/debian bullseye-updates InRelease
  Splitting up /var/lib/apt/lists/debian-mirror.wirenboard.com_debian_dists_bullseye-updates_InRelease into data and signature failed
Err:3 https://debian-mirror.wirenboard.com/debian-security bullseye-security InRelease
  Splitting up /var/lib/apt/lists/partial/debian-mirror.wirenboard.com_debian-security_dists_bullseye-security_InRelease into data and signature failed
Fetched 27.2 kB in 7s (3,943 B/s)

А Вы выполнили

Выполнил.
Всё там давно уже стоит и не удалялось.

root@wirenboard-A7IOITQU:~# apt install python3-yaml
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
python3-yaml is already the newest version (5.3.1-5).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

mqttrpc - это следующий модуль, который не видит диагностический скрипт, хотя он тоже установлен

Сейчас весь рутовый раздел забился под 100%. Всё стоит колом, еле ворочается.

wb-mqtt-adc грузит CPU почти на 70% (пришлось отключить)

кроме того, отсохли все

Контроллер и так старый и дохлый, в нём был Node.JS (для Zigbee2MQTT). Добавились тяжёлые модули питона и писец пришёл контроллеру :frowning:

Я бы вам порекомендовал сделать резервную копию и выполнить полный сброс с последующим обновлением на 2507.

Значит будем делать. Напомните пожалуйста ссылку на инструкцию про резервное копирование и сброс с обновлением.
Спасибо!

пн, 18 авг. 2025 г., 09:25 Dmitry Kuryatnikov через Wiren Board Support <info@wirenboard.com>:

Не получается до заводских настроек обновить.

>>> Recovering device certificates
>>> Mount /dev, /proc and /sys to rootfs /tmp/tmp.ai7t6RoOoz
>>> Running post-install scripts
>>> > Processing /tmp/tmp.ai7t6RoOoz/usr/lib/wb-image-update/postinst/10update-u-boot
Skipping u-boot update (use factory reset to do it)
>>> > Processing /tmp/tmp.ai7t6RoOoz/usr/lib/wb-image-update/postinst/10update-wbec-firmware
Skipping WBEC firmware update (use factory reset to do it)
>>> Unmounting /dev, /proc and /sys from rootfs /tmp/tmp.ai7t6RoOoz
>>> Switching to new rootfs
>>> Done!
>>> Removing FIT /mnt/data/.wb-restore/factoryreset.fit
>>> /mnt/data/.wb-restore/factoryreset.fit is a hardlink to factory-fit; saving factory-fit immutability
!!! Error at line 1194 ([[ -n "$was_immutable" ]])
>>> Removing FIT /mnt/data/.wb-restore/factoryreset.fit
>>> Unmounting rootfs
root@wirenboard-A7IOITQU:~#

Обновление тоже не заканчивается успешно:

>>> Checking SHA1 hash of install
>>> SHA1 hash of install ok
32+0 records in
32+0 records out
16384 bytes (16 kB, 16 KiB) copied, 0.0109721 s, 1.5 MB/s
>>> Firmware seems to be compatible with this controller
>>> Extracting install script
>>> Running install script
>>> Using flags from /mnt/data/.wb-update/install_update.web.flags: --force-repartition 
>>> Console logging enabled; tempfile /tmp/tmp.c1J99dStHC, final file /mnt/data/.wb-update/wb-console.log will be written on exit
>>> Reading uboot env offset/size from device tree...
>>> Could not read uboot-env-offset from device tree. Keeping old fw_env.config from rootfs
32+0 records in
32+0 records out
16384 bytes (16 kB, 16 KiB) copied, 0.00644604 s, 2.5 MB/s
>>> Firmware seems to be compatible with this controller
>>> Checking SHA1 hash of rootfs
>>> SHA1 hash of rootfs ok
>>> rootfs is valid, installing firmware update
>>> Checking, /tmp/tmp.f6pyI2ZwUt/.wb-restore/factoryreset.fit supports features: single-rootfs wb8-debug-network-update-fix wrong-ab-layout-fix
>>> No factory FIT found, storing this update as factory FIT to use as bootlet
awk: cannot open /proc/device-tree/chosen/u-boot-version (No such file or directory)
>>> Flashed U-boot version is too old, updating it before reboot
Das U-Boot installer for Wiren Board
You are about to install U-boot image '/usr/lib/u-boot/mx6ul_wirenboard6/u-boot-with-spl.imx' on '/dev/mmcblk0' (platform wb6)
Force installation requested
Writing U-boot image '/usr/lib/u-boot/mx6ul_wirenboard6/u-boot-with-spl.imx' on '/dev/mmcblk0' (options 'bs=512 seek=2')
831+1 records in
831+1 records out
425824 bytes (426 kB, 416 KiB) copied, 0.632111 s, 674 kB/s
Syncing device
>>> Watch logs in the debug console, or in /mnt/data/.wb-update/state/update.log
>>> Rebooting system to install update
>>> Waiting for Wiren Board to boot again...
>>> Reboot system
root@wirenboard-A7IOITQU:~# Failed to open initctl fifo: No such device or address
Failed to talk to init daemon.

Убедитесь, что используете подходящий fit файл.

Еще, если у вас в ходе обновления возникли ошибки, то попробуйте

dpkg --configure -a

А затем apt apdate && apt upgrade.

Возможно это решит проблему.

Квест закончен.
Удалил Zigbee2MQTT и некоторые другие тяжёлые модули. Освободил место на рутовом разделе. Обновил состояние через apt (без ошибок). Затем успешно сбросил до заводских настроек, потом увеличил размер рутового раздела. В конце, накатил самый свежий .fit файл. ADC и I/O задышали. Восстановил Zigbee и конфиги из бэкапа.
Контроллер задышал!!! Дальше сам…
Спасибо за помощь.

1 лайк