| Author |
|
MrGibbage
Super User
Joined: October 23 2006
Location: United States
Online Status: Offline
Posts: 513
|
| Posted: November 02 2015 at 17:58 | IP Logged
|
|
|
I installed a new dual band PLM. Besides a little wrangling with USB COM port numbers, it wasn't too bad. But
when I enabled pending, it took a few hours to get through. But now I have a lot red stuff in my links. See the
screen shot below:
Also, the whole time it was working the pending queue, there were lots of errors with both my new dual band
switches and with my old switches. For the most part, everything was working pretty good before installing the
new PLM. I just wanted to get the dual-band redundancy. I saved 2MB of the raw log to a file here:
http://pelorus.org/insteon_raw_log.txt
__________________
Skip
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: November 02 2015 at 19:40 | IP Logged
|
|
|
Skip,
Looking at your screenshot, nothing too much out of
the ordinary here. The [ID NOT FOUND] merely means
that the device whose Insteon address is 14.85.10 is
not defined in the Devices tab. Whatever this device
is, you'll either want to enter it as a Device in the
Devices tab or if the device truly doesnt exist,
you'll want to delete the links. If the ID is not
FOUND, then the INSTEON TYPE won't be found either.
Both of those errors will go away for that device once
you enter it.
The [INSTEON TYPE NOT FOUND] for your dual band PLM
means that a matching device type was not found in the
Types tab for your dual band PLM. Look at the Devices
tab and check what is selected for your Type for the
PLM. If necessary, create the appropriate type in the
Types tab and then set that type in the Devices tab.
Took a look at your Insteon raw log and for the most
part it looks pretty good. The only errors I found
were Insteon Timeout errors for some devices. This
would be indicative of poor communications for those
devices. An occasional timeout for a device that
really isnt repeated with regularity is normal but
when a device repeatedly gets an Insteon Timeout, that
is an indicator of poor communications with that
device. Either noise on the line or not enough devices
in the area or too far away. Quickly looking through
your log file tells me you've got some comm issues
with the following addresses:
05.DE.A3
13.3A.7C
1D.FE.92
06.D3.E3
13.3A.7C
26.2C.98
with 06.D3.E3 really having some problems. I'd look
into what this device is and where its located. Is it
located near a computer power supply or UPS. Are there
alot of CFL's close by. Is it real far away. Could a
range extender help.
Dave.
|
| Back to Top |
|
| |
MrGibbage
Super User
Joined: October 23 2006
Location: United States
Online Status: Offline
Posts: 513
|
| Posted: November 03 2015 at 19:46 | IP Logged
|
|
|
The 14.85.10 is the address of the OLD PLM that I am not using any more. These "ID NOT FOUND" errors are
on every device in the links tab. Will I need to go to each device in the links and manually delete those
old links? Any idea why they would even be there even though I used the replace address function?
As for the PLM itself, on the device tab, it still says "autodetect type". Soooo, I guess I need to add a
new PLM device on the types tab??? Can you tell me what needs to be there?
I'm looking into those other failed devices. The 06.D3.E3 device is my foyer light, which is right next
to my study where we have three computers on 24/7, plus a bunch of other stuff. I see it is on right now
so it came on at sunset like it is supposed to, so it's not completely dead. But I have had a feeling it
will need replacing soon.
__________________
Skip
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: November 04 2015 at 19:14 | IP Logged
|
|
|
Skip,
Not sure why the old PLM links would be there if you used the Replace Address function. It should have changed the old PLM address to the new PLM address.
In any event, before deleting them, it would be best to make sure that the link truly exists. You should be able to highlight one of these links and then press the Reverify
button. PowerHome will query the remote device and see if the link truly exists. After PowerHome verifies the link if the status of the link in the remote device (it will be the
blue column either Ctlr or Resp depending upon if its a Controller or Responder link...in any event, it will the blue column) changes from VERIFIED then the link doesnt actually
exist in the device and its just residual within PowerHome.
The easiest way to correct this is to actually temporarily recreate the device in the Devices tab and then close/reopen the Insteon Explorer. With the device added to the Devices
tab, you can now make this temporary device the "Currently selected device" in the Links tab. This will then show ALL the links (Controller and Responder) associated with this
Insteon address (this saves you from going the other way to multiple Insteon devices and fixing a couple of links per device).
Depending upon if the link is actual (the verify operation resulted in VERIFIED in the blue column with the remote device the currently selected device) or the link is bogus (link
not found in the blue column of the remote device), you'll fix it a couple of different ways. If the links are real, then highlight ALL the controller and responder links and drag
and drop them to the left hand listview. If the links are bogus, highlight all the links and drag/drop (or just press) the "Remove" button. Press Save. If you "Deleted" the links,
PowerHome will communicate with every device and actually delete them from the device database. If you "Removed" them, then PowerHome just deletes them from the PowerHome
database.
No need to add a new PLM device type in the Types tab. You can just select one of the existing PLM device types as it won't really be used for anything (just make sure you choose
an existing PLM vs a PLC device type). If you want to have a new type that actually matches the actual device, you can go to the Types tab and create a new device type modeled
after an existing PLM device type and give it an appropriate description. You'll need to close and reopen the Insteon Explorer in order for the new type to appear in the dropdown
of the Devices tab.
I wouldnt think it would be completely "dead". Otherwise, it would get flagged COMM disabled in the Devices tab. I would definitely check out the Insteon communication reports.
You'll pretty quick which devices are having issues. If your configuration has recently changed (alot of new devices, devices moved around, etc), you may want to clear all the
communication stats and let them rebuild so you have current accurate data in the reports.
Hope this helps,
Dave.
|
| Back to Top |
|
| |
|
|
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: Installed new PLM, Links look wonky now
