Argh! All is now well. Thanks Techstyle. You were correct and the wiki supplied the answer.  I can now grab my laptop and IP address 192.168.80.129 accesses the internal router. 192.168.1.1 accesses the external router. Problem solved.

Twodogs (embarrassed)

I'm trying to correctly set up two wireless networks with two WRT54GS routers. The first is external to LMCE , so that my wife can always log on regardless of what I'm doing with LCME. The second is the internal LMCE network. I have this partially working, but I always get locked out of the the web-based configuration utility of the LMCE router. If I need to get in, then I have to hit the button that resets it to factory. Seems like I'm doing something wrong. Here is my network configuration:

-DSL Modem
-WRT54GS external, set up as router ( DHCP server enabled, wireless chan 1, IP 192.168.1.1, with its own SSID and security password)
-LMCE Core
-WRT54GS internal, set up as wireless access point (DHCP server disabled, wireless chan 11, IP 192.168.1.2, with its own SSID and security password)

I thought this was the correct way to configure the network, but it behaves strangely.  I can connect my laptop to the internal wireless network and surf the web just fine, but when I try to enter the configuration utility I get "Firefox can't establish a connection to the server at 192.168.1.2." So I turn off the wireless on the laptop and connect via cable. Again I can surf the web just fine, but I get the same error when trying to connect to the WRT54G.

Now I check to see if I can access the external router from the internal network. I thought that this might not work because if could be invisible behind the LMCE core. I enter 192.168.1.1 and get right in to the config utility of the external router.  This blows my mind.

So the bottom line is that I can reach the configuration utility of the external router (set up as a DHCP enabled router) from either the internal or external network. I can't reach the config utility of the internal WRT54GS (set up as DHCP disabled WAP) from either the internal or external network until I do a factory reset and dump my config.

This differs from my expectations. I thought that, to reach the external WRT54GS, I'd have to connect to the external network and enter 192.168.1.1. Then to reach the internal WRT54GS, I'd have to connect to the internal network and enter 192.168.1.2.

Can any smart guys show me the error of my ways?

Things are working now. Not sure what caused the initial problem. When I first plugged in the DNS-321 it did not correctly plug and play. LMCE Admin showed that the NAS was in the unknown device list. I clicked the "unlock" button and reloaded the router, but this did not fix the problem. Manually clearing the PnP queue was what finally worked. I installed the device using the LMCE file structure. Then I ran into a problem with my Mint desktop machine that would not let me browse or add files to the NAS. The fix was simply right-clicking and unmounting the NAS folder, then opening it up again. I've copied all my videos over to the NAS and all is well.

Just fyi, while troubleshooting this, I plugged in my Synology DS207+ and this was immediately detected. I told LMCE to ignore it, because I'm going to use the Synology to store backups.

I set up the DNS321 as a samba share. Is there any advantage to using NFS instead? Also, jumbo frames are disabled in the default configuration. Any reason to mess with this?

See my previous post. I just cleared the database and it seemed to get things working. I expected to be able to browse to the file structure that LMCE should have installed on the NAS, but my desktop computer is whining about an unrecognized file type.

Making progress. I found the NAS in the unknown devices list. I also found a year-old post from tschak and gave it a shot.

Currently there is a bug which prevents the storage radar from finding the NAS again, if it has made it into the PnpQueue table, for now, do this:

Code:

mysql -uroot

mysql> use pluto_main
mysql> DELETE FROM PnpQueue;

Then reload the router.

PnP found the device and asked if I wanted to use it. I told it to use LMCE file structure and I think its good to go. My only issue now is how to get my movies over to it. I though I could drag and drop using my desktop computer (running Mint at the moment). No such luck yet.

Thank you for that. I'll start digging into it. I plugged in a Synology NAS to see if it was recognized, and it was. LMCE also asked me about using my desktop computer and my laptop, so I think my LMCE install is good - its a fresh install so I haven't had time to pork it up yet! I had already concluded that it had to be a problem with the DNS321 configuration. The most detailed LMCE wiki on D-link NAS's is for 0810 so I didn't know if setup was still the same.

I'm trying to install a DNS321. I just reset it to factory settings, and I just re-installed LMCE 1004 final. I connected the NAS to the internal LAN, but PNP does not recognize it.  I checked DHCP leases in LMCE admin and see that the NAS has been assigned 192.168.80.133. I can use that IP to access the NAS admin page. I can also browse the NAS on my home network. I expected that LMCE would recognize the device and ask if I'd like to use it for TV, movies, etc but its not happening. I'd like some advice on troubleshooting this.

