Add-on Throwing an Error on Start-up
Closed this issue · 1 comments
markwiese commented
What happened?
I had trouble after updating the add-on from version v2.2.0-102 to v2.3.0-103 (my Matter controller, Flic, was no longer communicating with Matterbridge) so I uninstalled the add-on from Home Assistant then installed it, again. Now, I get an error on start-up.
Your configuration
include_domains: []
include_patterns: []
include_labels: []
include_platforms: []
exclude_domains: []
exclude_patterns: []
exclude_labels: []
exclude_platforms: []
frontend_port: 8283
matter_port: 5540
Relevant log output
-----------------------------------------------------------
Add-on: Matterbridge
Populate your Home Assistant instance as Matter Bridge.
-----------------------------------------------------------
Add-on version: 2.3.0-103
You are running the latest version of this add-on.
System: Home Assistant OS 12.4 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2024.7.3
Home Assistant Supervisor: 2024.06.2
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level 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
#############################
CURRENT CONFIGURATION:
{
"homeAssistant": {
"url": "http://supervisor/core",
"accessToken": "{redacted}",
"matcher": {
"includeDomains": [],
"excludeDomains": [],
"includePatterns": [],
"excludePatterns": [],
"includeLabels": [],
"excludeLabels": [],
"includePlatforms": [],
"excludePlatforms": []
}
}
}
#############################
CLI: Matterbridge.loadInstance() failed with error: Error: [node-persist][readFile] /root/.matterbridge/storage/.matterbridge/92cd10e6b8b068a931196d1d73a032543d5ca1a5bf445e27a1af74258254517c does not look like a valid storage file!
CLI: Matterbridge.loadInstance() failed with error: Error: [node-persist][readFile] /root/.matterbridge/storage/.matterbridge/92cd10e6b8b068a931196d1d73a032543d5ca1a5bf445e27a1af74258254517c does not look like a valid storage file!
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 base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Version
2.3.0-103
markwiese commented
I found the persistent add-on storage in the Home Assistant file system and renamed the folder. The add-on now starts.