Jump to content

motion sensors not recognized after network module installed


johnnyt

Recommended Posts

All of a sudden none of my 4 motion sensors are being recognized by ISY. I don't know if it's related but it happened right after I added the network resources module and set up ISYAJAX for use with my iPod Touch as well as used the Function Exporter for some Sonos interaction. I suspect a pure coincidence but mention it - and post here - just in case there's a link.

 

I have 2 access points plus a dual band PLM and a dual Switchlinc in a ~2400 sq ft home that has been working almost flawlessly since I moved to Insteon last fall after 10 years of using X10.

 

Have unplugged and re-plugged the access points (after waiting at least 10 secs off) and confirmed (again) that there are on different phases, for what that’s worth.

 

I did notice that the access points are quite warm on the wall side when I unplugged them. Could they be working too hard for some reason? How can I find out? I’ve not added any motors or other electrically noisy equipment to my house. Also the ISY does not show any abnormal activity (with event viewer set to "Device communications events".)

 

Any suggestions, or known issues with network module use?

Link to comment

a couple more things about this.

 

1. I also have a dual band Lamplinc, so in other words 3 dual band devices + 2 access points

 

2. pressing switches/buttons is not updating the status in ISY and not activating any related programs, where applicable. In other words, the insteon signal does not appear to be recognized by ISY. I've tried many buttons so am pretty sure I've covered both phases. None work.

 

Scenes involving multiple devices are all working fine. I can manually run the program and that works too. As well I can query the device and the proper status does get updated in ISY.

 

What could be going on? Could it be a defective PLM? (I just ordered one as insurance but it hasn't arrived so I can't test that theory)

Link to comment

interesting. there were 31 links that were all "FF FF..." so I did a PLM restore, which appears to have fixed the problem. (I have 177 links now - hopefully that's all of them)

 

interestingly the restore procedure requires that I put my all motion sensors in linking mode, however the motion sensors appeared to link to each other and not go into steady linking mode. huh? now, of course, none of my motion sensors are recognized by ISY. I guess I'll have to re-add them one at a time. (don't have time right now so it'll have to do it later)

Link to comment

Hello johnnyt,

 

This usually points to a defective PLM (unless you actually factory reset your PLM yourself).

 

If you restore the same PLM, then in most cases (if nothing has changed), ISY does not touch the end devices. It simply recreates PLM links as it thinks the PLM should have it.

 

With kind regards,

Michel

Link to comment

Thanks for the reply.

 

When you say a "defective PLM", does that mean it's on its way out? is it just a matter of (a short) time before it does this again? should I replace it?

 

Also, I am expecting a new PLM any day now (a potentially timely insurance purchase I made). I assume that's like doing a factory reset. How does that make things different?

 

Thanks again.

Link to comment

okay, forget the 177 links I said earlier. There are 2065 links in my latest count. Yikes! I have about 48 devices.

 

That seems like a lotta links! Did I read somewhere before that PLM's start to give you grief above 800 links? I can't search the forum using the word "links" to find the reference; it ignores that word.

Link to comment

Do you have a 2412S PLM or a 2413S PLM?

 

The original 2412S PLM had a 417 link database.

 

Newer ones a >2000 link database. The Quick Users Guide just says >2000. The sales page for the 2413S now says >800 2412S implied here and 1023 for the 2413S?

 

2413S 1023 link database.

 

2065 sounds strange and is too big for even the later 2412S PLM that could be no larger than 2048.

Link to comment

Insure there is NO Insteon traffic when looking at PLM link records. It has been determined through testing that Insteon messages received by the PLM while the link records are being read will reset the "Next Record" pointer causing PLM link records to be skipped or duplicated. A 2412 PLM does not have memory large enough to hold 2065 records.

Link to comment

It could take two FilterLincs. Some folks have reported a single FilterLinc not being enough to block all traffic. When the Show PLM Links Table (with count) produces the same number 3-4 times the number can be considered accurate.

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...