RE: Slim connector problem (slightly long description!)

["Kevin Hawkins" <lists@xxxxxxxxxxxxxxxxx>]

> -----Original Message-----
> From: Paul Gordon [mailto:paul@xxxxxxx]
> Sent: 11 June 2004 14:17
> To: xap_automation@xxxxxxx
> Subject: RE: [xap_automation] Slim connector problem
> (slightly long description!)
>
> Thanks for the comprehensive reply Kevin!
>
> I Think there are a couple of questions for me to answer
> in there, so I'll attempt to do so...
>
> The conduit didn't just create a new Homeseer device
> without asking me,
> - It just surprised me that it detected a new xAP device
> and popped up the wizard accordingly... - I selected to
> let it create the HS device, since I didn't know what it
> was or what it was for, so I reckoned it must be better to
> have it than not to have it... :-o

You can always delete them anyway later if you find you don't need them -

>
> For info, when the slim connector service was first
> started, the HS device created was:
> jukebox slimp3 kcsoft.slimp3.jukebox:slimp3
> xAP-Audio.Audio.Event Audio.Mixer volume Device type =
> slimp3, and the Homeseer Status string is set to 50 (not
> sure what that means...)

That looks like a representation of the current volume for the device - at
50% - ie half which is probbaly the default - if you alter the SliMP3 vol
it
probably changes.  Currently there is not a schema definition included in
the HS download for the SliMP3 (and it doesn't use BSC) - we must fix that
(another one for the list). The lack of this means for example you can't
alter the vol from HS and it changes on the SliMP3.

>
> Subsequently, - and I said earlier that it occurred when I
> used the slim remote to play a track, (but now I'm not
> 100% certain that the timing of those events are related)
> the conduit detected another xAP device as
> follows:
> pauls-qbic mi4.desktop.pauls-qbic xAP-Audio.Transport
> Audio.Transport command Device type = Desktop, and the
> Homeseer status is "stop"

Ahh - this was actually from xAP Desktop - it is a new device to HS and
that
is why it popped up the wizard - it has happened because you clicked on one
of the audio transport controls in the SliMP3 display - and sent a
(targeted) message TO the SliMP3 to STOP playing.

K