… and? any progress?
oh, interesting… So… I’m terrible at the waiting thing.
I just did the following:
Advanced -> RoPieeeXL Disabled -> Commit -> Save
Waiting for config and then rebooted from web page.
After it booted Advanced -> RoPieeeXL Enabled -> Commit -> Save (this took a significantly longer amount of time then the previous time I enabled it)
After the “configuring” page returned the Pi popped-up as an Airplay endpoint. This is before doing another reboot. Webpage is now saying I need to reboot.
Issued Reboot. Waited 10 minutes and it did not return as Airplay device.
Disabled RoPieeeXL and rebooted.
Enabled RoPieeeXL and, again, as soon as it finished configuring Pi was displayed as an Airplay endpoint. I’ve not rebooted yet.
I can select as Airplay device (from iMac 10.14.5) and I see packets going to the Pi but no sound yet. Trying to troubleshoot that now.
*I use MDNS repeater which works fine with Apple devices but something is not excellent with the RoPieeeXL. What software is providing the Airplay support? Is it Shairplay? I can start doing some packet captures and try to identify what the difference is between Apple devices and Shairplay.
So guys… I pushed out an update.
The cool thing: if you use something other then USB it will work. I’ve been listening via Airplay for more than 1 hour already without issues.
The not so cool thing: USB is not working. Not only because you need to explicitely configure it (so I need to build something for that in the webpage), but also because it simply does not work even if you do.
So… if you’re using USB you need to wait a little bit until I’ve got this sorted out.
Going to bed for now 
1 Like
hmmm… I already know what it is
still requires some work though.
Excellent… yeah… I just identified that shairport-sync was crashing when trying to use USB DAC (but I know how to restart it now!)
OK, I put an Apple device on the same network as the Pi to make sure it wasn’t a MDNS thing. It appears not as I still get the strange behavior of having to disable/enable XL to get it to show-up as Airplay device.
Trying to use the on-board phono I get:
May 22 14:18:33 ropieeeXLbeta01 shairport-sync[9219]: ALSA lib pcm_hw.c:1820:(_snd_pcm_hw_open) Invalid value for card
Don’t have another way to connect besides USB and phono at this point. Anyway, thanks for the support and when USB starts working I’ll try again. Excellent progress though. Let me know if I can provide any details to help identify why I need to disable/enable to get it to broadcast as an Airplay device.
ok another update. back to USB, because right now more beta testers have USB.
For me it works now. Let’s see.
i made a change so it will restart automatically upon crash. however, it should work on usb now (it does for me).
The other issue about the broadcast; that’s something we should figure out.
Neat. OK, reflashing to make sure everything is clean.
May 22 15:30:56 ropieeeXLbeta01 systemd[1]: shairport-sync.service: Service RestartSec=2s expired, scheduling restart.
May 22 15:30:56 ropieeeXLbeta01 systemd[1]: shairport-sync.service: Scheduled restart job, restart counter is at 18.
May 22 15:30:56 ropieeeXLbeta01 systemd[1]: Stopped Shairport Sync - AirPlay Audio Receiver.
May 22 15:30:56 ropieeeXLbeta01 systemd[1]: Starting Shairport Sync - AirPlay Audio Receiver...
May 22 15:30:56 ropieeeXLbeta01 mkdir[7774]: /usr/bin/mkdir: cannot create directory '/var/lib/shairport-sync': Permission denied
May 22 15:30:56 ropieeeXLbeta01 systemd[1]: shairport-sync.service: Control process exited, code=exited status=1
May 22 15:30:56 ropieeeXLbeta01 systemd[1]: shairport-sync.service: Failed with result 'exit-code'.
May 22 15:30:56 ropieeeXLbeta01 systemd[1]: Failed to start Shairport Sync - AirPlay Audio Receiver.
[root@ropieeeXLbeta01 lib]# pwd
/var/lib
[root@ropieeeXLbeta01 lib]# mkdir shairport-sync
[root@ropieeeXLbeta01 lib]# systemctl status shairport-sync
* shairport-sync.service - Shairport Sync - AirPlay Audio Receiver
Loaded: loaded (/usr/lib/systemd/system/shairport-sync.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2019-05-22 15:34:00 PDT; 2min 3s ago
Testing sound now.
Glorious sound!
Source Devices:
iPhone 5S works!
iMac (10.14.5) Not working but this is very much a network issue on my part:
May 22 15:39:40 ropieeeXLbeta01 shairport-sync[8063]: Sync packet received before we got a timing packet back.
It appears shairport is doing something different than Apple<->Apple (I already know it’s using different ports) and I’ve got a firewall in-between some of my devices and the Pi. I’ll dig into the Shairport docs and identify if I can make it work. But on the same broadcast network now works! Thanks! I’m going to go listen now.
!UPDATE on broadcasting as Airport Device!
I may have found a path to what’s causing the issue with the Airplay device not coming up after reboot. It appears avahi-daemon is the cause of my problem.
#This is _just_ after Reboot and Pi _does not_ show-up as an Airplay device.
[root@ropieeeXLbeta01 ~]# journalctl -u avahi-daemon
-- Logs begin at Thu 2018-07-05 12:46:41 PDT, end at Wed 2019-05-22 16:05:56 PDT. --
May 22 16:05:51 ropieeeXLbeta01 systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: Found user 'avahi' (UID 978) and group 'avahi' (GID 978).
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: Successfully dropped root privileges.
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: avahi-daemon 0.7 starting up.
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: Successfully called chroot().
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: Successfully dropped remaining capabilities.
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: Loading service file /services/ropieee.service.
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.114.47.
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: New relevant interface eth0.IPv4 for mDNS.
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: Network interface enumeration completed.
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: Registering new address record for fe80::ba27:ebff:fe0a:8a3e on eth0.*.
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: Registering new address record for 192.168.114.47 on eth0.IPv4.
May 22 16:05:51 ropieeeXLbeta01 systemd[1]: Started Avahi mDNS/DNS-SD Stack.
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: Withdrawing address record for 192.168.114.47 on eth0.
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.114.47.
May 22 16:05:51 ropieeeXLbeta01 avahi-daemon[4034]: Interface eth0.IPv4 no longer relevant for mDNS.
May 22 16:05:53 ropieeeXLbeta01 avahi-daemon[4034]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.114.47.
May 22 16:05:53 ropieeeXLbeta01 avahi-daemon[4034]: New relevant interface eth0.IPv4 for mDNS.
May 22 16:05:53 ropieeeXLbeta01 avahi-daemon[4034]: Registering new address record for 192.168.114.47 on eth0.IPv4.
Now I restart avahi-daemon and as soon as I do this Pi pops-up in all my Apple devices as an Airplay device.
# systemctl daemon-reload
# systemctl restart avahi-daemon
#After systemctl restart avahi-daemon
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[4034]: Got SIGTERM, quitting.
May 22 16:06:31 ropieeeXLbeta01 systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[4034]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.114.47.
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[4034]: avahi-daemon 0.7 exiting.
May 22 16:06:31 ropieeeXLbeta01 systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
May 22 16:06:31 ropieeeXLbeta01 systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: Process 4034 died: No such process; trying to remove PID file. (/run/avahi-daemon//pid)
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: Found user 'avahi' (UID 978) and group 'avahi' (GID 978).
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: Successfully dropped root privileges.
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: avahi-daemon 0.7 starting up.
May 22 16:06:31 ropieeeXLbeta01 systemd[1]: Started Avahi mDNS/DNS-SD Stack.
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: Successfully called chroot().
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: Successfully dropped remaining capabilities.
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: Loading service file /services/ropieee.service.
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.114.47.
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: New relevant interface eth0.IPv4 for mDNS.
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: Network interface enumeration completed.
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: Registering new address record for fe80::ba27:ebff:fe0a:8a3e on eth0.*.
May 22 16:06:31 ropieeeXLbeta01 avahi-daemon[7028]: Registering new address record for 192.168.114.47 on eth0.IPv4.
May 22 16:06:32 ropieeeXLbeta01 avahi-daemon[7028]: Server startup complete. Host name is ropieeeXLbeta01.local. Local service cookie is 1639477715.
May 22 16:06:32 ropieeeXLbeta01 avahi-daemon[7028]: Service "RoPieee [ropieeeXLbeta01]" (/services/ropieee.service) successfully established.That’s … kinda weird. Because Avahi is already running.
So you’re saying that:
- booting the pi
- stuff is working, but not visible / discoverable
- restart avahi
- stuff is visible / discoverable
correct?
Is there anyway to manually set the beta flag, I tried three times, two different cards and each time I set ‘beta’ from the web interface it crashes and when I reboot it is still on the same version.
Starting from a working Ropiee 273 connected via WiFi
can you send me feedback? because I really want to know why it crashes.
I thought I fixed that in the last update…
Hi harry, feedback sent:
b3f3ff278d583845
I seems any ‘Save changes’ crashes the web interface. I then have to reboot manually.
RaspberryPi3b & HiFiBerry DAC+ Pro hat, Std Pi Power Supply
hmmm… I don’t see the crash because you need to reboot.
Are you familiair with SSH?
Yes, let me know what you want.
ok, let the webpage crash, login in and show me the result of:
journalctl | grep ropieee-web
OK, I was SSH’d in before hitting the Save on the web interface, but I got logged off and cannot reconnect?
huh? that should not happen…
I just tried it again, same thing. Here is the log (keys removed) when it has rebooted:
~/.local/share/nvim/swap//Jul 05 20:46:50 OwenPi ropieee-web[422]: config:read: reading from /data/ropieee.conf
Jul 05 20:46:50 OwenPi ropieee-web[422]: info: read config: {
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_oem”: “0”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_oem_identifier”: “ropieee-ose”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_uboot”: “0”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_dualroot”: “0”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_mender”: “0”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_arch_base”: “201808_00”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_repo”: “stable”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_repo_url”: “http://repo-RP_REPO.ropieee.org/”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_rescue_branch”: “master”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_hostname”: “OwenPi”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_audio”: “hifiberry-dacplus”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_audio_usb”: “0”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_reboot_schedule”: “never”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_reboottime”: “03:04”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_auto_update”: “on_boot”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_timezone”: “Europe/London”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_touchscreen_detected”: “0”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_touchscreen_orientation”: “rotated”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_touchscreen_zone”: “unknown”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_network_wired_method”: “dhcp”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_network_wired_ipaddr”: “undefined”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_network_wired_netmask”: “undefined”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_network_wired_gateway”: “undefined”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_network_wireless_enabled”: “1”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_network_wireless_essid”: “Dachshund”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_network_wireless_psk”: “REMOVED”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_raat_dop_enabled”: “0”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_raat_software_volume_enabled”: “0”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_led_function”: “blink”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_remote_control”: “none”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_remote_control_zone”: “unknown”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_force_mixer_onstart”: “0”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_force_mixer_level”: “1”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_sshd_port”: “22”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_extension_alarm_clock”: “0”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_network_wireless_psk2”: “REMOVED”,
Jul 05 20:46:50 OwenPi ropieee-web[422]: “rp_this_is_xl”: “0”
Jul 05 20:46:50 OwenPi ropieee-web[422]: }
Jul 05 20:46:50 OwenPi ropieee-web[422]: info: is_wifi_available() true
Jul 05 20:46:54 OwenPi ropieee-web[422]: info: wifi networks discovered: Dachshund,Labrador,TP-LINK_0CA0,Dachshund 5GHz
Jul 05 20:46:54 OwenPi ropieee-web[422]: info: RoPieee version: 273
Jul 05 20:46:54 OwenPi ropieee-web[422]: info: detected hardware: rpi3
Jul 05 20:46:54 OwenPi ropieee-web[422]: info: RoPieee Web Server running at http://0.0.0.0:80/
Jul 05 20:46:56 OwenPi ropieee-web[422]: info: cb_bonjour_up(): RoPieee [OwenPi]