Can't start version 1.0.6 (22.12.2023)

[timostr]

Version 1.0.16 from 22.12.2023 refuses to start: 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 Preparing to run modbus-proxy Upstream: 192.168.188.56:1502 Listen: 8887 Timeout: 60 Connection Time: 2.0 Loglevel: INFO Generated Config devices:

• modbus: url: 192.168.188.56:1502 # device url (mandatory) timeout: 60 # communication timeout (s) (optional, default: 10) connection_time: 2.0 # delay after connection (s) (optional, default: 0) listen: bind: 0:8887 # listening address (mandatory) logging: version: 1 formatters: standard: format: "%(asctime)s %(levelname)8s %(name)s: %(message)s" handlers: console: class: logging.StreamHandler formatter: standard root: handlers: ['console'] level: INFO /run.sh: line 29: ./venv/bin/activate: No such file or directory 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

[Vaszago]

I have the same error. Can't start

[jerhaag]

Same issue. Add-on does not start:

/run.sh: line 29: ./venv/bin/activate: No such file or directory

[Schlichi83]

I have the same problem. Shouldn‘t have updated :-(

[faithless11]

Yes same Problem here... /run.sh: line 29: ./venv/bin/activate: No such file or directory

[abard35]

Same issue

[requiemmg]

Add me to the list...

[daklemo]

Welcome to the club... ... same problem here

[Uhae]

Same problem here.

[ManfredGiesinger]

Same problem here with 1.0.16,

• restored 1.0.15, which works for me

[Schlichi83]

Same problem here with 1.0.16,

• restored 1.0.15, which works for me

How did you manage to restore?

[Uhae]

I also just restored and it works fine. Settings -> System -> Backups and then choose the backup you created while updating (in my case: addon_bc3b947b_modbus_proxy_1.0.15

[abard35]

Same problem here with 1.0.16,

• restored 1.0.15, which works for me

How did you manage to restore?

[Schlichi83]

Thank you - worked like a charm! :-)

[Vaszago]

The problem is that version 1.0.15 cannot be installed for me.

[MrMontesa]

Same issue. restored backup as workaround. keep in mind to untick the "enable automatic updates" for now.

[Akulatraxas]

Oh sorry, i did not expect that the base container of the addon does not get rebuilded but it uses the run of the new version. 1.18 will arrive soon that should fix the problem. Hit the "rebuild" button after update if the error persists.

[requiemmg]

Just to add, I tried with a rebuild and full system restart, issue persisted. Thanks for the update.

[turbolooser]

1.017 + rebuild error still persist. reverting back to 1.015

[Vaszago]

Now another mistake

[Akulatraxas]

Wait for the 1.0.18 to show up, then update. If the error persists hit the Rebuild button.

[Vaszago]

Thanks, problem solved. Works perfectly again.

[daklemo]

Confirm: 1.0.18 fixed the problem

[abard35]

Works again. Thanks