simplextech

There's some package dependency that's most likely broken somewhere. Unfortunately it will take the involvement of the Nodeserver author to help track down what it could be. My initial direction would be to run Tesla on Polyglot Cloud because it's cloud dependent anyways. However that's up to you.

Here's the diff of the pkg lists. You have newer versions of some things than I do and you have some packages that I don't. [admin@polisy ~]$ diff simplex.pkg gary.pkg 4,5c4,5 < ca_root_nss-3.47 < curl-7.66.0 --- > ca_root_nss-3.47.1 > curl-7.67.0 21c21 < libnghttp2-1.39.2 --- > libnghttp2-1.40.0 28c28 < node-13.0.0 --- > node-13.2.0 44c44 < perl5-5.30.0 --- > perl5-5.30.1 46c46 < polyglot-2.2.6 --- > polyglot-beta-2.2.6_1 47a48 > py37-acme-0.39.0,1 48a50,51 > py37-certbot-0.39.0,1 > py37-certifi-2019.9.11 49a53,55 > py37-chardet-3.0.4_1 > py37-configargparse-0.15.1 > py37-configobj-5.0.6_1 50a57,59 > py37-distro-1.4.0_1 > py37-idna-2.8 > py37-josepy-1.2.0 51a61,62 > py37-openssl-19.0.0 > py37-parsedatetime-2.5 53a65,69 > py37-pyrfc3339-1.1 > py37-pysocks-1.7.1 > py37-pytz-2019.3,1 > py37-requests-2.22.0 > py37-requests-toolbelt-0.8.0_1 55a72,76 > py37-urllib3-1.22,1 > py37-zope.component-4.2.2 > py37-zope.event-4.1.0 > py37-zope.interface-4.6.0 > python-3.7_3,2 60c81 < snappy-1.1.6_1 --- > snappy-1.1.7 I'll have to check for updates and see what happens....

Is that all that it's showing you? I have a lot more. Your output isn't even showing mongodb or mosquitto which are necessary for polyglot to run. I don't see node or npm or any of the python packages in your output.

On another note. I was able to replicate the error with a different nodeserver on my test system. The error is being caused by a missing dependency which is then display/presented by Polyglot as the "runInstallProcess: undefined" error. I'm not sure what your Polisy is missing compared to mine. If you run a "pkg info" and then paste the output I'll run a compare against what I have installed and see if there's a difference.

Well back to this then. See if you still get the same error: cd /var/polyglot/nodeservers/Tesla sudo -u polyglot npm install Make sure the first command runs correctly and you are actually in the Tesla directory. Then run the second sudo command.

Well can perhaps try upgrading node and npm and see... maybe... Try the following: sudo pkg upgrade node sudo pkg upgrade npm The next would be a remove and re-install.... sudo pkg remove npm sudo pkg remove node --- Re-Install sudo pkg install node sudo pkg install npm

The ldd output shows that the libcrypto library is there and available. That's point to a possible path issue from when you ran things manually. Yet it does not explain why it's failing when running through Polyglot or even why it didn't work when running through sudo. Hmm...

doubtful run a ldd /usr/local/bin/node and paste the output

now that's very odd as libcrypto is part of the FreeBSD base. Have you updated the system since receiving it?

Next try this. cd /var/polyglot/nodeservers/Tesla sudo -u polyglot npm install This is what my output looks like: [admin@polisy /var/polyglot/nodeservers/Tesla]$ sudo -u polyglot npm install npm WARN tesla@1.0.4 No repository field. audited 1164 packages in 8.834s found 0 vulnerabilities Post the errors or information if it's different than mine.

yeah... log rotation needs to be setup.... do this: sudo -s cat /dev/null > /var/polyglot/log/debug.log exit You have to do the sudo -s to change directly to root because the typical 'cat /dev/null ' will give a permission denied That will clear the log. Then run the install of Tesla NS again and see what info you get and post it.

That error is when it's trying to run the install.sh from local. The install is just trying to run npm install. None of that is python related. What's in your polisy logs?

That's because the package names are wrong. py37-certbot py37-pip py37-netifaces

Interesting. I'll find out soon enough if I run into this issue or not.

Very odd then. I just did an install from my rPi and from Polisy and both worked

You must have the "dimmer" outlet model? I don't use those. I only use the dual outlet on/off as I don't want to deal with these types of issues from an outlet.

SSH into the polisy and run the following from the prompt. pkg info node If that work fine then check npm pkg info npm If you get any error like this: pkg: No package(s) matching blah then node and npm are not installed and they need to be for the Tesla nodeserver.

Did you install node and npm on your Polisy?

I planned ahead for this circumstance as well. All of the outlets I use for any holiday lighting are smart outlets and I have the outdoor plugins for outside. Still contemplating replacing the rest of my outlets with OutLetLincs... figure why not right?

Gotcha... I always forget there's the Raspian desktop image. The "debian with rPi load" threw me off

Can I ask... what is " Debian with the RPi load" ??? Raspbian is just debian for arm with some additional edu packages and hardware specific packages for rPi.

Just checking. Can never be certain and safer to ask than to assume. Sounds like the PLM was wiped or dying....do you see an received traffic in the event viewer in Level 3?

No. I'm from Simplex Technology. Very odd that the PLM is empty. I'm guessing you do have devices in your Admin Console? And they did work at some time? Sorry haven't followed/remembered from the beginning of the thread.

Dumb question. Are the devices linked to the ISY? Can you list the device links and compare to the ISY and see if they match?

PSA: Just an update the Nuheat Signature nodeserver is coming along. I have a few quirks to iron out before I'm ready to release for public testing but it should be soon'ish.