To put my last post more simply.... Could we not just offer dev's the option to publicise a unique key of some sort that users can use when "searching" HPM?
HPM has, and always had, 3 search mechanisms.
Only the first one uses an external tool. Originally, it was Azure only. I thought it was rather slow, given other search experience we all have. I added Fast Search, doubling the external tools, back in May of 2022. Certainly Developers can offer instructions via either of the two BUT "just search for: <word>" does feel a bit more straightforward. 
5 Likes
Wouldn't tags be a similar solution?
similar to which discussion point??
'by Tags' doesn't use an external tool and neither does 'from URL'
My point is that human nature is what it is.. developers, being human, (most of them,) then they take the easy path and document to their users: "just click search by keywords...."
I think in a way the search works already kind if does that.
For instance, in my directions to install my Govee Integration i direct folks to use Keyword Govee. I am really not sure what benefit adding a additional tag seaerch would help. When i search for zooz zen driver i search for zen or zooz then check thr description of thr displayed packages for the device.
I would also add it could be beneficial to see more then just one result. When i do it triggers me to look and think a little deeper about what is avaliable and what the differences are.
1 Like
Not sure it has to be an external tool. Just a quick way to find an app for a specific purpose.
This is kinda what I was getting at.
I have most of the apps I need/want now from HPM. When I was first looking, I would browse looking for generic things I was looking for.
However, occaisionally, I would see one that I was looking for in particular in a community post. Sometimes, finding that specific one could have been made easier if it had a key number or specific tag unique to that specific app. Usernames do not always = developer names, and when multiples come back off of a search, you sometimes don't always get the one you wanted (scratching your head when the app interface doesn't match the screenshots on the community post).
Most definitely not knocking the app, it is flat out amazing at what it does at making things easy to install. Not sure how the tags work, if they are developer entries or not. If they are, they could easily give an app a unique tag that we could lookup for confirmation we are getting the correct (or better word, "specific") app we were looking for.
Tags are a specific list that is maintained adjacent to the Master Repo:
So making a unique Tag isn't an option, given the generic nature of Tags.
I don't know what Dominic's thinking was for "categories" vs "tags" except I do remember him saying Categories is obsolete, back in 2022 or earlier.
Equally, I don't know why he added unique UUIDs to both repository levels (Intermediate and PackageManifest) and then basically never used them.
2 Likes
I got the same error, I think?
app:92026-02-17 02:39:58.343 AMdebug No updates available
app:92026-02-17 02:39:56.722 AMinfoChecking for updates for hubitat_broadlink
app:92026-02-17 02:39:56.551 AMinfoChecking for updates for Tuya Zigbee Contact Sensor++ w/ healthStatus
app:92026-02-17 02:39:55.457 AMinfoChecking for updates for Zigbee Map
app:92026-02-17 02:39:55.298 AMinfoChecking for updates for Nightly Battery Monitor APP
app:92026-02-17 02:39:55.154 AMinfoChecking for updates for Device Activity Check
app:92026-02-17 02:39:54.963 AMinfoChecking for updates for Tuya Multi Sensor 4 In 1
app:92026-02-17 02:39:54.924 AMinfoChecking for updates for Hubitat Package Manager
app:92026-02-17 02:39:54.770 AMinfoChecking for updates for Echo Speaks
app:92026-02-17 02:39:54.598 AMinfoChecking for updates for Govee Matter Drivers
app:92026-02-17 02:39:54.428 AMinfoChecking for updates for Remote Builder
app:92026-02-17 02:39:54.227 AMinfoChecking for updates for Tuya Zigbee mmWave Sensor
app:92026-02-17 02:39:53.971 AMdebugUpdate chosen
app:92026-02-17 02:39:49.022 AMdebugUpdating HPM version to 1.9.9 from previous upgrade
app:92026-02-17 02:36:07.796 AMerrorjava.lang.NoClassDefFoundError: user_app_dcm_hpm_Hubitat_Package_Manager_138$_copyInstalledItemsToNewManifest_closure100 on line 4214 (method performUpdates)
app:92026-02-17 02:35:17.782 AMinfoUpgrading Hubitat Package Manager
app:92026-02-17 02:35:17.220 AMinfoDownloading Hubitat Package Manager
app:92026-02-17 02:35:16.737 AMdebugPerforming update
app:92026-02-17 02:35:00.282 AMdebugprefPkgVerifyUpdates
app:92026-02-17 02:34:53.627 AMdebugUpdates available
app:92026-02-17 02:34:38.703 AMdebugUpdates available
app:92026-02-17 02:34:36.716 AMinfoChecking for updates for hubitat_broadlink
app:92026-02-17 02:34:36.542 AMinfoChecking for updates for Tuya Zigbee Contact Sensor++ w/ healthStatus
app:92026-02-17 02:34:35.733 AMinfoChecking for updates for Zigbee Map
app:92026-02-17 02:34:35.520 AMinfoChecking for updates for Nightly Battery Monitor APP
app:92026-02-17 02:34:35.376 AMinfoChecking for updates for Device Activity Check
app:92026-02-17 02:34:35.234 AMinfoChecking for updates for Tuya Multi Sensor 4 In 1
app:92026-02-17 02:34:35.233 AMdebugUpdates found package for https://raw.githubusercontent.com/HubitatCommunity/hubitatpackagemanager/main/packageManifest.json -> null (force production: true)
app:92026-02-17 02:34:35.228 AMdebugUpdates found for package https://raw.githubusercontent.com/HubitatCommunity/hubitatpackagemanager/main/packageManifest.json
app:92026-02-17 02:34:35.186 AMinfoChecking for updates for Hubitat Package Manager
app:92026-02-17 02:34:35.029 AMinfoChecking for updates for Echo Speaks
app:92026-02-17 02:34:34.853 AMinfoChecking for updates for Govee Matter Drivers
app:92026-02-17 02:34:34.642 AMinfoChecking for updates for Remote Builder
app:92026-02-17 02:34:34.428 AMinfoChecking for updates for Tuya Zigbee mmWave Sensor
app:92026-02-17 02:34:34.155 AMdebug Update chosen
This thread is gigantic. Will take me forever to read. Can someone TLDR it for me and tell me if I need to do anything about this?
Click on the Home button:
Then go back into HPM, you'll probably see the version is correct:
When HPM is done upgrading ANY package, it wants to end by displaying this screen:
But, because the upgrade involved HPM itself, the code for that page has probably moved. This v1.9.9 has moved some code to the TOP, and future code changes are likely to be further down in the 4100 lines that are HPM. Ideally, that means the NEXT version of HPM will have the before and after code in the same spot. I wish all of us good luck with that
4 Likes
I just ran the most recent upgrade and this is what I have after 5 mins.
app:152026-02-17 03:23:07.479 PMerrorjava.lang.NoClassDefFoundError: user_app_dcm_hpm_Hubitat_Package_Manager_133$_copyInstalledItemsToNewManifest_closure100 on line 4212 (method performUpdates)
app:152026-02-17 03:22:26.483 PMinfoUpgrading Hubitat Package Manager
app:152026-02-17 03:22:26.105 PMinfoDownloading Hubitat Package Manager
app:152026-02-17 03:22:00.200 PMinfoSkipping a bad package manifest Basic Z-Wave tool. java.lang.NullPointerException: Cannot get property 'betaLocation' on null object Please notify the package developer.
app:152026-02-17 03:22:00.190 PMinfoSkip download of https://www.hubitatcommunity.com/hpm/BasicZwaveTool.json: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Please notify the package developer.
app:152026-02-17 03:21:59.272 PMinfoChecking for updates for Rachio Community Package
app:152026-02-17 03:21:58.590 PMdebugUpdates found package for https://raw.githubusercontent.com/imnotbob/webCoRE/hubitat-patches/HE/packageManager.json -> null (force production: true)
app:152026-02-17 03:21:58.588 PMdebugUpdates found for package https://raw.githubusercontent.com/imnotbob/webCoRE/hubitat-patches/HE/packageManager.json
app:152026-02-17 03:21:57.446 PMinfoSkipping a bad package manifest Xiaomi Aqara Mijia Sensors and Switches. java.lang.NullPointerException: Cannot get property 'betaLocation' on null object Please notify the package developer.
app:152026-02-17 03:21:57.440 PMinfoSkip download of https://raw.githubusercontent.com/waytotheweb/hubitat/main/drivers/Xiaomi_Aqara_Mijia_Sensors.manifest.json: groovyx.net.http.HttpResponseException: status code: 404, reason phrase: Not Found Please notify the package developer.
app:152026-02-17 03:21:57.089 PMdebugUpdates found package for https://raw.githubusercontent.com/HubitatCommunity/hubitatpackagemanager/main/packageManifest.json -> null (force production: true)
app:152026-02-17 03:21:57.083 PMdebugUpdates found for package https://raw.githubusercontent.com/HubitatCommunity/hubitatpackagemanager/main/packageManifest.json
app:152026-02-17 03:21:57.009 PMinfoChecking for updates for Hubitat Package Manager
app:152026-02-17 12:00:20.383 AMinfoSkipping a bad package manifest Basic Z-Wave tool. java.lang.NullPointerException: Cannot get property 'betaLocation' on null object Please notify the package developer.
app:152026-02-17 12:00:20.378 AMinfoSkip download of https://www.hubitatcommunity.com/hpm/BasicZwaveTool.json: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target Please notify the package developer.
app:152026-02-17 12:00:19.725 AMinfoChecking for updates for Rachio Community Package
app:152026-02-17 12:00:19.512 AMdebugUpdates found package for https://raw.githubusercontent.com/imnotbob/webCoRE/hubitat-patches/HE/packageManager.json -> null (force production: true)
app:152026-02-17 12:00:19.510 AMdebugUpdates found for package https://raw.githubusercontent.com/imnotbob/webCoRE/hubitat-patches/HE/packageManager.json
app:152026-02-17 12:00:15.392 AMinfoSkipping a bad package manifest Xiaomi Aqara Mijia Sensors and Switches. java.lang.NullPointerException: Cannot get property 'betaLocation' on null object Please notify the package developer.
app:152026-02-17 12:00:15.385 AMinfoSkip download of https://raw.githubusercontent.com/waytotheweb/hubitat/main/drivers/Xiaomi_Aqara_Mijia_Sensors.manifest.json: groovyx.net.http.HttpResponseException: status code: 404, reason phrase: Not Found Please notify the package developer.
app:152026-02-17 12:00:15.024 AMdebugUpdates found package for https://raw.githubusercontent.com/HubitatCommunity/hubitatpackagemanager/main/packageManifest.json -> null (force production: true)
app:152026-02-17 12:00:15.018 AMdebugUpdates found for package https://raw.githubusercontent.com/HubitatCommunity/hubitatpackagemanager/main/packageManifest.json
app:152026-02-17 12:00:14.987 AMinfoChecking for updates for Hubitat Package Manager
It looks to be stuck. Please let me know how to fix this? Thanks.
EDIT:
Closed the tab by mistake and went back. No upgrade to do so maybe it did upgrade? Just did not close completely? Checked the version.
I was on 1.9.7 and was getting similar errors. I fixed it by repairing HPM. After I did that, my next 'update' showed 6 packages needed update.
Go into HPM and select Repair, and then select HPM in the repair drop down. It might be helpful to have the live logs window open while this runs (with HPM selected), as it might not return the HPM menu.
1 Like
Thanks that seems to caused on errors and it completed.
Wonder if “special casing” HPM updates of HPM to change it into a REPAIR of HPM makes sense?
1 Like
I don't see how... the problem is really the same.. when Repair finishes, it also wants to display the Complete page, which isn't where it was either.
Got it. Maybe instead of returning to display that page, maybe preload a return to the “HE system” like Done from main page does.
Then starting it again would bring in the new version.
Just “spitballin’” here.
1 Like
Thanks for the ideas...
I've built a special version of HPM for myself that reverts my Development hub back to HPM v1.9.4. Which then allows me to do the Upgrade zillions of times a day. Although the potential is zillions, I've tried it a few dozen times and never hit the Hang. It's discouraging to not have a way to replicate, because I'd happily fix it.
Even with my 4 Production hubs, the upgrade hangs very rarely and 100% unpredictably.
3 Likes
Are there any docs for using .zip files for distributing apps with HPM?
I see there is an instal.txt and update.txt in the 2 apps .zip files I've found that use this method with examples for apps, drivers, libraries... but not files.
If there are not docs yet for this, what would the entry look like in instal.txt for image.png?
