-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Own packages only for airupnp or aircast #14
Comments
Awesome. I even didn't had to open the issue myself :) |
@Gummibando |
The UI integration for selecting airupnp/aircast (or both) is now integrated in the latest release. It would be great, if you could test it: 0.2.50.5-20210801 |
This sound fantastic. |
No problem :) |
I have created a DSM6 release for testing with the UI integration (backported from the dsm7 release). Thanks, René :) |
Sorry for replying late, but I just came back from being very AFZ (away from zuhause :). Status so far: I can install the package and the shared folder is created.
Package can be started after manually editing the (automatically created) airconnect.conf file (adding NAS IP address, adding UPNP port number), which, as per the documentation, should actually only be relevant for DSM 7 (?). After manually running A check with a Bonjour browser app (Bonjeff) shows no added airplay/raop service broadcast. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
This issue was closed because it has been stalled for 5 days with no activity. |
Sorry @Gummibando, the bot closed the issue because it was stale ;-) The DSM6 release with GUI + config file was a testing release, so the documentation in the readme is therefore not up to date. Empty config files for aircast and airupnp will be ignored. The empty files will be created by default so that they will be editable from the DSM GUI (File Station) for anybody that will not connect via SSH to the NAS. So in general, after your changes to the config file, the DSM 6 package is running but no devices will be found? it could be possible, that the default configuration does not allow your devices. which devices you are using? Sonos should be discovered by default. In short: For a first test, you can change the airconnect.conf configuration file and remove the Line If you remove this line, all speakers that are found on your network should be found by AirConnect. |
Exactly. Package running, no devices found. The device is a Naim streamer. |
Ok, thanks for the info. I have two other issues for the DSM6 packages that i want to implement in the upcoming weeks. I will have a look at it. |
The build scripts should be extended or adapted in that individual packages are built only for airupnp or aircast. (i.e. there is one package (airconnect) for both binaries and one package only for airupnp or aircast).
Alternatively, it could be considered to include the Synology Package Manager GUI and to integrate a selection menu during installation (WIZARD_UIFILES folder) which binaries should be installed and managed (Both, airupnp, aircast).
The text was updated successfully, but these errors were encountered: