C-8 package manager stopped working after migration

I have a C-8, running 2.3.7.144
Reserved IP, DHCP, connected to a 100MB hub

Yesterday, I migrated from my C-7 to my C-8
My timezone is set correctly and shows accurate time
I can see and trigger most or all of my devices
I don't have any zwave ghosts, I have done a zwave repair.
I'm not getting any excessive load errors
In my logs, in the past few hours, the only error/warn events were for a Ring device I wasn't using, so I removed that

PROBLEM: my Hubitat Package Manager won't repair or update.

I've removed the app, the app code and the package and re-installed.
I've removed all unused app codes

But when I run an update, I don't see any progress
Checking for updates
Checking for updates... Please wait...
And the logs show
app:1658 2023-12-31 09:57:27.478 AM debug Update chosen
app:1658 2023-12-31 09:57:22.391 AM info Refreshing repository list

And if I try a repair, I see, I don't see any progress
Repairing Package
Your changes are currently in progress... Please wait...
And the logs show
app:1658 2023-12-31 10:09:49.898 AM debug prefPkgModify
app:1658 2023-12-31 10:09:45.335 AM info Refreshing repository list

And it just sits here for a long time, never responding.

I did try a soft reset, but on a migration .. this probably shouldn't be necessary.
I've shutdown and powered off a few times to restart the hub.

Are you able to get updates for the hub platform? Also don't use a static and a dhcp reservation, use either or. And if you use static, do it outside your DHCP pool.

1 Like

I’d consider removing the Package Manager App and reinstalling…

1 Like

I did, I completely removed the app and app code and reinstalled the groovy code direct from the githubusercontent url. I'm able to match drivers and apps, but I'm unable to repair or update or install anything

I'm unable to install or update anything.

And I am using DHCP with a reservation on my router, not a habitat-static

What messages or errors are you getting when you attempt these?

not seeing any errors.
I have a tab I opened last night
and here, 10 hours later, the page hasn't errored or timed out

  • Checking for updates
  • Checking for updates... Please wait...

and a ctrl+refresh of /logs, looking at Past Logs, I see only these two entries

  • app:1658 2023-12-31 11:44:16.886 AM debug Update chosen
  • app:1658 2023-12-31 11:44:13.149 AM info Refreshing repository list

So If you are not even able to update the hub platform then there is a prob with the hub connecting to the internet. Are you blocking in any firewall rules? Running vlans? Press the network reset button on the bottom of the hub for 7 seconds with a toothpick or paperclip (it's the only round hole out of all the square ones) . This only resets the network. Then try to update the hub.

1 Like

No firewall rules or vlans. I was able to import the groovy from the GitHub URL. I was able to import repos and match existing drivers and apps. But then unable to update or repair. .. haven't tried, is there a shell on the habitat?

.. I'll reset after lunch. Thanks

reset networking
but still unable to update
network test seems to run clean

after reset, I removed the app, removed the app-code and pre the instructions
https://hubitatpackagemanager.hubitatcommunity.com/installing.html
I re-imported the bundle from
https://bit.ly/3VfykH9
and this time, I only matched a single package - the inovelli driver package


but "checking for updates" never completes

I tried to re-install but not match any packages - but the First Run won't let me complete unless I pick a package to match ( * == required field )

Uninstalled and re-installed and picked my leviton fan driver and the app matches, but still won't update.

Does the hubitat platform itself update?

what does this mean?
I am able to control most or all devices and alexa automations work.

Settings | Check for Update

Updates in no time at all - super fast response

Currently running version: 2.3.7.144

No updates available.

And I was able to upgrade to 2.3.7.145, but this didn't fix any of the broken parts

An unmatched device id was linked to broken scheduler entries.

After the device jobs were deleted, and I rebooted .. all my services came back online

My package manage is now about to update and install packages

I ended up sending a backup file to one if the support members and they were able to identify the broken process.

1 Like