Closed matthias-burgfried closed 4 years ago
My mistake. I have missed to expose the listening port.
docker-compose.yml
...
sonos2mqtt:
image: svrooij/sonos2mqtt
container_name: sonos2mqtt
environment:
- SONOS2MQTT_DEVICE=${SONOS1}
- SONOS2MQTT_MQTT=mqtt://${MQTT}:1883
- SONOS_LISTENER_HOST=${DOCKER_HOST}
- TZ=Europe/Berlin
depends_on:
- mqtt
restart: unless-stopped
ports:
- ${SONOS2MQTT_HOST}:6329:6329
...
No problem!!
I have a question, since you upgraded to the new Sonos S2 system, I’m curious what the changes are, could you run the service generator and push the changes to your fork? So first you fork Node-Sonos-ts then check it out on your machine and then run service generator.
Done. Are there differences between the devices (Beam, Play:5, Play One) used for discovery? As it looks like I don't have line-in, but I have infrared. I used the Beam. https://github.com/svrooij/node-sonos-ts/compare/master...matthias-burgfried:master
Thanks for the help I created an issue on how to solve the differences between multiple models. Hoping for some input.
Good evening. I updated my system to S2 yesterday and I ran into a problem. I can still control the system, but I can't get any more system changes via MQTT.
docker-compose.yml
My question: I' m using the Docker image, how can I turn on debug logging?