OOOOOOoooo I get it now. Yea, perhaps I released updates to HPM too rapidly.
4 updates in 2 weeks. Nothing in the pipeline though, so if anyone was hanging back.. the way is clear
OOOOOOoooo I get it now. Yea, perhaps I released updates to HPM too rapidly.
4 updates in 2 weeks. Nothing in the pipeline though, so if anyone was hanging back.. the way is clear
If you're concerned, look at the "packages" you have installed. Nearly every (possibly actually every?) developer with an app or driver in HPM has a release thread on the forums where they post about updates, and by necessity the source code is also available somewhere, usually GitHub. Be concerned if you see something there HPM doesn't see; otherwise, you might just not have anything newer available, odd as it may be to have been so long.
FWIW, I'm on HPM 1.8.6 and mine does see some updates (that I've been ignoring...), so it doesn't appear to be a universal problem if that's any consolation. I do confess that I manually updated HPM to the newer versions once instead of letting HPM update itself due to problems some others had initially (as did I on one hub), if that matters...
I just updated to 1.8.6 on my C7/2.3.2.127
Even through HPM says I'm now running 1.8.6, it sees updates available for two other versions of HPM:
It shows 2 HPMs in repair, too-
any advice?
EDIT: just found [SOLVED] Two Hubitat Package Manager (HPM) in View
After InfluxDB-Logger was added to HPM and it did an update when opeing InfluxDB-Logger I just get a blank screen on all 3 of my hubs. Is anybody else seeing this or some thoughts?
Did you do a Match Up so that HPM knew to include it? Or Install it from HPM?
Did a match up
Unable to reproduce...
This is what I just tried...
resulting in:
Basically what I did and when I go into it it's basically blank. Could something have happened to the code when it was moved to HubitatCommunity
Did you try a repair, this will usually fix this kind of problem.
"Will this affect the original code, and more importantly, the confidence in that code?" That's been my #1 test of each and every line of code I touched.
To gain confidence in the migration I very intentionally didn't alter any of the original Apps, Drivers or File pathways in the code.
The downside of keeping my fingers off the original code is... I didn't prevent/correct existing issues either. If HPM had an issue in July of last year, it probably has it still today.
Did some more testing, rolled back the firmware on the hub. Problem starts with 2.3.2.126 works under 2.3.1.142. Was just a coincidence that I only noticed it after it being added to HPM. Thanks for all you do for the community.
In case someone finds this topic before the active / specific topic.
I'm seeing a manifest error when I manually run hpm update check. Is there steps to take?
LOL
Use Un-Match
Will it ever end!?
Not until it's explained at least one hundred times.
Mind you we are getting close to that number.
In fairness, I didn't get the unmatch option until I went in and did a repair to HPM even though I was on the latest version. Unmatch wasn't even listed.
I'd need to see that. The only way to see v1.8.6 like this:
... is if the code, that contains un match was there. The "6" and all the Un Match code are part of a single package of code.
1.8.5 and less didn't have Un Match. If your eyes are like mine, a 5 and a 6 at screen distances are the same.
I have already fixed it (@bobbles made the suggestion to run a repair on HPM). I was about to head over here for help, but tried his suggestion first. Prior to repair, the settings page ended after repositories.
Edit.
It was almost like it got hung up somehow.