@ericm or @Eric_Inovelli any insight ?
1 Like
It's actually a great question and one that I've had myself tbh!
@ericm can definitely help 
One is a parent app and one is a child. They are both required for the tool to work.
1 Like
I'm using the latest version 1.2.1 and even fails pulling other files.
hpm manifest-add-driver packageManifest.json --location=https://raw.githubusercontent.com/dcmeglio/hubitat-packagemanager/master/apps/Package_Manager.groovy --required=false
An error occurred: The driver Groovy file https://raw.githubusercontent.com/dcmeglio/hubitat-packagemanager/master/apps/Package_Manager.groovy either was not found or is not valid.
just performed an update on the Package Manager and received an error. However it appeared the update was performed. ( as shown below) The subsequent Watchdog update appears to have gone without error.
I think it's an issue with hpm. I first tried Release hpm-1.2.2 · dcmeglio/hubitat-packagemanagertools · GitHub, which the assets under it are marked as 1.2.1. This is the one that gives me the unable to find the file.
I then tried the Release hpm-1.2.1 · dcmeglio/hubitat-packagemanagertools · GitHub release and that gave me a different issue.
First:
hpm manifest-add-driver packageManifest.json --location=https://raw.githubusercontent.com/funzie19/hubitat-solaredge/master/solaredge-driver.groovy --required=false
A fatal error occurred. The required library hostfxr.dll could not be found.
If this is a self-contained application, that library should exist in [C:\Users\username\Downloads\hpm-1.2.1].
If this is a framework-dependent application, install the runtime in the global location [C:\Program Files (x86)\dotnet] or use the DOTNET_ROOT(x86) environment variable to specify the runtime location or register the runtime location in [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation].The .NET Core runtime can be found at:
I then installed the missing package but have the following results:
hpm manifest-create packageManifest.json --name="Solaredge Monitoring" --author="usernameregloh" --version=1.1.0 --heversion=2.1.9 --datereleased=2020-05-01
A JSON parsing exception occurred in [C:\Users\username\Downloads\hpm-1.2.1\hpm.runtimeconfig.dev.json]: * Line 1, Column 2 Syntax error: Malformed token
A JSON parsing exception occurred in [C:\Users\username\Downloads\hpm-1.2.1\hpm.runtimeconfig.json]: * Line 1, Column 2 Syntax error: Malformed token
Invalid runtimeconfig.json [C:\Users\username\Downloads\hpm-1.2.1\hpm.runtimeconfig.json] [C:\Users\username\Downloads\hpm-1.2.1\hpm.runtimeconfig.dev.json]
How is the id field generated? I don't mind creating the json by hand.
I had to make mine by hand too. I just used an online GUID generator. Seems to have worked out.
Yup, I'm on it, should have a fix tomorrow. It'd be great if we could get bug reports on github, it is much easier to track and to make sure I don't miss something just because I miss a forum post.
Sent you a donation. Thanks for making this app. This is truly a great addition to HE.
1 Like
Thank you!
1 Like
This is awesome! Hubitat corp, please adopt this!
@dman2306 Do you have example manifests showcasing all the latest features somewhere?
1 Like
@dman2306 Is there a way to point this at a NAS share with the associated json files?
Only if your NAS can expose it over HTTP/HTTPS. To my knowledge Hubitat does not have an API to access SMB shares.
No but I can do that!
1 Like
If you end up doing this, perhaps you can take advantage of the cost saving techniques used by Troy Hunt in his HIBP service. It’s obviously not a direct match to a package service/search engine but there might be some things here that will work.
Thanks for the thoughts. I mostly have it working. I wanted to use the opportunity to learn Azure a bit (never really worked with it). A quick summary for any nerd interested (and I will publish the code once I add sufficient error handling to make it look a bit respectable) - An Azure App Service hosts the API. The repository JSON is stored in a Cosmos DB. This allows me to detect the additions of new packages, removal of old ones, etc. by comparing. Every hour the App Service queries the repository listings and compares them. If there are changes, the changes are stored to an index using Azure Cognitive Search. To quickly summarize, it's kind of like using Bing behind the scenes so you get a "real" search engine. Meaning, if I run a search for "contacts" and the text includes "contact" it know that's just a plural form and will match. The interface to the API will be via GraphQL (because I wanted to learn GraphQL )
I pretty much have it working... An interesting observation from my poll. So almost unanimously USERS want comments/reviews and DEVELOPERS voted no. Why is this? Are there really that many bad actors here that people are worried about people trying to game the system? It would be pretty easy to make it so you could only vote once per hubitat ID and IP address making it pretty difficult to submit duplicate reviews. Are people really that worried? I'll be honest, I'm a little surprised by the results.
1 Like
I just released 1.3.3 which fixes the null error about 'location'. I also published a sample manifest per @markus showing some of the various functions available now at hubitat-packagemanager/sampleManifest.json at master · dcmeglio/hubitat-packagemanager · GitHub
1 Like
Thank you! That makes it a bit more clear for me to keep my generator correct. Is "betaVersion" also accepted on a per app and driver basis or is it only per package?