@csteele honestly it has been happening to me for a long time. I learned quickly that the version number changed and when it did just exit that screen and all was good. I wouldnât have posted if not just for this thread because honestly it is NOTHING in the grand scheme of things.
You put enough time in keeping this massive system working for all of us. I wouldnât invest a lot more into this one unless you just want to add some note or something sometime. Thank you for your work on HPM.
3 Likes
This!!! HPM is awesome. I actually forget that it is @csteele maintaining it and not Hubitat, because other than Rule Manager it's possibly the most "core" thing to Hubitat. The hanging thing is what it is. We can learn to live with it. If Hubitat wants to pay you to fix it and you want to accept that job, that's one thing. But otherwise, you have done MUCH for everyone and deserve applause and kudos and thanks. So, THANK YOU for creating it and maintaining it and I wouldn't worry about it any more given the current situation.
2 Likes
Um... I didn't create it. Dominick Meglio created it.
In 2022, when Dominick left the Hubitat community, I volunteered to maintain it. I accepted the role of steward because there's not a lot of changes to the core. I released 1.8.5 with Bundles in June, 2022 and it's largely a copy of 1000 lines of Dom's code, adjusted to use the word "Bundles"
I've worked with Hubitat on specific endpoints to free HPM from 'scraping text' from the UI. I introduced UnMatch, also in June 2022 and now wonder if my best is behind me? 
But the important part is that Dominick's original work is still what we all rely on when using HPM.
8 Likes
Yes, Dominick is the one that kicked it off and developed it, and he deserves a major thank you. However, there is also something major to be said for taking it over and keeping it up and operational instead of just letting it fall away. So many of us depend on this to make things easier for us. Take your kudos you earn them.
4 Likes
I am thankful and grateful we have it, and that it is maintained. What I do not understand is why Hubitat itself didn't take it over and maintain it, given its central role. But such is life - there is much I cannot understand or do anything about. So, thanks to Dominick and @csteele .
I am sure one part of it is Hubitat only wants to control and release apps/driver/integration they can âofficiallyâ test and verify before they put their company name behind it. There is no way they can do this with everything in HPM.
Not saying a community member would ever do this (I truly believe they would NEVER intentionally) but place an app/driver/integration in HPM that bricked peoples hubs or created a privacy violation then Hubitat doesnât want that association. To be honest, if I was them I wouldnât either. I know they could make disclaimers and such but as a company it is more clean for them to leave a community tool management system with the community.
1 Like