search

hoobs-org / HOOBS

Build your Smart Home with HOOBS. Connect over 2,000 Accessories to your favorite Ecosystem.
https://hoobs.org
GNU General Public License v3.0
553 stars 51 forks source link

V 4.0.109 refuses to update #1717

Closed Wish2021 closed 2 years ago

Wish2021 commented 2 years ago

does anyone have a solution for Hoobs not updating system software? I've been stuck at V. 4.0.109 for a month. I've rebooted Hoobs and my Mac with no success.

The update window just spins.

askovi commented 2 years ago

Please run this fix command from the HOOBS terminal:

curl -sk https://dl.hoobs.org/fix | sudo bash -

Calorion commented 2 years ago

I did that and now the HOOBS interface is not loading.

BobbySlope commented 2 years ago

Try the following

hoobs.local hoobs/ Or the ip adress given by your router

jwvanderbeck commented 2 years ago

Having I think the same issue trying to update from 4.1.11. I purchased the prebuilt Homebridge in a box thing. I click update and it fails with the following information:

12:40:17 PM Some packages could not be installed. This may mean that you have
12:40:17 PM requested an impossible situation or if you are using the unstable
12:40:17 PM distribution that some required packages have not yet been created
12:40:17 PM or been moved out of Incoming.
12:40:17 PM The following information may help to resolve the situation:
12:40:17 PM The following packages have unmet dependencies:
12:40:18 PM hoobs-cli : Depends: nodejs (>= 16.13.0) but 14.18.2-deb-1nodesource1 is to be installed
12:40:18 PM hoobsd : Depends: nodejs (>= 16.13.0) but 14.18.2-deb-1nodesource1 is to be installed
12:40:18 PM E: Unable to correct problems, you have held broken packages.
12:40:18 PM WARNINGservice restart command received
12:40:13 PM restarting

I tried SSHing into the device to run the above command but the username/pw I use to login to the webapp doesn't appear to work for SSH.

Calorion commented 2 years ago

Try the following

hoobs.local hoobs/ Or the ip adress given by your router

I did all of that, but nothing worked. I eventually used the CLI to restore to factory settings, reinstall, and reload a backup, which worked—and, indeed, solved other problems.