Hey @csteele, I think my only package isn't showing up in HPM anymore when searching. If I look at the drop down of repositories, I don't see mine listed anymore. Can you help me figure out why?
Release: v1.9.12
PR#20: self-heal stale/removed app & driver heIDs cached
This change targets rollbacks caused by users manually deleting code that HPM has in its DB. The classic fix for this is to UnMatch the manually managed Package, then Match Up and Repair. The change tries to detect the specific situation and repair it on the fly.
Thanks to @jonozz for the PR.
Does this have any effect on code that was intentionally chaged? I.e. Say... I have edited lines in Echo Speaks to change the cookie refresh time. It isn't going to auto repair those changes is it?
HPM is focused on getting code aka Packages, onto or off your hub. HPM does not alter the code itself. Repair would replace the code with whatever is found in the repo for that Package. But you'd have to click the Repair button to cause that. Update will replace older code in Packages with newer code.
If you are manually manipulating the code, HPM can't possibly know that and protect you from yourself. Nothing about THAT has changed in this release.
IF you asked HPM to Install a Package, and let's imagine you asked for several optional components of that Package. Then days later you delete, manually, one of the components. Now the HPM DB and the Hub don't match. Trouble will find you eventually 
The classic solution has been to UnMatch the package and then Match Up to get back into alignment. But that requires that you remember that you manually broke the Package on your hub. This update TRIES to detect that and fix it.
So was trying to clean some stuff up and noticed i was still on the old Home Connect integration and tried to update. I keep getting a fatal error on uninstall and when I try to refresh the hood driver for Home Connect hood. It seems more of an HPM error. I have tried repairing as well and that has not worked either.
Also tagging @craigde
I installed it from scratch just a moment ago.. not able to duplicate since I've never installed it before. I also deselected the option to configure the Package, since I don't have any use for it. I've removed it too.
I suspect the errors come from HPM, not the home connect. I would try this
Old "Home Connect Integration" (non-v3):
- Delete its devices, then remove the old Home Connect app from Apps.
- Delete any remaining old Home Connect code by hand under Developer Tools → Apps Code and Drivers Code. Only remove entries without "v3" in the name.
- In HPM, go to Package Manager Settings → Un-Match a Package → Remove a Matched Package, choose the old Home Connect Integration, then click Next and Done. This only removes it from HPM's list. It doesn't change anything on the hub.
Home Connect Integration v3:
4. Use the same Un-Match steps for Home Connect Integration v3. Your devices and code stay as they are.
5. Run Match Up. HPM links the package to the v3 app and drivers that are actually installed, with the correct IDs.
6. If the Hood v3 driver isn't installed any more, use Modify a Package → Home Connect Integration v3 and select the Hood driver. Then run Update to get the latest version (3.3.25).
After that, Update and Repair should work normally.
At least I think that might work based on some investigation
Unmatch worked! Thank you. Was driving me a bit nuts. Once I did that and re did the login, my hood was created. Thank you sir!
Sorry, if my issue is something worth investigating, then happy to help, otherwise happy to fade into the background...
Huh?
I am very lost now...
Sorry, I wasn't making much sense earlier.... Please ignore my posts....
Whew.. glad to know it wasn't my reading skills
Nah. My posting skills are lacking.... It's been a while...
Feature request - sort of? Could HPM push this warning inside the app for when I run updates (or allow me to stop it here by adding a 'Enable Warn logging: )
instead of the log? I know what my OS version is and don't desire changing. IMHO, HPM isn't really needed to track my version of OS at all, thats Hubitats job and they do that well. I already have the red alarm 
I do understand the log entry - no one needs to explain that to me!
found a fix - disabling HPM solves it!