-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error installing #129
Comments
Where did you get the code from? The code doesn't import LazyMap so I'm confused why you'd get this error. Can you provide the exact url where you downloaded HPM? What version of Hubitat do youh have as well? |
EDIT- seems there are 2 versions floating around. 1.7 installed fine from copy paste while the 1.1.0 has the "LazyMap" error... I will go back track to find where I got the "bad" link to the "old code" and then updated the below accordingly.. EDIT - the "old code" is in "releases". Only 1.1.0 is in "Releases" HI, I am a newb as well and have come to the same problem mentioned here.. Be gentle this is a whole new world for me :). EDIT: - The below instructions will get you to the working version (v1.7.0) without the "LazyMap" issue. I got the code from the below url. I first tried to "import" the custom app into Hubitat by just putting in the git hub url but it didnt do anything, so then I did the "Download Zip" from GitHub to my pc, extracted, opened in Notepad and copy/pasted the code into "New App" of Hubitat. https://github.com/dcmeglio/hubitat-packagemanager --> Green Button "Download Code" --> Download Zip NOTICE version 1.7.0 When using 1.1.0 I got the below. |
Had the same error with 1.1.0. Had to go to branches and download 1.7.0 for it to work without error. |
Sorry if I'm such a noobie that I am doing something wrong, but you don't know what you don't know. I'm trying to install the hubitat-packagemanager on my habitat and getting the following message when I try to save:
Importing [groovy.json.internal.LazyMap] is not allowed
Can you give me any assistance with how to solve this?
The text was updated successfully, but these errors were encountered: