The Hubitat Package Manager Master Repo json file is probed (each repo read, each package manifest within is read, down each rabbit hole) to create the DB that Fast Search uses on :20 min, :40 and :00 marks. It takes just over 2 min to run. So, depending on when your change gets released by Github, you might wait 22 mins to find it in Fast Search.
I don't remember what Dominic's Fuzzy Search refresh timing is.. 2hours maybe??
thanks will try again in 1/2 hr and see.
ok now finding package but match up not finding it.. maybe different update schedule for that or some other issue.
Match Up requires that the name of the app/driver and namespace as shown in the code list, exactly matches the definition in the package manifest. I have seen where this was not done correctly and it breaks the matchup.
it also doesnt work if you specify a too high hub firmware version lol
I did that last month and it took WAY too long for me to discover. 
Released v1.9.2
same here
Hi I'm not seeing an option to update package manager in Package Manager update, I'm on v1.9.1, also when I do a repair on Package Manager it comes back with (The manifest file null no longer seems to be valid.)
It is true, those darn double quotes... 
I'll fix it asap.
You'll probably have to do a Repair because HPM treats itself as special
Thanks that did it. upgraded to v1.9.2
FYI, @csteele, in case it's supposed to be ready now HPM has hung on me doing the HPM update at:
That is, unfortunately, another example of HPM upgrading itself and landing on different code, because the upgrade moved it.
It's quite possible it's purely cosmetic. But I've been suggesting a Repair to make sure.
Interestingly, it did finally finish and says 1.9.2, so that's good.
I'm going to have to make a module that is a stand alone HPM Only Installer I think, like a Child App, so it doesn't move around during execution.
How long did yours take? I'm approaching 9 minutes on both hubs. With the same error in the logs. I knew I should of updated them one at a time.
[edit]
nevermind. It did finish, just never went to a finished screen. I went back to the main HPM page and saw it did update to 1.9.2. Did a repair on it just in case.
So besides all that. Does the 7 minute keep alive take care of the issue where we can't update webcore before it times out?
Hey, thank you for the continued dedication to this app. I use it both to manage my apps; and I have an app in the repo. So again, thank you!
Okay, so I noticed my HPM update page had an app that I had once tried on a device; and since removed (at least I thought). This is for a 3rd reality power monitoring plug. The plug was extremely chatty, and I removed it from hubitat (I thought).
Now, if I try to uninstall the 3rd reality driver from within HPM, I receive the following error:
So, HPM thinks this driver is in use by a device. Okay, that makes sense as I have been seeing an "unknown" in my zigbee device table.
I am assuming this is a route for the chatty plug I tried, and "thought" I removed. This was over two months ago, and the plug was returned to Amazon.
Any suggestions on how I might move forward with getting this deleted?
A route for an unknown device would not cause the driver code to be in use.
First thing you could try is manually deleting the code.
If that does not work, go to the devices list and look at the "Type" column. Look for any devices using that driver. It also seems like the search up top also searching that column so you could search for "Third Reality"
Any device using that driver is what would prevent the code from being deleted.
When I deleted the code for the driver; I tried to remove from HPM with the same result.
And more interesting; I deleted the app from hubitat; ran a matchup from HPM, and it was found again.
Thank you, I am sure it is not in use in the "types" column. I just triple-checked.
It's like hubitat has a "placeholder" for this device, although it is not in the devices list, and HPM is finding that somehow.
I know I did this to myself... just thought you may have encountered something similar in the past.
EDIT:
Exactly what I thought. I am sure that driver is not assigned to any devices in my devices list.
Download the Hubitat app
