SonoX

[normana]

Es wäre gut, wenn man sehen könnte, was der Grund des Netzwerk Fehlers ist. Aber ich vermute, dass der Port bereits belegt ist. Schon mal probiert, den Port zu wechseln?

[Diddi]

Nachdem ich MQTT eingeschaltet und gespeichert habe sind wieder alle Zonen gefunden worden.
???

[normana]

Und wenn du MQTT wieder ausschaltest, dann nicht mehr?

[Diddi]

Habs gerade mal probiert. Nach dem Deaktivieren verschwinden kurz die Zonen und kommen aber direkt wieder.
Also im Moment alles OK.

[normana]

Also die Zonen verschwinden nicht. Der API-Dienst wird nur neu gestartet. Das dauert aber vielleicht maximal 5 Sekunden.

[normana]

An alle: Das aktuelle Prerelease unterstützt MQTT. Es werden Zonen-Daten übetragen, Änderungen der Lautstärke, Änderungen der Topologie, also Gruppen-Änderungen oder auch Titel-Änderungen. Ich würde gern erfahren, wie das genutzt wird und was man hier verbessern kann.

[djatwork]

Servus,

würde auch gerne das neue Plugin testen. Leider findet es aber keine Player!.

Neue dietpi vm installation, sonosx installation läuft ohne fehler durch! bei loxberry restart kommt dann nur die meldung dass das sonos-http-api.service nicht gestartet werden kann..

