[Bug]: Matterbridge Add-on Not Starting After 2.6.0 Update #262
Comments
chalk-hwang
changed the title
chalk-hwang
changed the title
chalk-hwang
changed the title
|
Okay, I see several things there:
|
|
Is this the configuration you wanted to test with? include_domains: []
include_patterns: []
include_labels: []
include_platforms: []
exclude_domains:
- sensor
exclude_patterns: []
exclude_labels: []
exclude_platforms: []
frontend_port: 8283
matter_port: 5540
overrides: |
{
"domains": {
},
"entities": {
}
} |
|
can you fix it asap ? i lost functions because cant run , I didn't toke backup before upgrade and I regret it |
|
👆 See pull request link above Issue caused by node-ansi-logger dependency update to v2.0.7 used in Matterbridge. |
|
@tammeryousef1006 since this is a bug with matterbridge we need to wait for the pull request to be merged and published. I’ll keep this issue open for others to find it. |
|
Interestingly I couldn’t reproduce it with my local development environment. Even with explicitly upgrading to the broken version… anyway I have added an ugly hotfix which patches the NodeAnsiLogger to work both ways (the static and non-static way). could someone please upgrade to 2.6.1 and test? |
|
thanks , i upgrade to 2.6.1 and GUI frontend came up , its running |
|
got this after adding some temp and humd sensors |
|
crashed again |
|
} |
|
i found an old backup version 1.5.0-71 , i restored and running well , waiting for update later |
|
Now you got a corrupted storage... We don't have a fix for that at the moment. But maybe we can use yours to investigate a bit more:
|
|
Hmm weird:
Sadly the old logs are not available after a restart. |
|
if i delete the addon will this fix the issue ? |
|
Probably not, because Home Assistant does not reliably delete the addon storage. I dont have much experience with the filebrowser, but maybe this could help: |
|
thats what inside the corrupted file {"key":"globalModulesDirectory","value":"/usr/local/lib/node_modules"} |
|
and this is the whole folder if it helps |
|
i already toke backup and upgrade to latest , its stable now because I don't try to add or remove entities |
|
Thank you. |
What happened?
After updating the Home Assistant add-on, it terminates with the following error. Suspecting that an error might have occurred during the update process, I tried removing the add-on, deleting the configuration values from addon_config, completely rebooting the Home Assistant OS, and reinstalling the add-on, but the issue persists.
Your configuration
Relevant log output
Version
2.6.0
The text was updated successfully, but these errors were encountered: