SolisCloud Solar PV

Kash 0

@sdetweil Yes, sorry! I’ll edit my original post

Rags

@Kash-0 Hello- 0. Well, I would suggest you to delete the existing folder (MMM-Solis Cloud if it exists) and then do a clean install in the MM Modules directory. The dependencies folder is created during NPM install in the same directory and are automatically registered ( I Guess) so there should not be any issue. Lots of my such issues with other modules were resolved by this method thanks to advice from @sdetweil .

sdetweil

@Rags just delete the node_modules folder and the npm install again

Kash 0

@sdetweil said in SolisCloud Solar PV:

just delete the node_modules folder and the npm install again

Thank you both. I deleted the folder node_modules from within the Soliscloud parent folder, then ran npm install again, but it produced the same result. I then deleted the Soliscloud folder and did a clean install of the module. Unfortunately, that also produced the same result. The biggest errors seem to be:

Failed to remove directories: There are warnings indicating that some directories could not be removed during cleanup, specifically related to the lzma-native dependency.

Error during epoll installation: The installation process encounters an error while trying to rebuild the epoll dependency.

Any and all help greatly appreciated :) - also, let me know if I should move the query to the Troubleshooting section.

sdetweil

@Kash-0 a few changes needed to the package…

try my pull request

cd to the module folder

git fetch origin pull/1/head:test_install
git checkout test_install

then npm install should work

npm install

Kash 0

@sdetweil said in SolisCloud Solar PV:

git checkout test_install

Nailed it! Thank you Sam, you absolute legend :)

sdetweil

@Kash-0 this change has been accepted into the base module. so

to reset, in the module folder do

git checkout main
git pull

no code change

cyberphox

Looks like a cool module - although I have 3 inverters for my setup and I see there is no way to add more than 1 currently?

sdetweil

@cyberphox I would open an issue on the module GitHub page to engage the author