Hi Raymond,

I haven't tried what you are suggesting, so ymmv.

But I do have a Merten push-button with two buttons (or four as the two are spring-loaded and you can press both up and down on them), so I guess it will appear much the same to LMCE.
The problem with your scenario is that the device will only appear as one device for LMCE. So whenever one of the sensors trigger, LMCE will see an event from the same device. In other words you have no way of telling sensor 1 from sensor 2 etc...

At least, this is how I understand the problem.

br,
sambuca

You're correct, freepbx is not used anymore, and the Advanced -> Configuration -> Phone Setup menu should be removed. Instead, use Wizard - devices - phone lines to set up trunks.
Choose the SPA protocol, and iirc; the username and phone number needs to be equal. It is quite simple.

The SPA configuration is more difficult though, but that should be the same as for 810, so the wiki article still applies.

- sambuca

It depends on how you want to use it? Are you using it as an adapter to connect a analog phone to LMCE, or are you connection LMCE to your analog phone line?

Both scenarios are described in the wiki, iirc.

br,
sambuca

When setting up events, it is useful to see what events are actually sent in the system. The DCERouter.log will list all events, and the type of event. The texts in the event drop down is sometimes a bit misleading, or there are several selection that could match you purpose.

Also note that after adding event commands, you need to reload the router. Adding or changing event criteria does not require reloading.

br,
sambuca

It should be possible to send PCM data to xine. PCM data uses more bandwith, but not enough to justify converting it to something else. I also suspect that the audio has already been converted once from mp3 to PCM. Maybe there is some way to get the original data from libspotify instead of PCM?
The CD playback is just xine streaming audio from one MD to another, nothing special there.

Whether you need a scenario or not depends on your implementation and design. But a scenario button to open the spotify-specific screen seems to be the best way. From that screen, I would imaging that you can search and play tracks. The searching and playing part is what needs to send commands to the spotify device. When the spotify device has a stream ready, a MH_Play_Media command needs to go to the MediaPlugin to register the media stream in the system and direct it to the correct playback device. If you use the Streamed Audio media type, the MediaPlugin will automatically send the proper commands to xine.

So a first step would be to create a spotify device, with the required commands (at least search and play), and have it present a stream on some port when it plays. Then test this by issuing a manual MH_Play_Media command with the stream url. When this works, you can start looking at the orbiter screens.

br,
sambuca

Hello all

For those of you who haven't followed the trac changelog closely or haven't been able to connect the dots... 

LinuxMCE 1004 now supports Audio streams(aka. Internet Radio) http://wiki.linuxmce.org/index.php/Internet_Radio
Xine_Player now accepts playlist URLs (very useful for Internet Radio), so you don't have to use the stream URL anymore.

best regards,
sambuca

Hi,

This would be a research project to find out what works and what breaks, and how to fix it.

I would also suggest that you try to get your changes integrated into LinuxMCE if you get anywhere.

br,
sambuca

There is no need to do a full or quick regen of the qorbiter.

The Android qOrbiter will crash. That is the short answer  It is still very much alpha quality and the media browser crash happens a lot.
Also note that from my experience, the skin is different when your device is in landscape when starting up, than it is when starting the orbiter in portrait mode. You might get different results depending on which one you use.

br,
sambuca

The playback is still xine-based, although there is a mplayer device too, but it is only used in a few cases.

I don't know anything about the obi 110 ata, but the SPA3102 works. Some manual config is needed though. (It is on my list of fixes/changes to look into)

br,
sambuca

It should be schema.linuxmce.org instead of sqlcvs.linuxmce.org. IIRC, there is a configuration option to set this address in one of the builder config files.

br,
sambuca

Hi,

I would put the device on the core if it does not really need to be on the MD.
I would always try to expose the audio as a stream, this allows us to seamlessly send audio to both squeezeboxes and MDs.
There is a spotify library iirc? Is that what you intend to use. Either way, it should be possible to implement several spotify clients within the same Spotify device, right? So it might not be necessary with several devices.

If possible, I'd use xine to play the stream on MDs, and then there be no reason for the spotify device to be on the MD itself. All of this is depending upon a spotify device that allows us to access the audio stream in some way, ofcourse.

Don't know the exact process of adding screens, but they need to be added in the Screen table in the database. I think this is used, at least as reference, in qOrbiter too.
After adding an entry in the table, and committing it to sqlCVS, you go ahead create a new Screen_xx.xml file in qOrbiter (from how I understand qOrbiter).

br,
sambuca

The proper way would be to change the plutodhcp binary(iirc) to output the domain name configured in the web admin. This could also be extended to add more specific settings if needed.

I'm not sure how custom your setup is, but I think the above should get you at least part of what you need and should be useful for for other too. At least myself have also been thinking of the domain name issue.

Maybe check trac if there is a ticket for this, and add one(or several to keep them focused/specific) if there isn't.

br,
sambuca

Be sure to look up the doc on every metadata format to see if it says anything about default encoding. I would think that ogg and flac metadata has a default encoding(utf8 maybe?). For mp3/id3 on the other hand, I don't think the standard specifies anything, but I would recommend you to double-check that.

I've also seen some mp3-tags where there is an encoding string at the beginning. Don't know how common that is, but maybe it's something to examine further?

I would use UTF-8 as much as possible, and convert to (and from) utf8 only at the input (and output). The database should already be utf8, so from what I understand, option 1 seems the best. Maybe even default to latin1 for metadata formats that doesn't have a standard encoding?

br,
sambuca

It might be that the connection used does not handle UTF-8 in all cases (I think there is a connection parameter for that..). For instance that the UpdateMedia connection does not use UTF-8 while the web-admin connection does?

br,
sambuca

Hi,

You only need one USB ZWave dongle, for instance on the core, which is supposed to be running all the time. If you are unsure about the range, every ZWave device that is plugged into external power acts as repeaters.

br,
sambuca