01-14-2024, 09:35 PM
(This post was last modified: 01-14-2024, 09:56 PM by Tim Curtis.
Edit Reason: sp
)
The only way to run a script in moOde other than vis SSH is via the GPIO Buttons feature. Allowing scripts to be run via a field on a form would be a bad idea.
There are two ways moOde monitors renderers:
1. Renderer event scripts (/var/local/www/commandw/)
This is the approach used for shairport-sync, librespot and squeezelite but the scripts are different and unique to each renderer. The event script updates moOde state to indicate whether a renderer is active or not.
2. Renderer binary running.
This is the approach used for Bluetooth (bluealsa-aplay), RoonBridge and Multiroom-receiver (trx-recv) which don't support event scripts. moOde's worker daemon simply polls and checks whether the binary is running or not to determine whether it's active.
Multiroom receivers like trx and roc are based on rdp/udp network protocols which are "connectionless". Clients don't really connect to these receivers they just start sending packets to a multicast or multi-unicast address(s). A receiver is "active/playing" when it's receiving packets. When no packets are received (within some timeout period) then it could be considered "stopped/listening".
There are two ways moOde monitors renderers:
1. Renderer event scripts (/var/local/www/commandw/)
This is the approach used for shairport-sync, librespot and squeezelite but the scripts are different and unique to each renderer. The event script updates moOde state to indicate whether a renderer is active or not.
2. Renderer binary running.
This is the approach used for Bluetooth (bluealsa-aplay), RoonBridge and Multiroom-receiver (trx-recv) which don't support event scripts. moOde's worker daemon simply polls and checks whether the binary is running or not to determine whether it's active.
Multiroom receivers like trx and roc are based on rdp/udp network protocols which are "connectionless". Clients don't really connect to these receivers they just start sending packets to a multicast or multi-unicast address(s). A receiver is "active/playing" when it's receiving packets. When no packets are received (within some timeout period) then it could be considered "stopped/listening".