I've been digging around in the documentation.

http://wiki.linuxmce.org/index.php/How_to_add_your_own_GSD_device

If your Ruby code contains an error, LinuxMCE may decide to disable the device. So, check that your device is not disabled: on Wizard-->Devices-->Generic Serial Devices click on "Advanced" for your device and make sure the Disabled box is NOT ticked. If it is, untick it, save, and do a quick reload of the router.

Turns out the device was disabled. I guess that might mean an error in the ruby code on the template. Unticking the box and reloading the router allows me to send commands to the device. I'll have to get it off my test bench, plug things in and see if it is completely functioning now.

Thanks for those suggestions. I did not know about the "dont detect serial ports" option. Good info.

However...

The only way I've been able to send commands to the receiver is to install with the script. I have just enough time (before the next PNP script activation) to open webadmin, select the device, and send a command or two. Oddly, even though the receiver works, the template says "please select" in the comm port box (in both the AV and GSD device. When I select ttyS0 and update the template, then I find that the GSD template has been automatically updated with ttyS0. But after issuing a reload router, the Yamaha no longer responds to commands.

Next I tried the "don't detect serial port" option. I added the GSD manually, but again the Yamaha does not respond.

Found a screaming deal on a Yamaha RX-V1700 with HDMI switching, so I'm replacing my old Denon AVR-3805. I'm using a null serial cable (not a USB adapter) to connect. After a few minutes, the pnp script starts searching to see what has been added. It correctly identifies the Yamaha and the wizard starts. After the router reloads I can go into webadmin and send commands to the receiver. But then the pnp script starts up again, so the receiver is effectively stuck in installation limbo. Any ideas about what's going on?

Twodogs

Dave,

It would be great to see a short wiki page on how to use the DSC. Most of the LMCE info is on Honeywell, who stopped making the internet connection module (ebay prices are sky high).

John

I'm curious if you figured this out. I'm still trying to make sense of Insteon, but I had a light switch that deleted itself. It only worked after I cross linked the devices (switch to PLM, then PLM to switch).

Perhaps we should make a wiki page with a chart so that everyone can rate their user experience? I think this would be valuable info for both users and devs to see at a glance exactly how LMCE is being employed, and how well things are working. Something like the following (couldn't figure out how to make a chart). We could rate each item on a scale from 1 to 10 (or Not Applicable if you have no experience with something). We'd probably need a lot more columns, but this gives the idea. If we get a significant number of users to fill in their info, we could scan the columns to identify features that are completely unused, popular features that work great, and popular features that work poorly.

User              lights,            movies,           music,          mythtv,         hulu,          satellite/cable box,         climate,           security,           webcams,          telecom
Twodogs         5 (insteon)        9                   2                  0                NA               NA                              NA                    NA                   NA                  5

Success!

I disconnected everything and reset to factory default. Then I connected PLM and Switchlink and crosslinked them. Then I connected to LMCE core and recreated the PLM device. I checked the PLM log to see if it found the hex address of the Switchlink - it did.

I used admin to manually add a light switch device. When I reset the router and returned to admin to look at the device, I saw that the configuration box had been magically filled in (no longer just asterisks). The light did not work at first, so I thought I still had problems. But after a few minutes, I had a working switch. I wish I could say that I identified and solved the problem I was having - maybe the insteon devices were not properly crosslinked.

I'm trying to follow the written guidance but having no luck. Here is now I spent the evening.

• Reset the modem to default (unplug for 10 sec then plug back in holding the reset button for 3 seconds). By the way, modem was serially connected to LMCE during the reset. Seems to go OK.
• Reset the light switch to default (press top paddle for 10 sec, then tap reset button, then push and hold reset button for 10 seconds). Seems to go OK.
• Create PLM device (admin, template 1932, select serial port 0 for my installation). Seems to go OK - software downloads, logs are filled with code, LED on PLM shows activity.
• Plug in the insteon light switch. Nothing magically happens. I think this is normal - have to link the switch to the PLM.
• Link the switch to the PLM (press/hold paddle on light switch until the led on the switch starts blinking, press/hold set button on PLM until its LED flashes).
• LMCE reset router to see if light magically appears. It doesn't.
• Maybe I have to crosslink the switch (press/hold set button on PLM, then press/hold paddle on light switch).
• LMCE reset router to see if light magically appears. It doesn't.
• Manually create light switch device (admin, light switch template, enter six digit hex code from sticker on light switch)
• LMCE reset router. I look in admin to check the newly added light. The "configuration" box is just asterisks (***************). Switch doesn't work.

Can anyone spot what I'm doing wrong?