Closed paulianttila closed 2 years ago
What does the console show if you send debug
to sonos/cmd/setlogging
? This will change logging to debug, that might show you what’s wrong.
And also set the environment variable DEBUG
to sonos:*
.
is the beam playing music or television?
And also set the environment variable DEBUG to sonos:*.
Thanks, by adding this, I saw that no subscription events was received from the Bean.
Root cause was my bad :pensive:. Bean IP address was changed in some point of time even IP addresses are fixed rather than dynamic. Firewall rule had still the old IP address, so it was blocking communication from Bean to 192.168.10.20:6329.
I have 3 Sonos players; Bean, One and Play:1. Bean is connected via Ethernet and two others are connected via SonosNet throw Bean.
Sonos speakers are in different VLAN than sonos2mqtt, so I have defined the Bean to be the "discovery" device (192.168.30.82).
Firewall settings:
Configuration:
sonos2mqtt find all 3 devices:
http://192.168.10.20:6329/status contains all 3 devices (Device id's are masked!):
In MQTT, discovery message is published to all 3 devices, but only 2 is available (Bean is missing):