AirConnect running on DS412+ tagetting to Onkyo AV TX-N

[yakup38]

Hello,

I've tried to use this nice piece of software, but unfortunately i can't see the AirCast server from my daughter iPad.

Here is my setup :

iPad >>> Syno DS412+ running AirCast and AirUPnP as daemon >>> Gigabit home LAN >>> Onkyo TX-NR3009

Everything seems to work OK but however on iPad connected to 2.4GHz wifi LAN i can't see AirCast server. Maybe the AirCast doesn't detect the Onkyo ?

Onkyo is set on Net > DLNA input

Any idea how should i proceed ?

Thanks in advance !

[eizedev]

Hi @yakup38 and sorry for the late reply. I am very busy in my private life at the moment and only now have the time to reply.

hmm.. strange. Could you please upload and post the airconnect log from /var/log/airconnect? Best is to stop aircast, delete log and start aircast again, wait a few seconds until aircast can discover all network devices so you don't have to filter the individual entries from the logfile.

normally, if aircast and airupnp are running, you should see all devices that are found by using airplay on your ipad. The logfile should show if the onkyo device was successfully discovered.

Do you have any other apple device where you can test the airplay connection to the onkyo device (and the aircast server)?

Also, can you please describe your local network setup? So, do you have any special router or managed network switches in your environment?

[yakup38]

Hello @eizedev ,

sorry for the late reply, as you can guess we're all busy... So, i have tried once more this time with a more "rested head" let's say..and Aircast seems to work OK, i'm still adding the log file for info in case you need to compare to the airupnp log that i'll attach either. However, i had less success with airupnp which is not detecting my Onkyo TX-NR3009 which is set on NET > DLNA input, and Onkyo can see my Asus laptop as a source but not AirUpnp ... I'm still putting both log files for your info. As my Nvidia shield supports GoogleCast by default, so there is no point of running this relay between iPad and Nvidia but still works and is displayed in AirCast menu from the iPad. It is just a shame the AirUpnp doesn't detect directly my Onkyo, i fit worked there will be no need running Nvida for streaming music.....Now, the other option is going spotify Premium connect... But for the fun of developping, i really appreciate this feature and it can make sense in many other configuration than mine..

Thanks, Yakup

PS: Here are my commands for starting servers :

./airupnp -b 192.168.0.37:49154 -l 1000:2000 -x "/volume1/@appstore/AirConnect/config.xml" -o ",S1,S3,S5,S9,S12,ZP80,ZP90,S15,ZP100,ZP120" -z -f "/var/log/airupnp.log" -d all=debug

./aircast -b 192.168.0.37 -l 1000:2000 -x ./config-cast.xml -z -f /var/log/aircast.log -d all=debug

airupnp.log aircast.log

[eizedev]

@yakup38

Sorry for the late reply. The fact that your Onkyo AVR does not get discovered from airupnp is due to the start command of airupnp. The default start command of Airconnect-Synology is using the -o parameter.

With -o <NULL>,S1,S3,S5,S9,S12,ZP80,ZP90,S15,ZP100,ZP120,1.0,LibreWireless the sonos/UPnP speakers that are natively supporting AirPlay or AirPlay2 will be ignored from AirConnect/airupnp and only the ones listed with -o will be used. Since no new "non airplay" speakers (from sonos) will be released in the future, that should work in any case. So they will be not displayed twice in the list. <NULL> will discover all devices which do not have (or do not publish) a model number.

You could remove the -o parameter from your airupnp startup command for testing, then your Onkyo AVR should be discovered, since the filter does not exist anymore. Then you should find a line in the airconnect.log with the information of the onkyo avr device. I could add the Onkyo TX-NR3009 to the default list, but i cannot find the UPNP Model number online for this device. You could try it by adding -o TX-NR3009 to your command But I don't think this is the right model number either. Also you can use a tool like upnp-info or any other upnp discovery tool to discover the device xml file and there you can find the model number and model name.

You can also find more information in the Airconnect-Synology Readme

[yakup38]

Thanks a lot René !!

I'll try and keep you updated.

Good evening !

On Mon, 17 May 2021 at 22:05, René @.***> wrote:

@yakup38 https://github.com/yakup38

Sorry for the late reply. The fact that your Onkyo AVR is due to the start command of airupnp. The default start command of Airconnect-Synology is using the -o parameter.

With -o ,S1,S3,S5,S9,S12,ZP80,ZP90,S15,ZP100,ZP120,1.0,LibreWireless the sonos/UPnP speakers that are natively supporting AirPlay or AirPlay2 will be ignored from AirConnect/airupnp and only the ones listed with -o will be used. Since no new "non airplay" speakers (from sonos) will be released in the future, that should work in any case. So they will be not displayed twice in the list.

