Addon stops on connection timeout

Question

Addon stops on connection timeout

Opened this issue 2 years ago · 22 comments

Describe the bug
My ComWIFI periodcally loses WiFi connectivity, when it does texecom2mqtt reports "connection timeout" and stops itself, despite me having the restart option turned on. So when the ComWIFI regains wifi I have to manually restart texecom2mqtt :(

When it encounters a timeout can it do an exponential backoff or something and keep retrying, instead of just dying

Application version
1.2.3

Texecom alarm type
Premier Elite 64

Home Assistant version
2022.8.4

Debug log
Will post next time it occurs, but a message to the effect of "connection to panel timed out"

Answer 1 · 2022-08-26T12:01:53.000Z

I have the same issue, just now my addon was stopped for 6 days.

Answer 2 · 2022-08-26T13:49:08.000Z

It's the same issue for me. Since receiving the August homeassistant updates the app stops very regularly and doesn't auto restart.

Answer 3 · 2022-08-31T11:26:56.000Z

Hi, also getting the same issue, the error file showed, the following error. I've now got a script to restart it if the alarm becomes unavailable, but a recent update somewhere has upset something.

Answer 4 · 2022-09-01T15:01:02.000Z

I'm having this happen now at least once every other day. Any idea on what the issue is or anything I can log to help resolve?

Answer 5 · 2022-09-02T18:51:22.000Z

I have experienced this as well - every couple days the texecom2mqtt stops and has to be manually restarted

version 1.2.3

home assistant 2022.7.7
ha os 8.4
Mosquito 6.1.3

Answer 6 · 2022-09-09T21:16:17.000Z

Same problem here.
Versions:
Home Assistant 2022.8.7
Supervisor 2022.08.6
Operating System 8.5
Frontend 20220802.0 - latest
Add-on: 1.2.3

Answer 7 · 2022-10-18T11:05:11.000Z

Hi, also getting the same issue, the error file showed, the following error. I've now got a script to restart it if the alarm becomes unavailable, but a recent update somewhere has upset something.

I am also getting this exact same error.

Starts up immediately if I manually start the add-on.

Answer 8 · 2022-10-18T13:24:21.000Z

OK so this isn't a fix but a workaround that saves me having to manually restart the service... if you put this into your automation yaml file the system will start the texecom2mqtt addon if the alarm is unavailable for 1 minute. You need to change your alarm entity_id and texecom2mqtt addon name as appropriate.

- id: restarttexecom
  alias: restarttexecom
  trigger:
  - platform: state
    entity_id: alarm_control_panel.house
    to: 'unavailable'
    for:
      minutes: 1
  condition: []
  action:
  - service: hassio.addon_start
    data:
      addon: c15a2434_texecom2mqtt
  mode: single

Answer 9 · 2022-11-04T16:38:51.000Z

Even using an automation to restart the add-on doesn't work for me, the automation runs but looks like the add-on keeps falling over with the same error. Strangely when the alarm is armed it seems to be stable.

Answer 10 · 2022-11-10T18:24:13.000Z

That automation doesn't do it for me either :(. Still need to start it manually again.

Answer 11 · 2022-12-27T14:02:42.000Z

Add-on still crashes quite a bit for me (multiple times per day), as I mentioned in my last post, the automation within Home Assistant hasn't worked for me either. I have found though, that creating an automation within node-red and looping it until the add-on is successfully running seems to at least have kept it running now for well over a week. I'm sure this could be achieved within Home Assistant but I find node-red easier to work with sometimes.

Answer 12 · 2022-12-28T09:52:56.000Z

Does anyone know if the integration has been abandoned by @dchesterton? He used to be very responsive in fixing stuff.
Hope he's all right.

Answer 13 · 2022-12-28T12:37:26.000Z

He was pushing code on the 24th.... Perhaps we can send him some mince pies

Answer 14 · 2022-12-28T16:15:56.000Z

Hey folks, I'm still here! I've got a 7-month old baby now so my spare time is very limited unfortunately. I will try and look at this at some point but I can't promise when.

Answer 15 · 2022-12-28T17:29:56.000Z

@dchesterton Wonderful to hear! Congrats! And I'm glad you're ok :)
Just bought you some cups of coffee, please buy some nice toy for the baby :)

Answer 16 · 2022-12-29T07:47:25.000Z

Also got a 7 month old, I feel your pain :)

~~Bribes~~ Coffees also given 👍

Answer 17 · 2023-02-01T22:58:17.000Z

I'm also having the same issue, but just setup this Automation to restart after X minutes
Simillar to the one above, but works by enabling the running status of the addon

https://www.youtube.com/watch?v=z3rBG0ioaPY

alias: Addon Texecom Delayed Restart
description: Restarts the texecom addon when it's been down more than 5 mins
trigger:
  - type: not_running
    platform: device
    device_id: 9c7869f797e49c960874b6070ce90ad5
    entity_id: binary_sensor.texecom2mqtt_running
    domain: binary_sensor
    for:
      hours: 0
      minutes: 5
      seconds: 0
condition: []
action:
  - service: hassio.addon_start
    data:
      addon: c15a2434_texecom2mqtt
mode: single

Answer 18 · 2023-02-08T21:35:02.000Z

I'm seeing this situation as well. But I have a comIP module, hardwired into my switch.

Answer 19 · 2023-02-09T21:05:45.000Z

I'm also having the same issue, but just setup this Automation to restart after X minutes Simillar to the one above, but works by enabling the running status of the addon

Doesn't work for me. The add-on doesn't restart :(

Answer 20 · 2023-02-19T21:48:10.000Z

I'm also having the same issue, but just setup this Automation to restart after X minutes Simillar to the one above, but works by enabling the running status of the addon

Doesn't work for me. The add-on doesn't restart :(

Is there any trace information on the automation? It's been running for me a few weeks now.

Answer 21 · 2023-08-17T19:08:02.000Z

2023-08-17 18:37:16 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)...
node:events:368
      throw er; // Unhandled 'error' event
      ^
Error: connect EHOSTUNREACH xxx.xxx.xxx.xxx:10001
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -113,
  code: 'EHOSTUNREACH',
  syscall: 'connect',
  address: 'xxx.xxx.xxx.xxx',
  port: 10001
}

Answer 22 · 2024-06-12T08:34:01.000Z

Same issue every 4-5 days or so. SmartCom and ComIP (which this is connected to):

Error: connect EHOSTUNREACH 192.168.0.21:10001
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -113,
  code: 'EHOSTUNREACH',
  syscall: 'connect',
  address: '192.168.0.21',
  port: 10001
}
2024-06-12 06:49:42 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)...
node:events:368
      throw er; // Unhandled 'error' event
      ^

Manual restart was fine.

@dchesterton I know you were busy with life a year or two ago - is it likely that you will be able to put any more time into this to handle these exceptions gracefully? I know it's so difficult when you're a one-man integration dev! Many thanks.