Skip to content
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

Install script issues #3

Open
mattbrain opened this issue Oct 22, 2021 · 0 comments
Open

Install script issues #3

mattbrain opened this issue Oct 22, 2021 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@mattbrain
Copy link
Contributor

Reported by John W:

I used your new install script as a guide, but with deviations.
I had to knife and fork my way through it as I was getting all sorts of funnies (wrong versions of modules, missing modules, npm not correctly configured, manager and node-red threads crashing, etc), so I uninstalled everything, including removing the references to node_8 which were causing issues.
The following is a rough overview of what I did, and how it deviates from your script.
I installed Node v10.16.0 as per your script (tried 12 but had issues so gave up on that).
I installed [email protected] (not 0.19.4 as your script specifies, and not v2.x.x as it needs node v12).
I installed [email protected] (not latest v3.0.4 as that needs node v12, and v2.30.0 needs n-r v2)
I pulled down your latest main.zip and copied its contents as specified, but had problems. It seems you have changed the name of the cytech js file (now called 10-ucmpi_os.js/html). This didnt match my .config.nodes.json file, so i had no cytech nodes in the nodes toolbar until I edited the file.
I had problems with not being able to create some folders unless running under sudo, and then chowning after to fix owner/permissions. This was what stopped me from running the script as extracted from within the zip file in the first place, resorting to doing stuff manually.
npm was doing funny stuff. Installing global worked fine, but local was just not configured correctly (I'm still not convinced it is 100% correct but I have it working and don't want to mess with it further).
What kicked all of this off was the alexa-smart-home not being able to connect, so I (stupidly) did an update on all of those items that had one within the pallette. I won't be doing that again without checking first :face_with_rolling_eyes:☺️ (edited)

@mattbrain mattbrain self-assigned this Oct 22, 2021
@mattbrain mattbrain added the bug Something isn't working label Oct 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant