| Author |
|
WayneW
Groupie
Joined: March 29 2005
Location: United States
Online Status: Offline
Posts: 50
|
| Posted: June 25 2006 at 12:44 | IP Logged
|
|
|
I seem to have broken my Insteon stuff as I cannot control Insteon devices from the PH "Device Status" screen anymore. I do not see any "Insteon Out" in the event log and I do not see any traffic in the SDM window. PH can receive Insteon signals just fine and it rebuilt the PH database OK. I turned off the background polling for now to reduce the clutter in the SDM window.
I was mucking around with things yesterday, but I don't know how I broke transmit, but not receive. I tried to change from a 2414S serial to a 2414U USB. I thought I had it working, but something (details fuzzy) wasn't working right, so I gave up and went back to getting the 2414S updated with some new devices so I could move it back to my Elk M1.
But then the 2414S was giving me trouble, well actually it was SDM that kept crashing as soon as it was launched. I couldn't resolve that, so I switched from the 226/227 SDM back to the 163 version which had worked pretty well for me.
So:
1) any ideas why I can receive, but not send?
2) can one change from a 2414S to a 2414U with no changes to PH? Or swap 2414S units? It seems like it should all be handled by the SDM, but I am not sure.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: June 28 2006 at 00:00 | IP Logged
|
|
|
Wayne,
You should be able to swap a 2414S for a 2414U and vice versa with no problems but you will need to make some changes. However, it should be relatively simple. Since most devices will probably have links to and from the original PLC, you should use the "Replace Device" function to rebuild all the device links so that the remote devices understand the new PLC and vice versa. You would also need to do the "Initialization" steps in the "Insteon DM Control" window. To swap a PLC for another PLC, this would be the steps:
1. Shutdown PowerHome and make sure SDM is shutdown as well.
2. Disconnect old PLC, hook up new PLC. If new PLC uses a different port (USB, COM, etc.), you'll need to set the SDM to use the new port. Someone just posted a message on the Insteon SDK developers forum (was it you) that had a similar problem where the SDM kept crashing on startup because they had inadvertantly set the port=1 instead of port=COM1. The way to fix this is by directly editing the registry key: HKEY_CURRENT_USER\Software\SmartHome\SmartHomeDeviceManager\ port. Change it to the proper setting and the SDM should be good to go.
3. Once the SDM is properly communicating with the new PLC, restart PowerHome.
4. Go to the Insteon Devices screen and you should see a new device entry for the new PLC which should be POWERLINC2 (the old one should be POWERLINC1). Verify that this is the case.
5. Right click the Insteon Devices screen and open the "Insteon DM Control" window. Select your "controller" ID (different from the PLC ID) and press the following buttons: Download Core Application, Clear PLC Database, and Add ID's to PLC. This will ensure the new PLC has the proper core application, erase any "old" PLC data and update the PLC with all of the proper Insteon device ID's for proper communication (missing this step is probably what is causing you to not be able to send Insteon messages).
6. Exit the "Insteon DM Control" window and go to the Insteon Groups screen. Right-click and choose the "Replace Device" function. Select your old PLC ID (should be POWERLINC1) and select your new PLC ID (should be POWERLINC2). Hit the "Replace Device" button and then wait for all the links to be updated (could take awhile). Use the Controller screen to check for VERIFIED to see when link changes are complete.
7. Back to the Insteon Devices screen, delete the old PLC (or rename it) and change the new PLC from POWERLINC2 to POWERLINC1. Save and you're done.
Let me know how it goes.
Dave.
|
| Back to Top |
|
| |
WayneW
Groupie
Joined: March 29 2005
Location: United States
Online Status: Offline
Posts: 50
|
| Posted: June 28 2006 at 00:34 | IP Logged
|
|
|
Dave,
I have all my switches & KPLs linked to both the powerlinc_usb and the powerlinc_serial, that way both PH and the M1 should be fully aware of all devices. So I don't need to do the "replace device" functions, but I appreciate the detailed steps and will give them a try.. I am having issues with SDM crashing immediately sometimes. What is the minimum firmware your recommend for the powerlinc? Any ideas why PH will not send, but it can receive?
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: June 28 2006 at 13:16 | IP Logged
|
|
|
Wayne,
I gotcha about having both PLC's already linked. Yes, that should be fine and you wouldnt need to do the "Replace Device".
The minimum firmware is 2.12 for the PLC. The 2.9 version will not work properly.
If the SDM crashes immediately, check the REGKEY in the post above and verify the PORT settings. If USB, the proper port setting is USB4. If a COM port, the proper setting would be COM1 for COM1, etc.
When switching the PLC's in PowerHome, at a minimum, you should do the "Clear PLC Database" and "ADD ID's to PLC" from the Insteon DM Control screen. Missing this step could cause the problems with sending. Another possibility on the sending problem could exist if you've defined separate "Controller ID's" for the USB and serial controllers (in the Setup|Controllers screen). If so, then you must make sure that the Controllers dropdown in the Insteon Devices screen matches the active controller ID.
Dave.
|
| Back to Top |
|
| |
WayneW
Groupie
Joined: March 29 2005
Location: United States
Online Status: Offline
Posts: 50
|
| Posted: June 29 2006 at 23:34 | IP Logged
|
|
|
Well, my USB PLC is 2.9, so that explains part of my problems. I don't know what SDM is suddenly so intermittent for me, even with my 2.12 serial PLC. So, my Elk M1 is running fine now, but I still cannot send from PowerHome. I don't know if I will be able to do any troubleshooting until I get a better PLC, but any advice is appreciated.
BTW, I have groups working (192 and up) as a good way to set scenes and control a group at once without the daisy chain timing issues.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: June 30 2006 at 07:16 | IP Logged
|
|
|
I believe SmartHome will take back your PLC and get you one with newer firmware.
|
| Back to Top |
|
| |
WayneW
Groupie
Joined: March 29 2005
Location: United States
Online Status: Offline
Posts: 50
|
| Posted: July 12 2006 at 21:22 | IP Logged
|
|
|
OK, I think I have this all working properly again. I installed a 2414U with supported firmware version. I just had to tell SDM to use USB4 and PH detected the address of the new 2414U and added it to the device list. Then I used the replace device function to move all my links from the old to the new 2414U.
But I still couldn't transmit from PH. I chatted with Tony and we were both stumped. I finally noticed that all my devices had the controller listed as "Insteon_USB", which no longer exists. My current controller is called "insteon_dm". Once I changed all my devices to the proper controller, everything worked. I don't know exactly how my devices got pointed to the wrong controller, but it probably happened while I actually had two controllers in the PH DB. So that is more user error than anything. But once I deleted the "insteon_usb" controller" and shot myself in the foot, could PH be enhanced to report the error of having devices configured to a controller that doesn't exist?
I have no idea how I could receive, but not transmit, but I might have been dealing with multiple issues, so I am not worried about that technicality.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: July 14 2006 at 22:07 | IP Logged
|
|
|
Wayne,
I'll see what kind of error checking/reporting I can add to help in troubleshooting this in the future.
Basically, the way PowerHome works, is any connected controller is capable of both receiving and sending. What the controller column for device is used for is to identify the "default" Send controller that PowerHome will use for commands that don't specify a controller. The ph_devicebtn, ph_insteon, the Device Status screen, etc. will all use the "Default" controller. Functions such as the ph_insteonraw function and others will allow you to specify which controller you wish to use for sending.
So, I don't really think it was user error. When you originally had the "INSTEON_USB" controller, this was naturally the default controller. When you got rid of this device and added a new controller, PowerHome did not automatically update or change the default controller (you may have just temporarily inactivated the controller, etc). So when you tried sending using a function that uses the default controller, it just basically was ignored. Receiving still worked since any connected controller is capable of receiving unless it supports having the receiving turned off.
HTH and I'll look into some kind of checking to help out in this situation.
Dave.
|
| Back to Top |
|
| |
|
|
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: cannot send Insteon from device list
