why cant spotifyd http act as a spotify connecties device itself?

[cortegedusage]

Hoi there I know thuis might nog be the right place, as it is no bug.
Bit why can't spotifyd-http nog act as a spotify connect device itself this would make controlling it with a ir remote a lot easier.
Or can it be done and am I missing something?

[SimonTeixidor]

I wanted spotifyd-http to not depend on alsa/pulseaudio/portaudio.

Why does running two processes make things more difficult for you?

[cortegedusage]

It's not that I don't want to run two processes, it's just that I don't know how to automate the process of identifying the right spotify connect device and connect to it, so it can be controlled by a remote control. Anyways it's not a complete must and I can definitely live without, it would just make the WAF of my pi based music player one step nearer. I'll give it another chance when I find the time, or just wait until someone with the same needs comes with a smart solution. thank you. 2017-04-18 20:10 GMT+02:00 Simon Persson <notifications@github.com>:

…

I wanted spotifyd-http to not depend on alsa/pulseaudio/portaudio. Why does running two processes make things more difficult for you? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#12 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AV69TenTXmaclwjg_9bW-2h970g16_BLks5rxPysgaJpZM4NAmPa> .

[cortegedusage]

okay just looked a bit better, and figured out that the device itselfs gets a ID nr regardless of who's logged in.
I just assumed that this number would be different everytime the device reconnects.
this makes it a bit easier for me to accomplish what I want.

Do you by any chance know if this number changes during time?