services/pipewire: use node volume controls when routeDevice missing

For bluez audio streams and potentially other types of synthetic
device, volume controls are managed via the node and persistence is
handled by the service.

changelog/next.md

@@ -26,6 +26,7 @@ set shell id.
 ## Bug Fixes
 
 - Fixed volume control breaking with pipewire pro audio mode.
+- Fixed volume control breaking with bluez streams and potentially others.
 - Fixed escape sequence handling in desktop entries.
 - Fixed volumes not initializing if a pipewire device was already loaded before its node.
 - Fixed hyprland active toplevel not resetting after window closes.

src/services/pipewire/node.cpp

@@ -222,8 +222,11 @@ void PwNode::onInfo(void* data, const pw_node_info* info) {
 				self->routeDevice = id;
 				if (self->boundData) self->boundData->onDeviceChanged();
 			} else {
-				qCCritical(logNode) << self << "has attached device" << self->device
+				qCDebug(
-				                    << "but no card.profile.device property.";
+				    logNode
+				) << self
+				  << "has attached device" << self->device
+				  << "but no card.profile.device property. Node volume control will be used.";
 			}
 		}
 

src/services/pipewire/node.hpp

@@ -244,7 +244,9 @@ public:
 	qint32 routeDevice = -1;
 	bool proAudio = false;
 
-	[[nodiscard]] bool shouldUseDevice() const { return this->device && !this->proAudio; }
+	[[nodiscard]] bool shouldUseDevice() const {
+		return this->device && !this->proAudio && this->routeDevice != -1;
+	}
 
 signals:
 	void propertiesChanged();