Help With Insteon Motion sensors

[Michaelv]

I recently replaced my ISY994 with an Eisy after some initial learning curve challenges, I am stuck trying to add the Insteon 2842-222 motion sensors back into the mix. 

During the linking process, it will not automatically detect the sensor after holding the set button down until the LED starts blinking. 

So, I enter the sensors address manually and it will add it to the ISY but I can't get a status when I query it, I can't see any communication when I use the event viewer.  I am right next to an access point when I did this and have even tried to install the sensor right next to a brand new PLM still no luck. 

 

I also have the 5th jumper pin disabled is that correct?

 

Any help would be appreciated.

 

Thanks

 

MV

[Techman]

The 5th jumper when enabled will put the sensor in night only mode, so you most likely want it disabled.

The device status on the admin console will only update when the sensor status changes. You can query it only if it's in the linking mode

You may have to wait for the sensor to time out, then be activated before its status will appear in the admin console.

Edited July 19, 2023 by Techman

[larryllix]

After you put the MS into linking mode you should be able to Query it for a few minutes before it times out. This was done to protect battery drain from constant queries.

Edited July 20, 2023 by larryllix

[Michaelv]

Ok, So I was able to query the Low Battery Node and the Dawn Dusk Node and I can see the status in the admin console. 

When I query the Sensor mode, there is nothing in the Status box in the Admin Console. 

I then created a test program:

I placed the motion sensor directly in front of me as I work at my computer and launched the event viewer Level 3.

This is what the communication looks like.

 

My guess is that all those events are the MS picking up my movements every 30 seconds, but it does not display the devices address and the test program will not run.  I tried a full restore and there was no change.

Any more thoughts?

[Geddy]

1 hour ago, Michaelv said:

My guess is that all those events are the MS picking up my movements every 30 seconds

No, those are just clock entries. Not sure why they're happening, but they remain out of sync. That's been an issue some commented on when the eisy was released.

The only traffic is are the events at 12:46:16 mentioning "Restore".

I just opened my event viewer for a few minutes and get this:

Wed 07/19/2023 02:06:24 PM : [            Time] 14:06:25 1(0)
Wed 07/19/2023 02:06:54 PM : [            Time] 14:06:55 1(0)
Wed 07/19/2023 02:07:24 PM : [            Time] 14:07:25 1(0)
Wed 07/19/2023 02:07:54 PM : [            Time] 14:07:55 1(0)
Wed 07/19/2023 02:08:23 PM : [            Time] 14:08:25 1(0)
Wed 07/19/2023 02:08:53 PM : [            Time] 14:08:55 1(0)

I don't have any motion sensors and had no other Insteon traffic during this time.

[Michaelv]

ok, but isn't that traffic going from Eisy to the Motion detector? How do I know the motion detector can communicate to the Eisy?

[larryllix]

Those are the internal Eisy hardware clock updating the software copy of the time every 30 seconds. With no packet information included in each line, they cannot be from any devices.

Insteon devices are not polled regularly and are 99% push technology. No action = no traffic.

Edited July 20, 2023 by larryllix

[Michaelv]

Ok, that explains that. Any Ideas why the EISY is not receiving the motion sensors on command?

 

 

[Techman]

The eisy should show motion status once motion has been detected. After motion is detected, and the sensor times out, the node should show OFF.

If the sensor is in night only mode you won't get any motion status updates during the day.

[Michaelv]

I checked, Night mode is not enabled. anything else?

[Techman]

Have you tried bringing the MS next to the PLM which will eliminate a communication range issue.

Also when next to the PLM, put the sensor into the linking mode and do a restore device.

Let me know the results.  I have several of the sensors linked to the eisy without any issues.

[Andy P]

This is what the log entry should look like:

Tue 07/25/2023 06:36:46 AM : [55 A9 F 1       ]      DON   1
Tue 07/25/2023 06:36:46 AM : [55 A9 F 1       ]       ST 255 (uom=100 prec=0)
Tue 07/25/2023 06:36:46 AM : [55 A9 F 1       ]      DON   1
Tue 07/25/2023 06:37:22 AM : [55 A9 F 1       ]      DOF   1
Tue 07/25/2023 06:37:22 AM : [55 A9 F 1       ]       ST   0 (uom=100 prec=0)
Tue 07/25/2023 06:37:23 AM : [55 A9 F 1       ]      DOF   1
 

Here are my settings:

Andy

[Michaelv]

I can't even get to the options page. Eisy says can't find it.

[Michaelv]

and yes, I brough the motion sensor right next to the PLM when I tried to add it into the system.

[larryllix]

On 8/1/2023 at 10:32 AM, Michaelv said:

and yes, I brough the motion sensor right next to the PLM when I tried to add it into the system.

Did you put the MS into linking mode?

Is the hardware jumper set to "soft" adjust parameters?

Turn your brightness up to about 70 so you can see LED responses to motion.

Turn your sensitivity up to 70 so it can see motion.

Is your MS set to off mode? It will not return to normal for 495 minutes (you setting) then and you won't see any packets sent.

If your MS times off it must see no motion for at least 30 seconds (your setting) to reset, or it will not send another On signal...EVER. (bug in design)

Edited August 18, 2023 by larryllix