More detailed instruction

[mxdalchau]

Hey,

could you write a more detailed instruction please?

thanks :)

[jmt-gh]

Could you be a bit more specific in what you're looking for? The "how to use" section is step by step on how to get things running. I'm more than happy to add additional information, but I'm not sure what exactly you're looking for

[prolife86]

He might mean weather you are going to publish it on DockerHub?
This might make it easier for people to implement.
Just guessing here, and following this project with great interest!

[mxdalchau]

Hey, sorry my english is no t so good...

If i use docker-compose with docker file.. which file i should edit?

[mxdalchau]

so the docker-compose is running http://xxx.xxx.xxx.xxx:3333/wsdl

there is only a white site

could i see a log ... to analyze whats the problem

[mreitschuster]

I think a more detailed how-to might help. I am struggling with quite a few point:

1. where can the file "soap-server.js" be found? it is described and when running without docker it seems to be the mian file ("run node soap-server.js") but I cannot find that file not found in this repo

Since I couldnt find it I tried via docker-compose

2. docker-compose refers to node-docker but that cannot be found or installed.

audiobookshelf-sonos Error  
Error response from daemon: pull access denied for node-docker, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

3. The "ABS_TOKEN=" likely stands for the audiobookshelf user token, that can be found when logging in as root and clicking on settings -> users -> specific username

4. ABS_LIBRARY_ID= is not clear. Does it expect a ID (likely numeric) or the name of the library?

5. are the modifications of config.js and sonos.wsdl also necessary when running via docker compose? if yes how does docker compose know which files to take - the only volumne defined there is sonos.wsdl?

[jt196]

I've spent a bit of time looking at this and have a few answers to the above.

1. The file is server.js, I think it's been renamed but the docs haven't been updated.
2. The docker image isn't hosted anywhere, so you need to build it. If you cd into the cloned directory, and run the command docker build -t node-docker:latest, the command will run and it should work.
3. Pretty sure this is correct.
4. This is a bit confusing, if you've got just one library, I belive the id is just "main". If you have a second library, you can see the id in the URL, "lib_xxxx".
5. I think you need to add the environment variables in the Docker compose, and modify the sonos.wsdl file as well. From what I can see, you need to avoid inverted commas in the docker-compose ENV variables.

Anyway, I've tried all these, and still not working.

[jt196]

@jmt-gh, what sort of response should we be getting from the URLs: https://soap.server.com/wsdl or https://soap.server.com/manifest?

I get a 200 response but 0 bytes return from the /wsdl, and this response from the /manifest:

{
  "schemaVersion": "1.0",
  "endpoints": [
    {
      "type": "reporting",
      "uri": "https://soap.server.com/wsdl/playback/v2.1/report"
    }
  ]
}

Seems like there should be a bit more in the wsdl response at least.

By the way, if I use this for the env variable in the docker-compose:

- SOAP_URI="https://soap.server.com/wsdl"

The return from the manifest shows this:

      "uri": '"https://soap.server.com/wsdl"/playback/v2.1/report'

When I remove the "", it displays correctly.

[mxdalchau]

should the abs uri only a http or could be https?

[mxdalchau]

i get {"schemaVersion":"1.0","endpoints":[{"type":"reporting","uri":"https://soabs.xxxx.de/wsdl/playback/v2.1/report"}]}
what is right, but i can´t access in sonos

[jt196]

should the abs uri only a http or could be https?

I'd have thought whatever you have set up. Mine is https, so that's what I've put in.

[mxdalchau]

ok me too.. but the sonos app can´t read the libary

[jt196]

Mine can't either, I get a connection error. There's no feedback on the log of the container, so it's quite hard to debug it.

[mxdalchau]

schade eigentlich wirkte das Projekt vielversprechend

[robwalster]

@jt196 did you ever get this working?

[jt196]

@jt196 did you ever get this working?

Hacked away at it for half a day but never got it to work. I could add the service to Sonos by unchecking "Support Manifest File", that's about as far as I got. There were no logs on the Docker container when I tried to access it in Sonos, and Sonos itself have disabled a lot of the log checking functions in their speakers. I went a little through their docs, but had little success I'm afraid.