Using 2868-222 Siren

[j.rieff]

I just updated my ISY to Version 5.0.16C. So far everything is going OK 

I have an application to alerts me when the dog wants to come in at the kitchen back door. I am using a Motion Sensor II and a 2868-222 Siren (in Chime Mode). Prior to the firmware upgrade, the Motion Sensor II features were limited to the Motion Sensor I features. Basically, ON-OFF motion detection. The 2868-222 was not in the list of devices in Version 4.7.3. Therefore, I manually linked these 2 devices together. At that time, there was no scene that involved these 2 devices. Everything work basically OK. I occasionally would also detect a bird that wanted to roost above the door and an occasional squirrel that would run by the door. 

After upgrading the firmware, I updated the Motion Sensor II to include the features available and installed the 2868-222 into the Insteon Network in the ISY. I also created Scene where the Motion Sensor II was the controller and the Siren was the responder. I also set the options for the Siren for Chime rather than Siren. Motion is detected, but the Chaime is not activated. Did I miss something (probably in the Motion Sensor setup - I have it to be connected Always and to Report ON and OFF).

 

Suggestions are much welcomed. 

[kclenden]

Did you delete the manual links in the MS II and Siren (or factory reset both devices) before creating the new scene using v5?

[Teken]

I just updated my ISY to Version 5.0.16C. So far everything is going OK 
I have an application to alerts me when the dog wants to come in at the kitchen back door. I am using a Motion Sensor II and a 2868-222 Siren (in Chime Mode). Prior to the firmware upgrade, the Motion Sensor II features were limited to the Motion Sensor I features. Basically, ON-OFF motion detection. The 2868-222 was not in the list of devices in Version 4.7.3. Therefore, I manually linked these 2 devices together. At that time, there was no scene that involved these 2 devices. Everything work basically OK. I occasionally would also detect a bird that wanted to roost above the door and an occasional squirrel that would run by the door. 
After upgrading the firmware, I updated the Motion Sensor II to include the features available and installed the 2868-222 into the Insteon Network in the ISY. I also created Scene where the Motion Sensor II was the controller and the Siren was the responder. I also set the options for the Siren for Chime rather than Siren. Motion is detected, but the Chaime is not activated. Did I miss something (probably in the Motion Sensor setup - I have it to be connected Always and to Report ON and OFF).
 
Suggestions are much welcomed. 

When you go into the device tree are there any pending writes for the MS II? When going to the scene which links the two do you see both devices called out as controller / responder?

Lastly, you can delete both units from the scene than add them back to confirm they are correctly linked. Always check the level 3 logs to help trouble shoot Insteon activity.


Sent from my iPhone using Tapatalk

[j.rieff]

@kclenden and @teken - I thought I did all of this and checked for pending writes. I made sure the Motion Sensor was in setup mode whenever I made a change. The scene does correctly show the sensor as the controller and the chime as the responder. 

However, I am not quite sure if I did the factory reset of the Chime device. So, that is what I will do now. I will also clean out the scene then "recreate" it. I will add the motion sensor first as the controller then the chime as the responder. 

 

Thanks for all the help. 

[Teken]

@kclenden and@teken - I thought I did all of this and checked for pending writes. I made sure the Motion Sensor was in setup mode whenever I made a change. The scene does correctly show the sensor as the controller and the chime as the responder. 
However, I am not quite sure if I did the factory reset of the Chime device. So, that is what I will do now. I will also clean out the scene then "recreate" it. I will add the motion sensor first as the controller then the chime as the responder. 
 
Thanks for all the help. 

Let us know how it all ends and the root cause. As I am sure someone else can benefit from the very same!


Sent from my iPhone using Tapatalk

[j.rieff]

Here is what I did and the results.

1. I removed the Chime/Siren from the Scene.

2. I removed the Chime/Siren from the ISY Network.

3. I removed the Motion Sensor II from the Scene (made sure it was in Setup Mode).

4. I performed a Factory Reset on the Chime/Siren according to the Documentation instructions. 

5. Added the Chime/Sirent to the ISY Network. When I add this device, there are actually 6 sub-devices added. The odd numbered sub-devices have bell (probably a chime) icon associated with it in the tree. The even numbered devices have what looks like a shield. Everything I performed with relationship to the Chime/Siren is with the device with ".1" associated with the name. 

6. Added the Motion Sensor II to the Scene (made sure it was in Setup Mode).

7. When everything stabilized, I performed a test - result as a 10 Second Siren.

8. I went to the Scene and highlighted the Chime. Three options were presented: Duration (default = 10 seconds), Delay (default = Immediate), and Tone (default = Siren).

9. I changed Duration to 1 second and Tone to Chime (making sure Motion Sensor II was in Setup Mode)

10. Result - motion detected with a 10 second Siren.

11. Found a pending write to another Motion Sensor II that was updated after upgrading to firmware version 5.0.16C. Put that device into Setup Mode and performed a Write Changes to the device. 

12 Another test - motion detected with a 10 second Siren.

 

[j.rieff]

@teken - I "dumped" the Log Files. How do I find Level 3. There only errors I see pertain to NTP DNS errors. 

[Brian H]

Level 3 is one of the choices in the Event Viewer. You may get some helpful information. By opening the Event Viewer then pick Level 3 in the choices of what is captured.  It will capture things like what happens when you change a parameter and then write the updates to the devices. It will also capture what messages are happening when you have the motion sensor try and trigger the siren. Mine seems to stay in Level 3 when the Event Viewer is closed. Probably until a close the Administrative Console.

