Does anyone else have an issue with the Hubitat package manager not being able to search by keyword? This has been going on for a while.
It only happens when I go to install and search by a keyword. Searching by tag seems to work fine. I uninstalled and reinstalled it. I’m not quite sure what happened.
Here is the flow:
-
-
-
Working fine here…. Tagging @csteele to see if he has any suggestions for you.
The error indicates that the version of HPM on your hub is out of date. You need to install the latest version (or any version after @csteele took over its maintenance. The current version is 1.9.11.
To clarify "hubitatpackagemanager.azurewebsites.net" was maintained by the person who created HPM, but is no longer maintaining it. The search site maintained by @cteele is "hubitatpackagemanager.hubitatcommunity.com"
Please follow the directions provided in this post:
I haven’t spoken to Dom in years, but the last time I did, he said he had no plans to end the Azure search tool he created. However, he also said that the site was hosted ‘for free’ under a friend’s Azure account. Today, years later, and ‘free’ is a popular thing to get taken away.
Hubitat Package Manager (HPM) quit using Azure in v1.9.9, published on Feb 15, 2026 when ‘fuzzy search’ merged with ‘fast search’ 
Well, damn. I sure seem to be out of date by a while. How did everyone else figure this out? I don’t know what I was supposed to do to keep this up-to-date anymore than I do to keep everything else up-to-date. I even uninstalled it and reinstalled it just the other day.
Hang on that post is from 2022. I bought my Hubitat in 2025. I have been using The Hubitat package manager successfully for almost a year. Surely the solution can’t be updating to a version from four years ago…
2022 is when @csteele initially took over maintaining HPM. It has been updated many times since by him and other contributors.
HPM is not a built-in app, so you must have installed it on your hub. Therefore, only you know why you installed a deprecated version.
The current version of HPM was released earlier this year, as @csteele mentioned above:
HPM is currently at v1.9.11.
v1.9.9 was when HPM stopped using Azure.
This version is installed in my Hubitat because when you go to apps > add user app and search Hubitat package manager and install it, you get the below. This is what I got when I went to reinstall it just now.
It’s the only thing that comes up. It’s the only option. And it worked just fine at the time I downloaded it last year. How was I supposed to know this wasn’t the right thing, I was brand new to this. There’s nothing here that indicates there’s a problem or a different version or that this is now defunct.
Surely I’m not the only person who’s experiencing this. I didn’t go out of my way to make this happen. I did the most direct straightforward approach as I was told to do it from posts in here.
Whenever there has been an update of HPM available it shows up when you click the Update button and then you can update it.
There is also an option in settings to have HPM notify you when updates are available.
That means you downloaded and installed the code for version 1.8.3. Maybe you used a deprecated link when you downloaded the HPM app code.
The code for HPM, like other user apps, has to be installed manually.
I understand that you are following the old instructions AND that they still work, they still successfully provide you with the old HPM. I intentionally left them, to retain a historical path, in case people wanted to use the Azure search that is now, no longer available. Maybe that was a good choice then, and now, years later, I should break the old path.
There’s new Instructions too. Those are the ones that will get the modern version of HPM onto your hub. That 4 year old version, worked right up until the day it didn’t and the path forward is to use the new instructions.
I mentioned this elsewhere, but maybe duplicating it here might help the next person that discovers Azure search isn’t working…
For years I used a Bit.Ly url shortener for adding HPM to a hub. The bundle method is a very good method but typing in long urls, which is what github uses, is typo burdensome. However, Bit.Ly changed their terms of service a year or so ago and now do NOT redirect correctly for a Hub. They send the redirect to a nag page, hoping to get subscribers.
So I built my own url shortener and the HPM Instructions use that. However, the long URL still works too… if you don’t typo it 
This is what Bit.Ly offers:
Your hub is simply not going to make it through that humans can, Hubs, no.
Apparently not in the old version, and I have that setting enabled. it updates the packages that it manages, not itself, because this version doesn’t update anymore.
I’ll admit it it’s been a while since I added any user apps I forgot about the code import and all of that, it’s starting to make sense how this happened.
thank you all for the assistance. I think I’ve got it from here.
@csteele just FYI, when I followed your link from the Hubitat app using the native iOS Safari browser the app defaults to when opening links within the app, here’s what the page is looking like:
sheesh.. that is one ugly phone display, sorry. But it works great on a desktop browser
Regarding the old upgrade path… here’s the PackageManifest, from the old site, showing that it was most recently updated 4 years ago AND that it points to the new repository:
What was supposed to happen is, the contents of that 1.8.3 code has the NEW repository defined. AND anyone using a version older than 1.8.3 would (using the PackageManifest) also get sent to the new repository. Thus everyone would magically shift from old to new.
I guess ‘everyone’ is not as complete a grouping as I imagined.
I made a small correction to the page and it now displays nicely on MY phone. Can you confirm, please?
Interesting. I went through the process of installing through your documentation, but I forgot to delete the app code for the old HPM and so I think I essentially just reinstalled the old one again because it displayed version 1.9.1.1 with Dominic’s name. But it worked again. The search by keyword was totally functional again.
Trying again after deleting the app code lol
