Device won't show up

I put the latest version of Volumio on my Raspi ZeroW (with Pirate Audio line out hat) that had a previous version on it from 2022 (got corrupted and I couldn’t find the copy) using the free MyVolumio. I had to change the date/time to match the current date/time, which seems to be staying correct after a reboot. I’m currently hooked to my work laptop’s hotspot and am able to SSH and get to the UI no problem. I can log in to MyVolumio through the UI, but my device never seems to show up even after waiting 5-10 minutes. I basically just want to ad the Pirate Audio display/button and Spotify plugins.

Here is the log from when I logged into MyVolumio. It may be our work firewall, so I’ll try it at home in a couple hours, but if not, can anyone point me in the right direction? I know practically nothing about linux.

Starting Live Log…

process exited with code nullinfo: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CorePlayQueue::getTrack 0
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses
info: CALLMETHOD: system_controller system enableLiveLog true
info: CoreCommandRouter::executeOnPlugin: system , enableLiveLog
info: Launching a new LiveLog session
info: Killing previous LiveLog session
info: Live Log process terminated: null
info: CoreCommandRouter::executeOnPlugin: my_volumio , setMyVolumioToken
info: MyVolumio login type: Token
info: MYVOLUMIO SUCCESSFULLY LOGGED IN
info: MyVolumio token set successfully
info: MYVOLUMIO: Adding device
info: MYVOLUMIO: Evaluating Server
info: Removing browser output: myVolumio user plan is not superstar
info: Removing audio output:
info: Stoppping Tunnel 1
 volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl stop sshtunnel.service
pam_unix(sudo:session): session opened for user root by (uid=0)
info: Setting Geolocation for MyVolumio to us1
info: CoreCommandRouter::executeOnPlugin: system , getConfigParam
info: CoreCommandRouter::executeOnPlugin: system , getConfigParam
pam_unix(sudo:session): session closed for user root
info: Remote SSH Stopped
error: Failed to add MyVolumio device: {"message":"USER_NOT_FOUND"}
info: Updating MyVolumio device info
info: CoreCommandRouter::executeOnPlugin: system , getConfigParam
info: CoreCommandRouter::executeOnPlugin: system , getConfigParam
error: Failed to update MyVolumio device: {"message":"DEVICE_NOT_FOUND"}
info: MYVOLUMIO: Adding device
info: MYVOLUMIO: Evaluating Server
info: Setting Geolocation for MyVolumio to us1
info: CoreCommandRouter::executeOnPlugin: system , getConfigParam
info: CoreCommandRouter::executeOnPlugin: system , getConfigParam
error: Failed to add MyVolumio device: {"message":"USER_NOT_FOUND"}
info: Updating MyVolumio device info
info: CoreCommandRouter::executeOnPlugin: system , getConfigParam
error: Failed to update MyVolumio device: {"message":"DEVICE_NOT_FOUND"}
wlan0: CTRL-EVENT-DISCONNECTED bssid=92:65:84:9b:7d:19 reason=0 locally_generated=1
wlan0: carrier lost
wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=US
Withdrawing address record for 192.168.137.87 on wlan0.
Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.137.87.
wlan0: deleting route to 192.168.137.0/24
wlan0: deleting default route via 192.168.137.1
Interface wlan0.IPv4 no longer relevant for mDNS.
info: Discovery: A device disappeared from network
info: Discovery: Device volumio disappeared from network
Deleting interface #4 wlan0, 192.168.137.87#123, interface stats: received=161, sent=168, dropped=0, active_time=486 secs
172.235.32.243 local addr 192.168.137.87 -> 
173.73.96.68 local addr 192.168.137.87 -> 
108.61.73.244 local addr 192.168.137.87 -> 
66.118.228.14 local addr 192.168.137.87 -> 
104.167.215.195 local addr 192.168.137.87 -> 
23.111.186.186 local addr 192.168.137.87 -> 
23.168.24.210 local addr 192.168.137.87 -> 
72.30.35.88 local addr 192.168.137.87 -> 
142.202.190.19 local addr 192.168.137.87 -> 
135.134.111.122 local addr 192.168.137.87 -> 
193.122.140.187 local addr 192.168.137.87 -> 
144.202.66.214 local addr 192.168.137.87 -> 
162.159.200.123 local addr 192.168.137.87 -> 
23.142.248.9 local addr 192.168.137.87 -> 
24.229.44.105 local addr 192.168.137.87 -> 
23.150.41.123 local addr 192.168.137.87 -> 
23.150.41.122 local addr 192.168.137.87 -> 
info: Volumio Network Manager: Network status updated: 0
wlan0: Trying to associate with SSID 'DA9LT233057'
wlan0: Associated with 92:65:84:9b:7d:19
wlan0: CTRL-EVENT-CONNECTED - Connection to 92:65:84:9b:7d:19 completed [id=0 id_str=]
wlan0: carrier acquired
wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlan0: IAID eb:ff:7c:ec
wlan0: soliciting an IPv6 router
wlan0: rebinding lease of 192.168.137.87
wlan0: probing address 192.168.137.87/24
wlan0: leased 192.168.137.87 for 604800 seconds
Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.137.87.
wlan0: adding route to 192.168.137.0/24
New relevant interface wlan0.IPv4 for mDNS.
Registering new address record for 192.168.137.87 on wlan0.IPv4.
wlan0: adding default route via 192.168.137.1
info: Volumio Network Manager: Network status updated: 2
Listen normally on 5 wlan0 192.168.137.87:123
new interface(s) found: waking up resolver
info: Discovery: adding dc9b28e9-c09b-4e40-bdf6-89144c6469ee
info: Discovery: Found device Volumio
info: CoreCommandRouter::volumioGetState
info: CorePlayQueue::getTrack 0
193.122.140.187 local addr 192.168.137.87 -> 
24.229.44.105 local addr 192.168.137.87 -> 
Soliciting pool server 216.229.4.69
Soliciting pool server 149.248.12.167
144.202.66.214 local addr 192.168.137.87 -> 
23.142.248.9 local addr 192.168.137.87 ->

