Messages - williammanda

Yes I agree the cost is a deturant at $66 per channel. I talked to someone that had it, basically you use this product to make use of the voip (Skypeout and in) but you can add the Skype friends to your softphone and communicate with them just as in the Skype gui.

... on 7.10 if you installed with CD's you where asked about the network.... on 710 with DVD it installed automatically.... on 810 it installs automatically.

So if you have a core/hybrid with 2 NICs eth0 will connect to the external dsl modem/router/internet. Eth1 will be the internal LinuxMCE DHCP 192.168.80.1 network.

If you want to change this after installation you can make changes using webadmin on the Network page.

Hope this is what you were asking about.

Cheers.

I'm not sure how you install a fresh copy if Kubuntu 8.10 ( not lmce 7.10 or 8.10 ) but I have to install the distro with one nic card. I'm not that good to be able to install Kubuntu 8.10 with the lmce network setup using 2 nic's. If you could be more specific on your setup during the installation using the following: 1. Install Kubuntu 0810 Desktop i386 2. Install all the latest update and upgrades (incl. kernel packages), when prompted after the reboot. 3. Reboot and open a terminal session 4. Become root (sudo -i) 5. Download the latest new installer (wget http://deb.linuxmce.org/ubuntu/new-installer-alpha-latest.tar.gz) 6. Unpack the new-installer (tar xf new-installer-alpha-latest.tar.gz) 7. Change into the new-installer dir (cd new-installer) 8. ./pre-install-from-repo.sh 9. ./mce-install.sh (can take a few hours!) 10. ./post-install.sh 11. Reboot - follow the instructions on screen. 12. If you get a fully black screen (without cursor), look up the wiki on black screen, your monitor is probably not connected to your VGA port)

From my testing last night I used the 1 nic for steps 1 - 10 and reconfigured to the 2 nic setup before step 11. If I'm wrong. please advise.Thanks

HelloI'm trying out the alpha version of lmce 8.10. I have a question about the network configuration. When during the setup do I change from the standard setup ie broadband to router to network card....to the lmce network setup ie broadband to network card 1 from network card 2 to switch? I'm following the directions here:http://linuxmce.org/news.php?id=39#commentsWould it be before the reboot, step 11?ThanksMarty

I had my PLM working with 710, and about 20 insteon devices, about 40% of the time when I would restart the core which is where my PLM is connected, I would lose a device or two on the floor plan. I have looked through all of the ruby code to try and fix this problem, and also add support for the HVAC adapter and for the motion sensor. The time out errors are because the PLM cannot communicate with the device at that address. The chip inside the PLM that sends and receives commands form your power lines is about 75% as strong as the chips all other insteon devices. So even though one device commutates perfectly with another device, It might not be getting the signal to the PLM. I fix this problem in my network, and now it works 100% of the time and even the response time on sending commands is faster. A few ways you can fix this problem.1) Access Points should be located on the 1st receptacle on the line, As close as you can get it to the actual breaker box(this fixed my problem), and make sure one on is on each phase of your power.2) Do not plug the PLM into a surge protector.3) It would be ideal to have the PLM as close to the breaker box as possible.4) Move the PLM to a different line that does not have lots of electronics on it.

After you get the communication problem fixed you should not see the timeout error any more.

I did look at trying to update the driver to support more devices, and I got the HVAC half way working, but I kept running into the problem of not having any link management available. You can link every insteon device from the PLM and never have to go around and push the dumb button in for 10 seconds. I could not figure out a good way to accomplish device linking natively in LinuxMCE, so I stopped working on the driver. I spent a lot of time looking around to see how others are handling insteon networks, and most of them have gone with ISY-99. It has a lot of advantages over using just the PLM. I just received it in the mail last week, and started working on a driver for it.Hope this helps,Chris

Any results on the ISY-99 and also have you tried 8.10 yet?ThanksMarty

I'm not sure if this will help you or not, but here is my experience, I got my basic Insteon setup working on my Hybrid (7.10) using PC serial port, by following the wiki instructions "http://wiki.linuxmce.org/index.php/Setting_Up_PLM_Template" step by step and cleaning the Ruby code first before I pasted in the template, by copying the code from the wiki page to a text file, removing some html code, then I pasted the code from the text file to the template, and I removed code #141 ruby code(CD/DVD) from the template, after rebooting my Hybrid, and linking my "Insteon Outlinc" to my PLM (Serial port), another Hybrid reboot, then I added a lamp to the floor map, and I was able to turn On/Off the lamp which is connected to Insteon Outlinc "http://www.insteon.net/2473SWH-outletlinc.html".

currently i'm trying the same configuration on 8.10 hybrid using default insteon PLM template, with "USB to Serial adapter", I replaced "/dev/ttyS0" on the default template with "/dev/ttyUSB0" with no luck, I know my "/dev/ttyUSB0" is working using

Ok. Over the holidays, I built my core from scratch, changing the main drive to a 500G SATA disk, to allow for recordings from mythtv. Now after I had the core discover all my media drives, and set them up, everything is working great. So I figure I would get my insteon set up running again.

Pinging 192.168.80.1 from the windows machine:Destination is unreachable

This machine was a linuxmce computer. It had no problem getting a ip address from the core and working properly.Thanks

This means it has no routeability to the core's internal IP address, which given that the core is on the same subnet probably means that the XP machine doesn't have an IP address at all, hence no ability to route and so it drops the packets because the destination is unreachable.

This would happen because either:

1) It isn't set to DHCP and still has a static IP that isn't valid for that subnet (ie isn't 192.169.80.x)2) It isn't successfully receiving a DHCP lease3) The NIC port is disabled

1. Not sure2. Not sure3. As I state before, this was a working linuxmce MD that worked.Thanks

All the XP machine needs is to be set to get an IP address/DNS via DHCP. Even if the hybrid doesn't pnp it, it will allow you access to the Internet through the hybrid just fine. Have you set DHCP? What IP address did it get?

The hybrid didn't announce the windows machine.

The default setting for the windows computer is set for obtain ip & dns. DHCP is default also.