ring: Error loading plugin "homebridge-ring"
Bug Report
Describe the Bug
A clear and concise description of the problem...I just updated to version 11.5.0 and now i keep getting the following error
11/13/2022, 3:37:13 PMRing BridgeWARNINGNo plugins installed. 11/13/2022, 3:37:13 PMRing BridgeLoading 1 platforms… 11/13/2022, 3:37:13 PMRing BridgeBridge is running on port 51826. 11/13/2022, 3:39:01 PMringbridge stopping 11/13/2022, 3:39:06 PMRing Bridge starting 11/13/2022, 3:39:24 PMRing BridgeERRORError loading plugin “homebridge-ring” 11/13/2022, 3:39:24 PMRing BridgeWARNINGNo plugins installed. 11/13/2022, 3:39:24 PMRing BridgeLoading 1 platforms… 11/13/2022, 3:39:25 PMRing BridgeBridge is running on port 51826.
To Reproduce
Steps to reproduce the behavior:
- Start Homebridge
- Attempt to …
- See error
Expected behavior
A clear and concise description of what you expected to happen.Screenshots/Logs
If applicable, add screenshots and log output to help explain your problem.Additional context
Add any other context about the problem here.Homebridge Ring Config
Post homebridge-ring platform config without sensitive information
HIGHLIGHT THIS TEXT AND POST CONFIG HERE
DO NOT INCLUDE YOUR REFRESH TOKEN OR EMAIL/PASSWORD (replace them with xxx)
Environment
- OS: [e.g. Raspbian]
- Node.js: [e.g. 12.14.1]
- NPM: [e.g 6.13.4]
- homebridge-ring: [e.g 6.0.3]
- homebridge: [e.g. 0.4.50 or N/A]
- hoobs: [e.g. 0.4.50 or N/A]
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 18 (2 by maintainers)
Commits related to this issue
- Switch back to tsc for building homebridge-ring Possible fix for #1096 and #1098 — committed to dgreif/ring by dgreif 2 years ago
Currently experiencing this issue as well after updating to 11.5.0 @dgreif
YES !!! 👍
11.5.1 update works for me
@dgreif Helpful tip for anyone might be experiencing this issue. I was able to restore my HOOBS Box containing the plugin from a backup that plugin version 11.3.1 (which just so happened to be the version I had previously before updating to the latest). According to the logs, the error I encounter previously went away after the restore, and the plugin now works as expected. Perhaps this issue is isolated to the latest the version, so maybe restoring to an older version of the plugin if possible might work in the short term, until a fix is pushed for the latest version.