Communication Issue with Motion Sensor

[rorichmond]

Running v4.4.5 of both the UI and firmware on an ISY994i.

 

Getting the following error when I try to change the options on a motion detector:

 

Cannot communicate with <device name here>. Please check connections.

 

The device reports on and off status perfectly, but I cannot change the options. Here are the logs (you can see me trigger the motion detector at the end). Any ideas?

 

Wed 03/23/2016 05:04:49 PM : [All         ] Writing 1 bytes to devices

Wed 03/23/2016 05:04:49 PM : [iNST-TX-I2CS] 02 62 31 DC E3 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9

Wed 03/23/2016 05:04:49 PM : [iNST-ACK    ] 02 62 31.DC.E3 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 06        (00)

Wed 03/23/2016 05:04:58 PM : [iNST-TX-I2CS] 02 62 31 DC E3 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9

Wed 03/23/2016 05:04:58 PM : [iNST-ACK    ] 02 62 31.DC.E3 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 06        (00)

Wed 03/23/2016 05:05:07 PM : [iNST-TX-I2CS] 02 62 31 DC E3 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9

Wed 03/23/2016 05:05:07 PM : [iNST-ACK    ] 02 62 31.DC.E3 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 06        (00)

Wed 03/23/2016 05:05:11 PM : [D2D EVENT   ] Event [31 DC E3 1] [ERR] [1] uom=0 prec=-1

Wed 03/23/2016 05:05:11 PM : [  31 DC E3 1]      ERR   1

Wed 03/23/2016 05:05:15 PM : [iNST-SRX    ] 02 50 31.DC.E3 00.00.01 CF 11 01    LTONRR (01)

Wed 03/23/2016 05:05:15 PM : [std-Group   ] 31.DC.E3-->Group=1, Max Hops=3, Hops Left=3

Wed 03/23/2016 05:05:15 PM : [D2D EVENT   ] Event [31 DC E3 1] [DON] [1] uom=0 prec=-1

Wed 03/23/2016 05:05:15 PM : [  31 DC E3 1]      DON   1

Wed 03/23/2016 05:05:15 PM : [D2D EVENT   ] Event [31 DC E3 1] [ERR] [0] uom=0 prec=-1

Wed 03/23/2016 05:05:15 PM : [  31 DC E3 1]      ERR   0

Wed 03/23/2016 05:05:15 PM : [D2D EVENT   ] Event [31 DC E3 1] [sT] [255] uom=0 prec=-1

Wed 03/23/2016 05:05:15 PM : [  31 DC E3 1]       ST 255

Wed 03/23/2016 05:05:15 PM : [iNST-SRX    ] 02 50 31.DC.E3 00.00.01 CF 11 01    LTONRR (01)

Wed 03/23/2016 05:05:15 PM : [std-Group   ] 31.DC.E3-->Group=1, Max Hops=3, Hops Left=3

Wed 03/23/2016 05:05:15 PM : [iNST-DUP    ] Previous message ignored.

Wed 03/23/2016 05:05:16 PM : [iNST-SRX    ] 02 50 31.DC.E3 3D.C8.19 45 11 01    LTONRR (01)

Wed 03/23/2016 05:05:16 PM : [std-Cleanup ] 31.DC.E3-->ISY/PLM Group=1, Max Hops=1, Hops Left=1

Wed 03/23/2016 05:05:16 PM : [iNST-DUP    ] Previous message ignored.

Wed 03/23/2016 05:05:16 PM : [iNST-SRX    ] 02 50 31.DC.E3 11.01.01 CF 06 00           (00)

Wed 03/23/2016 05:05:16 PM : [std-Group   ] 31.DC.E3-->11.01.01, Max Hops=3, Hops Left=3

Wed 03/23/2016 05:05:16 PM : [iNST-INFO   ] Previous message ignored.

Wed 03/23/2016 05:05:16 PM : [iNST-SRX    ] 02 50 31.DC.E3 11.01.01 CF 06 00           (00)

Wed 03/23/2016 05:05:16 PM : [std-Group   ] 31.DC.E3-->11.01.01, Max Hops=3, Hops Left=3

Wed 03/23/2016 05:05:16 PM : [iNST-INFO   ] Previous message ignored.

 

 

 

 

[LeeG]