I connected the pi thru wifi to my home network. Same issue. The pi is not being picked up as a device in My Volumio.

I’m experiencing a similar issue: I have two pi zero w’s with DAC hats, one connected over WIFI, the other connected over an Ethernet-to-USB adapter. The wifi one is running version 3.3224 (11 Jul 2022), and has no problem with discovery. The hardwired one is running version 3.785 (16 Dec 2024), and it disappears from all network discovery after it’s booted.

I am only using them for the airplay remote speakers with my OwnTone server, and they each have a static DHCP lease. The wifi one that remains discoverable also still shows the web UI at the .local address, but the one that loses discoverability only remains accessible by IP address (either web UI or ssh). I can’t see anything obvious in the logs, but something odd is that the response when I stop streaming to the problematic one is that it shows “response”: “startAirplayPlaybackSuccess Success” in the message, even though the request was to stop airplay playback.

Heres a snippet of the logs, from just before I stopped streaming to the airplay device, until it disappeared from my list of available outputs.

info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::servicePushState
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
{“time”:1736300944311,“response”:“startAirplayPlayback Success”} % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
info:
---------------------------- Client requests Stop Airplay Playback
info: CoreCommandRouter::executeOnPlugin: airplay_emulation , stopAirplayPlayback
info: Airplay playback stop
info: Airplay Playback Stopped, clearing state
info: CoreStateMachine::resetVolumioState
info: CoreStateMachine::getcurrentVolume
info: CoreCommandRouter::volumioRetrievevolume

0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
100 63 100 63 0 0 588 0 --:–:-- --:–:-- --:–:-- 594
100 63 100 63 0 0 588 0 --:–:-- --:–:-- --:–:-- 588
info: CoreStateMachine::pushState
info: CoreCommandRouter::volumioPushState
info: CoreCommandRouter::volumioGetState
info: CoreCommandRouter::volumioGetState
info: Listing playlists
info: Listing playlists

The strange thing is that socket.io is still working, so the two volumio devices can see each other no problem, it’s just the mdns broadcasting that goes down a handful of seconds after I stop using the speakers.