You could remove the -o parameter from your airupnp startup command for testing, then your Onkyo AVR should be discovered, since the filter does not exist anymore. Then you should find a line in the airconnect.log with the information of the onkyo avr device. I could add the Onkyo TX-NR3009 to the default list, but i cannot find the UPNP Model number online for this device. You could try it by adding -o TX-NR3009 to your command. Also you can use a tool like upnp-info https://github.com/tenable/upnp_info or any other upnp discovery tool to discover the device xml file and there you can find the model number and model name.

You can also find more information in the Airconnect-Synology Readme https://github.com/eizedev/AirConnect-Synology#supported-upnp-speakers

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/eizedev/AirConnect-Synology/issues/23#issuecomment-842595528, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADCD53AUPPHWSOHEW4RHZDTTOFZJ5ANCNFSM427LAHGQ .

-- Kind regards,

Yakup AKSU

[eizedev]

if you are familiar with linux commands you could also use tcpdump to discover upnp devices on your network. You can install tcpdump on any synology NAS by using synogear install. See documentation here: FAQ-synogear. synogear also installs a few other useful commands. I have installed the diagnostic tool (synogear) on every synology device that i own.

Change en0 to your network adapter name (wait a few seconds until the devices get discovered)

sudo tcpdump -vv -A -s 0 -i en0 host 239.255.255.250 and port 1900 | grep LOCATION

Then you need to find your Onkyo AVR ip and catch the Location URL.

With the curl command (or the browser of your choice) you can then search for the modelNumber in the device xml configuration:

curl http://192.168.1.122:1400/xml/device_description.xml | grep modelNumber

S12 is a Sonos Play:1 in this example.

This modelNumber is the number that i need.

[yakup38]

Okay Let's get a try....Do you have Teams ?

On Mon, 17 May 2021 at 22:30, René @.***> wrote:

if you are familiar with linux commands you could also use tcpdump to discover upnp devices on your network:

Change en0 to your network adapter name

sudo tcpdump -vv -A -s 0 -i en0 host 239.255.255.250 and port 1900 | grep LOCATION

[image: image] https://user-images.githubusercontent.com/6794362/118552071-bd8ee700-b75e-11eb-94a5-9190d62ee5a7.png

Then you need to find your Onkyo AVR ip and catch the Location URL.

With the curl command (or the browser of your choice) you can then search for the modelNumber in the device xml configuration:

curl http://192.168.1.122:1400/xml/device_description.xml | grep modelNumber

[image: image] https://user-images.githubusercontent.com/6794362/118552462-473eb480-b75f-11eb-9156-54e96ab5bd8b.png

S12 is a Sonos Play:1 in this example.

This modelNumber is the number that i need.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/eizedev/AirConnect-Synology/issues/23#issuecomment-842618207, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADCD53DLLBSOQLH26RSGRHDTOF4E7ANCNFSM427LAHGQ .

-- Kind regards,

Yakup AKSU

[eizedev]

In Germany it is just shortly before 11 o'clock in the evening, I'm going to sleep for now. Take yourself some time. And as I said, if in doubt, test it without -o, it should work. 😃

Edit:

./airupnp -b 192.168.0.37:49154 -l 1000:2000 -x "/volume1/@appstore/AirConnect/config.xml" -z -f "/var/log/airupnp.log" -d all=info

And then take a look at /var/log/airupnp.log

[eizedev]

@yakup38 Any news on this?

[yakup38]

İ will double check after holidays torn but as far as i remember, streaming video was OK but streaming audio not..

On Fri, Jul 16, 2021, 11:23 René @.***> wrote:

@yakup38 https://github.com/yakup38 Any news on this?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/eizedev/AirConnect-Synology/issues/23#issuecomment-881306374, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADCD53CSM3VI5ZIOJ4RUVPLTX73BPANCNFSM427LAHGQ .

[eizedev]

@yakup38

in the latest release 0.2.50.5-20210801 i have integrated a configuration file for AirConnect-Synology. You also can specify the filter for the airplay devices in the configuration file. Also you can disable filtering as in the example below. Perhaps this can fix your problem.

• Uninstall the existing package first
• Install the newest release: 0.2.50.5-20210801
• Open FileStation (or connect via ssh) - /volume/airconnect/airconnect.conf
• Edit the configuration parameter FILTER_AIRPLAY2_DEVICES
  • Remove FILTER_AIRPLAY2_DEVICES line
  • Save the file
• Restart AirConnect

The final airconnect.conf should look something like this:

AIRCAST_ENABLED=1
AIRCAST_LATENCY="1000:2000"
AIRCAST_LOGLEVEL="all=info"
AIRUPNP_ENABLED=1
AIRUPNP_LATENCY="1000:2000"
AIRUPNP_LOGLEVEL="all=info"
AIRUPNP_PORT=49154
SYNO_IP="192.168.1.10"

[github-actions[bot]]

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.

[yakup38]

Hi René, very busy after hollidays come back..but definitely i'll give it a try and report the result here. Thx a lot for your hard work !

[github-actions[bot]]

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.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.