I’m also getting stuck trying to run my node server.js.
i get this in putty:
~/smartthings-nodeproxy$ node server.js
[2020-03-10T03:45:45.534Z] [stnp] SmartThings Node Proxy listening at http://0.0.0.0:8080
[2020-03-10T03:45:45.586Z] [stnp] Loaded plugin: envisalink
[2020-03-10T03:45:45.593Z] [evl3] Connected to Envisalink at 192.168.1.40:4025
[2020-03-10T03:45:47.220Z] [evl3] {"type":"partition","partition":1,"state":"ready","alpha":"****DISARMED**** Ready to Arm"}
[2020-03-10T03:45:47.254Z] [stnp] Notify error: Error: connect ECONNREFUSED
so where it says 0.0.0.0:8080, that should display as the IP of my SmartThings hub if it was working correctly? and you and @redloro are saying that it’s because it’s being blocked or in use already?
i somewhat recently started using this, which uses a server that i’m running from the same Synology NAS that i’m trying to do this node proxy from. would that be the culprit? they would both be servers running from the NAS, but that other one is not really pushing anything to the hub, but just hosting a database with info it gets from ST.
side note: the Github readme says to install plugin dependencies, but when i try to execute “npm install run:envisalink” i get this:
$ npm run install:envisalink
> smartthings-nodeproxy@1.0.0 install:envisalink (path edited)/smartthings-nodeproxy
> npm install
npm WARN package.json smartthings-nodeproxy@1.0.0 No README data
i don’t get why that won’t run, or why it’s included if that step was omitted from all the early posts. perhaps it was added at a later date and i haven’t gotten to that point in this thread yet.
edit: I replaced the files for server.js, the plugin, and package.json, as well as added restart.me to the directory, and no longer got the npm WARN message when installing the plugin, but didn’t really get much more confirmation that it did much.