Luligu/matterbridge

AI Summary: A user reports that Matterbridge (v3.5.3) has stopped working after a recent update, specifically due to the `matterbridge-shelly` plugin entering an error state and halting the bridge startup. The issue is likely caused by an incompatibility between the new Matterbridge version and an older version of the plugin, which the user mentions is approximately one year old.

AI Summary: The user is experiencing issues pairing their Matterbridge instance (running in a Docker container on a Raspberry Pi) with the Google Home app. The issue manifests as a "Device Not Found" error. The task involves troubleshooting the pairing process, analyzing logs (tcpdump, Matterbridge logs), and potentially investigating network configuration or Docker setup issues to identify why Google Home cannot discover the Matterbridge device despite seemingly correct mDNS advertisement.

AI Summary: Investigate why Matterbridge version 3.1.0 cannot be updated to the latest version via the frontend. Determine if a forced update is possible, or if there's a bug preventing updates beyond 3.1.0. This may involve examining update mechanisms within the frontend code, checking for version compatibility issues, or looking for error logs that aren't being displayed.

AI Summary: The user is encountering an error ('ERR_UNKNOWN_FILE_EXTENSION') while trying to install and run the Matterbridge application on macOS. The error stems from the way the application's executable is specified in the package.json file, which is incompatible with the Node.js version being used. The solution likely involves either updating the Matterbridge package to correctly handle the file extension or adjusting the Node.js environment to support the current package configuration.

AI Summary: The task requires installing and configuring two instances of Matterbridge on a single PC, each managing a separate set of Shelly devices for distinct Matter 'Homes' on the same LAN. This involves potentially configuring different network settings or using distinct ports for each Matterbridge instance to avoid conflicts.