Добрый день.
Вчера в доме самопроизвольно выключился весь свет. Изучая логи выяснил, что была самопроизвольная сработка скрипта мастер выключателя на счетчик долгих нажатий (как и остальных правил, завязанных на счетчики нажатий).
Судя по логам произошло это после того, как отвалился и заново восстановился mqtt-бридж из Home Assistant (крутится на отдельном мини PC в локальной сети).
Mar 03 21:33:36 wirenboard-AC6A3GB6 mosquitto[3819]: 1741030416: Client core-mosquitto.wb-bridge closed its connection.
Mar 03 21:34:42 wirenboard-AC6A3GB6 mosquitto[3819]: 1741030482: New connection from 192.168.88.100:57352 on port 1883.
Mar 03 21:34:42 wirenboard-AC6A3GB6 mosquitto[3819]: 1741030482: New bridge connected from 192.168.88.100:57352 as core-mosquitto.wb-bridge (p2, c1, k60).
...
Mar 03 21:34:44 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching action on 'wb-mdm3_163/Input 1 Long Press Counter' ---> сработка правила на счетчик
Конфиг mqtt-моста на HA
connection wb-bridge
address 192.168.88.150:1883
topic /devices/+/controls/+/# both 2 wb ""
try_private true
cleansession true
notifications true
Логи
Mar 03 21:11:38 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:11:38Z E! [inputs.mqtt_consumer::mqtt-consumer-string] Error in plugin: connection lost: pingresp not received, disconnecting
Mar 03 21:11:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:12:01 wirenboard-AC6A3GB6 mosquitto[3819]: 1741029121: New connection from /var/run/mosquitto/mosquitto.sock:0 on port 0.
Mar 03 21:12:01 wirenboard-AC6A3GB6 mosquitto[3819]: 1741029121: New client connected from /var/run/mosquitto/mosquitto.sock:0 as wb-cloud-agent-telegraf-Dw6Ko0YE (p2, c1, k60).
Mar 03 21:12:01 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:12:01Z I! [inputs.mqtt_consumer::mqtt-consumer-string] Connected [unix:///var/run/mosquitto/mosquitto.sock]
Mar 03 21:12:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:13:42 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:13:42Z E! [outputs.influxdb_v2::influx-wbc] When writing to [https://influx.wirenboard.cloud]: 521 : 521
Mar 03 21:13:42 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:13:42Z E! [agent] Error writing to outputs.influxdb_v2::influx-wbc: failed to send metrics to any configured server(s)
Mar 03 21:13:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:14:33 wirenboard-AC6A3GB6 NetworkManager[3543]: <info> [1741029273.9265] dhcp4 (eth0): state changed new lease, address=192.168.88.150
Mar 03 21:14:48 wirenboard-AC6A3GB6 wb-mqtt-serial[23579]: WARNING: [modbus] failed to read 4 input(s) @ 4668 of device </dev/ttyRS485-1 115200 8 N 2> modbus:186: Serial protocol error: request timed out
Mar 03 21:14:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:15:42 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:15:42Z E! [outputs.influxdb_v2::influx-wbc] When writing to [https://influx.wirenboard.cloud]: 521 : 521
Mar 03 21:15:42 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:15:42Z E! [agent] Error writing to outputs.influxdb_v2::influx-wbc: failed to send metrics to any configured server(s)
Mar 03 21:15:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:16:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:17:01 wirenboard-AC6A3GB6 CRON[25576]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Mar 03 21:17:01 wirenboard-AC6A3GB6 CRON[25580]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 03 21:17:01 wirenboard-AC6A3GB6 CRON[25576]: pam_unix(cron:session): session closed for user root
Mar 03 21:17:46 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:17:46Z E! [outputs.influxdb_v2::influx-wbc] When writing to [https://influx.wirenboard.cloud]: 521 : 521
Mar 03 21:17:46 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:17:46Z E! [agent] Error writing to outputs.influxdb_v2::influx-wbc: failed to send metrics to any configured server(s)
Mar 03 21:17:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:18:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:19:46 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:19:46Z E! [outputs.influxdb_v2::influx-wbc] When writing to [https://influx.wirenboard.cloud]: 521 : 521
Mar 03 21:19:46 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:19:46Z E! [agent] Error writing to outputs.influxdb_v2::influx-wbc: failed to send metrics to any configured server(s)
Mar 03 21:19:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:20:07 wirenboard-AC6A3GB6 wb-mqtt-serial[23579]: WARNING: [modbus] failed to read 24 input(s) @ 4864 of device </dev/ttyRS485-1 115200 8 N 2> modbus:186: Serial protocol error: malformed response: invalid crc
Mar 03 21:20:09 wirenboard-AC6A3GB6 kernel: RTL871X: set group key camid:2, addr:00:00:00:00:00:00, kid:2, type:TKIP
Mar 03 21:20:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:21:51 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:21:51Z E! [outputs.influxdb_v2::influx-wbc] When writing to [https://influx.wirenboard.cloud]: 521 : 521
Mar 03 21:21:51 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:21:51Z E! [agent] Error writing to outputs.influxdb_v2::influx-wbc: failed to send metrics to any configured server(s)
Mar 03 21:21:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:22:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:23:52 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:23:52Z E! [outputs.influxdb_v2::influx-wbc] When writing to [https://influx.wirenboard.cloud]: 521 : 521
Mar 03 21:23:52 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:23:52Z E! [agent] Error writing to outputs.influxdb_v2::influx-wbc: failed to send metrics to any configured server(s)
Mar 03 21:23:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:24:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:25:52 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:25:52Z E! [outputs.influxdb_v2::influx-wbc] When writing to [https://influx.wirenboard.cloud]: 521 : 521
Mar 03 21:25:52 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:25:52Z E! [agent] Error writing to outputs.influxdb_v2::influx-wbc: failed to send metrics to any configured server(s)
Mar 03 21:25:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:26:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:27:56 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:27:56Z E! [outputs.influxdb_v2::influx-wbc] When writing to [https://influx.wirenboard.cloud]: 521 : 521
Mar 03 21:27:56 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:27:56Z E! [agent] Error writing to outputs.influxdb_v2::influx-wbc: failed to send metrics to any configured server(s)
Mar 03 21:27:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:28:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:29:33 wirenboard-AC6A3GB6 NetworkManager[3543]: <info> [1741030173.9143] dhcp4 (eth0): state changed new lease, address=192.168.88.150
Mar 03 21:29:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:30:00 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:30:00Z E! [outputs.influxdb_v2::influx-wbc] When writing to [https://influx.wirenboard.cloud]: 521 : 521
Mar 03 21:30:00 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:30:00Z E! [agent] Error writing to outputs.influxdb_v2::influx-wbc: failed to send metrics to any configured server(s)
Mar 03 21:30:09 wirenboard-AC6A3GB6 kernel: RTL871X: set group key camid:1, addr:00:00:00:00:00:00, kid:1, type:TKIP
Mar 03 21:30:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:31:01 wirenboard-AC6A3GB6 wb-mqtt-db[4063]: INFO: [dblogger] Group data limit is reached: group all, row count 1020010, limit 1000000
Mar 03 21:31:11 wirenboard-AC6A3GB6 mosquitto[3819]: 1741030271: Client wb-cloud-agent-telegraf-Dw6Ko0YE closed its connection.
Mar 03 21:31:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:32:04 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:32:04Z E! [outputs.influxdb_v2::influx-wbc] When writing to [https://influx.wirenboard.cloud]: 521 : 521
Mar 03 21:32:04 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:32:04Z E! [agent] Error writing to outputs.influxdb_v2::influx-wbc: failed to send metrics to any configured server(s)
Mar 03 21:32:18 wirenboard-AC6A3GB6 wb-mqtt-serial[23579]: WARNING: [modbus] failed to read 4 input(s) @ 4284 of device </dev/ttyRS485-1 115200 8 N 2> modbus:186: Serial protocol error: request timed out
Mar 03 21:32:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
-----> Mar 03 21:33:36 wirenboard-AC6A3GB6 mosquitto[3819]: 1741030416: Client core-mosquitto.wb-bridge closed its connection. ---> отключение бриджа HA
Mar 03 21:33:58 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] _update_git_status started!
Mar 03 21:34:09 wirenboard-AC6A3GB6 telegraf[18122]: 2025-03-03T19:34:09Z E! [inputs.mqtt_consumer::mqtt-consumer-string] Error in plugin: connection lost: pingresp not received, disconnecting
-----> Mar 03 21:34:42 wirenboard-AC6A3GB6 mosquitto[3819]: 1741030482: New connection from 192.168.88.100:57352 on port 1883. ---> восстановление бриджа HA
-----> Mar 03 21:34:42 wirenboard-AC6A3GB6 mosquitto[3819]: 1741030482: New bridge connected from 192.168.88.100:57352 as core-mosquitto.wb-bridge (p2, c1, k60).
-----> Mar 03 21:34:44 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching action on 'wb-mdm3_163/Input 1 Long Press Counter' ---> сработка правила на счетчик
Mar 03 21:34:44 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] switching off 'wb-mdm3_163/K1'(was state=on)
Mar 03 21:34:44 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] switching off 'wb-mr6c_161/K1'(was state=off)
Mar 03 21:34:44 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] switching off 'wb-mr6c_161/K2'(was state=off)
Mar 03 21:34:44 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] switching off 'wb-mr6c_161/K3'(was state=on)
-----> Mar 03 21:34:44 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching action on 'wb-mdm3_163/Input 3 Long Press Counter' ---> сработка правила на счетчик
Mar 03 21:34:44 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] switching off 'wb-mdm3_163/K3'(was state=on)
Mar 03 21:34:44 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] switching off 'wb-mr6c_135/K4'(was state=off)
Mar 03 21:34:44 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] switching off 'wb-mr6c_135/K5'(was state=off)
Mar 03 21:34:44 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] switching off 'wb-mr6c_135/K6'(was state=off)
-----> Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Master switch fired ---> сработка правила на счетчик
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off R1.K1(wb-mr6c_75/K1) was 'off'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off R1.K6(wb-mr6c_75/K6) was 'off'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off LED2.K1(wb-led_47/Channel 1) was 'off'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off D1.K1(wb-mdm3_93/K1) was 'off'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off D1.K2(wb-mdm3_93/K2) was 'off'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off R2.K3(wb-mr6c_95/K3) was 'off'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off LED3.K1(wb-led_48/Channel 1) was 'on'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off LED3.K2(wb-led_48/Channel 2) was 'on'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off LED3.K3(wb-led_48/Channel 3) was 'on'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off LED3.K4(wb-led_48/Channel 4) was 'on'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off LED4.K1(wb-led_52/Channel 1) was 'on'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off LED4.K2(wb-led_52/Channel 2) was 'on'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off LED4.K3(wb-led_52/Channel 3) was 'on'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off LED4.K4(wb-led_52/Channel 4) was 'on'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off LED5.K1(wb-led_67/Channel 1) was 'on'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off LED5.K2(wb-led_67/Channel 2) was 'on'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off R9.K5(wb-mr6c_170/K5) was 'on'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off R9.K6(wb-mr6c_170/K6) was 'off'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off D2.K1(wb-mdm3_153/K1) was 'off'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off D2.K2(wb-mdm3_153/K2) was 'off'
Mar 03 21:34:45 wirenboard-AC6A3GB6 wb-rules[4134]: INFO: [rule info] Switching off D2.K3(wb-mdm3_153/K3) was 'off'
По идее такого происходить не должно, так как бридж отвалился всего на минуту и за это время не было изменений счетчиков нажатий.
После этого я подправил логирование нажатий в скриптах, чтобы выводился текущий счетчик.
Пока разбирался, заметил, что устройства, подключенные через WM_MIO-E горят красным, хотя в конфигураторе устройств ошибок не было и при этом устройства моргали быстро, т.е. шел опрос по модбасу.
Решил перезагрузить сервис wb-mqtt-serial и снова получил срабатывания счетчиков нажатий со значением 0.
Логи 2
Mar 03 23:15:49 wirenboard-AC6A3GB6 wb-mqtt-serial[23579]: INFO: [signal handling] Received signal 15
Mar 03 23:15:49 wirenboard-AC6A3GB6 systemd[1]: Stopping MQTT Driver for serial devices...
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-mqtt-db[4063]: WARNING: [conventions] converting empty value to boolean "false"
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-rules[15083]: WARNING: [frontend] failed to remove external control wb-mio-gpio_173:1/K7: No such control
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-rules[15083]: WARNING: [frontend] failed to remove external control wb-mio-gpio_173:1/K7: No such control
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-rules[15083]: WARNING: [frontend] failed to remove external control wb-mio-gpio_173:1/K4: No such control
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-mqtt-db[4063]: WARNING: [conventions] converting empty value to boolean "false"
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-mqtt-db[4063]: WARNING: [conventions] converting empty value to boolean "false"
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-rules[15083]: WARNING: [frontend] failed to remove external control wb-mio-gpio_173:2/K3: No such control
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-rules[15083]: WARNING: [frontend] failed to remove external control wb-mio-gpio_173:2/K3: No such control
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-rules[15083]: WARNING: [frontend] failed to remove external control wb-mio-gpio_173:2/K3: No such control
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-rules[15083]: WARNING: [frontend] failed to remove external control wb-mio-gpio_173:4/K1: No such control
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-rules[15083]: WARNING: [frontend] failed to remove external control wb-mio-gpio_173:5/K1: No such control
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-rules[15083]: WARNING: [frontend] failed to remove external control wb-mwac_64/K1: No such control
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-rules[15083]: WARNING: [frontend] failed to remove external control wb-mwac_64/K2: No such control
Mar 03 23:15:50 wirenboard-AC6A3GB6 wb-rules[15083]: WARNING: [frontend] failed to remove external control wb-mwac_64/K2: No such control
...
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 480>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 481>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 482>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 483>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 484>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 485>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 496>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 497>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 498>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 499>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 500>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 501>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 512>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 513>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:129:input: 514>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are disabled for <modbus:129: reboot>
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Init: secp_waiting_time_title: setup register <<192.168.88.50:23> modbus:105:holding: 1143> <-- 200 (0xc8)
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial device] device <192.168.88.50:23> modbus:105 is connected
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Continuous read enabled [slave_id is 148]
----> Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-rules[15083]: INFO: [rule info] Switching action on 'wb-mr6c_129/Input 5 Single Press Counter'(counter=0) ----> Сработка правила на счетчик
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-rules[15083]: INFO: [rule info] switching 'wb-mr6c_170/K5'(was state=on)
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Init: Mode: setup register <</dev/ttyMOD2 9600 8 N 2> modbus:148:holding: 275> <-- 0 (0x0)
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Init: Mode: setup register <</dev/ttyMOD2 9600 8 N 2> modbus:148:holding: 276> <-- 0 (0x0)
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial device] device </dev/ttyMOD2 9600 8 N 2> modbus:148 is connected
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Continuous read enabled [slave_id is 170]
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Init: Mode: setup register <</dev/ttyRS485-1 115200 8 N 2> modbus:170:holding: 16> <-- 6 (0x6)
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Init: Mode: setup register <</dev/ttyRS485-1 115200 8 N 2> modbus:170:holding: 9> <-- 6 (0x6)
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Init: secp_waiting_time_title: setup register <</dev/ttyRS485-1 115200 8 N 2> modbus:170:holding: 1140> <-- 200 (0xc8)
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Init: Mode: setup register <</dev/ttyRS485-1 115200 8 N 2> modbus:170:holding: 10> <-- 6 (0x6)
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Init: sp_title: setup register <</dev/ttyRS485-1 115200 8 N 2> modbus:170:holding: 554> <-- 3 (0x3)
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Init: secp_waiting_time_title: setup register <</dev/ttyRS485-1 115200 8 N 2> modbus:170:holding: 1141> <-- 0 (0x0)
Mar 03 23:16:23 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Continuous read enabled [slave_id is 16]
...
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:75:input: 487>
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are enabled for <modbus:75:input: 519>
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [serial client] Events are disabled for <modbus:75: reboot>
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Continuous read enabled [slave_id is 108]
------> Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-rules[15083]: INFO: [rule info] Master switch fired ----> Сработка правила на счетчик (мастер выключатель)
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-rules[15083]: INFO: [rule info] Switching off R1.K1(wb-mr6c_75/K1) was 'off'
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-rules[15083]: INFO: [rule info] Switching off R1.K6(wb-mr6c_75/K6) was 'off'
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-rules[15083]: INFO: [rule info] Switching off LED2.K1(wb-led_47/Channel 1) was 'off'
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-mqtt-serial[27540]: INFO: [modbus] Init: Dimmer Mode: setup register <<192.168.88.50:23> modbus:108:holding: 4000> <-- 34 (0x22)
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-rules[15083]: INFO: [rule info] Switching off D1.K1(wb-mdm3_93/K1) was 'off'
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-rules[15083]: INFO: [rule info] Switching off D1.K2(wb-mdm3_93/K2) was 'off'
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-rules[15083]: INFO: [rule info] Switching off R2.K3(wb-mr6c_95/K3) was 'off'
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-rules[15083]: INFO: [rule info] Switching off LED3.K1(wb-led_48/Channel 1) was 'off'
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-rules[15083]: INFO: [rule info] Switching off LED3.K2(wb-led_48/Channel 2) was 'off'
Mar 03 23:16:28 wirenboard-AC6A3GB6 wb-rules[15083]: INFO: [rule info] Switching off LED3.K3(wb-led_48/Channel 3) was 'off'
Вроде писали, что поведение со счетчиками было исправлено. Кейс показывает что не до конца.
Использую последний Stable.
Диагностический архив прилагаю.
diag_output_AC6A3GB6_2025-03-04-11.05.32.zip (798,2 КБ)
P.S. Прошу отнестись к проблеме серьезно. Инсталляция используется в уже жилом доме и это крайне неприятно получить выключение света, или наоборот, самопроизвольное включение ночью. И это довольно простые автоматизации на свет, без критических последствий. Но могли быть и открытые ворота, и остановленные насосы. Правила написаны по рекомендуемой производителем схеме со счетчиком нажатий, которая на данном этапе выглядит весьма небезопасно.