[[Category: Hardware]]
{{Versioninfo}}
[[Category: Cameras]]
[[Category: IP Cameras]]

[[Image:Foscam-FI8908W.jpg|right|thumb|300px]]

== Info ==
Cheap IR wireless IP/Network Pan/tilt Camera

== Status ==
Provisionally working either as a plug and play IP camera with pan/tilt commands or as a 'Generic Motion IP camera' under motion wrapper and used as a sensor as well as recording movement etc.

If using under motion the pan/tilt commands do not work. It can be installed under motion (my preferred option) by adding the mac range of both the wireless and wired adapters into the 'Generic Motion IP Camera' template:
Wireless
79373008896 to 79389786111 (DHCP).
Wired
414170742784 to 414171791359 (DHCP).

After the device has been detected and assigned a room just give it a sensible name and add the following to the path parameter in web admin:
hxxp://<CAMERA_IP_ADDRESS>/videostream.cgi?user=XXXXX&pwd=XXXXX

Replace the ip address and the XXXXX with your settings

Pros:
Plug and Play (Just give it a sensible name)
Installed under motion for security monitoring/recording
Cons:
Path must be manually set as described above
No Pan/Tilt other than via its own web interface

This camera is fully plug and play as a stand-alone pan/tilt camera by duplicating the panasonic template and inserting the following scripts.

#84 Get video frame
<pre>
conn_.Reconnect()
auth_s="user="+device_.devdata_[114]+"&pwd="+device_.devdata_[115];

fix_path=device_.devdata_[2]+auth_s;
fix_path='/'+fix_path if(fix_path[0]!='/'[0]);

s = "GET "+fix_path+" HTTP/1.0\r\n"
s+= "Accept: */*\r\n"
s+= "\r\n"

conn_.Send(s)
recv=""
while(true)
buff=conn_.Recv(16384, 5000)
if(buff.length() == 0)
break
end
recv = recv + buff
end
if (recv=~ /^HTTP[^\r\n]+200\sOK.+?\r\n\r\n(.+)$/m)
fileName="/tmp/ip_camera_img"+device_.devid_.to_s
imageFile=File.new(fileName+".jpg",'w')
imageFile.print $1
imageFile.close()
system("/usr/bin/convert "+fileName+".jpg "+fileName+".png");
size=File.stat(fileName+".png").size
imageFile=File.new(fileName+".png",'r')
img = imageFile.read(size);
imageFile.close()
data_set(img)
format_set('png')
end
</pre>
#201 Move Down
<pre>
conn_.Reconnect()
auth_s="user="+device_.devdata_[114]+"&pwd="+device_.devdata_[115];
s = "GET /decoder_control.cgi?command=2&onestep=1&"+auth_s
s+= " HTTP/1.0\r\n Accept: */*\r\n"
s+= "\r\n"

conn_.Send(s)
recv=""
while(true)
buff=conn_.Recv(256, 5000)
if(buff.length() == 0)
break
end
recv = recv + buff
end
</pre>
#202 move left
<pre>
conn_.Reconnect()
auth_s="user="+device_.devdata_[114]+"&pwd="+device_.devdata_[115];
#auth_a=Array.new;
#auth_s.each{|c| auth_a.push(c)}
s = "GET /decoder_control.cgi?command=4&onestep=1&"+auth_s
s+= " HTTP/1.0\r\n Accept: */*\r\n"
#s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
s+= "\r\n"

conn_.Send(s)
recv=""
while(true)
buff=conn_.Recv(256, 5000)
if(buff.length() == 0)
break
end
recv = recv + buff
end
</pre>
#203 Move Right
<pre>
conn_.Reconnect()
auth_s="user="+device_.devdata_[114]+"&pwd="+device_.devdata_[115];
#auth_a=Array.new;
#auth_s.each{|c| auth_a.push(c)}
s = "GET /decoder_control.cgi?command=6&onestep=1&"+auth_s
s+= " HTTP/1.0\r\n Accept: */*\r\n"
#s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
s+= "\r\n"

conn_.Send(s)
recv=""
while(true)
buff=conn_.Recv(256, 5000)
if(buff.length() == 0)
break
end
recv = recv + buff
end
</pre>
#200 Move Up
<pre>
conn_.Reconnect()
auth_s="user="+device_.devdata_[114]+"&pwd="+device_.devdata_[115];
#auth_a=Array.new;
#auth_s.each{|c| auth_a.push(c)}
s = "GET /decoder_control.cgi?command=0&onestep=1&"+auth_s
s+= " HTTP/1.0\r\n Accept: */*\r\n"
#s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
s+= "\r\n"

