Closed Yakkity closed 1 year ago
Will add a guard against this & log an error, but it seems that we receive an invalid value/set topic on MQTT, which is probably coming from HA.
Do you have any automation that changes a progX_time
sensors? Or any progX_
sensor?
Please try v0.5.0
Updated and now get this:
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 services-up: info: copying legacy longrun sunsynk (no readiness notification) /usr/local/bin/python3: No module named ha_addon_sunsynk_multi [08:53:19] WARNING: Halt add-on with exit code 1 s6-rc: info: service legacy-services successfully started s6-rc: info: service legacy-services: stopping [08:53:20] INFO: Service restart after closing 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
The new packaging did not go as smooth as planned. Should be fixed now
Issue related to
Sunsynk / mbusd Home Assistant Add-On
Describe the issue/bug
Updated HA core and add on terminates with python error
Expected behavior Normal startup
Your environment
Logs