[RELEASE] Hubitat Package Manager (HPM) -- HubitatCommunity

I have fixed this. I found a similar issue at this link a few days ago. The Hub event log kept showing a device issue with device 217:

I tried copy/pasting the URL that the page in the URL above describes, but it just redirected to my Hubitat startup page. Turns out I had to use https:// versus http://

So as an example: https://your-hub-IP/hub/advanced/deleteDeviceJobs/XYZ
http://your-hub-IP/hub/advanced/deleteAppJobs/XYZ

Thanks,

Travis

2 Likes

Update

It seems it is not an HPM issue because I was able to update different apps using HPM. It seems mainly the both apps "Ambient Ecowitt weather Drivers" and "Weather Service Monitor 4 Hubitat Drivers" are causing the issue. @snell did you change anything which coud cause this issue?

Thanks!


Hi @csteele, today I tried to do some updates on my C7 (running latest 2.3.9.158, HPM 1.9.3). Getting error messages and fatal error messages while trying to update apps with HPM.

Also get error messages in the log files

Also saw same bad manifest messages in the log

Any help is very appreciated

Please let me know if you need further information

Thanks in advance

I do not know what the "Be sure the package is not in use with devices." message in HPM means. Nothing has changed about how I updated the manifest(s) for either of those. There were updates to the drivers and I changed their respective version numbers same as always. I even used the Hubitat driver code Import function for the WeatherSensorChild driver (I needed to update it myself on one of my other hubs) and it worked without issue, so it appears my website is working properly.

A repair of both apps/driver resolved the issue for me.

I don't know, what was the issue but currently it looks fine...... Hopefully it stays this way :slight_smile:

1 Like

@csteele I want to uninstall an app via HPM. Unfortunately I get the following message

The developer of Bundle Manager told me that the main app is dead and I could remove the app from my hub. I guess even the github link isn't existing anymore.

What's the best way to remove Bundle Manager without messing up with HPM?
I guess I can remove the app manually but what's do I consider regarding HPM to stay in sync?

Thanks

Go to your apps list (installed apps not code) and make sure the app is removed from there first, then you can uninstall via HPM.

If you want to manually remove it, In HPM go to settings > Unmatch (at bottom) and unmatch the package. That makes HPM forget about it. Then you can manually remove the app code.

3 Likes

I'd use that method if it were me:

UnMatch it and then remove the code from Apps Code, Drivers Code and Libraries Code.

2 Likes

I did some stupid things with Owntracks app and installed app manually. Now I would like to return back to situation where HPM updates app when necessary.
This one is manually installed by me:

As I chose "repair" option HPM said:
image

After that Apps code shows two instances:

Lower one is installed by using HPM. Now the problem is that it doesn't say that is is used by Owntracks App. Upper one is and it says "Used by Owntracks". I would like to remove that upper one and start to use lower on handled by HPM. Is there a way to do that?

I tried "Match up" option but that did not find anything to match up.

Did you do the matchup before or after you installed the duplicate?
You need to uninstall from HPM now, to remove the duplicate, THEN do a matchup and match to installed code.

Tried both. Before and after. If I remove owntracks doesnt it remove both app and drivers then? That is what Im trying to avoid because if drivers are gone then the devices are gone too.

The hub wont let you delete the code if its in use by an installed app or driver. You need to get it out of HPM totally (and remove the duplicate code) before you can run the matchup. Either by uninstalling or by using UnMatch (in HPM settings). If the matchup is not working at that point then the manifest for the package is not setup correctly.

The method to get HPM to manage manually installed code is MatchUp.

You should have been able to simply run MatchUp and be offered OwnTracks. To test, Unmatch OwnTracks and MatchUp, it should find the not-in-use instance, at least.

To get back from having two copies:

  1. UnMatch OwnTracks.
  2. Manually Delete the not-in-use copy of the code (3 bits of code).
  3. MatchUp to detect the original manual install and have HPM manage the code.
  4. Repair to make sure all the pieces are installed.
2 Likes

Oh man.. running from issue to new issue.. I do not see "unmatch" option at all.

EDIT: ah..version 1.8.2.. maybe I should update HPM first.

EDIT2: so the reason for getting nothing out from the match up was that I did have HPM version 1.8.2 which is quite old. After I manually pasted newest code to HPM app it finally found owntrack to match..but also hpm and webcore to match.. so that was the reason.

1 Like

I think any updates you have done with the old HPM possibly installed duplicate code as well, so you may want to check things over in the List in HPM and also in the code lists. You may need to unmatch and re-match some packages if anything else got messed up from the old HPM version.

The use of older code, and thus the lack of features, is probably pretty common. It's the main reason I added a version on each page of HPM:

Screenshot 2024-08-08 at 9.27.10 AM

So... not seeing ANY version in that upper right corner, means you're running very old code. (more than 2 years ago)

3 Likes

Couple of hours ago as I was completely lost what to do.. I checked app list and saw 5 different lines of owntracks app. One that was in use and other 4 that was months old. This explains a lot.

Yeah that was empty..so the version was.. if I remember right from 2022. :roll_eyes:

1 Like

It was suggested my post may get better response if posted here -
I'm getting a 500 error specifically from the Garage Door driver of the HADB. Wondering if anyone has solved or recognizes the existence of a problem.

I resolved this with HPM - Repair.

Unable to duplicate.

As you know, HPM goes to a Success screen the moment all of the components of a package are installed/updated and so that screen cap is the final one I got, before it vanished. However, GDO is in there, successfully.

1 Like

Also unable to duplicate, but I do have Garage Door Opener device on HADB (ratGDO).