I have no idea if it will be or not, but it may be helpful if you'd identify the specific app or driver you're attempting to manage/update there.
This was all covered (to death) a year or so ago. Go to Bundle Manager and read. It really is that simple.
To get rid of the error. Again, read the second post in the Bundle Manager thread. Section "How to unmatch BPTWorld Apps from HPM".
3 Likes
Thanks for the clarification.
I'd read that thread (to death). It wasn't clear when you were directing anyone that made a comment to see post #1, nor did my lack of understanding the topics could be expanded (that's on me), nor the fact that it looks like it was edited today so I don't really know what it looked like before.
Thanks for your time and effort, and sorry to bother.
2 Likes
Sorry .. is this normal ? Get this every time I enter it from the APPS tab.
Have you read this Topic yet?
If you upgraded to platform v2.3.6++ before upgrading HPM to v1.9.0 then there is an issue. That Topic also covers how to recover.
2 Likes
For us "normal's" and or "newbies" looking at problems we see in the logs.
We do not always know what to do like the seasoned professionals of HB.
Thats why we ask questions ..
Would it had been that hard to say ..
Hey warlock you need to update take a look at the MAIN topic ?
Thanks for a response.
No, you're certainly right.
Despite it being a Holiday...he took the time to write a response, link the actual instructions for a likely solution and did it in just a few minutes after you asked.
So, you got a direct response from the author, on Thanksgiving Day.
I'm very sorry you were disappointed.
Maybe next time you ask a question, we can do better!
S.
3 Likes
Ok then .. that was super nice of you .. soooo glad you responded in such a nice way.
I guess it just better for us never to ask any questions .. I will try to do better next time.
Let me split my response into What I Said versus How I said it:
What I said pointed to a topic that was a first guess at what might solve your problem. Recognize that your message did not give any indication of you having tried anything.. which is ok, but it's also the only reasonable starting point. If you had read the topic and it didn't solve the problem then I'd probably spend a couple hours trying to duplicate your problem, looking for a flaw in my recovery instructions. I'm happy to spend the time researching for you, by the way, it's what I signed up for when I accepted / took on HPM when Dominic left the Community.
It is uncommon for Hubitat to introduce a breaking change. Therefore it's uncommon for Hubitat Users to read the Release Notes looking for breaking changes. I knew that getting-the-word-out and then the lack of getting-the-word-out would be the hardest part of Supporting HPM for a long time. I tried by creating a Topic, coordinated with Hubitat to get the Topic mentioned in the Release Notes and have answered this exact question in this topic several times.
How I said it: Sorry. I'll take the hit on "tone" any time with a smile.
I've answered with the same words multiple times in this topic as well as several others.
Bottom Line:
I'm far more concerned about getting a solution into the hands of the user community than most anything else. In other words, my answer appears to be to you but it's aimed more at me in the sense of "Is there something wrong in my explanation and remediation document?"
References:
18 Likes
Is your problem resolved? Did the Recovery method help you?
2 Likes
Thank you very much for your response. I really appreciate it. As newbies don't always understand how all this stuff works. And all we see is errors in the logs. That we know aren't supposed to be there. HB is a very robust. Very complicated. System for the general user. I came from an X10. Era. And many of the things that you need to do in HB. Are amazingly. Not as easy. However, it has the flexibility. To do a million things other systems can't do. If you can figure out how to make it do it, lol.
Sometimes it's hard to read through 550 comments. Worse. Look at the very top topic. When it automatically brings you to the bottom. Very much appreciated.
All, I was saying. Is that sometimes it's easier to give a simple answer. To a simpleton like me.
And yes with your help .. I was able to fix the problem. I'm not sure if I did it correctly,
I went to " Bundles" and used import zip and basically just reinstalled it. and now the errors are gone 
thank you very much for your help. And I appreciate Everyone here at HB !
PS.
I did go back and read the top topic
I did not see anything about how to "re-install" Or Update. I Just Guessed.
Again Thanks for the help.
1 Like
The errors being gone is great... but there's also the element of Duplicate Apps in that 'recipe' for recovering. Having duplicates will cause a problem 'tomorrow' and none of us want that.
I really wish I could like this post multiple times.
6 Likes
Hmmm ok so in layman's terms / a simpleton like me .. how do I check that ?
I do not see : Any Duplicate Apps in the : Apps < tab
That's it.
The problem arises when you are using Platform v2.3.6 and try and click Update in pre-v1.9.0 HPM and select an App. HPM will try and get a list of the Apps installed to find the correct app number to update. It won't find one on platform v2.3.6, and will import another copy. If you never attempted an App Update with the pre-v1.9.0 HPM, then you would not have gotten duplicates.
2 Likes
A takeaway: this is a very common issue with the WRITTEN word (SMS, Email, forum posts, etc) - it is WRITTEN in the writer's frame of mind and it is READ in the readers frame of mind.
The WRITER may be in a joyous mood, the READER may have just had his dog die. As such, two dramatically different interpretations of the exact same words are possible.
I'm happy to see a resolution was achieved satisfactorily. Cooler heads prevailed.
1 Like
Released v1.9.1
3 Likes
I'm not on the beta, and it hung on one of my hubs. But when I just reloaded the app 10 minutes later, it had updated to 1.9.1.
1 Like
