-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot access to the homebridge ui after updating 4.0.0 #169
Comments
Same issue, hopefully there is a fix soon :( |
Same here. |
same here, even tried completely uninstalling, deleting the shared folder and re-installing from fresh. DS1821+ on DSM 7.2.2-72806 Update 3 |
Same here. |
You can temporarily downgrade to 3.1.3 (or whatever version you want) until they get a fix out: Uninstall Homebridge from the Package Center |
Tks for the feedback, I was trying to update the package this am. And it looks like it has issues |
Same errors on 7.2.2-72806... Thank you everyone for looking into it! |
Same issue here |
Looks like I've joined the club too. A great pity there were no notes warning of the issue. |
These are the notes as it's just being discovered lol |
Guys if I uninstall 4.0.0 prior to downgrading do I lose all the configuration files, etc? If that is the case I'll hold off on the uninstall and wait on a fix. |
I downgraded as suggested. Homebridge runs again however the top widget showing the status of available updates is empty. Any suggestions for that? edit: fixed the widget issue: reinstalled the previous version (homebridge-braswell-3.1.1.spk) and instead of restoring I did a new setup. Confirmed all was fine and did the update of the UI that was available. After that I restored my previous config and all was good again. |
Same issue here |
Same here |
Same here - Uninstalled, then manual install homebridge-braswell-3.1.3 |
One challenge we have is that we do not have access to a synology device to test releases prior to mass release. And do not have a synology sme available. #143 |
so are you saying you are running on 4.0 now? |
Sorry nope - this fixed the "update information" widget to work again |
I have the same issue after upgrading to 4.0. |
Same here, 4.0.0 stuck in reset loop with the same error message as others have demonstrated. Initially I logged in via SSH, then did the following:
The last command faulted out reporting I finally set proper permissions:
All of this has the result of allowing homebridge to start up normally and allow me to log in the web UI, but the instance reported not being paired to HK (which obviously was not the case), while attempting to add it anew resulted in a message that the accessory was already added - and indeed, it was. The accessories in HK were all reported as not responding as well. Eventually, I had to uninstall v4.0.0 and manually reinstall 3.1.3 as others have suggested. The not responding errors did not resolve until after restoring from a backup, but the Update Information widget was coming up empty. Unlocking the web UI home screen and resetting it did the trick, and the setup is working again. TL;DR: Can jimmy 4.0.0 into working, but the pairing with HK doesn't. Had to manually downgrade, waiting for a fix. |
Same here |
How did you unlock the webui home screen, to make the update information widget load again? |
Using the two lock/unlock buttons on the top right of the UI. Clicking the eye icon opens up a menu with several possible widgets and a reset button. |
Same for me. I was in DSM 7.1 with an old nodejs 18 and wanted to make a full update today... No luck. |
I reverted to 3.1.3 and will wait for a re-release of the updated package, but several affected users had success installing "reflect-metadata" in the /homebridge/app/lib/node_modules/homebridge-config-ui-x directory. See the related reddit discussion: https://www.reddit.com/r/homebridge/comments/1il3tdj/hb_400_on_synology_nas_broken/ |
Shame this wasnt tested before being released |
shame people cannot read the comments and understand why! |
This worked for me.... had to fix permissions. Thanks for the link! |
Rolled back the current release 4.0.0 to 3.1.3 |
This worked for me as well. Needed step 1 and step 4. Back up and running. Thanks! |
^ I’m interested in whether both steps 1 and 4 are really needed, or whether for example only step 4 is needed but people are doing step 1 anyway. Could anyone confirm this? I’m referring to the steps in the above comment reddit link |
yes, both are needed. |
thanks for confirming! |
I eventually used the Reddit link and steps to get me up and running again (phew)..... However on logging into Homebridge I'm informed that:
So is it safe to do these updates? |
Hello Node is updated by Synology. You can do it with terminal but not needed. It always warn for new version |
Just to confirm I've done a complete fresh install (removed the package and homebridge directory), reinstalled the 4.0.1 pre-release. Everything came online first time with no tinkering, restored from backup and everything working as should. Thank you! |
Hi all, I wanted to share my feedback, like all my HB tanked on Sunday when going to V4.0.0. I had not completed any manual steps to uninstall or rollback to V3. I just stopped the service until I had time to look at it. I manually downloaded V4.0.1 beta then triggered a manual update, restarted the service and HB is back fully working. So from my prospective V4.0.1 beta is a winner and HB runs on V4. |
Likewise, a manual install of 4.01 and all is working fine Homebridge v2.0.0-beta.27 |
Tks for the feedback on 4.0.1, just published as latest |
Thanks for your hard work :) |
Thank you! 4.0.1 installed through the normal route and full functionality resumed |
+1, updated successfully to 4.0.1. thank you! |
Thanks I'll update in that case. |
You can update Homebridge but Node.js won't update, that's a Synology package they have to release which they haven't as yet. I've moved to the Docker version now as it adds support for everything needed. This doesn't pose a problem but could avoid potential issues in the future. You can hide the node.js update notification from the gear icon on the widget. |
Thanks I'll wait on the Node.js update from Synology coming through. |
Thank you for your work on this, really appreciate you getting an updated version out so quickly, thank you. |
Describe The Bug
hello.
I just updated to 4.0.0 because there was a new update in the DSM package update, but I think it was a pre-release version.
However, since updating to this version, my homebridge ui url has become unreachable (localhost:8581)
I checked the logs, and I suspect that there was an error in the nest.js server startup.
Model: DS920+
DSM: DSM 7.2.2-72806 Update 3
Logs
The text was updated successfully, but these errors were encountered: