ioBroker / ioBroker.sonos

Control and monitor SONOS player from ioBroker
MIT License
37 stars 20 forks source link

Control Sonos devices outside the iobroker LAN #189

Open ymurawski opened 1 year ago

ymurawski commented 1 year ago

Hi, i have some different VLANS at home for different usages. The iobroker is running at 192.168.1.200 and all my Sonos devices are in my IOT network under 192.168.10.x i can access everything (ping) but when i enter the sonos devices in the adapter it just creates the devices but cant read any settings from them.

any advice ?

Apollon77 commented 1 year ago

Are UDP/MDNS packages routet between the VLANs?

ymurawski commented 1 year ago

Are UDP/MDNS packages routet between the VLANs?

Yes its activated in all Networks. Devices like my shelly plugs wich are connected to the same IOT network just working fine.

ymurawski commented 1 year ago

Any news ? :(

Apollon77 commented 1 year ago

No idea what you expect ... maybe also try asking in the Forum if other users have experiences with such setups?

Me as a developer (if you would have Sonos at all) most likely would not have such a setup ... When I google that then I find several users in general have issues with such setups and works for others ... (not directly iobroker but in general): https://community.ui.com/questions/VLAN-inter-accessibility-for-MultiCast-devices-SONOS-Chromecast-Airtame-etc/f4d7a07c-d4ea-4238-8265-38ccd6e904c7 ... So I assume you need to investigate your self a bit more also.

Sorry that I can not provide a better solution for now

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within the next 7 days. Please check if the issue is still relevant in the most current version of the adapter and tell us. Also check that all relevant details, logs and reproduction steps are included and update them if needed. Thank you for your contributions. Dieses Problem wurde automatisch als veraltet markiert, da es in letzter Zeit keine Aktivitäten gab. Es wird geschlossen, wenn nicht innerhalb der nächsten 7 Tage weitere Aktivitäten stattfinden. Bitte überprüft, ob das Problem auch in der aktuellsten Version des Adapters noch relevant ist, und teilt uns dies mit. Überprüft auch, ob alle relevanten Details, Logs und Reproduktionsschritte enthalten sind bzw. aktualisiert diese. Vielen Dank für Eure Unterstützung.