Upgraded to 1.0.23 seem to have an MQTT error

[iMiMx]

Was previously running 1.0.22, without issue as far as I'm aware, manually upgraded to 1.0.23 and I seem to now get an MQTT error:

2021-02-13 07:39:48 - INFO: Starting texecom2mqtt v1.0.23...
2021-02-13 07:39:48 - INFO: Connected to alarm, sleeping for 0.5 seconds...
2021-02-13 07:39:48 - INFO: Connection ready
2021-02-13 07:39:48 - INFO: Fetched serial number: xxxx
2021-02-13 07:39:48 - INFO: Logging in
2021-02-13 07:39:49 - INFO: Successfully logged in
2021-02-13 07:39:49 - ERROR: Unhandled rejection - Error: getaddrinfo ENOTFOUND core-mosquitto:1883

Config:

texecom:
  host: x.x.x.x
  udl_password: 'xxxxxx'
mqtt:
  host: 'mqtt://core-mosquitto:1883'
  username: texecom2mqtt
  password: xxxxxxxx
homeassistant:
  discovery: true
areas:
  - id: area_a
    full_arm: armed_away
    part_arm_1: armed_night
zones: []

Have tried an HA restart, but haven't done any further poking yet

[iMiMx]

Adding a debug log:

2021-02-13 07:47:32 - INFO: Starting texecom2mqtt v1.0.23...
2021-02-13 07:47:32 - INFO: Connected to alarm, sleeping for 0.5 seconds...
2021-02-13 07:47:33 - INFO: Connection ready
2021-02-13 07:47:33 - DEBUG: Executing serial number command
2021-02-13 07:47:33 - DEBUG: Received data chunk of length 11
2021-02-13 07:47:33 - INFO: Fetched serial number: xxxxxx
2021-02-13 07:47:33 - INFO: Logging in
2021-02-13 07:47:33 - DEBUG: Executing command 1
2021-02-13 07:47:33 - DEBUG: Received data chunk of length 7
2021-02-13 07:47:33 - INFO: Successfully logged in
2021-02-13 07:47:33 - ERROR: Unhandled rejection - Error: getaddrinfo ENOTFOUND core-mosquitto:1883
2021-02-13 07:47:33 - DEBUG: Ending socket connection to panel
2021-02-13 07:47:33 - DEBUG: Socket connection to panel ended

[iMiMx]

Did a snapshot restore of the addon only, back to 1.0.22, issue fixed:

2021-02-13 07:58:26 - INFO: Starting texecom2mqtt v1.0.22...
2021-02-13 07:58:26 - INFO: Connected to alarm, sleeping for 0.5 seconds...
2021-02-13 07:58:26 - INFO: Connection ready
2021-02-13 07:58:26 - INFO: Fetched serial number: xxxxx
2021-02-13 07:58:26 - INFO: Logging in
2021-02-13 07:58:26 - INFO: Successfully logged in
2021-02-13 07:58:27 - INFO: Connected to MQTT
2021-02-13 07:58:27 - INFO: Fetched panel info: Premier Elite 24 (V5.02.01LS1)
2021-02-13 07:58:28 - INFO: Fetched Zone 2: Hall (Type: Guard Access; Areas: A)
2021-02-13 07:58:28 - INFO: Fetched Zone 3: Study (Type: Guard; Areas: A)
2021-02-13 07:58:29 - INFO: Fetched Zone 4: Living Room (Type: Guard; Areas: A)
2021-02-13 07:58:29 - INFO: Fetched Zone 6: Landing (Type: Guard; Areas: A)
2021-02-13 07:58:34 - INFO: Fetched Zone 9: Entry Door (Type: Entry/Exit 1; Areas: A)
2021-02-13 07:58:34 - INFO: Fetched Zone 10: Garage (Type: Guard Access; Areas: A)
2021-02-13 07:58:34 - INFO: Fetched Zone 11: GARAGE DOOR (Type: Entry/Exit 1; Areas: A)

[B-Hartley]

Exactly the same issue for me.
Snapshot restore to previous version fixed it.

[markbooth73]

Same here,

2021-02-13 08:39:18 - INFO: Starting texecom2mqtt v1.0.23...
2021-02-13 08:39:18 - INFO: Connected to alarm, sleeping for 0.5 seconds...
2021-02-13 08:39:18 - DEBUG: Received data chunk of length 5
2021-02-13 08:39:19 - INFO: Connection ready
2021-02-13 08:39:19 - DEBUG: Executing serial number command
2021-02-13 08:39:19 - DEBUG: Received data chunk of length 4
2021-02-13 08:39:19 - ERROR: Unhandled rejection - Error: Could not fetch serial number
2021-02-13 08:39:19 - DEBUG: Ending socket connection to panel
2021-02-13 08:39:19 - DEBUG: Socket connection to panel ended

[RogerSelwyn]

I think you will need to move the port number to the port attribute. It works for me on 1.0.23. So use host, username, password, port for mqtt. Or if port is empty it defaults to 1883.

[B-Hartley]

I took the port off my url and it works now. Thanks.

[iMiMx]

I think you will need to move the port number to the port attribute. It works for me on 1.0.23. So use host, username, password, port for mqtt. Or if port is empty it defaults to 1883.

Yep - good spot. Should have RTFM-ed ;)