conn_.Send(s)
recv=""
while(true)
buff=conn_.Recv(256, 5000)
if(buff.length() == 0)
break
end
recv = recv + buff
end
</pre>

Pros:
Plug and play (Just give it a sensible name)
Pan and Tilt work from on screen arrows
Cons:
No motion capture except using the cameras in-built web interface in a browser.

== Features ==
* Browser based
* 10/100mbit LAN

== Links ==
* [http://www.gadgetvictims.com/2009/07/foscam-ip-camera-part-two.html Foscam IP Camera (Part Two)]
* [http://forum.linuxmce.org/index.php?topic=9969.0 Forum discussion]

Foscam FI8908W

2010-10-12T23:27:02Z

B4rney: /* Status */

LG 42LB5D

2010-10-04T15:36:51Z

B4rney: /* 'Add Ruby snippets to commands' */

[[Category: Hardware]]
{{Versioninfo}}
[[Category: Video]]
[[Category: Displays]]

{| align="right"
| __TOC__
|}
==Features==
===Basics===
* 42" (diagonal) [[16:9|widescreen]] [[LCD]] television
* Good build quality on the whole, though some edges on the plastic casing were left "sharp" (I'm OCD about fit and finish)
* Not that heavy for its size (one person can lift it, in or out of packing carton)
Special features and nice touches:
* [[RS232 port]] at the back to allow external control (by LinuxMCE for example)
* Power LED is red on standby, and switches to green when set is on (thank goodness, blue-LED fever is abating! :-)
* Brightness can be instantly adjusted via two remote buttons -- the only thing better would be a photosensor that adjusts things automatically for ambient light (but that's what hacking is all about ;-)
===Picture fidelity===
* Crisp picture when provided with full quality source (e.g. true HD)
* Crisp picture with some ghosting when using the RGB-PC input with a standard (though longer than average) VGA video cable -- I will try to add a photo of the effect; the lowest-tech connections ([[S-Video]], RF, and the like) for PC video are NOT recommended!
* A touch blurry with low-end sources ([[S-Video]], RF) like older game systems, but still a fairly good overall picture; I have yet to test other signal methods with my game systems (requires special cables I don't yet have).
===Usability===
* The [[OSD]] UI and remote are excellent. Both the menus and the buttons are laid out sensibly, and the system incorporates a great idea for settings that are cyclic (most are): the first time you press a button (e.g. [[aspect ratio]]), it brings up an [[OSD]] reminder of the current setting; subsequent presses will cycle through the available options. It's simple, and effective at preventing accidental setting changes by a single inadvertent button press on the remote.
Resolutions:
* 1024x768
* 1280x768
* 1360x768

== Adding new template ==
Here is a description of adding a Template for LG LCD TV with serial connections for control. According to the manual the following models should work:
LCD TV MODELS 37LB5D / 42LB5D / 47LB5D 52LB5D/ 32LB4D / 37LB4D / 42LB4D
I have the 42LB5D, so I know that this one works.

=== Specify device data and parameters ===

On the LinuxMCE admin website go to: Advanced > Configuration > Device Templates

Select: Manufacturer 'LG', Device Category 'TVs/Plasmas/LCD's/Projectors' and press 'Add device template'

Description : XXLB4/5D
Implements DCE : yes
Command line : Generic_Serial_Device
Device Category AV TVs/Plasmas/Projection... #77
Manufacturer LG

Also have added following parameters (You need to add them one by one under the header 'Device data'):

Device data
Current Data Comments Default Value
#37 COM Port on PC(string) The serial port
#76 COM Port ParityBit/Stop(string) Parity/Stop bits (factory defaults) N81
#78 COM Port BaudRate(string) Baud rate (factory default) B9600
#157 Discrete Volume(bool) Indicates if the volume on... 1

Settings are factory defaults and shouldn't be changed (9600 baud rate, 8 bits, 1 stop bit). Make sure that the check box for Allowed to Modify is checked, so that you can change to the appropriate COM port later.

=== 'Edit Ruby code' (on template page) ===

==== 'Add/remove commands' ====
First, I clicked on 'Add/remove commands' and clicked on commands that are supported by device...

* Ruby Internal Commands
* Standard TV

==== 'Add Ruby snippets to commands'====
Edited corresponding Ruby snippets for each command. Basically those are just simple strings that get send on rs232 to take proper action on device according to received command from LinuxMCE... Use the extended editor for the multiline entries (otherwise ruby won't understand it and gives lot's of errors)
<pre>
#193 Off
log('Sending OFF Command')
<$"ka 01 00\r"$>
#192 On
log('Sending ON Command')
<$"ka 01 01\r"$>
Inputs
#419 Antenna

#316 AV 1
log('Switching Input to AV1')
<$"kb 01 02\r"$>
#317 AV 2
log('Switching Input to AV2')
<$"kb 01 03\r"$>
#712 Component 1
log('Switching Input to Component 1')
<$"kb 01 04\r"$>
#713 Component 2
log('Switching Input to Component 2')
<$"kb 01 05\r"$>
#426 External 3
log('Switching Input to HDMI 3')
<$"kb 01 09\r"$>
#361 HDMI
log('Switching Input to HDMI 1')
<$"kb 01 07\r"$>
#767 HDMI 2
log('Switching Input to HDMI 2')
<$"kb 01 08\r"$>
#376 Input 3
log('Switching Input to HDMI 3')
<$"kb 01 09\r"$>
#154 RGB
log('Switching Input to RGB/PC')
<$"kb 01 06\r"$>
#166 Tuner
log('Switching Input to Analog Tuner')
<$"kb 01 01\r"$>
#873 Tuner - Digital
log('Switching Input to Digital Tuner')
<$"kb 01 00\r"$>
Aspect Ratios
#879 16:9
log('Switching Aspect Ratio to 16:9')
<$"kc 01 02\r"$>
#877 4:3
log('Switching Aspect Ratio to 4:3')
<$"kc 01 01\r"$>
Disk Handle
#48 Eject Disk

DSP Modes
#116 DSP Mode
log('Switching DSP Modes: Toggled Only')
<$"mc 01 52\r"$>
General
#190 Enter/Go
log('Sending Enter/Go Command')
<$"mc 01 44\r"$>
Internal
#373 Private Method Listing
def log(line)
$log = File.open("/var/log/pluto/" + device_.devid_.to_s + "_Generic_Serial_Device.log", "a")
$log.puts "(***):" + line.to_s
$log.close
end
#351 Process IDLE

#350 Process Incoming Data
buff = ''
loop do
buff=conn_.Recv(30,200)
if buff.empty?
log('Nothing Received')
break
end
log('Received: ' + Regexp.escape(buff.to_s))
if buff.include?("OK")
log(Regexp.escape(buff.to_s) + ': Command Processed Successfully')
elsif buff.include?("NG")
log(Regexp.escape(buff.to_s) +': Command Processed Unsuccessfully')
end
end
#355 Process Initialize
for iRetry in 0...4
print "Initializing unit\n"
conn_.Send("ke 01 01\r") # Send UnMute Command
buf = conn_.Recv(30,200) # Expected Return # ke 01 01\r\ne 00 OK01x\r\n
if !buf.nil? && buf.include?("OK")
print "Initialized ok\n"
print "Setting volume to 30%\n"
cmd_313(15)
SetDeviceDataInDB( device_.devid_, 158, "15" )
# 158 = DEVICEDATA_Volume_Level_CONST
return
end
print "Failed to initialize. Wait 1 secs and try again\n"
sleep(1)
end
#DisableDevice( device_.devid_, true )
#print "The device would not respond. Disabling it.\n"
#384 Process Receive Command For Child

#356 Process Release

Misc
#548 Menu
log('Sending Menu Command')
<$"mc 01 43\r"$>
#676 Video Mute
log('Sending Video Mute Command')
<$"kd 01 00\r"$>
Numbers
#364 -/--/---

#204 0
log('Sending 0 ')
<$"mc 01 10\r"$>
#205 1
log('Sending 1 ')
<$"mc 01 11\r"$>
#206 2
log('Sending 2 ')
<$"mc 01 12\r"$>
#207 3
log('Sending 3 ')
<$"mc 01 13\r"$>
#208 4
log('Sending 4 ')
<$"mc 01 14\r"$>
#209 5
log('Sending 5 ')
<$"mc 01 15\r"$>
#210 6
log('Sending 6 ')
<$"mc 01 16\r"$>
#211 7
log('Sending 7 ')
<$"mc 01 17\r"$>
#212 8
log('Sending 8 ')
<$"mc 01 18\r"$>
#213 9
log('Sending 9 ')
<$"mc 01 19\r"$>
#363 Back / Clear Entry
log('Sending Back/Clear Command ')
<$"mc 01 1A\r"$>
On-Screen Menu Navig
#240 Back / Prior Menu
log('Sending Exit Command ')
<$"mc 01 5B\r"$>
#225 Display

#368 Help

#86 Menu (Show Menu)
log('Sending Menu Command ')
<$"mc 01 43\r"$>
#201 Move Down
log('Sending Move Down Command ')
<$"mc 01 41\r"$>
#202 Move Left
log('Sending Move Left Command ')
<$"mc 01 07\r"$>
#203 Move Right
log('Sending Move RighCommand ')
<$"mc 01 06\r"$>
#200 Move Up
log('Sending Move Up Command ')
<$"mc 01 40\r"$>
Simple Control
#92 Pause
log('Sending Pause Command ')
<$"mc 01 BA\r"$>
#139 Play
log('Sending Play Command ')
<$"mc 01 B0\r"$>
#102 Record
#log('Sending Record Command ')
#<$"mc 01 BD\r"$>
#64 Skip Back - Channel/Track Lower
log('Sending Channel Down Command ')
<$"mc 01 01\r"$>
#63 Skip Fwd - Channel/Track Greater
log('Sending Channel Up Command ')
<$"mc 01 00\r"$>
#95 Stop
log('Sending Stop Command ')
<$"mc 01 B1\r"$>
Sound & Volume
#97 Mute
if @mute
<$"ke 01 00\r"$>
else
<$"ke 01 01\r"$>
end
@mute=!@mute
#313 Set Volume
@volume=level.to_i()
ilevel = @volume.to_i
log( 'setting volume to '+ ilevel.to_s)
log('Sending the Following Command: kf 01 '+ilevel.to_s(16)+'\r')
<$"kf 01 "+ilevel.to_s(16)+"\r"$>
SetDeviceDataInDB( device_.devid_, 158, ilevel.to_s)
# 158 = DEVICEDATA_Volume_Level_CONST # "volume and corresponding device data set\n"
#90 Vol Down
log('lowering volume from ' + @volume.to_s)
cmd_313(@volume-1)
#89 Vol Up
log('Increasing volume from ' + @volume.to_s)
cmd_313(@volume+1)
Speed Ctrl
#125 Scan Back/Rewind
log('Sending Rewind Command ')
<$"mc 01 8F\r"$>
#93 Scan Fwd/Fast Fwd
log('Sending Fast Fwd Command ')
<$"mc 01 8E\r"$>
#98 Slow Scan Back

#99 Slow Scan Forward

TV
#136 Previous Channel
log('Sending Previous Channel Command ')
<$"mc 01 B2\r"$>
</pre>

== Adding device ==

This is a simple process that you can now add via the [[LinuxMCE Admin Website]] at '''Wizard > [[AV Devices|A/V Equipment]]'''
=== Add device based on created template ===
Just search for the device template that you created and select it from the list
=== Specify COM port for it ===
Just tell LinuxMCE which com port to use.
=== Assing it to new room ===
Tell LinuxMCE which room to assign this device
=== Specifiy Audio pipe connections to inputs on receiver ===
Tell LinuxMCE how you have thing attached to the LG TV and how the LG TV is attached to the computer.

''I have it attached via RGB port and I have my cable box attached to AV1 and my HDTV connected to Tuner-Digital input.''

==Making Plug&Play==
This is not needed to use the TV, but I post as an option.
Location: /usr/pluto/pnp

vi /usr/pluto/pnp/20_LGLCD.sh
add the following and then make the file executable.

<pre> #!/bin/bash
#Play and Play script for LG TV's Models Numbers:LGXXLB4/5D
#Set ID needs to be set to 01
#Serial feedback is very slow so it requires several seconds to get feedback
#Device Template Number:1905 on my local Machine.
#Serail Command for Power On ka 01 01
#Serial Command for Power OFF ka 01 00
#Returns two different strings depending on whether or not the TV is On or Off, so we will try to turn it ON then resend the ON command as it returns proper string (ka 01 01\r\na 00 OK01x\r\n)
echo "LG TV Detection script queue $2"
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 9600 -t "ka 01 01\r"
sleep 5s
/usr/pluto/bin/TestSerialPort -p $3 -P N81 -b 9600 -t "ka 01 01\r" -i 5 -s "OK01x\r"
if [[ "$?" -ne 0 ]]; then
echo "It's not a LG TV"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 0
else
echo "It is a LG TV"
/usr/pluto/bin/MessageSend dcerouter -r 0 $1 1 806 224 $2 13 "$4" 44 1905
fi</pre>

the plugin will run the script with 4 parameters: the device id of the plugin, the unique id for this event (the PK_PnpQueue), a path where the device is located (ip address for ethernet devices, serial port for rs232 devices, etc.), and the name of the pnp detection script.

The detection script should attempt to determine what device template is on the path using any appropriate means. If it finds a match, it should fire a message using the paramters it received, such as this:

/usr/pluto/bin/MessageSend dcerouter -r 0 $1 806 224 $2 13 "$4" 44 1905(this is the template id for the devicetemplate you created above)

=====================================

==
'''== Adapting these instructions for other LG rs232 TVs == =='''

This seems to be a good template for LG TVs with serial ports. Some of the command need to be changed for later models <$xb 01 90\r$> instead of <$kb 01 07\r$> for inputing HDMI 1 for example, but generally a good guide for adapting it to your TV.

The major problem is undocumented above but is critical to making this work: You need to look up the device id number of your LG TV from the Wizard \ Devices \ AV Equipment in the upper left hand corner and replace the number "158" in all the scripts above with this number (for example, in my case 310). This allows the script to process successfully.

Otherwise it will cause a compile error in 7.10 in the "follow log" on the "advanced" link of the A/V device and will not allow your template to run. The compile error will state that it found a "kend" and was expecting "$end".

The code that breaks it is:

----------------------------
#355 Process Initialize
for iRetry in 0...4
print "Initializing unit\n"
conn_.Send("ke 01 01\r") # Send UnMute Command
buf = conn_.Recv(30,200) # Expected Return # ke 01 01\r\ne 00 OK01x\r\n
if !buf.nil? && buf.include?("OK")
print "Initialized ok\n"
print "Setting volume to 30%\n"
cmd_313(15)
SetDeviceDataInDB( device_.devid_, 158, "15" )
# 158 = DEVICEDATA_Volume_Level_CONST
return
end
print "Failed to initialize. Wait 1 secs and try again\n"
sleep(1)
end

-------------------------------
which is also necessary for the volume set, volume up and volume down commands the way they are written.
Carefully replacing "158" with the LG TV device ID number on your setup in the extended editor will make all these commands functional.

Please note that the description for the plug and play implementation discussed above has not been tested with this fix.

Buffalo Terastation

2009-01-29T14:07:35Z

B4rney:

[[Category: Hardware]]
[[Category: Network Attached Storage]]

The [[http://www.buffalotech.com/products/network-storage/terastation/ Buffalo TeraStation]] is a 4 hard drive, software RAID 5 Linux computer running SAMBA. It has versions with 10/100/1000 Gigabit Ethernet port and up to 1.6 Terabytes of storage. It also has USB ports for attaching more storage and/or sharing and managing a USB printer on the network using a built-in print server.

==Setup==
Using the TeraStation's web-based admin page, configure the TeraStation to accept a DHCP address. Also create a share. In the example below, it will be called "share_name". You may also want to create an user and give the user a strong password. In the example below, this will be "user_name" and "password", respectively.

==LinuxMCE Device Configuration==
# From the bottom of the Wizard menu, click "Show Devices Tree".
# In the Devices Tree, click "Add Top Level Device".
# From the main window, click "Pick Device Template". A new window will pop open and give you options.
# In the "Device Category", scroll down to "Peripherals" and click on "Network Storage #150".
# Under models choose "Generic Windows Share" and click "Add device". You will be returned back to the main window.
# In the "Device Info" section, give your TeraStation a description, add the TeraStation's MAC address in xx:xx:xx:xx:xx:xx format.
# In the "Device Data" section, set the following:<br><br>

* Type(string)
<pre>samba</pre>
* TCP Address(string)
<pre>share_name</pre>
* Username(string)
<pre>user_name</pre>
* Password(string)
<pre>password</pre>
* Use LinuxMCE Directory Structure(int)
<pre>1</pre>

where "share_name" is the share that you defined when setting up the TeraStation. At the very least, you can use the "public" username with no password as default by TeraStation. But it is better to configure the TeraStation with a unique username and strong password and to input that information in the Device Data section as per above. If you leave "Mount Point(string)" blank, LinuxMCE will mount the share on /mnt/<description_device#> where description is what you input in step 6 above.
[[Category: Storage]]

Buffalo Terastation

2009-01-29T14:06:34Z

B4rney:

[[Category: Hardware]]
[[Category: Network Attached Storage]]

The [[http://www.buffalotech.com/products/network-storage/terastation/]] is a 4 hard drive, software RAID 5 Linux computer running SAMBA. It has versions with 10/100/1000 Gigabit Ethernet port and up to 1.6 Terabytes of storage. It also has USB ports for attaching more storage and/or sharing and managing a USB printer on the network using a built-in print server.

==Setup==
Using the TeraStation's web-based admin page, configure the TeraStation to accept a DHCP address. Also create a share. In the example below, it will be called "share_name". You may also want to create an user and give the user a strong password. In the example below, this will be "user_name" and "password", respectively.

==LinuxMCE Device Configuration==
# From the bottom of the Wizard menu, click "Show Devices Tree".
# In the Devices Tree, click "Add Top Level Device".
# From the main window, click "Pick Device Template". A new window will pop open and give you options.
# In the "Device Category", scroll down to "Peripherals" and click on "Network Storage #150".
# Under models choose "Generic Windows Share" and click "Add device". You will be returned back to the main window.
# In the "Device Info" section, give your TeraStation a description, add the TeraStation's MAC address in xx:xx:xx:xx:xx:xx format.
# In the "Device Data" section, set the following:<br><br>

* Type(string)
<pre>samba</pre>
* TCP Address(string)
<pre>share_name</pre>
* Username(string)
<pre>user_name</pre>
* Password(string)
<pre>password</pre>
* Use LinuxMCE Directory Structure(int)
<pre>1</pre>

where "share_name" is the share that you defined when setting up the TeraStation. At the very least, you can use the "public" username with no password as default by TeraStation. But it is better to configure the TeraStation with a unique username and strong password and to input that information in the Device Data section as per above. If you leave "Mount Point(string)" blank, LinuxMCE will mount the share on /mnt/<description_device#> where description is what you input in step 6 above.
[[Category: Storage]]

File:Asus eee box b202.jpg

2009-01-24T23:52:32Z

B4rney:

Web Orbiter

2009-01-23T16:40:40Z

B4rney: /* Changing default room */

{| align="right"
| __TOC__
|}
[[Category: Orbiters]]
[[Category: Hardware]]
[[Category: Tutorials]]

A Web Orbiter is any device (such as a laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.

== Setup ==
The procedure to setup a Web Orbiter is simple but the order of steps is important.
#First of all, add a new Generic Web Device as a Child Device for your Core:
##Goto the LinuxMCE Admin website-->Show devices tree-->CORE. The CORE's detail page should appear.
##Click 'Create Child Device'.
##In the Add child device window, click the button 'Pick device template'. The new pop-up window contained device templates will be opened.
##In the 'Device Category' dropdown list, choose 'Peripherals'.
##In the 'Device Template' dropdown list, find and select "Generic Web Device".
##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.
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard-->Devices-->Orbiters.
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.
#Do a "[[Quick reload router]]". Otherwise, the Orbiter won't work properly.

==Access to the Web Orbiter==

===From within your home===
You can access the Web Orbiter from any web browser (Mozilla Firefox, IE, Safari):

*In the browser address bar, type the URL ''<nowiki>http://<core_ip>/pluto-admin/weborbiter.php</nowiki>''.
:* From within the "internal" LinuxMCE LAN, for example:
::::''http://192.168.80.1/pluto-admin/weborbiter.php''
:::::(This assumes the IP address range set by default at installation.)
:*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:
::::''<nowiki>http://dcerouter/pluto-admin/weborbiter.php</nowiki>''
:*From the "external" home LAN, the core_ip would be the LAN IP address of the core. If, for example, the core is at 192.168.0.50 on the home LAN, use:
:::: ''<nowiki>http://192.168.0.50/pluto-admin/weborbiter.php</nowiki>''

:::::(Note: To use this method, [[Outside Access]] must be enabled.)

===From the Internet===
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).
*''This is an advanced topic and may not be secure in the current version.''.

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]].

===Login page===
*A simple login page should be displayed. Input an existing user name and password, then click "Login".
*From the dropdown list of devices, choose Generic Web Device.
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]

==Troubleshooting==
===Connect failed===
If you try to connect to the Web Orbiter and see this message:
<code>"Connect to proxy orbiter failed, please try again"</code>,
this means that Orbiter generation hasn't finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].

=== Size ===
I was able to change the size of the rendered image in the Wizard-->Orbiters page. Find the Web Orbiter device in the list and resize it. After another orbiter regen, it was the right size for me. (''Source http://forum.linuxmce.org/index.php?topic=3833.0'')

=== Problems with rapid refresh rate ===

Problem:
When using the Web Orbiter over the Internet (instead of from within my home LAN), it refreshed every 5 seconds, making it difficult to use. The images were repeatedly downloaded each time.

Solution:
*Go to [[LinuxMCE Admin Website]]-->Device tree-->CORE-->Generic Web Device-->Device Data
*Set the Refresh Interval to a higher value (I used 60 seconds for mine).

=== Changing default room ===
Changing the default room in the Wizard-->Devices-->Orbiters page has no effect.

Solution:
*Go to [[LinuxMCE Admin Website]]-->Device tree-->CORE-->Generic Web Device
*Check the box for the room to control

Web Orbiter

2009-01-23T16:39:59Z

B4rney: /* Troubleshooting */

{| align="right"
| __TOC__
|}
[[Category: Orbiters]]
[[Category: Hardware]]
[[Category: Tutorials]]

A Web Orbiter is any device (such as a laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.

== Setup ==
The procedure to setup a Web Orbiter is simple but the order of steps is important.
#First of all, add a new Generic Web Device as a Child Device for your Core:
##Goto the LinuxMCE Admin website-->Show devices tree-->CORE. The CORE's detail page should appear.
##Click 'Create Child Device'.
##In the Add child device window, click the button 'Pick device template'. The new pop-up window contained device templates will be opened.
##In the 'Device Category' dropdown list, choose 'Peripherals'.
##In the 'Device Template' dropdown list, find and select "Generic Web Device".
##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.
##A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard-->Devices-->Orbiters.
#Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.
#Do a "[[Quick reload router]]". Otherwise, the Orbiter won't work properly.

==Access to the Web Orbiter==

===From within your home===
You can access the Web Orbiter from any web browser (Mozilla Firefox, IE, Safari):

*In the browser address bar, type the URL ''<nowiki>http://<core_ip>/pluto-admin/weborbiter.php</nowiki>''.
:* From within the "internal" LinuxMCE LAN, for example:
::::''http://192.168.80.1/pluto-admin/weborbiter.php''
:::::(This assumes the IP address range set by default at installation.)
:*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:
::::''<nowiki>http://dcerouter/pluto-admin/weborbiter.php</nowiki>''
:*From the "external" home LAN, the core_ip would be the LAN IP address of the core. If, for example, the core is at 192.168.0.50 on the home LAN, use:
:::: ''<nowiki>http://192.168.0.50/pluto-admin/weborbiter.php</nowiki>''

:::::(Note: To use this method, [[Outside Access]] must be enabled.)

===From the Internet===
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).
*''This is an advanced topic and may not be secure in the current version.''.

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]].

===Login page===
*A simple login page should be displayed. Input an existing user name and password, then click "Login".
*From the dropdown list of devices, choose Generic Web Device.
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]

==Troubleshooting==
===Connect failed===
If you try to connect to the Web Orbiter and see this message:
<code>"Connect to proxy orbiter failed, please try again"</code>,
this means that Orbiter generation hasn't finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].

=== Size ===
I was able to change the size of the rendered image in the Wizard-->Orbiters page. Find the Web Orbiter device in the list and resize it. After another orbiter regen, it was the right size for me. (''Source http://forum.linuxmce.org/index.php?topic=3833.0'')

=== Problems with rapid refresh rate ===

Problem:
When using the Web Orbiter over the Internet (instead of from within my home LAN), it refreshed every 5 seconds, making it difficult to use. The images were repeatedly downloaded each time.

Solution:
*Go to [[LinuxMCE Admin Website]]-->Device tree-->CORE-->Generic Web Device-->Device Data
*Set the Refresh Interval to a higher value (I used 60 seconds for mine).

=== Changing default room ===
Changing the default room in the Wizard-->Devices-->Orbiters page has no effect.
Solution:
*Go to [[LinuxMCE Admin Website]]-->Device tree-->CORE-->Generic Web Device
*Check the box for the room to control