loxberry@loxberry:~ $ systemctl status sonos-http-api.service
× sonos-http-api.service - Sonos HTTP API
     Loaded: loaded (/etc/systemd/system/sonos-http-api.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Wed 2025-03-19 06:19:27 CET; 12min ago
   Duration: 4ms
    Process: 53288 ExecStart=/usr/bin/node /opt/loxberry/bin/plugins/sonox/node-sonos-http-api/server.js (code=exited, status=203/EXEC)
   Main PID: 53288 (code=exited, status=203/EXEC)
        CPU: 973us

bei der neuen Install scheint es Pfadprobleme zu geben..

loxberry@loxberry:~ $ /usr/bin/node /opt/loxberry/bin/plugins/sonox/node-sonos-http-api/server.j
-bash: /usr/bin/node: No such file or directory

/usr/bin/node existiert nicht....

ohne pfad würde der dienst zumindest kurz starten...

loxberry@loxberry:~ $ node /opt/loxberry/bin/plugins/sonox/node-sonos-http-api/server.js
2025-03-19T05:25:19.260Z INFO Could not find file /opt/loxberry/bin/plugins/sonox/node-sonos-http-api/settings.json
2025-03-19T05:25:19.437Z INFO Presets loaded: {
example: {
players: [
{ roomName: 'Bathroom', volume: 10 },
{ roomName: 'Kitchen', volume: 10 },
{ roomName: 'Office', volume: 10 },
{ roomName: 'Bedroom', volume: 10 },
{ roomName: 'TV Room', volume: 15 }
],
playMode: { shuffle: true, repeat: 'all', crossfade: false },
pauseOthers: false
}
}
/opt/loxberry/bin/plugins/sonox/node-sonos-http-api/server.js:105
if (settings.mqtt.active) {
^

TypeError: Cannot read properties of undefined (reading 'active')
at Object.<anonymous> (/opt/loxberry/bin/plugins/sonox/node-sonos-http-api/server.js:105:19)
at Module._compile (node:internal/modules/cjs/loader:1734:14)
at Object..js (node:internal/modules/cjs/loader:1899:10)
at Module.load (node:internal/modules/cjs/loader:1469:32)
at Function._load (node:internal/modules/cjs/loader:1286:12)
at TracingChannel.traceSync (node:diagnostics_channel:322:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:151:5)
at node:internal/main/run_main_module:33:47
​

habt ihr vielleicht einen Tip?

lg
Werner

[normana]

Die Settings für MQTT scheinen nicht da zu sein. Entweder fehlt die komplette settings.json-Datei oder die Variable mqtt ist nicht gesetzt. Probiere in den Settings zu speichern. Es muss nichts geändert werden.

nodejs müsste under /usr/bin/node installiert sein. Das Plugin Express Server https://wiki.loxberry.de/plugins/express_server/start installiert nodejs an der richtigen Stelle.
Für künftige Versionen baue ich nodejs direkt ein bzw. eine Prüfung, ob es an der richtigen Stelle installiert ist.

[normana]

Teste mal das neue Prerelease bitte

[djatwork]

Servus,

den express server habe ich installiert... ohne Verbesserung....

Die settings.json existert unter /opt/loxberry/data/plugins/sonox/ gesucht wird sie aber unter /opt/loxberry/bin/plugins/sonox/node-sonos-http-api/ !?

lg

[normana]

Teste mal das neue Prerelease

[djatwork]

Danke, jetzt funktioniert das Plugin!

[Stekkieman]

Hi,

Can somebody tell me what the correct settings are in the Loxone config to use my Sonos as a doorbell for my Loxone Intercom ? Is there a step by step guide ? Thank you !

Grts

[normana]

It depends on what kind of doorbell you have. If it can be used as an input for loxone it should also have an output that can trigger a virtual output that calls the clips-endpoint provided in the plugin.

[Stekkieman]

Hi,

I use the Intercom gen2 of Loxone and I would like to use my sonos speaker to play a ding dong sound when somebody is at the door. I installed Sonox on a Odroid board. When I execute a clip the Sonos plays the dingdong sound , but when I press the Intercom button nothing happens..

[normana]

There is an doorbell output which can trigger a virtual output. https://www.loxone.com/enen/kb/virtual-inputs-outputs/

[Stekkieman]

I used this doorbell output. This is the error and my settings.

[normana]

The port is missing. From the doc: In the Properties window of the virtual output connector the protocol, address and port of the device to be controlled can be entered. For http, tcp and udp you need to include the protocol before the address is entered (e.g. tcp://192.168.1.199:23).

If you did not change the port it should run under http://192.168.1.230:5005

[Stekkieman]

Thank you ! Now it works

[normana]

You can also try out the clipavailable endpoint. It runs the doorbell on every player in your house that is currently not playing. But you can also try what you are currently using the clip end point. It should return to the play state it was before.

[KenV]

Thank you for this great plugin!
It allows me to still use MP3 playback and TTS even with my old Sonos S1 devices and app - at least for now...

I am running the latest 1.0 version.

Has anyone else noticed "Text-to-Speech in all rooms" ("sayall") not working?

I receive the following error:

{"status":"error","error":"allPlayerAnnouncemen t is not a function","stack":"TypeError: allPlayerAnnouncement is not a function\n at /opt/loxberry/bin/plugins/sonox/node-sonos-http-api/lib/actions/sayall.js:34:14\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"}

The same message plays fine using individual room-specific TTS ("say").

[KenV]

I have a Loxone flow in which, at the start of the day (based on certain button presses, window blinds opening, motions sensors etc) a T2S voice weather report+forecast is played (mostly based on the weather4loxone plugin), and afterwards a specific radio station is played in certain Sonos zones.

There are also 'clipall' custom mp3 clips played for certain events in the house like Doorbell, a door being open for too long a time, door/window not having been closed at night etc.
I saw that 'upload for custom mp3s' is still mentioned on your roadmap, but it seems that it already works perfectly, just by uploading the mp3 to the data/plugins/sonox/clips directory?

[normana]

Yes this is true. You can upload it directly but there is no official UI for handling uploads and management of custom clips.

[normana]

Would you like to share a screenshot of the config in Loxone? That would be interesting. Did you also use the plugin for manual control of your sonos setup with loxone?

[DJGoeddek]

Vielen Dank für das tolle Plugin. Eine Frage habe ich noch. Ich würde gerne nachts entsprechende Radiosender auf den jeweiligen Sonos setzen. Hier gibt es ja die Funktion Play favorite in a room. Hier wird der Favorit dann ja auch direkt abgespielt. Hast du eine Möglichkeit hier noch eine option zu integrieren, dass lediglich der Sender gesetzt aber nicht abgespielt wird?

Vielen Dank!

[sennevb]

is it possible to put the artist and title in a separate mqtt tag, loxone has trouble extracting text from a mqtt tag, integers is no problem
Or do you have any workaround to displat the artist and title, so ican see in app whats playing?

[normana]

This is already supported in SonoX.

For example:
`sonox_{room}_playback_track_title` provides the current track title, and
`sonox_{room}_playback_track_artist` provides the artist name.

However, the Loxone Miniserver does not support dynamic text values directly in its virtual inputs.
This means that while the data is available via MQTT, it cannot be displayed natively as a string inside the Loxone user interface.

There are workarounds (such as the one described here:
https://loxwiki.atlassian.net/wiki/s...+to+Miniserver)
which allow text to be reconstructed character-by-character using ASCII values and Status blocks – but this is complex and not natively supported.

In summary: SonoX provides the data, but displaying it inside Loxone requires significant effort or external integration (e.g. custom web dashboard or iFrame).

[sennevb]

This is already supported in SonoX.

For example:
`sonox_{room}_playback_track_title` provides the current track title, and
`sonox_{room}_playback_track_artist` provides the artist name.

However, the Loxone Miniserver does not support dynamic text values directly in its virtual inputs.
This means that while the data is available via MQTT, it cannot be displayed natively as a string inside the Loxone user interface.

There are workarounds (such as the one described here:
https://loxwiki.atlassian.net/wiki/s...+to+Miniserver)
which allow text to be reconstructed character-by-character using ASCII values and Status blocks – but this is complex and not natively supported.

In summary: SonoX provides the data, but displaying it inside Loxone requires significant effort or external integration (e.g. custom web dashboard or iFrame).

That workaround is too complex for what i need, its some kind of overkill IMO
pity Loxone doesnt handle text without those workarounds.

Is there a possiblity to get it into a virtual input, just like sonos4lox, this issue is the only thing thats holding me back jumping from sonos4lox to sonox..

[Liver_64]

use a Loxone Virtual Text Input, then you can display Textstrings send by MQTT or UDP (as Long as the App sends Text data!)
It works now for years in my sonos4lox for free

[sennevb]

Thanks for your response, i am currently using sonos4lox, but am trying to switch to sonore, but cant set the virtual inputs there

[normana]

Virtual text inputs in Loxone listen to a specific endpoint of the miniserver (/dev/sps/io/{name_of_your_text_input}). At least miniserver 1 does not provide virtual text input integration via MQTT. Therefore the playing now feature, when enabled, sends metadata to the Miniserver via HTTP GET requests whenever a track changes or playback state updates. The data is sent using this specific Loxone SPS/IO interface. It uses a event based publish mechanism. No polling or other network overhead. It refreshes the following data instantly when one of them is changing:
/dev/sps/io/sonox_<room>_current_title
/dev/sps/io/sonox_<room>_current_artist
/dev/sps/io/sonox_<room>_current_radio
/dev/sps/io/sonox_<room>_current_state