http://wiki.linuxmce.org/api.php?action=feedcontributions&user=Brake16&feedformat=atomLinuxMCE - User contributions [en]2024-03-29T07:51:02ZUser contributionsMediaWiki 1.24.1http://wiki.linuxmce.org/index.php?title=Problem-accessing-webadmin&diff=27224Problem-accessing-webadmin2011-03-16T23:28:37Z<p>Brake16: </p>
<hr />
<div>[[Image:678px-Avequipment.jpg]]<br />
<br />
If you are having problems accessing the webadmin site the following might be useful;<br />
<br />
Linux MCE assumes it is DHCP controller for the network and as such assumes its IP address wil be 192.168.80.1. When you select WEBADMIN the firefox session will be pointed to 192.168.80.1 expecting the webadmin to be there. <br />
<br />
If (say your router is DHCP or you have another DHCP controller on your network) your IP address is different you will just get a page not found error.<br />
<br />
Drop to the KDE desktop and open up a Konsole session. Type then enter the following;<br />
<br />
Sudo ifconfig -a<br />
<br />
This will list your IP address against eth0 (your ethernet card). IF you copy and paste that IP address into a Firefox session you should now see the webadmin.<br />
<br />
<br />
TODO post picture of ifconfig -a<br />
<br />
"***PLEASE NOTE***" The above is describing a failure case within MCE and how to get access to your webadmin. You should set MCE up to be the DHCP controller for its internal network for lots of reasons (which you can find by searching). If however for some reason you are having problems accessing Webadmin the above is a good place to start.<br />
<br />
---For Dianemo systems---<br />
Webadmin is located at http://192.168.80.1/pluto-admin/index.php<br />
<br />
[[ Category : Admin Website ]]</div>Brake16http://wiki.linuxmce.org/index.php?title=USB_UIRT&diff=27220USB UIRT2011-03-16T01:54:14Z<p>Brake16: Removed duplicate line</p>
<hr />
<div>[[Category: Hardware]]<br />
{{versioninfo|810Status=Working|810UpdatedDate=3rd May 2010|810UpdatedBy=Kezza}}<br />
<br />
[[Category: Infrared]]<br />
<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
[[Image:USB_UIRT.jpg|right]]<br />
<br />
* Manufacturer home page: http://www.usbuirt.com/<br />
* Seems to work in [[Video#Equipment_used_in_the_demo|the LinuxMCE 704 demo video]]<br />
<br />
==Use in LinuxMCE==<br />
===Connection===<br />
* This device is [[Plug&play]], which means no significant amount of modifications are required to get it to work. Don't forget to [[Quick reload router]] after installation is complete.<br />
* '''MAKE SURE YOU HAVE PERFECTLY GOOD BATTERIES IN YOUR REMOTE, IF YOU ENCOUNTER PROBLEMS RECORDING IR CODES'''<br />
<br />
===Adding Remotes===<br />
* Windows XP MC Remote is added automatically.<br />
* Adding different remotes please see following page. Tested and worked perfectly 27/01/2010 http://wiki.linuxmce.org/index.php/Add_support_for_new_remote_controls<br />
<br />
===Controlling AV Devices===<br />
* [[AV Devices]] is the main page used for making and adjusting control over A/V Equipment.<br />
* Also take a look at [[Infrared Codes]] if you are having problems with the prepopulated Codesets.<br />
<br />
== Sales Pitch ==<br />
The USB-UIRT, along with Automation Software such as [[LinuxMCE]], allows your PC to both Receive and Transmit infrared signals -- exactly like those used by the collection of remote controls you've acquired for your TV, VCR, Audio System, etc. The USB-UIRT can:<br />
* Receive signals from the remote controls you already have (allowing your PC to perform actions when the 'Play' button is pressed on your VCR remote, for example)<br />
<br />
* 'Learn' from remotes you already have and Transmit a duplicate of these signals from your PC (for example, your PC could automatically turn ON your VCR and tune it to channel 3)<br />
<br />
* Use codes available from the Web for other remotes (such as the Philips Pronto) to control all of your equipment with Remote (IR) receivers (including special 'discrete' remote codes your brand-name remote doesn't include!). For example, the USB-UIRT could transmit the discrete 'Input 3' code to your TV to directly switch it to input 3, rather than cycling through all of the inputs.<br />
==Technical Details==<br />
===IR Reception===<br />
* 34-40KHz Frequency Range<br />
* 56KHz IR Receiver Add-On Option*<br />
* UIR-compatible Receiver Mode<br />
* >8 Meter Sensitivity<br />
* IR Wavelength Filtered<br />
* USB Wake-from-Standby Capability<br />
* Built-in wideband IR detector for accurate Learning, including carrier frequency.<br />
<br />
===IR Transmission===<br />
<br />
* 20-60KHz Frequency Range<br />
* Two (2) built-in High-Power Emitters<br />
* 1/8" Mini-Jack for External Emitters<br />
* UIRT-compatible Struct and Raw modes<br />
* Extended-length code support in hardware (up to 96burst-pairs)<br />
* Max-length burst code support in driver (up to 2048 burst-pairs)<br />
<br />
===Dimensions===<br />
<br />
* 2.4"W x 1.5"D x 0.7"H<br />
<br />
==Troubleshooting (0710)==<br />
<br />
Because of a bug within ftdi_sio.c, the UIRT can't transmit commands.... <br />
<br />
SethJ has prepared an excellent [[USB-UIRT_x86_Fix|description of the fix]].<br />
<br />
==Availability==<br />
USA : http://www.usbuirt.com<br />
Europe : http://www.hightechpad.com/?q=content/usb-uirt-56k-enchanced-version - dead domain for Europe shop :(<br />
<br />
==See also==<br />
* [[USB-UIRT x86 Fix]]<br />
* http://www.mythtv.org/wiki/USB-UIRT<br />
* https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/177166</div>Brake16http://wiki.linuxmce.org/index.php?title=Samsung_HL-S5087&diff=27154Samsung HL-S50872011-03-11T21:18:36Z<p>Brake16: first page</p>
<hr />
<div>[[Category: Hardware]]<br />
[[Category: Video]]<br />
[[Category: Displays]]<br />
{{Versioninfo|810Status=works with caveats|810UpdatedDate=11th March 2011|810UpdatedBy=[[User:brake16|brake16]]}}<br />
<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
=Basics=<br />
*General info<br />
**50 inch<br />
**DLP<br />
**1080p capable with lmce, if you can get around the bug<br />
**I'd put more info, but it's no longer available for purchase. Either you have one, or you don't.<br />
<br />
If you own this tv, be aware that there is a bug in the nVidia code (post 195) that does not play nice with this tv when connected to a MD by HDMI. In my case, connecting the MD's HDMI to a Denon amp, and then connecting the amp to the tv by HDMI fixed this problem completely. <br />
<br />
You'll know you have this bug if you have the tv hooked up while setting up your MD. You'll be able to see console prompts as they scroll by, but when it's time for the AVWizard to pop up, the screen will go black and you'll see the error message "Weak or no signal." If you are able to push an audio signal through the MD, the AVWizard screen will appear. As soon as the audio is gone, so is the video.<br />
<br />
*Not-confirmed-working alternatives<br />
**DVI<br />
**Component<br />
**HDMI switch</div>Brake16http://wiki.linuxmce.org/index.php?title=Web_Orbiter_2.0&diff=26841Web Orbiter 2.02011-01-26T20:27:08Z<p>Brake16: </p>
<hr />
<div>{{versioninfo|810Status=Relevant|810UpdatedDate=23rd July 2010|810UpdatedBy=Purps}}<br />
{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category: Orbiters]]<br />
[[Category: Tutorials]]<br />
<br />
A Web Orbiter is any device (such as a iPhone, iPod Touch, iPad, laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.<br />
<br />
The new Web Orbiter 2.0 has been re-written from the ground up to make sure it has a much smoother performance overall but especially on slower lower powered devices and devices that are connected over slow LAN connections or even slower external connections...such as a Mobile 3G network or slow WiFi connection.<br />
<br />
So what has changed? Well visually your Orbiter UI will look like it does on your existing standard Orbiters but you will notice that unlike the original Web Orbiter the new 2.0 version does not refresh every 5 secs. The new Web Orbiter now only updates if something changes in the system and that requires the UI screen you are currently viewing to be updated or if you click on a UI button or other UI element and that causes a screen update. <br />
<br />
To achieve this the proxy_orbiter has been updated so that it sets a flag called 'ANYNEWS' to 'true' if some element of the current displayed screen has been updated. The Web Orbiter makes a light weight call to query the state of this flag once every second and only gets an updated UI screen if the flag is set to 'true' otherwise no screen update is requested. So in use the new Web Orbiter 2.0 behaves in a very similar fashion to the Orbiter on one of your MD's - and now it even performs with a similar performance level too.<br />
<br />
Whats a proxy_orbiter? Proxy_orbiter runs on the Core and its job is to render the UI for the Web Orbiter that is running remotely on some other device. Each Web Orbiter has an associated proxy_orbiter and the two work in partnership. Proxy_orbiters do all the 'heavy lifting' rendering the UI and this allows the remote device that is running the Web Orbiter to be much less powerful and very simple devices indeed if needed.<br />
<br />
Another change in the new 2.0 Web Orbiter is that screen refreshes are double buffered so that the new Web Orbiter receives the new screen update from your Core in the background and only redraws the screen when it has the complete image stored in memory - this makes the update process smoother and faster.<br />
<br />
The overall effect of all these changes is to vastly improve the performance and usability while at the same time reducing the processing overhead of the Web Orbiter massively.<br />
<br />
== Setup ==<br />
The procedure to setup a Web Orbiter is simple but the order of steps is important.<br />
#First of all, add a new Generic Web Device as a Child Device for your Core:<br />
##Goto the LinuxMCE Admin website--> Pull down Advanced --> Configuration --> Devices --> This shows the devices tree on the left window --> click CORE. The CORE's detail page should appear.<br />
##Click 'Create Child Device'.<br />
##In the Description, enter the name of the specific web orbiter.<br />
##In the Add child device window, click the button 'Pick device template'. The new pop-up window containing device templates will be opened.<br />
##In the 'Device Category' dropdown list, choose 'Peripherals'.<br />
##In the 'Device Template' dropdown list, find and select "Generic Web Device" (or just type the template id: 1748 and press go).<br />
##Click the button 'Pick Device Template'. The Add Child Device Window will close, and the Generic Web Device will be added to the Core, as the updated Device Tree will show.<br />
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard-->Devices-->Orbiters.<br />
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.<br />
#Set the appropriate screen resolution to suit the device your Web Orbiter is intended for from the 'Size' drop down<br />
#Set the 'Skin' drop down to the skin you want to use (normally this would mean the UI1 Standard Variation or a derivative)<br />
#Click on your new Generic Proxy Orbiter in the device tree, give it a unique name and then scroll to the bottom of the page on the right and look for the field called 'Listen Port'. This field will be set to '3461' by default (if this Web Orbiter is not your first then you should increment this value by one ie to '3462' - each Web Orbiter must have a unique 'Listen Port' number)<br />
#Now click the 'Save' button at the bottom of the screen to save the changes you have made.<br />
#Now do a 'Full Regen' from the 'Wizard - Orbiters' page (use the 'Full Regen' for the specific Web Orbiter you have created and not the overall 'Full Regen' button at the top of the page). Next when the Regen has completed do a "[[Quick reload router]]". Otherwise, the Web Orbiter won't work properly.<br />
<br />
==Device Screen Resolutions==<br />
If the 'Device' your planning to use your Web Orbiter on is a Desktop or Laptop then use the biggest resolution that will comfortably fit onto your screen. If your device is a touch screen device like an iPad, iPhone or iPod Touch then choose a resoltion that matches the overall resolution of the devices display; '''Do Not use 16:9'''<br />
<br />
===iPad===<br />
The iPad has a screen resolution of 1024x768 so if your creating an Orbiter for the iPad this is the resolution you should select for this Web Orbiter.<br />
<br />
===iPhone (pre iPhone 4) or iPod Touch===<br />
The iPhone/iPod Touch have a screen resolution of 480x320 so if your creating an Orbiter for either of these this is the resolution you should select for this Web Orbiter.<br />
<br />
===iPhone 4===<br />
The iPhone 4 has a screen resolution of 960x640 so if your creating an Orbiter for the iPhone 4 this is the resolution you should select for this Web Orbiter.<br />
<br />
===Google Nexus One or HTC Desire (Android)===<br />
If you have a Nexus One you will need to select a resolution of 480x800 (select N770 in the web admin, it is 480x800) so if your creating an Orbiter for the Nexus One this is the resolution you should select for this Web Orbiter.<br />
<br />
On the HTC Desire you might also have to go into the web browser settings and change the default zoom to "far away" (mine is danish, so don't know the exact english decription). After that it should be full screen.<br />
<br />
===Nokia 5800 XpressMusic===<br />
For a fullscreen orbiter, iPhone resolution 480x320 works quite well. For a screen that's full width (but requires some vertical scrolling), 640x480 (Standard TV) works well. This resolution allows for easier reading of some orbiter buttons, without the need for zooming in.<br />
<br />
===Nintendo DSi===<br />
Best screen resolution, 480x320 so far. Lower resolutions may work well also with "Mobile Phone Basic" skin applied.<br />
[[Image:Web_orbiter_dsi.jpg|center]]<br />
<br />
==Good skins for small screens==<br />
<br />
here we should list the skins that can be used on the smaller screens of Phones and alike.<br />
<br />
The skin "Mobile Phone Basic" is OK readable on the HTC Desire at 480x800.<br />
<br />
iPhone/iPod Touch - The "Basic" skin works well. The Titanium skins should also work ok although might be a little bit harder to make out text in file lists etc. "Mobile Phone Basic" isn't a good choice as it is missing a few buttons (eg. Random in the remote) as it was designed for devices with hardware buttons. Once you load up the web-orbiter on your iPhone the Safari 'menu' bars get in the way a bit. This can be overcome by hitting the '+' symbol on the bottom bar and adding an icon to your home screen. This will then open up with only the 'status' bar at the top.<br />
<br />
==Access to the Web Orbiter==<br />
<br />
===From within your home===<br />
You can access the Web Orbiter 2.0 from any of the following Web browsers (Google Chrome, Mozilla Firefox, Safari). Others may also work but have not been tested (your experiences with other web browsers would be welcome here) :<br />
<br />
<br />
'''For the 810 releases the correct URL is:'''<br />
''<nowiki>http://&lt;core_ip&gt;/lmce-admin/weborbiter.php</nowiki>''<br />
<br />
:* From within the "internal" LinuxMCE LAN, for example: <br />
::::''http://192.168.80.1/lmce-admin/weborbiter.php'' (0810)<br />
:::::(This assumes the IP address range set by default at installation.)<br />
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named "dcerouter" during the default installation, you could use:<br />
::::''<nowiki>http://dcerouter/pluto-admin/weborbiter.php</nowiki>''<br />
:*From the "external" WAN side of the Core, the core_ip would be the WAN IP address of the core (ie the one offered to the WAN side NIC on the Core by your broadband Router). If, for example, the core has a WAN side address of 192.168.0.50 offered up by your Broadband Router, use:<br />
:::: ''<nowiki>http://192.168.0.50/lmce-admin/weborbiter.php</nowiki>''<br />
<br />
:::::(Note: To use this method, [[Outside Access]] must be enabled.)<br />
<br />
===From the Internet===<br />
You could use the IP address:port for your home LAN, with port forwarding to the Core's LAN IP address (enabled by your home LAN router). <br />
*''This is an advanced topic and may not be secure in the current version.''<br />
<br />
By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home. You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security & Privacy Issues]].<br />
<br />
===Login page===<br />
*A simple login page should be displayed. Input an existing user name and password, then click "Login".<br />
*From the dropdown list of devices, choose the Web Orbiter you would like to use and click or touch 'Open'. If you have got several web orbiters in your system then they will be displayed in the dropdown and you can choose which one to use. (only one user can use any Web Orbiter at a given time)<br />
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]<br />
*Here is another UI1 variation loaded into Web Orbiter 2.0: [[Image:web_orbiter_20_in_chrome1.jpg|center]]<br />
*This image is of Web Orbiter 2.0 running on an iPod Touch: [[Image:Web orbiter on iPod Touch4.JPG|center]]<br />
<br />
===How do I save my login details?===<br />
<br />
NOTE: I have no idea how secure this is, if at all.<br />
:From a security standpoint, this is horribly insecure. Anyone with access to http://yourcore/weborbiter/login.html can see your uname/pass. [[User:KlfJoat|KlfJoat]] 16:39, 24 November 2010 (CET)<br />
<br />
On your core (or ssh into it, see "[[Logging In]]") we need to edit /var/www/lmce-admin/weborbiter/login.html. But first, let's make a backup...<br />
cp /var/www/lmce-admin/weborbiter/login.html /var/www/lmce-admin/weborbiter/loginbackup.html<br />
Should you need to, restore the original file using...<br />
cp /var/www/lmce-admin/weborbiter/loginbackup.html /var/www/lmce-admin/weborbiter/login.html<br />
Once you've made your backup and are ready to make the changes, open login.html in your favourite text editor...<br />
sudo nano /var/www/lmce-admin/weborbiter/login.html<br />
And look for the following line...<br />
<input id="username" type="text" name="username" value="" /></p><br />
Add your username to the "value" part, between the quotation marks...<br />
<input id="username" type="text" name="username" value="YourUsernameHere" /></p><br />
Then find this line...<br />
<input id="password" type="password" name="password" value="" /></p><br />
Add your password to the "value" part, between the quotation marks...<br />
<input id="password" type="password" name="password" value="YourPasswordHere" /></p><br />
Save, exit, and that should be it!<br />
<br />
==Where is the Web Orbiter code on my system?==<br />
<br />
===Look in the following directories on your Core===<br />
<br />
Look in;<br />
/var/www/lmce-admin/<br />
<br />
You will see the following Web Orbiter related files (there are many other unrelated files in this directory too);<br />
<br />
weborbiter_command.php<br />
weborbiter_image.php<br />
weborbiter.php<br />
<br />
Look in;<br />
/var/www/lmce-admin/weborbiter<br />
<br />
You should see the following files;<br />
<br />
IT.php <br />
jquery.min.js <br />
jquery.timers.js<br />
login.html<br />
waiting.gif<br />
weborbiter.css<br />
weborbiter.html<br />
weborbiter.js<br />
weborbiter_select.html<br />
<br />
==Devices that have been tested with Web orbiter 2.0==<br />
This is a simple list of devices that have been tested with Web Orbiter 2.0. If you have got a new device to add to this list then please add it below...or if you have some experiences with a device already listed then please add some simple notes here too.<br />
<br />
===Ipad===<br />
<br />
===iPod===<br />
<br />
===iPhone 3GS===<br />
<br />
===iPhone 4===<br />
<br />
===HTC Hero (Android 1.6)===<br />
<br />
I can confirm that the HTC Hero does work. I am using 2.1 firmware though (Sprint)<br />
<br />
===HTC Desire (Android 2.1)===<br />
Screen size is a little bit small I think, it is difficult to hit the up/down keys.<br />
<br />
For '''full screen''' orbiter - take a look above at "Device Screen Resolutions" for the right settings<br />
<br />
===AT&T Motorola Bravo (Android 2.1)===<br />
Screen resolution should be that of the Nokia 770. Need Root if you have AT&T as they lock down apps that are not secure.<br />
Runs well as '''Full Screen'''<br />
After Rooted, download com.linuxmce.apk, install using - adb install path/to/.apk file.<br />
Works Great!!<br />
<br />
===Nokia N800===<br />
<br />
===Nokia N900===<br />
<br />
===Nokia 5800 XpressMusic===<br />
Both "S60 Browser" (default) and "Opera Mobile" work well.<br />
<br />
===Nintendo DSi===<br />
<br />
===Eken M002===<br />
<br />
See M002 info here [[Eken_m002]]. See video of the M002 running Web Orbiter 2.0 here; [http://www.youtube.com/watch?v=eA0SaYYQb7E Eken m002]<br />
<br />
==Web Orbiter 2.0 has been tested on the following browsers==<br />
<br />
===Firefox 3.6===<br />
Works fine.<br />
<br />
===Chrome 6.0.453.1 dev===<br />
Works fine.<br />
<br />
Also works fine as a chrome application shortcut.<br />
Just create the shortcut when you are logged into the orbiter and have the right device chosen.<br />
<br />
===OperaMini===<br />
Works fine.<br />
<br />
===OperaMobile 10===<br />
Works fine.<br />
<br />
===Midori 0.2.2===<br />
Works fine.<br />
<br />
===Internet Explorer===<br />
Not working due to javascript issues.<br />
<br />
===S60 v5 Browser===<br />
Default Symbian browser - works fine (tested on Nokia 5800 XpressMusic)<br />
<br />
===Nintendo DSi Browser===<br />
(based on Opera)<br />
<br />
==Troubleshooting==<br />
===Connect failed===<br />
If you try to connect to the Web Orbiter and see this message:<br />
<code>"Connect to proxy orbiter failed, please try again"</code>, <br />
this means that Orbiter generation hasn't finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].<br />
<br />
Keywords: WebOrbiter</div>Brake16http://wiki.linuxmce.org/index.php?title=VistaICM&diff=25173VistaICM2010-09-28T01:50:19Z<p>Brake16: </p>
<hr />
<div>{{Versioninfo}}<br />
[[Category: Security]]<br />
== Overview ==<br />
<br />
The VistaICM is an alarm panel interface which will allow you to fully integrate panels supported by it with LinuxMCE. It allows both control of the security panel modes, and monitoring of the security panels zones. This means that any sensor connected to the security panel can be used to trigger events with any other device on your LinuxMCE system.<br />
<br />
'''Note:''' The VistaICM was discontinued [http://www.security.honeywell.com/hsc/products/wiring/ic/92291.html] by Honeywell in January of 2010. As of April 2010 no replacement has been announced.<br />
<br />
'''Note:''' Please add compatible panels to the security category as you find them.<br />
<br />
<br />
== Features ==<br />
<br />
* Full control over panel modes from LinuxMCE<br />
* LinuxMCE monitors panel mode changes from keypads and acts accordingly<br />
* Zone monitoring<br />
* Trigger events from zone sensors<br />
* Virtually everything that works when using LinuxMCE as your security panel is supported with this interface<br />
<br />
== Preparation ==<br />
<br />
You need to do a few things to prepare for your integration with LinuxMCE. The first thing you should to is to configure your alarm panel which the VistaICM is connected to for your LinuxMCE pincodes. You will need to refer to your security panel's installer manual for the detailed instructions. You can either set all of your LinuxMCE user's to use the same pincode or if your security panel supports it, you can create a user code for each of your LinuxMCE users.<br />
<br />
<br />
'''Note:''' To configure the pin code in LinuxMCE go to '''Wizard > Basic Info > Users > Change Pin.'''<br />
<br />
<br />
You will also want to have a list of your zones with descriptions and sensors connected to each zone prepared. This will make the process of configuring your sensors in LinuxMCE absolutely painless.<br />
<br />
<br />
== Installation ==<br />
<br />
The VistaICM is plug and play with the exception of the fact that you will need to manually configure your zones and sensors after the device has been detected and installed.<br />
<br />
<br />
To configure your sensors to to '''Wizard > Devices > Security'''<br />
Add a device for each sensor installed on your security panel. Make sure to set the Port/Channel Number of each sensor to the zone they are installed in. You also want to be sure to give each sensor a clear Description and assign it to the appropriate room.<br />
<br />
<br />
To configure your zones go to '''Wizard > Devices > Security > Security Zones'''<br />
Add a zone for each zone you have and assign the sensors attached to each zone to the zone you just created.<br />
<br />
<br />
The last part of the installation is to place the sensors on your floorplan.<br />
To do this go to '''Wizard > Devices > Floorplan Wizard''' then select your floorplan and be sure the dropdown is on Security Zone. Now just drag and drop the sensors where they are located on the floorplan.<br />
<br />
<br />
== Known Issues/Bugs ==<br />
<br />
'''FIXED:'''The VistaICM device thread crashes in LinuxMCE randomly, need to do more troubleshooting to finally nail this bug down once and for all.<br />
<br />
<br />
When the panel is set to Armed - Stay the VistaICM does not send zone trigger information. This is [http://forum.linuxmce.org/index.php?topic=10758.msg74010#msg74010| an odd bug in the implementation of the ICM itself. We were not able to find a workable solution for it.] <br />
<br />
<br />
When the security panel is in alarmed state LinuxMCE's mode and the panel's mode can become out of sync until disarmed/armed/disarmed again.</div>Brake16http://wiki.linuxmce.org/index.php?title=TV_tuner_card&diff=24967TV tuner card2010-08-31T17:34:27Z<p>Brake16: added Category: TV Cards and link to Capture Cards</p>
<hr />
<div>[[Category: Video| ]]<br />
[[Category: TV Cards ]]<br />
<br />
A '''TV tuner card''' allows television signals to be received by a computer. LinuxMCE systems featuring such cards can stream live TV to any [[media director]] in the home using [[MythTV]]. TV tuners are available as PCI-bus expansion card, PCIe (PCI Express) bus or USB devices.<br />
<br />
Please see also:<br />
*[[:Category:TV Cards|TV cards category]]<br />
*[http://www.mythtv.org/wiki/index.php/Category:Video_capture_cards MythTV tuner cards category]<br />
*[http://www.mythtv.org/wiki/index.php/Video_capture_card MythTV tuner cards article] This is a good place to start if you are wondering which cards are supported by MythTV, one of two PVR programs used by LinuxMCE. <br />
*[[Capture Cards|Capture Cards]] a listing and rating of LinuxMCE v8.10 compatible cards<br />
<br />
==Types of tuner card on the market==<br />
* Cards for analog TV. Cheaper models output raw tuner data, which requires intensive encoding by another device, normally the system CPU. More expensive models encode the signal to MPEG, relieving the main CPU of this load. This is called '''Hardware Encoding''' and is worth every penny. Many cards also have analog input (composite video or S-Video). and many also provide FM radio reception.<br />
<br />
* Cards for digital TV, including satellite TV. Digital TV is broadcast as an MPEG stream, so no encoder is necessary; instead, the digital cards must extract the correct PIDs from the transport stream, which requires much less processing power.<br />
<br />
* Hybrid tuners that handle both analog and digital inputs. A Hybrid tuner has one tuner that can be configured to act as an analog tuner or a digital tuner. Switching in between the systems is fairly easy, but can not be done "on the fly". The card operates as a digital tuner or an analog tuner until reconfigured.<br />
<br />
* Combo tuners that have both analog and digital tuners on one card. This is similar to a hybrid tuner, except there are 2 separate tuners on the card. One can watch analog while recording digital, or visa versa. The card operated as an analog tuner and a digital tuner. The advantages over 2 separate cards are cost and utilization of expansion slots in the computer. As the US converts from analog to digital broadcasts, these tuners are gaining popularity.</div>Brake16http://wiki.linuxmce.org/index.php?title=Honeywell_Vista-250BP/FBP&diff=22882Honeywell Vista-250BP/FBP2010-04-26T23:47:31Z<p>Brake16: /* This security panel is fully supported via the VistaICM from In2 Networks. */</p>
<hr />
<div>[[Category: Security]]<br />
<br />
== This security panel is fully supported via the VistaICM from In2 Networks. ==<br />
<br />
Setup instructions may be found on the [[Honeywell_Vista-20P]] page.<br />
<br />
'''Note:''' The VistaICM has been discontinued. As of April 2010, a replacement is not available. [http://wiki.linuxmce.org/index.php/VistaICM]</div>Brake16http://wiki.linuxmce.org/index.php?title=Honeywell_Vista-20P&diff=22881Honeywell Vista-20P2010-04-26T23:46:19Z<p>Brake16: /* This security panel is fully supported via the VistaICM from In2 Networks. */</p>
<hr />
<div>[[Category: Security]]<br />
<br />
== This security panel is fully supported via the VistaICM from In2 Networks. ==<br />
<br />
'''Note:''' The VistaICM has been discontinued. As of April 2010, a replacement is not available. [http://wiki.linuxmce.org/index.php/VistaICM]<br />
<br />
==Configuration with MCE Instructions==<br />
<br />
This instruction set assumes that the VistaICM module has been installed into security panel and is cabled into the MCE network. Also, it's critical that all zones and sensor information is documented as it's hooked up to your security panel. It's also critical that the user pin in MCE web admin matches the alarm code for that user.<br />
<br />
<br />
<br />
WebAdmin page setup:<br />
<br />
'''Panel Configuration'''<br />
<br />
1. Go to Wizard>Devices>Interfaces <br />
<br />
2. Click Add Device, then select the VistaICM2 template<br />
<br />
3. Put in your password for your alarm panel and the IP address of the panel (not necessary to add the MAC address) and click Update<br />
<br />
'''Sensor and Zone Configuration'''<br />
<br />
1. Go to Wizard>Devices>Security<br />
<br />
2. Click Add Device<br />
<br />
3. Add each Sensor device, on each sensor you add set the Port/Channel to the Zone number it is connected to on your security panel (other fields may be ignored). Put in a nice description while you're adding them and you can assign them to rooms if you want.<br />
<br />
4. Now scroll to the bottom and click on Security Zones<br />
<br />
5. Add a zone for each zone on your panel with a nice description of what is monitored in that zone, these zones will be used by LinuxMCE to notify you when a zone is faulted<br />
<br />
6. Pull the dropdown to add each of the sensors to the zone you created for them<br />
<br />
7. Perform a reload router and regen on all orbiter devices<br />
<br />
'''Test the system'''<br />
<br />
<br />
==Troubleshooting==<br />
<br />
Go to http://IPAddressofyourICM/setup<br />
<br />
Click Devices then you should see a Security node show up, click on that - Verify ECP1 is honeywell_vista and network is In2_Web<br />
<br />
Go ahead and put in the model of your security panel under the Device Name for ECP 1 and click next<br />
<br />
Go to Configure and click the Security node and verify the device address (I have it set to 18, default was 23 and I have 2 keypads in my home)<br />
<br />
Go ahead and click next and finish out<br />
<br />
Click advanced>diagnostics and then click the security node then startup select the PDA Web Page as the default web page and submit - make sure allow server control is set to yes and group is set to all groups while you're there.<br />
<br />
Test your pin via http://IPAddressofyourICM/ <--- verify it works here - 4 digit password then add a 1 to the end of it for disarming / 3 for armed stay</div>Brake16http://wiki.linuxmce.org/index.php?title=Honeywell_Vista-15P&diff=22880Honeywell Vista-15P2010-04-26T23:45:33Z<p>Brake16: /* This security panel is fully supported via the VistaICM from In2 Networks. */</p>
<hr />
<div>[[Category: Security]]<br />
<br />
== This security panel is fully supported via the VistaICM from In2 Networks. ==<br />
<br />
Setup instructions may be found on the [[Honeywell_Vista-20P]] page.<br />
<br />
'''Note:''' The VistaICM has been discontinued. As of April 2010, a replacement is not available. [http://wiki.linuxmce.org/index.php/VistaICM]</div>Brake16http://wiki.linuxmce.org/index.php?title=Honeywell_Vista-128BP/FBP&diff=22879Honeywell Vista-128BP/FBP2010-04-26T23:45:02Z<p>Brake16: /* This security panel is fully supported via the VistaICM from In2 Networks. */</p>
<hr />
<div>[[Category: Security]]<br />
<br />
== This security panel is fully supported via the VistaICM from In2 Networks. ==<br />
<br />
Setup instructions may be found on the [[Honeywell_Vista-20P]] page.<br />
<br />
'''Note:''' The VistaICM has been discontinued. As of April 2010, a replacement is not available. [http://wiki.linuxmce.org/index.php/VistaICM]</div>Brake16http://wiki.linuxmce.org/index.php?title=Honeywell_Vista-10P&diff=22878Honeywell Vista-10P2010-04-26T23:44:26Z<p>Brake16: /* This security panel is fully supported via the VistaICM from In2 Networks. */</p>
<hr />
<div>[[Category: Security]]<br />
<br />
== This security panel is fully supported via the VistaICM from In2 Networks. ==<br />
<br />
Setup instructions may be found on the [[Honeywell_Vista-20P]] page.<br />
<br />
'''Note:''' The VistaICM has been discontinued. As of April 2010, a replacement is not available. [http://wiki.linuxmce.org/index.php/VistaICM]</div>Brake16http://wiki.linuxmce.org/index.php?title=ADT_Safewatch_Pro_3000&diff=22877ADT Safewatch Pro 30002010-04-26T23:42:10Z<p>Brake16: </p>
<hr />
<div>[[Category: Security]]<br />
[[Category: Works without caveats on 0710]]<br />
[[Category: Works without caveats on 0810]]<br />
<br />
== This security panel is fully supported via the VistaICM from In2 Networks. ==<br />
<br />
'''Note:''' The VistaICM has been discontinued. As of April 2010, a replacement is not available. [http://wiki.linuxmce.org/index.php/VistaICM]</div>Brake16http://wiki.linuxmce.org/index.php?title=First_Alert_FA168C-GP&diff=22876First Alert FA168C-GP2010-04-26T23:06:37Z<p>Brake16: </p>
<hr />
<div>[[Category: Security]]<br />
<br />
== This security panel is fully supported via the VistaICM from In2 Networks. ==<br />
<br />
'''Note:''' The VistaICM has been discontinued. No replacement is available as of April 2010. [http://wiki.linuxmce.org/index.php/VistaICM]</div>Brake16http://wiki.linuxmce.org/index.php?title=VistaICM&diff=22875VistaICM2010-04-26T23:00:20Z<p>Brake16: updated to reflect that it's no longer available</p>
<hr />
<div>[[Category: Security]]<br />
<br />
= VistaICM =<br />
<br />
<br />
== Overview ==<br />
<br />
The VistaICM is an alarm panel interface which will allow you to fully integrate panels supported by it with LinuxMCE. It allows both control of the security panel modes, and monitoring of the security panels zones. This means that any sensor connected to the security panel can be used to trigger events with any other device on your LinuxMCE system.<br />
<br />
'''Note:''' The VistaICM was discontinued [http://www.security.honeywell.com/hsc/products/wiring/ic/92291.html] by Honeywell in January of 2010. As of April 2010 no replacement has been announced.<br />
<br />
'''Note:''' Please add compatible panels to the security category as you find them.<br />
<br />
<br />
== Features ==<br />
<br />
* Full control over panel modes from LinuxMCE<br />
* LinuxMCE monitors panel mode changes from keypads and acts accordingly<br />
* Zone monitoring<br />
* Trigger events from zone sensors<br />
* Virtually everything that works when using LinuxMCE as your security panel is supported with this interface<br />
<br />
== Preparation ==<br />
<br />
You need to do a few things to prepare for your integration with LinuxMCE. The first thing you should to is to configure your alarm panel which the VistaICM is connected to for your LinuxMCE pincodes. You will need to refer to your security panel's installer manual for the detailed instructions. You can either set all of your LinuxMCE user's to use the same pincode or if your security panel supports it, you can create a user code for each of your LinuxMCE users.<br />
<br />
<br />
'''Note:''' To configure the pin code in LinuxMCE go to '''Wizard > Basic Info > Users > Change Pin.'''<br />
<br />
<br />
You will also want to have a list of your zones with descriptions and sensors connected to each zone prepared. This will make the process of configuring your sensors in LinuxMCE absolutely painless.<br />
<br />
<br />
== Installation ==<br />
<br />
The VistaICM is plug and play with the exception of the fact that you will need to manually configure your zones and sensors after the device has been detected and installed.<br />
<br />
<br />
To configure your sensors to to '''Wizard > Devices > Security'''<br />
Add a device for each sensor installed on your security panel. Make sure to set the Port/Channel Number of each sensor to the zone they are installed in. You also want to be sure to give each sensor a clear Description and assign it to the appropriate room.<br />
<br />
<br />
To configure your zones go to '''Wizard > Devices > Security > Security Zones'''<br />
Add a zone for each zone you have and assign the sensors attached to each zone to the zone you just created.<br />
<br />
<br />
The last part of the installation is to place the sensors on your floorplan.<br />
To do this go to '''Wizard > Devices > Floorplan Wizard''' then select your floorplan and be sure the dropdown is on Security Zone. Now just drag and drop the sensors where they are located on the floorplan.<br />
<br />
<br />
== Known Issues/Bugs ==<br />
<br />
'''FIXED:'''The VistaICM device thread crashes in LinuxMCE randomly, need to do more troubleshooting to finally nail this bug down once and for all.<br />
<br />
<br />
When the panel is set to Armed - Stay the VistaICM does not send zone trigger information. I emailed In2 Networks about this and received a canned response that seems to indicate it could be a setting in the configuration of my security panel. If anyone has any idea please let me know.<br />
<br />
<br />
When the security panel is in alarmed state LinuxMCE's mode and the panel's mode can become out of sync until disarmed/armed/disarmed again.</div>Brake16http://wiki.linuxmce.org/index.php?title=Insteon&diff=22140Insteon2010-01-18T16:48:12Z<p>Brake16: </p>
<hr />
<div>[[Category: Power Line Control]]<br />
[[Category: Automation]]<br />
<br />
Insteon is the product name for a series of devices which communicate using either powerline signaling, RF signaling, or a combination of both. LinuxMCE support for Insteon devices is currently under development. More information on the Insteon devices can be found at [http://www.insteon.com Insteon]. Products are available at [http://www.smarthome.com SmartHome]<br />
<br />
Insteon development is currently underway.<br />
<br />
There are currently 3 types of Insteon controllers:<br />
<br />
1. PowerLinc Controller USB (PLC)<br /><br />
[[Image:2414u.jpg]]<br /><br />
2. PowerLinc Controller Serial (PLC)<br /><br />
[[Image:2414s.jpg]]<br /><br />
3. PowerLinc Modem (PLM)<br /><br />
[[Image:2414s.jpg]]<br /><br />
<br />
'''Please Note:''' The PowerLinc Controller Serial and PowerLinc Modem are using the same picture, however they are NOT the same device. They have different part numbers. The PLM is 2412s, the PLC is 2414s.<br />
<br />
Among these controllers, there is another device called the EZBridge that uses a PLM to interface ethernet to insteon.<br />
Communication to the EZBridge is accomplished via an XML commandset over an established IP Port.<br />
I have implemented the EZBridge via GSD/Ruby. Source is currently located in the developers forum. (search for EZBridge)<br />
[[Image:31272.jpg]]<br />
<br />
The EZBridge is IDEAL for remote locations, summer houses, etc. All communication is via a TCP Socket in xml form.<br />
<br />
It is feasable to actually have MORE THAN ONE location set up in your linuxmce system. With the use of an EZBridge, it's just like being there. Lights/Appliances can be turned on/off as if they were local.<br />
<br />
<br />
1. What is an INSTEON network?<br />
The INSTEON network protocol is a new cost-effective dual-mesh (radio frequency - RF and powerline) home management network technology, that provides a secure, highly-available, affordable, robust home management network for home innovations. INSTEON technology is simple to integrate and will be widely available in a broad set of products offered by SmarthomeTM, Inc. and many other product innovators.<br />
<br />
2. Is INSTEON a secure network?<br />
Yes. Every INSTEON device has a unique 24 bit address, all transmissions are encoded onto the network. Additionally, INSTEON is designed to support additional device based encryption technologies.<br />
<br />
3. What is a mesh network and how does it work?<br />
The INSTEON network is an integrated (RF, Powerline) redundant, non-supervised, peer-to-peer network. There is no need for routing tables, each device in the network receives messages simultaneously, independent of whether the message originated via a wireless or powerline device. Network devices will "repeat" the signal based on message settings.<br />
<br />
4. When will products with INSTEON technology be available?<br />
The first INSTEON products launched the second quarter of 2005. Currently, INSTEON-compatible devices are available from over 15 manufacturers with approximately 50 products available to date.<br />
<br />
5. How much will INSTEON-compatible devices cost?<br />
Devices will start at $19.99 retail. INSTEON is a very cost-effective technology to integrate into a wide range of products.<br />
<br />
6. How many partners are developing INSTEON products?<br />
SmartLabs is in the process of working with a wide variety of business partners. INSTEON technology is easy to integrate and is priced to be able to include in a broad base of products, from simple inexpensive wireless sensors to large home appliances. To find out more regarding Smarthome's Smart partner program call 866-243-8022. Many of the partners are listed in the partner section of this website.<br />
<br />
7. How does INSTEON compare with ZigBeeTM, BluetoothTM, HomePlugTM, X-10TM?<br />
<br />
* Bluetooth - Bluetooth is designed as an ad-hoc network technology and as such is not designed to be a home control networking technology.<br />
* ZigBee/Z-Wave - INSTEON is not limited to a single physical network technology and does not require a network controller. It supports both RF and Powerline, enabling a broader set of applications. INSTEON technology is also a more cost-effective and reliable technology allowing it to be integrated into a broader range of products.<br />
* HomePlug - INSTEON is compatible with HomePlug but focused on different applications. HomePlug is tuned to broadband applications while INSTEON is focused on home control. INSTEON is a more cost-effective technology for home management.<br />
* X-10 - INSTEON is a more robust and reliable network yet, it is priced similarly and is compatible with industry standard X-10 devices.<br />
<br />
8. If a home has a broadband network, why do I need INSTEON?<br />
Homes will have two networks (Multimedia and Management). The broadband network is focused on a home's multimedia needs and is ideal for sending voice, video and internet throughout the home. The management network (INSTEON) is focused on sending control and simple data between devices within the home (i.e. a light switch turning on multiple lights/devices within the home). While the broadband network could also serve the management needs, on a device basis it is too expensive. Additionally, customers are not willing to plug their washer, microwave or garage door into an Ethernet cable.<br />
<br />
9. Does INSTEON work with other home network technologies?<br />
Yes, INSTEON will be introduced with an Ethernet, USB and serial bridge to allow communications with the Internet, computers and wide variety of security and wiring panels. Additionally, INSTEON supports communications with existing X-10 based devices. Smarthome expects development of additional bridges to other network technologies based on market demand.<br />
<br />
10. Should I continue to purchase X-10 based products or wait for INSTEON?<br />
One of the significant advantages of the new INSTEON technology is it's backwards compatibility with existing X-10 products. As an example, an INSTEON switch can turn on an X-10 lamp module and an X-10 switch can turn on an INSTEON lamp module. Homeowners can continue to purchase X-10 devices today and then migrate over time to INSTEON.<br />
<br />
11. Can the INSTEON technology handle high-bandwidth for application such as A/V distribution?<br />
The protocol is designed to handle simple data, up to 16 bytes per message @ up to 10 messages a second. INSTEON will not support higher-bandwidth application. These applications are best suited for standard Ethernet. Higher band-width support results in higher overall cost. INSTEON is optimized for affordable, reliable, and secure control.<br />
<br />
12. What applications are a good fit for the INSTEON technology?<br />
<br />
* Scene and remote control lighting<br />
* Security alarm interfaces and sensors<br />
* Home sensors (e.g. water, humidity, temperature)<br />
* Access control (e.g. door locks)<br />
* Heating and cooling (HVAC) control and management<br />
* Audio-video control<br />
* Appliance management<br />
* Energy savings<br />
<br />
13. Does INSTEON support other voltages, such as 50Hz/220VAC?<br />
Although Smarthome has not yet designed devices for voltages other than 110VAC/60Hz, the INSTEON technology could be adjusted for 50Hz timing. We do not have a schedule as yet for doing this effort.<br />
<br />
14. What platforms (i.e. Windows, Mac, Linux) are supported by the INSTEON protocol?<br />
Supported platforms depend on the interface used to communicate with the INSTEON network. Smarthome's PowerLinc (USB and Serial) and Powerline Modem (Serial) support any platform that can communicate with either a serial or USB port. Additionally, we have partners that have developed and are selling IP interfaces.<br />
<br />
15. What devices do not repeat INSTEON signals?<br />
To conserve power, message repeating can be disabled in devices, such as battery operated devices.<br />
<br />
16. How is INSTEON support implemented into products?<br />
Smarthome offer's Developer Kits which interface with products to allow communications between the product and the INSTEON network. The interface can be an internal INSTEON chip, a small PC board or an external plug-in adapter with I/O ports connecting to the host product(s).<br />
<br />
17. How likely is RF interference?<br />
Very unlikely. In the few situations we've encountered interference with other wireless devices, simply changing the frequency (commonly referred to as "Channels") on the offending device will solve any issues. INSTEON messages are very brief, leaving only a small amount of time for interference to occur.<br />
<br />
18. Is every INSTEON compatible device required to be X10 compatible?<br />
X10 compatibility is determined by the product manufacture/vendor. The INSTEON protocol does not mandate X10 compatibility. SmartLab's INSTEON compatible devices are made to support X10.<br />
<br />
19. Will I be able to sell the product(s) I develop with the developer's kit?<br />
Yes, you will be able to sell your software product(s) developed from the INSTEON developers kit. Prior to offering for sale, you must submit the product to Smarthome for INSTEON compatibility testing and INSTEON certification. This is a free service that Smarthome provides to insure the software complies with proper INSTEON protocols. Once you are at a stage where the product can be tested, contact us.<br />
<br />
20. How do I sell my software or hardware I created using the developer's kits?<br />
Once the product passes compatibility testing, you sell the software and/or hardware through any distribution channels. Additionally, the product may also be submitted to Smarthome category managers for consideration to distribute through Smarthome web and catalog channels.<br />
<br />
[[Setting Up PLM Template]]<br />
<br />
Images used are Copyright 1995-2008 [http://www.smarthome.com SMARTHOME]</div>Brake16http://wiki.linuxmce.org/index.php?title=LinuxMCE-0810_alpha2&diff=19587LinuxMCE-0810 alpha22009-07-03T14:44:19Z<p>Brake16: Included update & upgrade commands in the command box</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
<br />
==Installation==<br />
# Install Kubuntu Intrepid, update it and enable the restricted (video) drivers if needed. (download Kubuntu 8.10 '''desktop''' release from one of these: [http://mirrors.ccs.neu.edu/releases.ubuntu.com/kubuntu/8.10/ Northeastern University Mirror, USA], [http://swtsrv.informatik.uni-mannheim.de/pub/linux/distributions/ubuntu-release/kubuntu/8.10/ Mannheim University Mirror, Germany]) '''Currently, only the 32bit version of LinuxMCE is available. Only download the i386 version of 8.10 Kubuntu, even if your system can support 64bit versions.'''<br />
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.<br />
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu here], unpack them and change into the freshly created ''new-installer'' directory.<br />
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.<br />
# Reboot, wait for the activity to stop (see progress on console 8).<br />
<br />
In other words, after installing Kubuntu:<br />
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.<br />
aptitude update<br />
aptitude dist-upgrade<br />
wget -c http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz<br />
tar xvf new-installer-alpha-latest.tar.gz<br />
cd new-installer<br />
./pre-install-from-repo.sh<br />
./mce-install.sh<br />
./post-install.sh<br />
reboot<br />
=== nVidia Restricted Driver ===<br />
<strike>Install the nVidia restricted driver (177) from KDE using the Hardware Manager ''before'' installing LinuxMCE 0810 Alpha for the best results</strike> The installer will now automatically choose and install the correct restricted driver during setup.<br />
<br />
=== MythTV ===<br />
<strike>Remove reference to hardy in /etc/apt/sources.list<br />
<br />
from terminal<br />
<pre><br />
sudo apt-get install pluto-mythtv-player<br />
</pre><br />
<br />
Install updated version of pluto-mythtv-plugin</strike><br />
<br />
=== Setup Diskless MD ===<br />
<strike>Follow the steps from [[LinuxMCE-0810_alpha1#Setup_Diskless_MD|alpha1]].</strike><br />
<br />
=== Upgrading kernel ===<br />
<strike>There are issues with the ''fglrx'' driver that are documented in Ubuntu's bug tracking system. If you're experiencing those issues, upgrade the kernel to ''2.6.27-13'' or better. [[Upgrading the Kernel]] has been updated with instructions on doing this.</strike> The latest official kernel is -14<br />
<br />
== Updates ==<br />
Check if there is no junk like references to hardy in /etc/apt/sources.list then:<br />
sudo apt-get update<br />
sudo apt-get dist-upgrade<br />
Or use a package manager on the KDE desktop for more convenience.<br />
<br />
=== 20090218 (alpha-2.1) ===<br />
*lmce-datalog-db_2.0.0.44.0902180810<br />
*lmce-datalogger-plugin_2.0.0.44.0902180810<br />
*lmce-enocean-tcm120_2.0.0.44.0902180810<br />
*lmce-src-datalogger-plugin_2.0.0.44.0902180810<br />
*lmce-src-enocean-tcm120_2.0.0.44.0902180810<br />
*lmce-src-lmce-datalog_2.0.0.44.0902180810<br />
*pluto-dcerouter_2.0.0.44.0902180810<br />
*pluto-dhcpd-plugin_2.0.0.44.0902180810<br />
*pluto-hald-src_2.0.0.44.0902180810<br />
*pluto-hald_2.0.0.44.0902180810<br />
*pluto-mythtv-plugin_2.0.0.44.0902180810<br />
*pluto-orbitergen_2.0.0.44.0902180810<br />
*pluto-src-dcerouter_2.0.0.44.0902180810<br />
*pluto-src-hal-device-finder_2.0.0.44.0902180810<br />
*pluto-src-mythtv-plugin_2.0.0.44.0902180810<br />
*pluto-src-orbitergen_2.0.0.44.0902180810<br />
*pluto-src-updatemedia_2.0.0.44.0902180810<br />
*pluto-updateentarea_2.0.0.44.0902180810<br />
*pluto-updatemedia_2.0.0.44.0902180810<br />
*pluto-zwave-lighting_2.0.0.44.0902180810<br />
*lmce-game-player_2.0.0.44.0902180810<br />
*lmce-game-plugin_2.0.0.44.0902180810<br />
*lmce-src-game-player_2.0.0.44.0902180810<br />
*lmce-src-game-plugin_2.0.0.44.0902180810<br />
<br />
==== 20090222 (alpha-2.1.1) ====<br />
*pluto-dcerouter_2.0.0.44.0902220810<br />
*pluto-bluetooth-dongle_2.0.0.44.0902220810<br />
<br />
=== 20090301 (alpha-2.2) ===<br />
SVN revision: 21746<br />
<br />
To avoid a known problem when upgrading pluto-storage-devices, forcefully remove it before upgrading and let apt fix it:<br />
dpkg -r --force-all pluto-storage-devices<br />
apt-get update<br />
apt-get install -f<br />
Also please note that installing the upgrade of pluto-system-database will OVERWRITE your existing pluto_main database. It is therefore advisable to make a backup first!<br />
mysqldump --skip-extended-insert pluto_main >pluto_main_$PK_Installation-`date '+%Y%m%d:%H%M%S'`.sql<br />
*pluto-boot-scripts_2.0.0.44.0903010810<br />
*pluto-network-storage_2.0.0.44.0903010810<br />
*pluto-skins-basic_2.0.0.44.0903010810<br />
*pluto-src-network-storage_2.0.0.44.0903010810<br />
*pluto-src-std-plugins_2.0.0.44.0903010810<br />
*pluto-src-updatemedia_2.0.0.44.0903010810<br />
*pluto-std-plugins_2.0.0.44.0903010810<br />
*pluto-storage-devices_2.0.0.44.0903010810<br />
*pluto-system-database_2.0.0.44.0903010810 <br />
*pluto-updatemedia_2.0.0.44.0903010810<br />
*pluto-website-admin_2.0.0.44.0903010810<br />
<br />
=== 20090308 (alpha-2.3) ===<br />
SVN revision: 21765<br />
<br />
Again it is wise to backup your database as there is a new pluto-system-database package, but this one will not overwrite your pluto_main database if it is already installed, it should do an sqlCVS update instead. <br />
Also remove the pluto-storage-devices, hopefully for the last time. <br />
See the previous upgrade [[LinuxMCE-0810_alpha2#20090301_.28alpha-2.2.29|above]] for details on how to do these things. <br />
<br />
*pluto-asterisk_2.0.0.44.0903080810<br />
*pluto-src-asterisk_2.0.0.44.0903080810<br />
*pluto-src-text-to-speech_2.0.0.44.0903080810<br />
*pluto-src-updatemedia_2.0.0.44.0903080810<br />
*pluto-storage-devices_2.0.0.44.0903080810<br />
*pluto-system-database_2.0.0.44.0903080810<br />
*pluto-text-to-speech_2.0.0.44.0903080810<br />
*pluto-updatemedia_2.0.0.44.0903080810<br />
*pluto-website-admin_2.0.0.44.0903080810<br />
<br />
=== 20090315 (alpha-2.4) ===<br />
SVN revision: 21798<br />
<br />
The web admin is being moved from pluto-admin to lmce-admin with this build. A redirect has been placed in pluto-admin to redirect to the new web admin URL to help smooth the transition. While every attempt has been made to make this a smooth transition, please be sure to file a trac ticket if you find bugs related to this move so I can get them taken care of - [[User:jondecker76|jondecker76]]<br />
<br />
<br />
The Asterisk IVR is broken in this release. For those that need to get it working/wish to try out new changes, do the following:<br />
sudo apt-get install libsox-fmt-all <br />
cd /usr/pluto/bin<br />
sudo rm generate_users_voicemenu.pl<br />
sudo wget http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-0810/src/Asterisk/generate_users_voicemenu.pl?format=raw<br />
sudo chmod 755 generate_users_voicemenu.pl<br />
sudo ./generate_users_voicemenu.pl<br />
Be sure to have the default voice set up in the Text_To_Speech device's device data (its default is the ugly one we're already used to)! I also highly recommend following the instructions located at [http://wiki.linuxmce.org/index.php/Text_To_Speech http://wiki.linuxmce.org/index.php/Text_To_Speech] on how to install some better voices, and set the default voice to voice_nitech_us_slt_arctic_hts after you install the better voices (this is the best free voice available ATM). This should all work on next weeks build for those that can wait.. I'm still working on getting the better voices included by default, but need to check on licensing issues first.<br />
<br />
<br />
<br />
*pluto-asterisk_2.0.0.44.0903150810<br />
*pluto-boot-scripts_2.0.0.44.0903150810<br />
*pluto-makerelease_2.0.0.44.0903150810<br />
*pluto-newmdinteractor_2.0.0.44.0903150810<br />
*pluto-orbitergen_2.0.0.44.0903150810<br />
*pluto-proxy-orbiter_2.0.0.44.0903150810<br />
*pluto-src-asterisk_2.0.0.44.0903150810<br />
*pluto-src-makerelease_2.0.0.44.0903150810<br />
*pluto-src-newmdinteractor_2.0.0.44.0903150810<br />
*pluto-src-orbitergen_2.0.0.44.0903150810<br />
*pluto-src-proxy-orbiter_2.0.0.44.0903150810<br />
*pluto-src-std-plugins_2.0.0.44.0903150810<br />
*pluto-src-text-to-speech_2.0.0.44.0903150810<br />
*pluto-std-plugins_2.0.0.44.0903150810<br />
*pluto-system-database_2.0.0.44.0903150810<br />
*pluto-text-to-speech_2.0.0.44.0903150810<br />
*pluto-updateentarea_2.0.0.44.0903150810<br />
*pluto-website-admin_2.0.0.44.0903150810<br />
<br />
=== 20090322 (alpha-2.5) ===<br />
SVN revision: 21827<br />
<br />
*freepbx_0+2.3.1-2<br />
*pluto-asterisk_2.0.0.44.0903220810<br />
*pluto-dhcpd-plugin_2.0.0.44.0903220810<br />
*pluto-install-scripts_2.0.0.44.0903220810<br />
*pluto-raid-tools_2.0.0.44.0903220810<br />
*pluto-skins-basic_2.0.0.44.0903220810<br />
*pluto-src-asterisk_2.0.0.44.0903220810<br />
*pluto-website-admin_2.0.0.44.0903220810<br />
<br />
=== 20090401 (alpha-2.6) ===<br />
Note: This build will attempt to use Launch Manager to co-ordinate startup and shutdown of devices. While it is not 100% finished, it is working and stable. Please test it out and file any problems against trac ticket #48. Also, please note the following:<br />
I'm not sure on this, but you may have to manually install LM via apt-get<br />
After you upgrade, reboot your core <br />
CLI output of LM can be viewed on tty8 on the core, and tty1 on MD's (alt+ctrl+F8 and alt+ctrl+F1 respectively). You will have to manually switch back to the orbiter on tty7 when finished<br />
CLI output is not yet completely finished, so the top fields will be blank (this is normal for now)<br />
CLI output of the log messages is working however, so please take a peek at them on tty8/tty1 shortly after you hear the 2nd set of beeps on boot up (when the "x" cursor appears on the screen).<br />
You can further test out LM by switching to tty8/tty1 right after doing a router reload and watching the output and comparing it to what you would expect it to be.<br />
LM dos not yet track regen process and report the % done. This should be working in next week's build, however.<br />
If there are problems and/or you wish to restore previous functionality, the original /usr/pluto/bin/startCore.sh file can be restored from the backup /usr/pluto/bin/startCore.sh._backup, and the LM package removed<br />
LM is not yet properly daemonized. I'm saving this step for last after the socket layer is implemented and we get a client coded.<br />
'''Note:''' All orbiters will likely do a FULL REGEN after this update, and it may appear that your system is hanging because of this. Please give it some time to finish the regen (could take up to an hour on large installs)<br />
<br />
* lmcevdr_1.1-10_all.deb<br />
* pluto-website-admin_2.0.0.44.0904010019_i386.deb<br />
* pluto-dynamic-dns_2.0.0.44.0904010019_i386.deb<br />
* lmce-launch-manager_2.0.0.44.0904010019_i386.deb<br />
* pluto-boot-scripts_2.0.0.44.0904010019_i386.deb<br />
* pluto-system-database_2.0.0.44.0904010019_i386.deb<br />
* pluto-orbitergen_2.0.0.44.0904010019_i386.deb<br />
* pluto-updateentarea_2.0.0.44.0904010019_i386.deb<br />
* pluto-orbiter_2.0.0.44.0904010019_i386.deb<br />
<br />
=== 20090405 (alpha 2.7) ===<br />
From now on, the SVN version will part of the deb name.<br />
You may need to uninstall 'lmcevdr' (dpkg -r --force-all lmcevdr) and reinstall it (apt-get install lmcevdr) to get around the install-script bug in last weeks .deb package. It worked for me. <br />
* lmce-game-player_2.0.0.44.090405.21873_i386.deb<br />
* lmce-game-plugin_2.0.0.44.090405.21873_i386.deb<br />
* lmce-launch-manager_2.0.0.44.090405.21873_i386.deb<br />
* lmce-phoenix-solo-usb_2.0.0.44.090405.21873_i386.deb<br />
* lmcevdr_1.1-10_all.deb (This is no main package, and therefore does not contain the regular version designation. It is based upon version 21875)<br />
* pluto-bluetooth-dongle_2.0.0.44.090405.21873_i386.deb<br />
* pluto-simplephone_2.0.0.44.090405.21873_i386.deb<br />
* pluto-system-database_2.0.0.44.090405.21873_i386.deb<br />
* pluto-website-admin_2.0.0.44.09040521873_i386.deb<br />
<br />
=== 20090412 (alpha 2.8) ===<br />
* pluto-text-to-speech_2.0.0.44.09041221886_i386.deb (283,284) - Finally, good voices will actually install (Nitech HTS Arctic). <br />
* pluto-system-database_2.0.0.44.09041221886_i386.deb (211) - New default voice is voice_nitech_us_slt_arctic_hts. - game plugin and player template cleanups<br />
* mce-diskless-tools_2.0.0.44.09041221886_i386.deb (627,628) - Update kernel image for diskless MDs upon regenning.<br />
* pluto-website-admin_2.0.0.44.09041221886_i386.deb (220) - Infrared codes will now properly come from schema.linuxmce.org<br />
* pluto-boot-scripts_2.0.0.44.09041221886_i386.deb (234)- also schema.linuxmce.org IR codes related.<br />
* pluto-motion-wrapper_2.0.0.44.09041221886_i386.deb (455,456) - changed config variable from ffmpeg_filename to movie_filename<br />
* lmce_launch_manager_2.0.0.44.09041221886_i386.deb (298,299) - LM Actions now work from CLI(such as reload, regen, reboot, etc...)<br />
* lmce-game-player_2.0.0.44.09041221886_i386.deb (673,674) - Rebuilt for new device template<br />
* lmce-game-plugin_2.0.0.44.09041221886_i386.deb (671,672) - Rebuilt for new device template<br />
* pluto-updateentarea_2.0.0.44.09041221886_i386.deb (341,342) - may need to be rebuilt for device template changes<br />
<br />
=== 20090413 (alpha 2.9 jondecker special) ===<br />
* pluto-text-to-speech_2.0.0.44.09041321887_i386.deb (283,284) - fixes stupid post-install typo<br />
* pluto-zwave-lighting_2.0.0.44.09041321891_i386.deb (505,506) - thermostate support<br />
<br />
=== 20090419 (alpha 2.10 pbr) ===<br />
* pluto-text-to-speech_2.0.0.44.09041921897_i386.deb<br />
* pluto-website-admin_2.0.0.44.09041921897_i386.deb<br />
* lmce-screen-capture-camera_2.0.0.44.09041921897_i386.deb<br />
* pluto-system-database_2.0.0.44.09041921897_i386.deb<br />
* lmce-game-plugin_2.0.0.44.09041921897_i386.deb<br />
* lmce-game-player_2.0.0.44.09041921897_i386.deb<br />
* pluto-asterisk_2.0.0.44.09041921897_i386.deb<br />
<br />
=== 20090426 (alpha 2.11) ===<br />
With this release, MythTV now takes advantage of storage groups. Do some recordings, and try recording to a few different storage groups. <br />
Please test this out and report any problems such as duplicate attributes appearing in pluto_media, icon image not showing up, recordings failing to record, etc. Also, if you do have problems, try a reboot and see if it fixes the problem, then please let me know if the reboot fixed your problem. - jondecker76<br />
<br />
'''POST-BUILD UPDATE:''' A couple of small bugs have been found that will be fixed in next week's build. 1) Some storage groups are missing the leading "/" in the path, causing problems images in mythweb, downloads in the mythweb, etc. 2) Unmounted storage devices were being skipped. This means that you may not have a storage group for some of your devices at some times. I am changing this so that the storage groups are created, and if for some reason it is not available when a recording is set to use the storage group, then the recording will go to the (always present) Default storage group.<br />
For those wanting to fix #1 right now, just edit /usr/pluto/bin/StorageDevices_PlutoDirStructure.sh and add a preceeding slash before the path beginning with 'home/....' on lines 214 and 226. After this modification, MythTV works great in all of the storage groups! (You should do a reboot after making the change)<br />
<br />
* lmcevdr_1.1-10_all.deb - more setup fixes, this time for the MD<br />
* pluto-boot-scripts_2.0.0.44.09042621919_i386.deb (234) - small fix to get rid of a warning on DCERouter startup re missing dir., New MythTV directory structure stuff<br />
* pluto-asterisk_2.0.0.44.09042621919_i386.deb (270,271) - Added Support for Cisco 7910 phone<br />
* pluto-dhcpd-plugin_2.0.0.44.09042621919_i386.deb (302) - Added support for Cisco 7910 phone<br />
* pluto-system-database_2.0.0.44.09042621919_i386.deb (211) - '''If new devices are added, the pluto-system-database needs to be updates as well'''<br />
* pluto-storage-devices_2.0.0.44.09042621919_i386.deb (533) - Adds new tv_shows_* directories. Generates MythTV storage groups<br />
* pluto-std-plugins_2.0.0.44.09042621919_i386.deb (134,153) - adds some useful debugging snippets that helped trace down the problem of mythtv attributes not adding to pluto_media<br />
* pluto-mythtv-plugin_2.0.0.44.09042621919_i386.deb (134,153) - lots of changes to facilitate the new storage groups<br />
* pluto-network-storage_2.0.0.44.09042621919_i386.deb (503,508) - small changes to work with new tv_shows_* directories<br />
<br />
=== 20090429 (alpha 2.12) ===<br />
* pluto-storage-devices_2.0.0.44.09042921929_i386.deb (533) - Fixes some small bugs in MythTV storage groups<br />
* pluto-boot-scripts_2.0.0.44.09042921929_i386.deb (234) - misc. MythTV storage group enhancements<br />
* pluto-mythtv-plugin_2.0.0.44.09042921929_i386.deb (134,153) - misc. MythTV storage group enhancement<br />
* mce-diskless-tools_2.0.0.44.09042921929_i386.changes (627,628) - lots of fixes for MD boot- Changes effect new installs only<br />
* pluto-system-database_2.0.0.44.09042921929_i386.deb (211) - Fixes hardy issue in sources.list<br />
* pluto-nvidia-video-drivers_2.0.0.44.09042921929_i386.deb (490) - changed the package requirement to nvidia-glx-180 for intrepid<br />
<br />
=== 20090501 (alpha 2.13) ===<br />
There are a few more MythTV storage group changes in this build. Please understand that the storage group name changes may throw mythweb out of whack on some old recordings, but this should be minimal. The old "user_*/<storage_device>" naming scheme is replaced with a "<username>:<storage_device>" naming convention. This will appeal to many more users than the user_* convention. Also, there is now support for custom storage groups. You can make your own storage groups now on top of the auto-generated LMCE ones by prepending with "custom:" (for example, you may make a new storage group named "custom:MyDrive", and it will not be removed or overwritten by the scripts that generate the storage groups). One last change is in the "Default" storage group - it no longer points to the drive with most space. This was changed because eventually it would throw mythweb for a loop once the paths changed. I will look into a better way to defaultly record to the drive with most space, most likely using recording profiles.<br />
<br />
* lmce-launch-manager (298,299) - db wrapper fix to handle empty resultsets<br />
* pluto-bluetooth-dongle (124,143) - fix some connection issues in JavaMO<br />
* pluto-mythtv-plugin (134,153)<br />
* pluto-storage-devices (533)<br />
* pluto-boot-scripts (234) - MD fixes<br />
* mce-diskless-tools (391) - MD fixes<br />
* pluto-install-scripts (627,628) - MD fixes<br />
* pluto-x-scripts (520,523) - AV Wizard fix for MD<br />
* pluto-zwave-lighting (505,506) - Init speedup<br />
<br />
=== 20090503 (alpha2.14) ===<br />
* pluto-zwave-lighting_2.0.0.44.09050321942_i386.deb (505,506) - boolean fixes<br />
<br />
=== 20090505 (alpha2.15) ===<br />
KDE on the MD should work now. The first boot of the system after the update will take a bit longer, as stuff that has not worked, is now being executed for the first time.<br />
<br />
* mce-diskless-tools_2.0.0.44.09050521951_i386.deb (627,628) - Lots of small fixes<br />
* pluto-system-database_2.0.0.44.09050521951_i386.deb (211) - More hardy extinction<br />
* pluto-boot-scripts_2.0.0.44.09050521951_i386.deb (234) - Small bug with regards to MySQL authorization fixed, which results in a running KDE on the MD, again.<br />
<br />
=== 20090505 (alpha2.16 snafu fix) ===<br />
* pluto-boot-scripts_2.0.0.44.09050521958_i386.deb (234) - snafu causing weird things and corruption on updates<br />
<br />
=== 20090506 (alpha2.17) ===<br />
* pluto-asterisk_2.0.0.44.09050621962_i386.deb (270,271) - Additional australian provider in the web admin (VoIPWA) and some janitory work.<br />
* pluto-boot-scripts_2.0.0.44.09050621962_i386.deb (234) - Additional visual feedback during the first boot, after running the AV Wizard<br />
<br />
=== 20090507 (alpha2.18)===<br />
* pluto-dhcpd-plugin_2.0.0.44.09050721973_i386.deb (302) - Pnp script for Cisco 7910, aastra (aastra still needs a device template)<br />
* lmce-launch-manager_2.0.0.44.09050721973_i386.deb (298,299) - Launch manager is now started in its own screen session<br />
* pluto-system-database_2.0.0.44.09050721973_i386.deb (211) - Removal of X Client Data as a dependency<br />
* pluto-mythtv-plugin_2.0.0.44.09050721973_i386.deb (134,153) - small changes to keep backend in sync<br />
* pluto-storage-devices_2.0.0.44.09050721973_i386.deb (533) - Updates the Default and LiveTV storage groups so they use the drive with most space<br />
* pluto-boot-scripts_2.0.0.44.09050721973_i386.deb (234) - Better detection of Intel Mobile Graphics adapter<br />
<br />
=== 20090511 (alpha2.19) ===<br />
* lmcevdr - more VDR configuration settings<br />
* pluto-boot-scripts_2.0.0.44.09051121983_i386.deb (234) - Another KDE Desktop on MD fix<br />
* mce-diskless-tools_2.0.0.44.09051121984_i386.deb (627,628) - Be agnostic about the compression format of tar archives, and more forgiving on download problems<br />
<br />
=== 20090515 (alpha2.20) ===<br />
* lmcevdr_1.1-10_all.deb - more VDR configuration settings<br />
* pluto-system-database_2.0.0.44.09051522002_i386.deb (211) - Additional package definitions (vdr-plugin-streamdev-server and vdr-plugin-streamdev-client)<br />
* pluto-hald_2.0.0.44.09051522002_i386.deb (529,530) - USB detection, better MCE2 support<br />
* pluto-vdr-plugin_2.0.0.44.09051522002_i386.deb (466,467) - Additional dependency for pluto-vdr-plugin to vdr-plugin-streamdev-server<br />
* lmce-launch-manager_2.0.0.44.09051522002_i386.deb (298,299) - Prompt user for reload after new MD creation (Requires manual re-run of Diskless_CreateTBZ.sh)<br />
* pluto-orbiter_2.0.0.44.09051522002_i386.deb (119,138) - Prompt user for reload after new MD creation (Requires manual re-run of Diskless_CreateTBZ.sh)<br />
* pluto-storage-devices_2.0.0.44.09051522003_i386.deb (533) - some small MythTV storage group tweaks<br />
* pluto-slim-server-streamer_2.0.0.44.09051522002_i386.deb (289,290) - changes to the configuraton script to start squeezecenter instead of slimserver<br />
* pluto-website-admin_2.0.0.44.09051522002_i386.deb (220) - Screen Saver section fixed<br />
* pluto-plutoutils_2.0.0.44.09051522002_i386.deb (197,196) - fix FileUtils::ReadURL method<br />
* pluto-std-plugins_2.0.0.44.09051522002_i386.deb (116,135) - support for external media in conjunction with playlists<br />
<br />
=== 20090520 (alpha2.21) ===<br />
* pluto-website-admin_2.0.0.44.09052022008_i386.deb (220) - GSD/IR code update fixes<br />
<br />
=== 20090601 (alpha 2.22) ===<br />
This update contains lots of changes to the storage mechanism. Make sure you can live without a working system for a while, in case things don't work out ...<br />
<br />
* pluto-system-database_2.0.0.44.09060122043_i386.deb (211) - More VDR related changes in the package definitions.<br />
* pluto-boot-scripts_2.0.0.44.09060122043_i386.deb (234) - New installations will use our own new_installation script, starting with number 1000000<br />
* pluto-std-plugins_2.0.0.44.09060122043_i386.deb (116,135) - fixed bug in playlist support<br />
* pluto-network-storage_2.0.0.44.09060122043_i386.deb (503,508) - New /home/public/data/pvr directory structure related<br />
* pluto-storage-devices_2.0.0.44.09060122043_i386.deb (533) - New /home/public/data/pvr directory structure related<br />
* pluto-mythtv-plugin_2.0.0.44.09060122043_i386.deb (134,153) - Storage group enhancements to use the new pvr directory, as well as addition of a new script to handle mythtv storagegroup creation and maintenance. Hopefully this will also fix some stability issues. Mythtv auto expire set from 1GB to 10GB to match the LMCE low disk space nag.<br />
* pluto-website-admin_2.0.0.44.09060122043_i386.deb (220) - more Pluto -> LMCE renames...<br />
* pluto-skins-basic_2.0.0.44.09060122043_i386.deb (204) - new art work for MythTV remote<br />
* pluto-zwave-lighting2.0.0.44.09060122043_i386.deb (505,506) - inclusion enhancements<br />
<br />
=== 20090609 (alpha 2.23) ===<br />
* pluto-boot-scripts_2.0.0.44.09060922056 (234)- backup procedure backs up pluto_media and mediapics<br />
* pluto-skins-basic_2.0.0.44.09060922056 (204) - more art work for MythTV remote on a mobile, remove pluto from more orbiter screens<br />
* pluto-system-database_2.0.0.44.09060922056 (211) - Updates to the MythTV remote and EnOcean package<br />
* pluto-zwave-lighting_2.0.0.44.09060922056 (505,506) - device reset capabilities<br />
* lmce-shoutcast-radio-plugin_2.0.0.44.09060922056 (703,704) - Initial shoutcast support<br />
<br />
=== 20090628 (alpha 2.24) ===<br />
* lmce-mediatomb_2.0.0.44.09062822099_i386.deb (702) - Support for MediaTomb UPnP Server. One day, I will understand why people don't put UPnP into a name, when it handles the configuration of a UPnP Server<br />
* pluto-asterisk_2.0.0.44.09062822099_i386.deb (270,271) - Make sure asterisk is owner of all /etc/asterisk files after updating the dialplan.<br />
* pluto-dhcpd-plugin_2.0.0.44.09062822099_i386.deb (302) - Make sure asterisk is owner of all /etc/asterisk files after adding IP phones<br />
* pluto-orbiter_2.0.0.44.09062822099_i386.deb (119,138) - Support for Gyration 3101<br />
* pluto-skins-basic_2.0.0.44.09062822099_i386.deb (204) - more art work for voice mail<br />
* pluto-slim-server-streamer_2.0.0.44.09062822099_i386.deb (289,290) - support playing of URLs via SqueezeBoxes, turn off SqueezeBoxes after stopping from Orbiter<br />
* pluto-std-plugins_2.0.0.44.09062822099_i386.deb (116,135) - Updates to voice mail datagrid, media streams by default attempt to grab a synopsis from the attribute database, if available, support for Gyration 3101<br />
* pluto-system-database_2.0.0.44.09062822099_i386.deb (211) - Updates to the voice mail screens, cursor no longer visible in video playback (Yeah, TschakEEE go!!!), Support for Gyration 3101<br />
* pluto-zwave-lighting_2.0.0.44.09062822099_i386.deb (505,506) - enhanced logging<br />
<br />
=== upcoming... ===<br />
<br />
== Previous alpha releases ==<br />
* Notes about [[LinuxMCE-0810 alpha1]]<br />
* Notes about [[LinuxMCE-0810 alpha0]]</div>Brake16http://wiki.linuxmce.org/index.php?title=VOIP_Service_Providers&diff=19419VOIP Service Providers2009-06-16T14:33:45Z<p>Brake16: Added location info & noted that NuFone no longer exists</p>
<hr />
<div>[[Category:Phone Lines]]<br />
[[Category:Telecom]]<br />
<br />
If you do not see your VOIP Provider listed here also check [[:Category:Phone Lines| Phone Lines]]<br />
<br />
==Automatically Setup==<br />
* [[Broadvoice]] (US)<br />
* [[E-Fon_(Switzerland)]]<br />
* [[Inphonex]] (US)<br />
* [[NuFone]] (defunct - gone)<br />
* [[Sipgate]] (UK)<br />
* [[Teliax]] (US)<br />
* [[VoiceEclipse]] (US)<br />
<br />
==Require Manual Setup==<br />
<br />
Here is a description on [[Manual Phones Configuration | How to Configure Phone Lines Manually]]<br />
<br />
* gotalk - VoIP providers - Australia - [http://www.gotalk.com]<br />
* Voipwa - VoIP providers - Australia - [http://www.voipwa.com.au]<br />
* [[Free world dialup]]<br />
* [[VOIP with XS4All]]</div>Brake16http://wiki.linuxmce.org/index.php?title=Bluetooth_Dongle&diff=19163Bluetooth Dongle2009-05-23T12:22:50Z<p>Brake16: Things to Consider - revision</p>
<hr />
<div>[[Category: Hardware| ]]<br />
[[Category:Bluetooth]]<br />
<br />
==What is the purpose?==<br />
<p>If you have Bluetooth in the computer that you will use as a LinuxMCE Media Director, this device [http://wiki.linuxmce.org/index.php/Control_LinuxMCE_using_a_Symbian_Series_60_mobile_phone_with_Bl turns your mobile phone into a remote control] and gives you "follow-me" capabilities--your lighting preferences, media and more can follow you around the house.</p><br />
<br />
==Requirements and Compatibility==<br />
<p>Runs on both Linux, using the Bluez library, and Windows, using the standard Windows/Widcom drivers. Although it should work with all Bluetooth devices, we always use USB Bluetooth dongles with the CSR chipset for both Windows and Linux. The D-Link DBT-120 and TDK are some of the more common models.</p><br />
<br />
==Turning off automatic discovery==<br />
To prevent LinuxMCE from finding bluetooth devices outside of your home the autodetection (of any BT device) can be turned off as followed: [http://forum.linuxmce.org/index.php?topic=3139.msg16493#msg16493]<br />
# Login in Web Admin<br />
# Go to Advanced -> Configuration -> Devices<br />
# Open the CORE/MD where is located your bluetooth device<br />
# Open DCERouter and click on Orbiter Plugin<br />
# Check the Ignore check box under "Device data".<br />
<br />
Turn it back on again to autodetect new devices you're adding to the network, after which you can turn it off again once they're added.<br />
<br />
==Things to Consider When Purchasing an Adapter== <br />
<p> - A single Class 1 adapter (range 100m, 330 ft) will provide Bluetooth service to your whole house. With this setup, the system will not be able to detect which room you are in (ie: no follow-me functionality), but it will be able to detect when you arrive home. This adapter is best placed on the Core for always-on functionality.</p> <br />
<br />
<p> - A Class 2 adapter (range 10m, 33 ft) is good for Media Directors that are quite far apart (ie: on opposite sides of a large house). If the Bluetooth ranges don't overlap, then the system will be able to distinguish your location by room. If the Bluetooth ranges do overlap, the system may hop you back & forth between rooms rapidly.</p> <br />
<br />
<p> - A Class 3 adapter (range 1m, 3 ft) can be used for a setup with multiple Media Directors that are too close to use Class 2 adapters. The downside is that you must be fairly close to the Media Director to be detected. You might consider using a USB extension cord to move this adapter towards the middle of the room for better detection. A USB extension cord is also useful if two Media Directors are too close to each other (ie: opposite sides of an adjoining wall). Having said all of that, Class 3 adapters are not common for the simple reason that their range makes them practically useless except for true PANs, which is not an LinuxMCE use-case. While it is true that many devices can achieve 3m, many will only achieve the specified 1m, especially with local environment considerations, and this renders it useless for LinuxMCE.[http://forum.linuxmce.org/index.php?topic=8175.msg54219#msg54219]</p> <br />
<br />
<p> - Remember, Bluetooth is two-way communication, so the effective range will be the shorter of the two devices that are communicating. If you put Class 2 adapters on all of your Media Directors, but your Orbiter has a Class 3 adapter, then you will be limited to the Class 3 range.</div>Brake16http://wiki.linuxmce.org/index.php?title=Bluetooth_Dongle&diff=19122Bluetooth Dongle2009-05-20T18:49:44Z<p>Brake16: Things to consider</p>
<hr />
<div>[[Category: Hardware| ]]<br />
[[Category:Bluetooth]]<br />
<br />
==What is the purpose?==<br />
<p>If you have Bluetooth in the computer that you will use as a LinuxMCE Media Director, this device [http://wiki.linuxmce.org/index.php/Control_LinuxMCE_using_a_Symbian_Series_60_mobile_phone_with_Bl turns your mobile phone into a remote control] and gives you "follow-me" capabilities--your lighting preferences, media and more can follow you around the house.</p><br />
<br />
==Requirements and Compatibility==<br />
<p>Runs on both Linux, using the Bluez library, and Windows, using the standard Windows/Widcom drivers. Although it should work with all Bluetooth devices, we always use USB Bluetooth dongles with the CSR chipset for both Windows and Linux. The D-Link DBT-120 and TDK are some of the more common models.</p><br />
<br />
==Turning off automatic discovery==<br />
To prevent LinuxMCE from finding bluetooth devices outside of your home the autodetection (of any BT device) can be turned off as followed: [http://forum.linuxmce.org/index.php?topic=3139.msg16493#msg16493]<br />
# Login in Web Admin<br />
# Go to Advanced -> Configuration -> Devices<br />
# Open the CORE/MD where is located your bluetooth device<br />
# Open DCERouter and click on Orbiter Plugin<br />
# Check the Ignore check box under "Device data".<br />
<br />
Turn it back on again to autodetect new devices you're adding to the network, after which you can turn it off again once they're added.<br />
<br />
==Things to Consider When Purchasing an Adapter==<br />
<p> - A single Class 1 adapter (range 100m, 330 ft) will provide Bluetooth service to your whole house. With this setup, the system will not be able to detect which room you are in (ie: no follow-me functionality), but it will be able to detect when you arrive home. This adapter is best placed on the Core for always-on functionality.</p><br />
<br />
<p> - A Class 2 adapter (range 10m, 33 ft) is good for Media Directors that are quite far apart (ie: on opposite sides of a large house). If the Bluetooth ranges don't overlap, then the system will be able to distinguish your location by room. If the Bluetooth ranges do overlap, the system may hop you back & forth between rooms rapidly.</p><br />
<br />
<p> - A Class 3 adapter (range 1m, 3 ft) is good for a setup with multiple Media Directors that are too close to use Class 2 adapters. The downside is that you must be fairly close to the Media Director to be detected. You might consider using a USB extension cord to move this adapter towards the middle of the room for better detection. A USB extension cord is also useful if two Media Directors are too close to each other (ie: opposite sides of an adjoining wall).</p></div>Brake16http://wiki.linuxmce.org/index.php?title=Bluetooth_Dongle&diff=19115Bluetooth Dongle2009-05-19T20:52:06Z<p>Brake16: </p>
<hr />
<div>[[Category: Hardware| ]]<br />
[[Category:Bluetooth]]<br />
<br />
==What is the purpose?==<br />
<p>If you have Bluetooth in the computer that you will use as a LinuxMCE Media Director, this device [http://wiki.linuxmce.org/index.php/Control_LinuxMCE_using_a_Symbian_Series_60_mobile_phone_with_Bl turns your mobile phone into a remote control] and gives you "follow-me" capabilities--your lighting preferences, media and more can follow you around the house.</p><br />
<br />
==Requirements and Compatibility==<br />
<p>Runs on both Linux, using the Bluez library, and Windows, using the standard Windows/Widcom drivers. Although it should work with all Bluetooth devices, we always use USB Bluetooth dongles with the CSR chipset for both Windows and Linux. The D-Link DBT-120 and TDK are some of the more common models.</p><br />
<br />
==Turning off automatic discovery==<br />
To prevent LinuxMCE from finding bluetooth devices outside of your home the autodetection (of any BT device) can be turned off as followed: [http://forum.linuxmce.org/index.php?topic=3139.msg16493#msg16493]<br />
# Login in Web Admin<br />
# Go to Advanced -> Configuration -> Devices<br />
# Open the CORE/MD where is located your bluetooth device<br />
# Open DCERouter and click on Orbiter Plugin<br />
# Check the Ignore check box under "Device data".<br />
<br />
Turn it back on again to autodetect new devices you're adding to the network, after which you can turn it off again once they're added.<br />
<br />
==Things to Consider When Purchasing an Adapter==<br />
<p> - A single Class 1 adapter (range 100m, 330 ft) will provide service to your whole house. Best placed on the Core for always-on functionality. With this setup, the system will not be able to detect which room you are in (ie: no follow-me functionality).</p><br />
<br />
<p> - A Class 2 adapter (range 10m, 33 ft) is good for Media Directors that are quite far apart (ie: on opposite sides of a large house). If the Bluetooth ranges don't overlap, then the system will be able to distinguish your location by room.</p><br />
<br />
<p> - A Class 3 adapter (range 1m, 3 ft) is good for multiple Media Directors that are too close to use Class 2 adapters. The downside is that you must be fairly close to the Media Director to be detected.</p></div>Brake16