Latest Hubitat 2.3.6.136, fresh installation of HPM 1.9 using bundle URL https://bit.ly/3VfykH9
I have two hubs, C7 and C8, HPM stuck on both at "Matching packages... Please wait..."
Please help.
Have you tried waiting? 
(This can actually take a while.)
If so, the next thing I'd do is check "Logs" for errors or at least some activity from HPM, which may give you clues if there's a problem.
I saw the notice of 'waiting'. It has been more than 2 hours.
I already tried soft reset C-7, then install HPM. It still showing waiting after 2+ hours.
Is that normal?
Others may have some ideas, but I don't see anything wrong there off hand.
It seems like when I run HPM, it is stuck after the two log lines.
I don't understand why it happens to a freshly soft reset C-7.
Here is the step by step screenshot of the issue,
When I go back to 'Apps' and try again, it shows the same output.
Unable to duplicate.
I have a C-7 on Platform v2.3.6.136 and when I click Match Up, I get this at the very end:
"downloading package manifests" usually is visible for a moment, then the last 3 are nearly impossible to capture/see because the screen refreshes at that point with 1) the list of match options or 2) the no new matches screen.
Those screens get refreshed every two seconds and therefore, anything that completes in under two seconds is not seen. Which is why the "Retrieving list of installed apps", "Retrieving list of installed drivers" and "Matching up packages" are so hard to capture/see, as one example. However, those are logged and are fully visible:
I'm not sure what you are trying to tell me. "Refreshed Jonathan Fields" is where mine stops. I left it there for an hour.
I'm saying, the screens you are capturing and showing CAN sometimes not tell the whole story. Instead, can you get a screen cap of the logs page, please.
1 Like
HPM in both Hubitat shows running OK now this morning (passing the stuck-point).
I guess it is just taking time to complete the process.
So for those who encounter the similar situation, just wait for 12 hours. 
Rebooted>>Removed HPM>>rebooted>>rolled back to 2.3.5.152>>reinstalled HPM here is the result. I guess I'll let it bake overnight. app:102023-09-22 09:23:42.897 AMinfoRefreshed Dave Gutheinz(DavGut)
app:102023-09-22 09:23:42.875 AMinfoRefreshed storageaanarchy (SANdood)
app:102023-09-22 09:23:42.860 AMinfoRefreshed RMoRobert (BertABCD1234)
app:102023-09-22 09:23:42.741 AMinfoRefreshed Ramdev Shallem
app:102023-09-22 09:23:42.735 AMinfoRefreshed heidrickla (Lewis.Heidrick)
app:102023-09-22 09:23:42.699 AMinfoRefreshed dman2306
app:102023-09-22 09:23:42.688 AMinfoRefreshed bcopeland
app:102023-09-22 09:23:42.652 AMinfoRefreshed BPTWorld
app:102023-09-22 09:23:42.604 AMinfoRefreshed Victor Santana (Welasco)
app:102023-09-22 09:23:41.886 AMinfoRefreshing repository list
app:102023-09-22 09:23:41.792 AMdebugPerforming Package Matching
app:102023-09-22 09:23:38.606 AMdebugprefPkgMatchUp
app:102023-09-22 09:23:37.980 AMinfoRefreshing repository list
I was having trouble getting to Github last night. If Github was down, you might have seen this result.
1 Like
It completed overnight. Nothing in the log about completing, but all good now.
Looks like I was able to figure out the issue. The very last element in the repositories list was actually a duplicate:
{
"name": "Yonatan Striem Amit",
"location": "https://raw.githubusercontent.com/yonatan-mitmit/hubitat-repository/main/repository.json"
}
So, looks like HPM was unable to resolve it. I've tried removing it manually, and changing repositoryListing to point to the file without the duplicate — and everything worked just fine. @csteele , I could send a PR to fix it; could you please double check how is it handled within the HPM — I'm rather new with it, but I know for sure there is a lot of magic Groovy could do for you under the hood.
4 Likes
Master Repository has been updated.
2 Likes
