-
-
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
AirConnect shows manually stopped after installation and press start #85
Comments
I encountered the same problem. I used an earlier release of the package and it worked instantly. Check the solved problems-section for a corresponding thread. |
Hello, |
Did you tried to uninstall it completly using the package center? And re-install from downloaded package again? Does tje error persist? |
Yes, I have tried the uninstall and reinstall route couple of times. Problem occurs here on DS713+ with 7.1.1 and DS115 with 7.1.1 |
Ok, strange, thanks for the info. Our child was born a few days ago. Personally, it will be a while before I have time to look at it again :) @Tho1848 which earlier version worked for you? The automatic upgrade process of the AirConnect binaries has changed and i need to update the scripts to get the latest 1.5.x version of AirConnect. Not that hard, but i a few hours of concentration ;) |
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. |
i have released a new version (PRE-release) with latest AirConnect binaries. Could someone please test it and give me feedback if the package works and/or if the problem still exists? https://github.com/eizedev/AirConnect-Synology/releases/tag/1.6.3-20240114 I have no problem with installation on my 3 devices, so it is hard to troubleshoot your problems. But I will dick deeper into the startup process and installation files, since I will rewrite some parts in the next weeks. Also, for troubleshooting, can someone please upload the content of your My working example:
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
FILTER_AIRPLAY2_DEVICES="<NULL>,S1,S3,S5,S9,S12,ZP80,ZP90,S15,ZP100,ZP120,1.0,LibreWireless"
SYNO_IP="192.168.1.249" |
I encountered the same issue, the previous version worked but that's installed a long while ago so I want to update to the latest one. Here's my airconnect.conf: AIRCAST_ENABLED=1 |
I have found the cause for my situation... As mentioned early in the thread, I had the same issue on my DS115 as well as DS713+. After installing a new HD in the DS115 and a fresh DSM and Airconnect install today, the same problem as before occurred. |
Ok, that's a really nice find! Thanks! Any idea what PiHole is blocking here? The mDNS traffic? But then normal Airplay shouldn't work either? |
Hmm, just tried an uninstall and reinstall (pihole disabled) and the problem has returned. Looks like I was too optimistic. Need to dig a bit further. |
If you upgraded from a very old version the uninstall routine of the old package could probably leave some old files behind an did not remove some of these old file completely. Can you please check the part The Config file looks correct to me. |
Thank you for your reply. I followed your direction but no magic happened. The good news is it's running while I installed the version 'AirConnect-dsm7-arm-0.2.51.2-20211124'. (I have tried 'AirConnect-dsm7-arm-0.2.51.2-20220130' and newer but none worked). Again, my Synology is pretty outdated, it's a DS416 mode, and it just working without any issue so I am not willing to upgrade it, so maybe it's not worth trouble shooting with my case. Thank you and appreciate all your efforts to make our life better. |
Aaah, ok, now I've got it. Your system is too old (this could be related to the old device kernel (old kernel, old glibc).) to be able to run newer versions of airupnp, you can find more information in the following discussion in this issue Version 1.0.13 should be the latest supported version, on really old devices the latest one is 0.2.51.2 The info is somewhat hidden relatively high up in the readme, I'll pin it a little more obviously |
That's it! The downgrade to 0.2.51.2 on my DS115 with DSM 7.1.1-42962 has addressed the issue. So you gave me an excuse to buy a new DS ;-) to run the latest Airconnect version. |
Good morning René,
Indeed, here is the kernel and glibc version of my Synology DS1513+
* Linux version 3.10.108 ***@***.***) (gcc version 8.5.0 (GCC) )
* GNU C Library (GNU libc) stable release version 2.26, by Roland McGrath et al.
I expect to buy a new NAS when DS1524+ or DS1624+ will be available.
Thanks again for the tool and support
Xavier
De : René ***@***.***>
Envoyé : samedi 27 janvier 2024 00:14
À : eizedev/AirConnect-Synology ***@***.***>
Cc : Xavier BERTHIER ***@***.***>; Comment ***@***.***>
Objet : Re: [eizedev/AirConnect-Synology] AirConnect shows manually stopped after installation and press start (Issue #85)
Aaah, ok, now I've got it. Your system is too old (this could be related to the old device kernel (old kernel, old glibc).) to be able to run newer versions of airupnp, you can find more information in the following discussion in this issue
—
Reply to this email directly, view it on GitHub<#85 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWXNQBPO6ROXSDZW6SYPAS3YQQ2CZAVCNFSM6AAAAAA7HESCZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJSHAYTKMJTGY>.
You are receiving this because you commented.Message ID: ***@***.******@***.***>>
|
Download AirConnect-dsm7-x86_64-static-1.2.2-20231001 and installed on my Synology DS718+
After installation AirConnect didn't started. When I press 'Start' it do show started but turn down after few seconds which shows manually stopped.
I have 1 Sonos bean paired with 2 'play 1' it works with airplay2 on ios system. But I have another 'play 1' connected to wifi which would like to use airplay by AirConnect.
Pls kindly let me know how to fix it and what happened.
The text was updated successfully, but these errors were encountered: