Addon not working after update to 1.4.0

[janneho]

Was ok before update.

Logs:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[14:54:19] INFO: MQTT service found, using service config
2023-08-28T11:54:23.245Z [main] info: Setting log level to debug
2023-08-28T11:54:23.251Z [main] info: Opening serial connection to /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AB0LZ14G-if00-port0, slave ID 1
/app/entrypoint.sh: line 7:   146 Segmentation fault      (core dumped) node --unhandled-rejections=warn /app/eda-modbus-bridge/eda-modbus-bridge.mjs ${CMD_OPTIONS}
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
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 fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

[Jalle19]

Strange, this doesn't happen to me. What hardware do you run Home Assistant on?

[Jalle19]

I think I have a solution in the works

[janneho]

Raspberry pi 4 hassos, and this.

Config as here:

modbus:
  device: /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AB0LZ14G-if00-port0
  slave: 1
mqtt:
  host: ""
  ssl: false
  port: 1883
  username: ""
  password: ""
  publish_interval: 30
http:
  enabled: false
  listen_address: 0.0.0.0
  listen_port: 8080
logging:
  debug: true

[Jalle19]

I'll make a new version sometime tomorrow that should hopefully fix the issue. I don't have a Raspberry Pi 4 to test with unfortunately.

[Jalle19]

Try updating to version 1.5.0 of the addon 🤞

[janneho]

Try updating to version 1.5.0 of the addon 🤞

Evertyhing seems to be working again. Thanks for quick fix.

[Jalle19]

Good to hear!