Trouble right from the start

[merrick777]

As others have said- Sorry for newbie-type questions!

• per instructions I installed nstall node-sonos-http-api via Terminal (on my mac). When I looked for it via 'Finder' I found that it installed into {myusername}/node_modules/sonos-http-api. Inside the /sonos-http-api folder I have a few files, and folders 'cache', 'lib', and 'static'. I downloaded node-sonos-http-api/presets.json and (as per Step 3 instructions) need to put it into node-sonos-http-api root directory.... which doesn't exist (I have /sonos-http-api without "node").
• Step 4: Again, I don't have "/node-sonos-http-api" but I do have "/sonos-http-api". Can you pls tell me where I'm going wrong?? Thnaks!

[pheintzelman]

Sounds like you ended up with the wrong node package. Just download it from this link https://github.com/jishi/node-sonos-http-api/archive/master.zip

[merrick777]

Thank you... Yes, that was better. I'm not yet, but would it be OK to be doing this on my NAS drive (as a server)?

So I figured out some syntax issues with presets.json, and now it passes json validation... but still errors when NPM Start. The error mentions checking to see if I have latest versions of node.js and npm.... I'm on Node.js v6.9.4 and npm v3.10.10. Can you help with this...

[pheintzelman]

You need to do npm install before npm start

[merrick777]

Wow... Yes, looks like it worked. My bad, I somehow overlooked 'npm install' in the instructions. I'm getting there.... 1) Would it be ok to be having this on MyCloud NAS drive? I see that I shouldn't be doing this on my mac because I also have the Sonos client running. 2) Testing: I tried http://yourserverip:5005/zones with the IP external IP address that I got from whatismyip.com and also tried my internal (192.168....) and both returned 'Site Cannot Be Reached'. What should I be using?

(Thanks again and again!)

[pheintzelman]

1. I am not familiar with running node on MyCloud. If you are able to get the sever running it should be fine. I haven't had any issues using the server and client on one machine.

2. Are you able to hit localhost? Common issues here, firewall, network type (should be private), port forwarding not setup, no static ip for computer running node

[evansgo]

This is the same issue I had, something must have changed in the instructions... I've now downloaded from the link you sent (above) unzipped and moved it to the user folder. I then ran npm install, not much happened, I changed the presets, then ran npm start. All seems to be working, but spotify is still broken so that must be something else.

2017-03-24T08:34:42.845Z ERROR StatusCodeError: 400 - [object Object] at new StatusCodeError (/Users/g/node-sonos-http-api/node_modules/request-promise/lib/errors.js:26:15) at Request.RP$callback [as _callback] (/Users/g/node-sonos-http-api/node_modules/request-promise/lib/rp.js:68:32) at Request.self.callback (/Users/g/node-sonos-http-api/node_modules/request/request.js:188:22) at emitTwo (events.js:106:13) at Request.emit (events.js:191:7) at Request. (/Users/g/node-sonos-http-api/node_modules/request/request.js:1171:10) at emitOne (events.js:96:13) at Request.emit (events.js:188:7) at IncomingMessage. (/Users/g/node-sonos-http-api/node_modules/request/request.js:1091:12) at IncomingMessage.g (events.js:291:16) at emitNone (events.js:91:20) at IncomingMessage.emit (events.js:185:7) at endReadableNT (_stream_readable.js:974:12) at _combinedTickCallback (internal/process/next_tick.js:80:11) at process._tickDomainCallback (internal/process/next_tick.js:128:9)