Witajcie. Podepnę się pod temat, bo mam podobne objawy i kompletny brak pomysłów na ich rozwiązanie (dopiero raczkuję w temacie HA/zigbee).
W skrócie: HA wisi na VM Synology NAS, koordynator to HA SyConnect, na przedłużce.
Coś się zadziało (przypuszczam, że po jakiejś aktualizacji, ale bez pewności) i Z2MQTT przestał się uruchamiać. Godziny grzebania przy konfiguracjach (Mosquitto Broker, Z2M) i ruszył, ale bardziej nie działa, niż działa. Tzn. po restarcie VM (tylko to jest skuteczne, sam restart Z2M nie pomaga) koordynator i urządzenia przez jakiś czas działają, automatyzacje pracują. Ale nie trwa to długo i sensory przestają się aktualizować. Przy takim stanie dodatek Z2M można uruchomić, ale po kliknięciu np. w przełącznik światła wyskakuje błąd a podczas skanowania mapy sieci pojawia się komunikat: “failed to execute lqi for ‘coordinator’”. Oczywiście próbowałem przywracać z backup-ów, nawet jakichś zamierzchłych, lecz to nie rozwiązuje problemu.
Poniżej podstawowe info (nie chcę zaśmiecać mocno, więc jeśli czegoś będzie brakowało, proszę o info)
System Information
| version | core-2024.1.3 |
|---|---|
| installation_type | Home Assistant OS |
| dev | false |
| hassio | true |
| docker | true |
| user | root |
| virtualenv | false |
| python_version | 3.11.6 |
| os_name | Linux |
| os_version | 6.1.71-haos |
| arch | x86_64 |
| timezone | Europe/Warsaw |
| config_dir | /config |
Home Assistant Community Store
| GitHub API | ok |
|---|---|
| GitHub Content | ok |
| GitHub Web | ok |
| GitHub API Calls Remaining | 5000 |
| Installed Version | 1.33.0 |
| Stage | running |
| Available Repositories | 1376 |
| Downloaded Repositories | 4 |
AccuWeather
| can_reach_server | ok |
|---|---|
| remaining_requests | 41 |
Home Assistant Cloud
| logged_in | false |
|---|---|
| can_reach_cert_server | ok |
| can_reach_cloud_auth | ok |
| can_reach_cloud | ok |
Home Assistant Supervisor
| host_os | Home Assistant OS 11.4 |
|---|---|
| update_channel | stable |
| supervisor_version | supervisor-2023.12.1 |
| agent_version | 1.6.0 |
| docker_version | 24.0.7 |
| disk_total | 97.7 GB |
| disk_used | 9.6 GB |
| healthy | true |
| supported | true |
| board | ova |
| supervisor_api | ok |
| version_api | ok |
| installed_addons | File editor (5.7.0), Samba share (12.2.0), Cloudflared (5.0.1), Advanced SSH & Web Terminal (17.0.3), Home Assistant Google Drive Backup (0.112.1), Node-RED (17.0.2), Let’s Encrypt (5.0.9), openWakeWord (1.8.2), Whisper (1.0.1), Piper (1.4.0), Assist Microphone (1.0.0), Google Assistant SDK (2.5.0), Mosquitto broker (6.4.0), Zigbee2MQTT (1.35.1-1), motionEye (0.20.0) |
Dashboards
| dashboards | 2 |
|---|---|
| resources | 1 |
| views | 6 |
| mode | storage |
Recorder
| oldest_recorder_run | 7 stycznia 2024 10:39 |
|---|---|
| current_recorder_run | 16 stycznia 2024 12:06 |
| estimated_db_size | 108.35 MiB |
| database_engine | sqlite |
| database_version | 3.41.2 |
Konfiguracja Z2M:
data_path: /config/zigbee2mqtt
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: "-d -d"
log: false
mqtt:
server: mqtt://core-mosquitto:1883
user: homeassistant
password: my_password
serial:
port: /dev/ttyUSB0
adapter: ezsp
Logi Z2M:
2024-01-16T23:17:36.938Z zigbee-herdsman:adapter:ezsp:uart Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
2024-01-16T23:17:36.946Z zigbee-herdsman:adapter:ezsp:erro Connection attempt 2 error: Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:94:28)
at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:82:22)
at /app/node_modules/@serialport/stream/dist/index.js:118:18
2024-01-16T23:17:37.125Z zigbee-herdsman:adapter:ezsp:ezsp Next attempt 5
2024-01-16T23:17:37.127Z zigbee-herdsman:adapter:ezsp:erro Reset error Error: Failure to connect
at Ezsp.connect (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:277:19)
at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:139:9)
at Driver.onReset (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:111:17)
2024-01-16T23:17:37.127Z zigbee-herdsman:adapter:ezsp:driv Pause 60sec before try 59
2024-01-16T23:17:38.028Z zigbee-herdsman:controller:endpoint Read 0x70b3d52b60044d90/1 haElectricalMeasurement(["rmsVoltage","rmsCurrent","activePower"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false})
2024-01-16T23:17:38.034Z zigbee-herdsman:adapter:ezsp:debg sendZclFrameToEndpointInternal 0x70b3d52b60044d90:5017/1 (0,0,19)
2024-01-16T23:17:38.034Z zigbee-herdsman:adapter:ezsp:ezsp ==> setExtendedTimeout: {"remoteEui64":{"_value":{"type":"Buffer","data":[112,179,213,43,96,4,77,144]}},"extendedTimeout":true}
2024-01-16T23:17:38.037Z zigbee-herdsman:adapter:ezsp:erro Request error Error: Connection not initialized: Error: Connection not initialized
at Ezsp.execCommand (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:551:19)
at Driver.request (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:472:29)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at EZSPAdapter.sendZclFrameToEndpointInternal (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:466:35)
2024-01-16T23:17:38.038Z zigbee-herdsman:controller:endpoint Read 0x70b3d52b60044d90/1 haElectricalMeasurement(["rmsVoltage","rmsCurrent","activePower"], {"sendWhen":"immediate","timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":null,"transactionSequenceNumber":null,"writeUndiv":false}) failed (sendZclFrameToEndpointInternal error)
2024-01-16T23:17:38.221Z zigbee-herdsman:adapter:ezsp:ezsp Next attempt 4
2024-01-16T23:17:38.221Z zigbee-herdsman:adapter:ezsp:uart Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
2024-01-16T23:17:38.228Z zigbee-herdsman:adapter:ezsp:erro Connection attempt 4 error: Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:94:28)
at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:82:22)
at /app/node_modules/@serialport/stream/dist/index.js:118:18
2024-01-16T23:17:41.263Z zigbee-herdsman:adapter:ezsp:ezsp Next attempt 4
2024-01-16T23:17:41.264Z zigbee-herdsman:adapter:ezsp:uart Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
2024-01-16T23:17:41.273Z zigbee-herdsman:adapter:ezsp:erro Connection attempt 4 error: Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:94:28)
at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:82:22)
at /app/node_modules/@serialport/stream/dist/index.js:118:18
2024-01-16T23:17:41.407Z zigbee-herdsman:adapter:ezsp:ezsp Next attempt 4
2024-01-16T23:17:41.409Z zigbee-herdsman:adapter:ezsp:uart Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
2024-01-16T23:17:41.419Z zigbee-herdsman:adapter:ezsp:erro Connection attempt 4 error: Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:94:28)
at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:82:22)
at /app/node_modules/@serialport/stream/dist/index.js:118:18
2024-01-16T23:17:41.947Z zigbee-herdsman:adapter:ezsp:ezsp Next attempt 3
2024-01-16T23:17:41.948Z zigbee-herdsman:adapter:ezsp:uart Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
2024-01-16T23:17:41.956Z zigbee-herdsman:adapter:ezsp:erro Connection attempt 3 error: Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:94:28)
at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:82:22)
at /app/node_modules/@serialport/stream/dist/index.js:118:18
2024-01-16T23:17:43.231Z zigbee-herdsman:adapter:ezsp:ezsp Next attempt 5
2024-01-16T23:17:43.231Z zigbee-herdsman:adapter:ezsp:erro Reset error Error: Failure to connect
at Ezsp.connect (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:277:19)
at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:139:9)
at Driver.onReset (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:111:17)
2024-01-16T23:17:43.231Z zigbee-herdsman:adapter:ezsp:driv Pause 60sec before try 59
2024-01-16T23:17:46.047Z zigbee-herdsman:adapter:ezsp:ezsp Time to watchdog ... 0
2024-01-16T23:17:46.047Z zigbee-herdsman:adapter:ezsp:ezsp ==> nop: null
2024-01-16T23:17:46.047Z zigbee-herdsman:adapter:ezsp:ezsp ==> {"_cls_":"nop","_id_":5,"_isRequest_":true}
2024-01-16T23:17:46.047Z zigbee-herdsman:adapter:ezsp:uart --> DATA (2,2,0): da00010500
2024-01-16T23:17:46.047Z zigbee-herdsman:adapter:ezsp:uart --> [229821a9512a4eae7e]
2024-01-16T23:17:46.048Z zigbee-herdsman:adapter:ezsp:uart -?- waiting (3)
2024-01-16T23:17:46.061Z zigbee-herdsman:adapter:ezsp:uart <-- [2398a1a9512ad6367e]
2024-01-16T23:17:46.062Z zigbee-herdsman:adapter:ezsp:uart <-- DATA (2,3,0): 2398a1a9512ad6367e
2024-01-16T23:17:46.062Z zigbee-herdsman:adapter:ezsp:uart --> ACK (3)
2024-01-16T23:17:46.062Z zigbee-herdsman:adapter:ezsp:uart --> [83401b7e]
2024-01-16T23:17:46.062Z zigbee-herdsman:adapter:ezsp:ezsp <== Frame: da80010500
2024-01-16T23:17:46.062Z zigbee-herdsman:adapter:ezsp:ezsp <== 0x5: {"_cls_":"nop","_id_":5,"_isRequest_":false}
2024-01-16T23:17:46.062Z zigbee-herdsman:adapter:ezsp:uart -+- waiting (3) success
2024-01-16T23:17:46.277Z zigbee-herdsman:adapter:ezsp:ezsp Next attempt 5
2024-01-16T23:17:46.278Z zigbee-herdsman:adapter:ezsp:erro Reset error Error: Failure to connect
at Ezsp.connect (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:277:19)
at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:139:9)
at Driver.onReset (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:111:17)
2024-01-16T23:17:46.278Z zigbee-herdsman:adapter:ezsp:driv Pause 60sec before try 59
2024-01-16T23:17:46.418Z zigbee-herdsman:adapter:ezsp:ezsp Next attempt 5
2024-01-16T23:17:46.419Z zigbee-herdsman:adapter:ezsp:erro Reset error Error: Failure to connect
at Ezsp.connect (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:277:19)
at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:139:9)
at Driver.onReset (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:111:17)
2024-01-16T23:17:46.419Z zigbee-herdsman:adapter:ezsp:driv Pause 60sec before try 59
2024-01-16T23:17:46.957Z zigbee-herdsman:adapter:ezsp:ezsp Next attempt 4
2024-01-16T23:17:46.960Z zigbee-herdsman:adapter:ezsp:uart Opening SerialPort with {"path":"/dev/ttyUSB0","baudRate":115200,"rtscts":false,"autoOpen":false}
2024-01-16T23:17:46.975Z zigbee-herdsman:adapter:ezsp:erro Connection attempt 4 error: Error: Error while opening serialport 'Error: Error Resource temporarily unavailable Cannot lock port'
at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/uart.ts:94:28)
at SerialPort._error (/app/node_modules/@serialport/stream/dist/index.js:82:22)
at /app/node_modules/@serialport/stream/dist/index.js:118:18
2024-01-16T23:17:51.978Z zigbee-herdsman:adapter:ezsp:ezsp Next attempt 5
2024-01-16T23:17:51.981Z zigbee-herdsman:adapter:ezsp:erro Reset error Error: Failure to connect
at Ezsp.connect (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:277:19)
at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:139:9)
at Driver.onReset (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:111:17)
2024-01-16T23:17:51.981Z zigbee-herdsman:adapter:ezsp:driv Pause 60sec before try 59
2024-01-16T23:17:56.051Z zigbee-herdsman:adapter:ezsp:ezsp Time to watchdog ... 0
2024-01-16T23:17:56.052Z zigbee-herdsman:adapter:ezsp:ezsp ==> nop: null
2024-01-16T23:17:56.053Z zigbee-herdsman:adapter:ezsp:ezsp ==> {"_cls_":"nop","_id_":5,"_isRequest_":true}
2024-01-16T23:17:56.054Z zigbee-herdsman:adapter:ezsp:uart --> DATA (3,3,0): db00010500
2024-01-16T23:17:56.055Z zigbee-herdsman:adapter:ezsp:uart --> [339921a9512abbdb7e]
2024-01-16T23:17:56.055Z zigbee-herdsman:adapter:ezsp:uart -?- waiting (4)
2024-01-16T23:17:56.063Z zigbee-herdsman:adapter:ezsp:uart <-- [3499a1a9512aaea27e]
2024-01-16T23:17:56.063Z zigbee-herdsman:adapter:ezsp:uart <-- DATA (3,4,0): 3499a1a9512aaea27e
2024-01-16T23:17:56.064Z zigbee-herdsman:adapter:ezsp:uart --> ACK (4)
2024-01-16T23:17:56.064Z zigbee-herdsman:adapter:ezsp:uart --> [8430fc7e]
2024-01-16T23:17:56.064Z zigbee-herdsman:adapter:ezsp:ezsp <== Frame: db80010500
2024-01-16T23:17:56.064Z zigbee-herdsman:adapter:ezsp:ezsp <== 0x5: {"_cls_":"nop","_id_":5,"_isRequest_":false}
2024-01-16T23:17:56.064Z zigbee-herdsman:adapter:ezsp:uart -+- waiting (4) success
Konfiguracja Mqtt Broer
logins:
- username: homeassistant
password: my_password
require_certificate: false
certfile: fullchain.pem
keyfile: privkey.pem
customize:
active: false
folder: mosquitto
anonymous: true
Logi Mqtt Broker:
2024-01-16 22:46:22: Client <unknown> closed its connection.
2024-01-16 22:48:22: New connection from 172.30.32.2:50022 on port 1883.
2024-01-16 22:48:22: Client <unknown> closed its connection.
2024-01-16 22:50:22: New connection from 172.30.32.2:50110 on port 1883.
2024-01-16 22:50:22: Client <unknown> closed its connection.
2024-01-16 22:52:22: New connection from 172.30.32.2:56712 on port 1883.
2024-01-16 22:52:22: Client <unknown> closed its connection.
2024-01-16 22:53:39: Saving in-memory database to /data//mosquitto.db.
2024-01-16 22:54:22: New connection from 172.30.32.2:53976 on port 1883.
2024-01-16 22:54:22: Client <unknown> closed its connection.
2024-01-16 22:56:22: New connection from 172.30.32.2:54212 on port 1883.
2024-01-16 22:56:22: Client <unknown> closed its connection.
2024-01-16 22:58:22: New connection from 172.30.32.2:45720 on port 1883.
2024-01-16 22:58:22: Client <unknown> closed its connection.
2024-01-16 23:00:22: New connection from 172.30.32.2:44654 on port 1883.
2024-01-16 23:00:22: Client <unknown> closed its connection.
2024-01-16 23:02:22: New connection from 172.30.32.2:35592 on port 1883.
2024-01-16 23:02:22: Client <unknown> closed its connection.
2024-01-16 23:04:22: New connection from 172.30.32.2:43696 on port 1883.
2024-01-16 23:04:22: Client <unknown> closed its connection.
2024-01-16 23:06:22: New connection from 172.30.32.2:43728 on port 1883.
2024-01-16 23:06:22: Client <unknown> closed its connection.
2024-01-16 23:08:22: New connection from 172.30.32.2:51602 on port 1883.
2024-01-16 23:08:22: Client <unknown> closed its connection.
2024-01-16 23:10:22: New connection from 172.30.32.2:55982 on port 1883.
2024-01-16 23:10:22: Client <unknown> closed its connection.
2024-01-16 23:12:22: New connection from 172.30.32.2:41246 on port 1883.
2024-01-16 23:12:22: Client <unknown> closed its connection.
2024-01-16 23:14:22: New connection from 172.30.32.2:53618 on port 1883.
2024-01-16 23:14:22: Client <unknown> closed its connection.
2024-01-16 23:16:22: New connection from 172.30.32.2:47432 on port 1883.
2024-01-16 23:16:22: Client <unknown> closed its connection.
2024-01-16 23:18:22: New connection from 172.30.32.2:44520 on port 1883.
2024-01-16 23:18:22: Client <unknown> closed its connection.
2024-01-16 23:20:22: New connection from 172.30.32.2:41990 on port 1883.
2024-01-16 23:20:22: Client <unknown> closed its connection.
2024-01-16 23:22:22: New connection from 172.30.32.2:44624 on port 1883.
2024-01-16 23:22:22: Client <unknown> closed its connection.
2024-01-16 23:23:40: Saving in-memory database to /data//mosquitto.db.
2024-01-16 23:24:22: New connection from 172.30.32.2:48948 on port 1883.
2024-01-16 23:24:22: Client <unknown> closed its connection.
2024-01-16 23:26:22: New connection from 172.30.32.2:34538 on port 1883.
2024-01-16 23:26:22: Client <unknown> closed its connection.
2024-01-16 23:28:22: New connection from 172.30.32.2:49442 on port 1883.
2024-01-16 23:28:22: Client <unknown> closed its connection.
2024-01-16 23:30:22: New connection from 172.30.32.2:54076 on port 1883.
2024-01-16 23:30:22: Client <unknown> closed its connection.
2024-01-16 23:32:22: New connection from 172.30.32.2:46598 on port 1883.
2024-01-16 23:32:22: Client <unknown> closed its connection.
2024-01-16 23:34:22: New connection from 172.30.32.2:45880 on port 1883.
2024-01-16 23:34:22: Client <unknown> closed its connection.
2024-01-16 23:36:22: New connection from 172.30.32.2:36592 on port 1883.
2024-01-16 23:36:22: Client <unknown> closed its connection.
2024-01-16 23:38:22: New connection from 172.30.32.2:44102 on port 1883.
2024-01-16 23:38:22: Client <unknown> closed its connection.
2024-01-16 23:40:22: New connection from 172.30.32.2:45048 on port 1883.
2024-01-16 23:40:22: Client <unknown> closed its connection.
2024-01-16 23:42:22: New connection from 172.30.32.2:38316 on port 1883.
2024-01-16 23:42:22: Client <unknown> closed its connection.
2024-01-16 23:44:22: New connection from 172.30.32.2:48254 on port 1883.
2024-01-16 23:44:22: Client <unknown> closed its connection.
2024-01-16 23:46:22: New connection from 172.30.32.2:49520 on port 1883.
2024-01-16 23:46:22: Client <unknown> closed its connection.
2024-01-16 23:48:22: New connection from 172.30.32.2:41712 on port 1883.
2024-01-16 23:48:22: Client <unknown> closed its connection.
2024-01-16 23:50:22: New connection from 172.30.32.2:45730 on port 1883.
2024-01-16 23:50:22: Client <unknown> closed its connection.
2024-01-16 23:52:22: New connection from 172.30.32.2:38100 on port 1883.
2024-01-16 23:52:22: Client <unknown> closed its connection.
2024-01-16 23:53:41: Saving in-memory database to /data//mosquitto.db.
2024-01-16 23:54:22: New connection from 172.30.32.2:36968 on port 1883.
2024-01-16 23:54:22: Client <unknown> closed its connection.
2024-01-16 23:56:22: New connection from 172.30.32.2:49204 on port 1883.
2024-01-16 23:56:22: Client <unknown> closed its connection.
2024-01-16 23:58:22: New connection from 172.30.32.2:34750 on port 1883.
2024-01-16 23:58:22: Client <unknown> closed its connection.
2024-01-17 00:00:23: New connection from 172.30.32.2:39518 on port 1883.
2024-01-17 00:00:23: Client <unknown> closed its connection.
2024-01-17 00:02:24: New connection from 172.30.32.2:35650 on port 1883.
2024-01-17 00:02:24: Client <unknown> closed its connection.
2024-01-17 00:04:24: New connection from 172.30.32.2:35854 on port 1883.
2024-01-17 00:04:24: Client <unknown> closed its connection.
2024-01-17 00:06:24: New connection from 172.30.32.2:51388 on port 1883.
2024-01-17 00:06:24: Client <unknown> closed its connection.
2024-01-17 00:08:24: New connection from 172.30.32.2:34392 on port 1883.
2024-01-17 00:08:24: Client <unknown> closed its connection.
2024-01-17 00:10:24: New connection from 172.30.32.2:45184 on port 1883.
2024-01-17 00:10:24: Client <unknown> closed its connection.
2024-01-17 00:12:24: New connection from 172.30.32.2:57120 on port 1883.
2024-01-17 00:12:24: Client <unknown> closed its connection.
2024-01-17 00:14:24: New connection from 172.30.32.2:60946 on port 1883.
2024-01-17 00:14:24: Client <unknown> closed its connection.
2024-01-17 00:16:24: New connection from 172.30.32.2:49140 on port 1883.
2024-01-17 00:16:24: Client <unknown> closed its connection.
2024-01-17 00:18:24: New connection from 172.30.32.2:53414 on port 1883.
2024-01-17 00:18:24: Client <unknown> closed its connection.
2024-01-17 00:20:24: New connection from 172.30.32.2:56902 on port 1883.
2024-01-17 00:20:24: Client <unknown> closed its connection.
2024-01-17 00:22:24: New connection from 172.30.32.2:45766 on port 1883.
2024-01-17 00:22:24: Client <unknown> closed its connection.
Jestem ufoludkiem w tym temacie, choć na oko, te logi z Mosquitto Broker-a są podejrzane. Czytałem też, że koordynatory na ezsp mogą dawać różne problemy, tym bardziej, że mam tam tylko USB 3.0 (może myśleć o donglu na LAN?). Wszystko, by pozostać przy NAS-ie z pominięciem zakupu rPi.
Wycinek loga (nie wiem, czy o to właściwy fragment):
2024-01-16 15:32:21.533 ERROR (MainThread) [homeassistant.components.synology_dsm.coordinator] Unexpected error fetching Krzyho-K2 SynologyDSMCameraUpdateCoordinator data: {'api': None, 'code': -1, 'reason': 'Unknown', 'details': 'TimeoutError'}
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/synology_dsm/synology_dsm.py", line 317, in _execute_request
response = await self._session.get(url_encoded, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/client.py", line 601, in _request
await resp.start(conn)
File "/usr/local/lib/python3.11/site-packages/aiohttp/client_reqrep.py", line 965, in start
message, payload = await protocol.read() # type: ignore[union-attr]
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 622, in read
await self._waiter
asyncio.exceptions.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/synology_dsm/synology_dsm.py", line 316, in _execute_request
async with async_timeout.timeout(self._timeout):
File "/usr/local/lib/python3.11/site-packages/async_timeout/__init__.py", line 141, in __aexit__
self._do_exit(exc_type)
File "/usr/local/lib/python3.11/site-packages/async_timeout/__init__.py", line 228, in _do_exit
raise asyncio.TimeoutError
TimeoutError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 300, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/synology_dsm/coordinator.py", line 126, in _async_update_data
await surveillance_station.update()
File "/usr/local/lib/python3.11/site-packages/synology_dsm/api/surveillance_station/__init__.py", line 25, in update
raw_data = await self._dsm.get(self.CAMERA_API_KEY, "List", max_version=7)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/synology_dsm/synology_dsm.py", line 207, in get
return await self._request("GET", api, method, params, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/synology_dsm/synology_dsm.py", line 282, in _request
response = await self._execute_request(request_method, url, params, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/synology_dsm/synology_dsm.py", line 358, in _execute_request
raise SynologyDSMRequestException(exp) from exp
synology_dsm.exceptions.SynologyDSMRequestException: {'api': None, 'code': -1, 'reason': 'Unknown', 'details': 'TimeoutError'}
2024-01-16 15:37:00.602 WARNING (Recorder) [homeassistant.components.recorder.db_schema] State attributes for sensor.mi_10t_pro_active_notification_count exceed maximum size of 16384 bytes. This can cause database performance issues; Attributes will not be stored
Będę wdzięczny za jakieś sugestie.
**
