connection error

[bereska]

please help ...

---

Add-on: LifeSOS to MQTT MQTT client that interfaces with LifeSOS alarm systems.

Add-on version: 3.1 You are running the latest version of this add-on. System: Home Assistant OS 13.0 (aarch64 / raspberrypi4-64) Home Assistant Core: 2024.8.2 Home Assistant Supervisor: 2024.08.0

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service base-addon-log-level: starting s6-rc: info: service fix-attrs successfully started Log level is set to INFO s6-rc: info: service base-addon-log-level successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service init-nodesos-mqtt: starting

List all enrolled devices for the base unit

---

| \ | | _ _| | / | / \/ __| | \/ |/ _ | | | | |/ \ / ` |/ _ | | | _ \ | |\/| | | | || | | |
| |\ | () | (| | /) | || |__) | | | | | || || | | |
|| _|\/ _,|_|__/ _/|__/ || ||__|| |_|

NodeSOS_MQTT 2.0.0 - MQTT client to report state of LifeSOS security system and devices..

[2024-09-01T16:22:30.774] [ERROR] [NodeSOS.Protocol] Socket error: Error: connect ECONNREFUSED 192.168.2.87:1680 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '192.168.2.87', port: 1680 } node:internal/process/promises:288 triggerUncaughtException(err, true / fromPromise /); ^

Error: connect ECONNREFUSED 192.168.2.87:1680 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '192.168.2.87', port: 1680 }

Node.js v18.20.3 s6-rc: warning: unable to start service init-nodesos-mqtt: command exited 1 /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. /run/s6/basedir/scripts/rc.init: fatal: stopping the container. s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service base-addon-log-level: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service base-addon-log-level successfully stopped s6-rc: info: service base-addon-banner: stopping s6-rc: info: service base-addon-banner successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped

[bereska]

please HELP ....

[bratanon]

If IP 192.168.2.87 and port is 1680 as states, and you can't connect there is not much more I can do.

Please make sure the IP to your alarm unit is as states, and that the unit is set to "server mode".

On LS-20, it's Telnet Server/Client -> Server

[bereska]

thank you very much for your response the interesting thing is that it first successfully connects to the unit if I change the port to 80 but then disconnects with a different error:

[2024-09-16T10:31:57.249] [INFO ] [NodeSOS.Protocol] Socket connected to 192.168.2.87:80 [2024-09-16T10:31:57.254] [INFO ] [NodeSOSMQTT] Listing devices.... [2024-09-16T10:31:57.265] [ERROR] [NodeSOS.Protocol] Socket error: Error: read ECONNRESET at TCP.onStreamRead (node:internal/stream_base_commons:217:20) { errno: -104, code: 'ECONNRESET', syscall: 'read' } [2024-09-16T10:31:57.271] [INFO ] [NodeSOS.Protocol] Socket closed with error /usr/local/lib/node_modules/nodesos_mqtt/node_modules/nodesos/dist/main.js:1711 reject(new (0, $0457c6aac839a082$export$2e2bcd8739ae039)(command)); ^

$0457c6aac839a082$var$CommandTimeoutError at Timeout._onTimeout (/usr/local/lib/node_modules/nodesos_mqtt/node_modules/nodesos/dist/main.js:1711:24) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) { command: $23f20775a2eb2860$var$GetDeviceByIndexCommand { deviceCategory: $4cee450ceb319f74$var$DeviceCategory { code: 'c', description: 'Controller', maxDevices: 32, number: 0 }, index: 0 } }

maybe it's a different port other than 1680 I should try?

regards, Dmitry

---

From: Emil Stjerneman @.> Sent: Monday, September 16, 2024 6:28 AM To: bratanon/lifesos_addon @.> Cc: bereska @.>; Author @.> Subject: Re: [bratanon/lifesos_addon] connection error (Issue #4)

If IP 192.168.2.87 and port is 1680 as states, and you can't connect there is not much more I can do.

Please make sure the IP to your alarm unit is as states, and that the unit is set to "server mode".

On LS-20, it's Telnet Server/Client -> Server

— Reply to this email directly, view it on GitHubhttps://github.com/bratanon/lifesos_addon/issues/4#issuecomment-2352105258, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHKP7SMPI6HQ5DUIJ7L3Z73ZWZ3BFAVCNFSM6AAAAABNO3GMOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJSGEYDKMRVHA. You are receiving this because you authored the thread.

[bratanon]

There might be something else running on port 80, usually a webserver.

Which base unit do you have? LS20?

Can you access the base unit web interface?