Was the Motion Sensor placed into linking mode and Jumper 5 in place before changing Options?

[Teken]

I am assuming you pressed the set button to wake up the battery device? If you use the remote write update device this must be invoked using a program.

 

A wait from 0-3 seconds must be used so a little trial and error is possible. 

[rorichmond]

Had no idea I needed to put the device in linking mode before writing to it. First time with one of these. That did it!

 

Thank you!

[LeeG]

Happy to help.   Battery powered devices "sleep" to save battery power.  Putting a battery powered device into linking mode usually keeps the device "awake" for approx 4 minutes so it can be queried or updated.   

[Teken]

Had no idea I needed to put the device in linking mode before writing to it. First time with one of these. That did it!

 

Thank you!

 

As noted you can also use the remote write device option in the programs area too. This avoids the whole climb up a ladder, remove the screw, door, and pressing the set button.

 

All you need to do is walk by the MS FOV and it will force the unit to remain awake for 4 minutes to allow any pending writes to take hold. Again, you need to play around with the wait period which can range from 0-3 seconds for it to work.

 

Lastly, any battery only device which has the heart beat function can also be used to initiate a pending write. The only caveat to this method is you will need to wait 24 hours for the update to happen. It goes with out saying a strong Insteon RF mesh must be present otherwise the signal will never arrive or be received.

 

The hidden door sensor has the ability to reduce the heart beat interval from 24 hours but doing so will reduce its battery service life.

[rorichmond]

 

All you need to do is walk by the MS FOV...

 

So triggering the motion detection will keep it awake for 4 minutes? The timer on mine was set to 1 minute out of the box - I wonder if I had just continued moving in front of it, if that would have kept it awake?

[stusviews]

The MS is awake during the very short time it takes to send an On signal (if it's in that mode). Linking requires that the device be kept awake continuously during the linking process. Putting the device into linking mode keeps it awake for four minutes in the even there are any power line interruptions that slow the process (require resedning).

[larryllix]

So triggering the motion detection will keep it awake for 4 minutes? The timer on mine was set to 1 minute out of the box - I wonder if I had just continued moving in front of it, if that would have kept it awake?

Different timer function.

 

The timer you refer to is the hardware timer before the MS sends an Off signal to Insteon devices after last seeing motion. Most of us place jumper 5 on the two pins and transfer all control to ISY for setup, disabling the hardware (inside MS) setup dials and Off sending options. Most also disable the send Off option and let ISY do  the Off of the devices. Saves batteries and less Insteon traffic.

 

This is a time window newer battery devices have after seeing motion that ISY can do an attention grab to set parameters in the battery operated device. This time is not settable.

[rorichmond]

So how exactly do I (bear with me, I am still learning here) wake the MS up for 4 minutes using a program? Not having to climb a ladder is a compelling reason to take the time to learn this...

[larryllix]

So how exactly do I (bear with me, I am still learning here) wake the MS up for 4 minutes using a program? Not having to climb a ladder is a compelling reason to take the time to learn this...

IIRC you need the Pro module to have this feature. I have never used it, yet, so perhaps somebody else could chime in here.

[LeeG]

rorichmand

 

Example of a Program I use to write updates to Motion Sensor when motion is triggered.   The Program is gated with a time range so the process is limited to work only when I know I have pending updates.

 

UpdateMS - [iD 0075][Parent 0001]

 

If

        Control 'MS I2CS-Sensor' is switched On

    And From    10:00:00AM

        For      1 hour 

 

Then

        Set 'MS I2CS-Sensor' Write Device Updates

 

Else

   - No Actions - (To add one, press 'Action')

[Teken]

So how exactly do I (bear with me, I am still learning here) wake the MS up for 4 minutes using a program? Not having to climb a ladder is a compelling reason to take the time to learn this...

 

To further add to what LeeG has offered above I would like to note another consideration. Sometimes the user, condition, or the method the hardware is set up in requires that you monitor one or all three states.

 

Meaning if you watch for the *ON* signal there may be situations where it doesn't work. Case in point if the MS is programmed to only send a ON. So its best to monitor both On-Off conditions which increases your chances of a successful device write.

 

Also, you can also use the Dusk to Dawn node to activate the remote device write update  . . . I call this out because sometimes there are specific (user) environmentals that impact the success of the above feature.

 

Good luck . . .