After you do some things. You can open the Event Viewer and Click on the small icon near the bottom that look like a clipboard. What is in the event viewer has captured will be written to the clipboard or select the write to log choice and a log with the information will be created.

What revision firmware is reported for the motion sensor and siren modules. In the Administrative Console. My siren modules are early ones I did manual links until the ISY V5 firmware was released. 2 of my siren modules are v45 and three are v46. I know the siren modules acted differently between the two firmware revision through manual linking.

[Brian H]

I did a test with an MS II and a Siren module. MS II firmware v.47 and new enough to have the two pin Range  jumper below the USB connector. Siren firmware v.46
Added both to the Administrative Console.
Created a Scene Chime Test.
Add the motion node 1 for the sensor as a controller and the siren Siren Trigger Home node 1 as a responded. To the Scene.
Changes made to the Motion Sensor node 1 settings,  in the Scene. Not the main Scene settings. As the choices seem to be in two location.
Set the siren the chime.
Do updates. Every time I change something. Sensor is linking mode to wake it up.
Chime sounds 10 seconds.
Change the duration to 1 second. No chime duration too short.
Change to duration 2 and I get a 1-2 second chime.
Change to 15 seconds and then get a 15 second chime.

 

[j.rieff]

Thanks @Brian H I should have remembered to look at the device settings inside the Scene after selecting the device from the Scene mapping in the Admin Console. I learned that lesson when setting up 3-way and 4-way switch configuration using Insteon Switches since they do not use the traveler wires. Took me the longest to get all the ramp rates syched until I realized you need to look the device level in addition to the Scene level. I will pain that brain cell a neon color so I remember it in the future. 

It is really funny the Duration must be 2 seconds for the Chime. 

Bottom line - it works now. 

 

BTW - also thanks for the insight into Level 3 info in the Event Viewer. I looked at that before, but had not pursued it much. There is definitely lots on info in that Event Viewer. Probably will be one of my Go To troubleshooting sources when I add new features.

 

So far, everything is going well with Version 5.0.16C. I was really apprehensive given a lot of the comments I read in the Release thread. 

[Teken]

7 minutes ago, j.rieff said:

Thanks @Brian H I should have remembered to look at the device settings inside the Scene after selecting the device from the Scene mapping in the Admin Console. I learned that lesson when setting up 3-way and 4-way switch configuration using Insteon Switches since they do not use the traveler wires. Took me the longest to get all the ramp rates syched until I realized you need to look the device level in addition to the Scene level. I will pain that brain cell a neon color so I remember it in the future. 

It is really funny the Duration must be 2 seconds for the Chime. 

Bottom line - it works now. 

 

BTW - also thanks for the insight into Level 3 info in the Event Viewer. I looked at that before, but had not pursued it much. There is definitely lots on info in that Event Viewer. Probably will be one of my Go To troubleshooting sources when I add new features.

 

So far, everything is going well with Version 5.0.16C. I was really apprehensive given a lot of the comments I read in the Release thread. 

So, this is considered a success / win??

[Brian H]

Glad you got it working.

 

[j.rieff]

@Teken

I would consider this a win. Brian discovering 2 seconds for Chime duration was one of the magic keys. The other was the reminder to look at the device settings within the Scene (at the device level within the Scene mapping) beside just looking at the parameters at the Scene level. 

 

Thanks for your inputs. Always look forward to your insights and recommendations. Now, onto using the Motion Sensors that are outdoors to help determine when to turn on some indoor lights. I know this is really just finding the right sensitivity sweet spot. 

[Brian H]

Are your Motion Sensors new enough to have the two pin jumper header  below the USB connector? Present manual indicates putting the  jumper On reduces the sensing range by approximately ten feet from its normal range.

[j.rieff]

Have not noticed if such a jumper pin is present. I picked up most of the MS II around mid-year 2019. Interesting to know that feature. Did not see that feature in the documentation I downloaded when I acquired my first MS II in late 2017.

[Brian H]

My original MS II manual I downloaded when I accessed the FCC  Database. Did not mention it.

The one I downloaded recently after finally buying one. Is dated 8/15/19 and shows the jumper configuration. Mine was stored on one of the two pins. For use if I wanted to use it. Another user reported not having one on  the two pins. I also found a second one floating around the  carton. I suspect some where missing the jumper in assembly and they added a loose one in the box.

[dbwarner5]

On 2/10/2020 at 3:25 PM, j.rieff said:

Thanks @Brian H I should have remembered to look at the device settings inside the Scene after selecting the device from the Scene mapping in the Admin Console. I learned that lesson when setting up 3-way and 4-way switch configuration using Insteon Switches since they do not use the traveler wires. Took me the longest to get all the ramp rates syched until I realized you need to look the device level in addition to the Scene level. I will pain that brain cell a neon color so I remember it in the future. 

It is really funny the Duration must be 2 seconds for the Chime. 

Bottom line - it works now. 

 

BTW - also thanks for the insight into Level 3 info in the Event Viewer. I looked at that before, but had not pursued it much. There is definitely lots on info in that Event Viewer. Probably will be one of my Go To troubleshooting sources when I add new features.

 

So far, everything is going well with Version 5.0.16C. I was really apprehensive given a lot of the comments I read in the Release thread. 

@j.rieff I should have been clearer on my first response to you last month.. here is a screen shot of the SCENE set up that allows control of either siren or Chime. I have had not problems with this. You can have different scenes and choose different options within each scene and the siren responds accordingly. 

 

[j.rieff]

@dbwarner5 and @Brian H

 

Thanks for all your help. Now on to the next fun task as soon as I figure it out. Look for more requests for help in the future.