Hophead Posted November 20, 2013 Posted November 20, 2013 OK, so I'm not having any luck getting communication from the smoke bridge to the ISY. I've got one smoke alarm and one smoke bridge. I can ge the bridge to link to the alarm. I know its linked because the LED flashes red on the bridge when I test the alarm. When I add the device to the ISY it seems to add ok and I get 3 nodes (smoke, CO, & battery), but none of them show their state. I also don't see any traffic in the event viewer when I test the alarm (although I do see traffic for the bridge when I add the device). I've tried resetting the bridge back to factory defaults and I've tried adding the bridge through "start linking" and "new insteon device" but I'm not having any luck. Anyone have any other ideas? Thanks.
LeeG Posted November 21, 2013 Posted November 21, 2013 There should be 7 nodes for the Smoke Bridge. What does Help | About show for the ISY Firmware and UI levels. Sounds like the UI (Admin Console) is not at the required level.
Hophead Posted November 21, 2013 Posted November 21, 2013 Thanks Lee! I should have known to look at the FW. I go through this with customers at work using our servo drives. I thought I have upgraded before when I got the ISY back in April. I was at 3.xx for the ISY. I loaded the FW and have v4.0.5 for the ISY and v4.0.11 for the UI. I get all 7 nodes and I have the same results as junkycosmos. When I do a test, I see traffic in the event viewer and the test node shows an ON state but never goes to OFF. None of the other nodes have a value for current state. Is this normal?
LeeG Posted November 21, 2013 Posted November 21, 2013 Right click the node and select Query. As I remember that does not generate traffic to the Smoke Bridge but does reset the node to Off. Again from memory tapping the Smoke Bridge Set button causes it to send On or Off messages to several of the nodes.
Hophead Posted November 21, 2013 Posted November 21, 2013 You are correct. Both of those things work. I was able to test the smoke alarm with some smoke and get a Mobilinc notification and an e-mail so everything appears to be working. Thanks!
Rapidway Posted January 19, 2014 Posted January 19, 2014 I ordered a Smoke Bridge with 4 First Alert SCO501CN-3ST ONELINK's. It's a bit over my head but is it possible after these devises are installed linked-up to have the Smoke Bridge when triggered to turn on all of my Insteon (SwitchLinc) lights in the house? My goal would be to have the lights in them rooms turn on 2 secs/off 1 sec each interval, three times then they would all stay on. Now the room where the smoke/CO detector was violated it would blink at 1/2 sec on then 1/2 sec off for 5 seconds then stay on. I'm not sure if this will work but I'll try. Thanks Mark
kaphely Posted January 19, 2014 Posted January 19, 2014 Rapidway, you'll be able to do this using programs triggered by the smoke ridge smoke node. The only thing you will not be able to do is to figure out which smoke detector out of the 4 triggered the alarm. The smoke bridge will only have one smoke node which will be turned on when any of the detectors linked to it go in alarm.
Rapidway Posted January 19, 2014 Posted January 19, 2014 So It could possibly work if I link each detector to it's own Smoke Bridge. I would then have 4 SB's and 4 Detectors....
LeeG Posted January 19, 2014 Posted January 19, 2014 The detectors should be linked to each other so that all detectors alert regardless of which one trips. That is most important. That would also cause all the Smoke Bridge devices to trip.
radek Posted May 25, 2014 Posted May 25, 2014 For that I would use "If Control 'Smoke Bridge - Smoke' is switched On Or Control 'Smoke Bridge - CO' is switched On Then Notify.... Using 'If Control' will get a Notify each time the Smoke Bridge activates either node. Once the Status goes to ON I'm not sure what turns if back to OFF. Does the bridge need to be queried for this to work? Or will it alert the ISY of change of condition?
LeeG Posted May 25, 2014 Posted May 25, 2014 The Smoke Bridge sends state changes to the ISY automatically as other Insteon devices do. No need to query the Smoke Bridge.
junkycosmos Posted July 29, 2014 Posted July 29, 2014 (edited) I recent ran into some issues when changing out my PLM Seems the PLM update does not flow back into smoke bridge, OR in changing the PLM the link from Smoke Bridge to ISY is broken. In other words: when updating to new PLM my smoke bridge stopped working. I tried relinking it just with the ISY and that was not a fix Instead I had to relink each alarm back to each other, then back to my smoke bridge, and smoke bridge back to ISY I also found a small issue missing from programming. I cannot set "smoke bridge - test" to be queried by a program. Having the ability to query smoke bridge test via a program would be very useful since doing a query of that node is the only way to change "test node" status from ON to OFF. The other solution would be having the node status change to OFF when testing cycle is complete HOWEVER I believe we confirmed prior that smoke bridge does not send TEST OFF. Understood that doing a query of Smoke Bridge is not really live status but I am looking to be able to turn OFF Test status via a program after X minutes, that way if another test cycle is set to ON the ISY could see it. Edit: There is a work around for not being able to query a the smoke bridge test node in a program: add it to a scene and then query the scene. This works well. program: if SB Test is on send notification, wait 1 minute, query scene with SB Test node. This effectively sets up the ISY for next "test" cycle. I have not tested to see if querying the SB Test node before smoke alarm test cycle sets node off and then immediately back on or not. Edited July 29, 2014 by junkycosmos
mathewbeall Posted December 3, 2014 Posted December 3, 2014 (edited) Hi Folks - a quick question on this topic - I just set up (4) linked detectors and then linked the 4th to the smoke bridge. I linked the Smoke Bridge to my ISY and all is good there (I see 7 resources). I am seeing the same behaviour on the Test button - where it changes to "on" but never to "off". All the other resources have no value - even after a query from ISY - no value. Is that expected behavior? Or is there a way to get a value in there? I know I could do a "set". Matt Edited December 3, 2014 by mathewbeall
LeeG Posted December 3, 2014 Posted December 3, 2014 Normal for the test button on the actual sensor. Tap the Set button on the Smoke Bridge. That will generate 5 test messages, for Smoke, CO, and three other nodes. Initially Smoke and CO will be On. When the last test message is sent Smoke and CO will be Off. Watch the Event Viewer at LEVEL 3 to see the 5 test messages.
mathewbeall Posted December 3, 2014 Posted December 3, 2014 Ok - something is not quite right - I don't see those messages - let me try and repair it with the ISY.
LeeG Posted December 3, 2014 Posted December 3, 2014 These are the messages that should be seen under LEVEL 3. The Smoke Bridge LED will turn Red when the Set button is tapped and will blink Red as the messages are sent. Tue 12/02/2014 10:28:39 PM : [iNST-SRX ] 02 50 23.50.FD 00.00.01 CB 11 80 LTONRR (80) Tue 12/02/2014 10:28:39 PM : [std-Group ] 23.50.FD-->Group=1, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:39 PM : [D2D EVENT ] Event [23 50 FD 1] [DON] [128] uom=0 prec=-1 Tue 12/02/2014 10:28:39 PM : [ 23 50 FD 1] DON 128 Tue 12/02/2014 10:28:39 PM : [D2D EVENT ] Event [23 50 FD 1] [sT] [255] uom=0 prec=-1 Tue 12/02/2014 10:28:39 PM : [ 23 50 FD 1] ST 255 Tue 12/02/2014 10:28:39 PM : [iNST-SRX ] 02 50 23.50.FD 11.00.01 CB 06 00 (00) Tue 12/02/2014 10:28:39 PM : [std-Group ] 23.50.FD-->11.00.01, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:39 PM : [iNST-INFO ] Previous message ignored. Tue 12/02/2014 10:28:43 PM : [iNST-SRX ] 02 50 23.50.FD 00.00.02 CB 11 40 LTONRR (40) Tue 12/02/2014 10:28:43 PM : [std-Group ] 23.50.FD-->Group=2, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:43 PM : [D2D EVENT ] Event [23 50 FD 2] [DON] [64] uom=0 prec=-1 Tue 12/02/2014 10:28:43 PM : [ 23 50 FD 2] DON 64 Tue 12/02/2014 10:28:43 PM : [D2D EVENT ] Event [23 50 FD 2] [sT] [255] uom=0 prec=-1 Tue 12/02/2014 10:28:43 PM : [ 23 50 FD 2] ST 255 Tue 12/02/2014 10:28:43 PM : [iNST-SRX ] 02 50 23.50.FD 11.00.02 CB 06 00 (00) Tue 12/02/2014 10:28:43 PM : [std-Group ] 23.50.FD-->11.00.02, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:43 PM : [iNST-INFO ] Previous message ignored. Tue 12/02/2014 10:28:48 PM : [iNST-SRX ] 02 50 23.50.FD 00.00.06 CB 11 10 LTONRR (10) Tue 12/02/2014 10:28:48 PM : [std-Group ] 23.50.FD-->Group=6, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:48 PM : [D2D EVENT ] Event [23 50 FD 6] [DON] [16] uom=0 prec=-1 Tue 12/02/2014 10:28:48 PM : [ 23 50 FD 6] DON 16 Tue 12/02/2014 10:28:48 PM : [iNST-SRX ] 02 50 23.50.FD 11.00.06 CB 06 00 (00) Tue 12/02/2014 10:28:48 PM : [std-Group ] 23.50.FD-->11.00.06, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:48 PM : [iNST-INFO ] Previous message ignored. Tue 12/02/2014 10:28:53 PM : [iNST-SRX ] 02 50 23.50.FD 00.00.07 CB 11 08 LTONRR (08) Tue 12/02/2014 10:28:53 PM : [std-Group ] 23.50.FD-->Group=7, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:53 PM : [D2D EVENT ] Event [23 50 FD 7] [DON] [8] uom=0 prec=-1 Tue 12/02/2014 10:28:53 PM : [ 23 50 FD 7] DON 8 Tue 12/02/2014 10:28:53 PM : [iNST-SRX ] 02 50 23.50.FD 11.00.07 CB 06 00 (00) Tue 12/02/2014 10:28:53 PM : [std-Group ] 23.50.FD-->11.00.07, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:53 PM : [iNST-INFO ] Previous message ignored. Tue 12/02/2014 10:28:58 PM : [iNST-SRX ] 02 50 23.50.FD 00.00.05 CB 11 00 LTONRR (00) Tue 12/02/2014 10:28:58 PM : [std-Group ] 23.50.FD-->Group=5, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:58 PM : [D2D EVENT ] Event [23 50 FD 5] [DON] [0] uom=0 prec=-1 Tue 12/02/2014 10:28:58 PM : [ 23 50 FD 5] DON 0 Tue 12/02/2014 10:28:58 PM : [D2D EVENT ] Event [23 50 FD 1] [sT] [0] uom=0 prec=-1 Tue 12/02/2014 10:28:58 PM : [ 23 50 FD 1] ST 0 Tue 12/02/2014 10:28:58 PM : [D2D EVENT ] Event [23 50 FD 2] [sT] [0] uom=0 prec=-1 Tue 12/02/2014 10:28:58 PM : [ 23 50 FD 2] ST 0 Tue 12/02/2014 10:28:58 PM : [iNST-SRX ] 02 50 23.50.FD 11.00.05 CB 06 00 (00) Tue 12/02/2014 10:28:58 PM : [std-Group ] 23.50.FD-->11.00.05, Max Hops=3, Hops Left=2 Tue 12/02/2014 10:28:58 PM : [iNST-INFO ] Previous message ignored.
mathewbeall Posted December 3, 2014 Posted December 3, 2014 Repairing did the trick - I know see it cycle through "on" and then "off". I will test later with a real smoke test when the ladies aren't around - but I am confident it's working now! Matt
bernieb Posted April 5, 2015 Posted April 5, 2015 Hi Folks, Hoping that someone can assist and possibly suggest what may be the issue. First let me give you some of the basics: FW: 4.2.27 UI: 4.2.16 Smoke Bridge: R3.2 Smoke Detectors (3): SC0501CN (bought at Lowes) I was able to interconnect all my smoke alarm without any issues. I think, but not positive that I was able to pair one of my alarms with the Smoke Bridge. But attempting to pair my Smoke Bridge with the ISY hasn't worked. I've done several factory resets of the Smoke Bridge and tried to pair either a different smoke alarm or at one point, I tried to pair them all. I've read this entire thread and tried to follow suggestions from the ones that had luck. I am not sure if my issue stems from unsuccessful pairing of the alarms to the bridge or if I have an older version of the bridge. One thing that I notice, is that my model number of my smokes is SC0501CN but I did see somewhere else that others have model# SCO501CN-3ST so I am wondering if the "3ST" makes a difference. These smokes all look alike, I thought for the the one at Lowes is what I needed. Any ideal on how to get me going with this? Thanks Bernie
LeeG Posted April 5, 2015 Posted April 5, 2015 (edited) The Smoke Bridge does not need to be paired with a Smoke Alarm to be able to add the Smoke Bridge to the ISY. Also only one Smoke Alarm needs to linked to the Smoke Bridge. With all the Smoke Alarms linked they all alert so only one needs to trigger the Smoke Bridge. Use New INSTEON Device. Enter the Smoke Bridge Insteon address and Name of choice. Device Type remains at default Auto Discover and remove existing links. Explain the details of the symptom and what ISY firmware and UI is being used. The UI should be at the same level as the ISY firmware. Edited April 5, 2015 by LeeG
mcwxlsxn Posted August 5, 2015 Posted August 5, 2015 (edited) I seem to be having similar issues as other folks in this thread. Firmware: Insteon_UD994 v.4.2.30 UI: Insteon_UD994 v.4.2.30 I have tried everything in this thread. Factory resetting the Smoke Bridge many times. Purchased 3 smoke detectors from different vendors i.e. Amazon, Walmart & Smarthome under the model number of "First Alert SA521CN-3ST Onelink Integrated Wireless Smoke Alarm" Purchased 2 Smoke Bridges I've had my system running since this time last year, everything else is running flawlessly. I'm am racking my brain and patience trying to get this to work. Alarms link to bridge fine from what I can tell. The light goes red on the bridge and then green after pairing the smoke alarm(s). Testing the alarms does NOT change the color on the bridge, nor the status of any of the nodes. Nodes appearing on ISY: Smoke CO Clear Low Bat Malfunction Test Unknown Message Pressing the set button on the bridge shows this in Event Viewer level 3: Tue 08/04/2015 10:11:00 PM : [iNST-SRX ] 02 50 2E.FA.80 00.00.01 C7 11 80 LTONRR (80) Tue 08/04/2015 10:11:00 PM : [std-Group ] 2E.FA.80-->Group=1, Max Hops=3, Hops Left=1 Tue 08/04/2015 10:11:00 PM : [D2D EVENT ] Event [2E FA 80 1] [DON] [128] uom=0 prec=-1 Tue 08/04/2015 10:11:00 PM : [ 2E FA 80 1] DON 128 Tue 08/04/2015 10:11:00 PM : [D2D EVENT ] Event [2E FA 80 1] [sT] [255] uom=0 prec=-1 Tue 08/04/2015 10:11:00 PM : [ 2E FA 80 1] ST 255 Tue 08/04/2015 10:11:01 PM : [iNST-SRX ] 02 50 2E.FA.80 2C.07.3B 41 11 01 LTONRR (01) Tue 08/04/2015 10:11:01 PM : [std-Cleanup ] 2E.FA.80-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Tue 08/04/2015 10:11:01 PM : [iNST-DUP ] Previous message ignored. Tue 08/04/2015 10:11:01 PM : [iNST-SRX ] 02 50 2E.FA.80 2C.07.3B 42 11 01 LTONRR (01) Tue 08/04/2015 10:11:01 PM : [std-Cleanup ] 2E.FA.80-->ISY/PLM Group=1, Max Hops=2, Hops Left=0 Tue 08/04/2015 10:11:01 PM : [iNST-DUP ] Previous message ignored. Tue 08/04/2015 10:11:01 PM : [iNST-SRX ] 02 50 2E.FA.80 11.01.01 C7 06 00 (00) Tue 08/04/2015 10:11:01 PM : [std-Group ] 2E.FA.80-->11.01.01, Max Hops=3, Hops Left=1 Tue 08/04/2015 10:11:01 PM : [iNST-INFO ] Previous message ignored. Tue 08/04/2015 10:11:03 PM : [iNST-SRX ] 02 50 2E.FA.80 00.00.02 C7 11 40 LTONRR (40) Tue 08/04/2015 10:11:03 PM : [std-Group ] 2E.FA.80-->Group=2, Max Hops=3, Hops Left=1 Tue 08/04/2015 10:11:03 PM : [D2D EVENT ] Event [2E FA 80 2] [DON] [64] uom=0 prec=-1 Tue 08/04/2015 10:11:03 PM : [ 2E FA 80 2] DON 64 Tue 08/04/2015 10:11:03 PM : [D2D EVENT ] Event [2E FA 80 2] [sT] [255] uom=0 prec=-1 Tue 08/04/2015 10:11:03 PM : [ 2E FA 80 2] ST 255 Tue 08/04/2015 10:11:04 PM : [iNST-SRX ] 02 50 2E.FA.80 2C.07.3B 41 11 02 LTONRR (02) Tue 08/04/2015 10:11:04 PM : [std-Cleanup ] 2E.FA.80-->ISY/PLM Group=2, Max Hops=1, Hops Left=0 Tue 08/04/2015 10:11:04 PM : [iNST-DUP ] Previous message ignored. Tue 08/04/2015 10:11:04 PM : [iNST-SRX ] 02 50 2E.FA.80 11.01.02 C3 06 00 (00) Tue 08/04/2015 10:11:04 PM : [std-Group ] 2E.FA.80-->11.01.02, Max Hops=3, Hops Left=0 Tue 08/04/2015 10:11:04 PM : [iNST-INFO ] Previous message ignored. Tue 08/04/2015 10:11:08 PM : [iNST-SRX ] 02 50 2E.FA.80 00.00.06 C7 11 10 LTONRR (10) Tue 08/04/2015 10:11:08 PM : [std-Group ] 2E.FA.80-->Group=6, Max Hops=3, Hops Left=1 Tue 08/04/2015 10:11:08 PM : [D2D EVENT ] Event [2E FA 80 6] [DON] [16] uom=0 prec=-1 Tue 08/04/2015 10:11:08 PM : [ 2E FA 80 6] DON 16 Tue 08/04/2015 10:11:08 PM : [D2D EVENT ] Event [2E FA 80 6] [sT] [255] uom=0 prec=-1 Tue 08/04/2015 10:11:08 PM : [ 2E FA 80 6] ST 255 Tue 08/04/2015 10:11:09 PM : [iNST-SRX ] 02 50 2E.FA.80 2C.07.3B 41 11 06 LTONRR (06) Tue 08/04/2015 10:11:09 PM : [std-Cleanup ] 2E.FA.80-->ISY/PLM Group=6, Max Hops=1, Hops Left=0 Tue 08/04/2015 10:11:09 PM : [iNST-DUP ] Previous message ignored. Tue 08/04/2015 10:11:09 PM : [iNST-SRX ] 02 50 2E.FA.80 2C.07.3B 42 11 06 LTONRR (06) Tue 08/04/2015 10:11:09 PM : [std-Cleanup ] 2E.FA.80-->ISY/PLM Group=6, Max Hops=2, Hops Left=0 Tue 08/04/2015 10:11:09 PM : [iNST-DUP ] Previous message ignored. Tue 08/04/2015 10:11:09 PM : [iNST-SRX ] 02 50 2E.FA.80 11.01.06 C3 06 00 (00) Tue 08/04/2015 10:11:09 PM : [std-Group ] 2E.FA.80-->11.01.06, Max Hops=3, Hops Left=0 Tue 08/04/2015 10:11:09 PM : [iNST-INFO ] Previous message ignored. Tue 08/04/2015 10:11:13 PM : [iNST-SRX ] 02 50 2E.FA.80 00.00.07 C7 11 08 LTONRR (08) Tue 08/04/2015 10:11:13 PM : [std-Group ] 2E.FA.80-->Group=7, Max Hops=3, Hops Left=1 Tue 08/04/2015 10:11:13 PM : [D2D EVENT ] Event [2E FA 80 7] [DON] [8] uom=0 prec=-1 Tue 08/04/2015 10:11:13 PM : [ 2E FA 80 7] DON 8 Tue 08/04/2015 10:11:13 PM : [D2D EVENT ] Event [2E FA 80 7] [sT] [255] uom=0 prec=-1 Tue 08/04/2015 10:11:13 PM : [ 2E FA 80 7] ST 255 Tue 08/04/2015 10:11:14 PM : [iNST-SRX ] 02 50 2E.FA.80 2C.07.3B 41 11 07 LTONRR (07) Tue 08/04/2015 10:11:14 PM : [std-Cleanup ] 2E.FA.80-->ISY/PLM Group=7, Max Hops=1, Hops Left=0 Tue 08/04/2015 10:11:14 PM : [iNST-DUP ] Previous message ignored. Tue 08/04/2015 10:11:14 PM : [iNST-SRX ] 02 50 2E.FA.80 2C.07.3B 42 11 07 LTONRR (07) Tue 08/04/2015 10:11:14 PM : [std-Cleanup ] 2E.FA.80-->ISY/PLM Group=7, Max Hops=2, Hops Left=0 Tue 08/04/2015 10:11:14 PM : [iNST-DUP ] Previous message ignored. Tue 08/04/2015 10:11:14 PM : [iNST-SRX ] 02 50 2E.FA.80 11.01.07 C3 06 00 (00) Tue 08/04/2015 10:11:14 PM : [std-Group ] 2E.FA.80-->11.01.07, Max Hops=3, Hops Left=0 Tue 08/04/2015 10:11:14 PM : [iNST-INFO ] Previous message ignored. Tue 08/04/2015 10:11:18 PM : [iNST-SRX ] 02 50 2E.FA.80 00.00.05 C7 11 00 LTONRR (00) Tue 08/04/2015 10:11:18 PM : [std-Group ] 2E.FA.80-->Group=5, Max Hops=3, Hops Left=1 Tue 08/04/2015 10:11:18 PM : [D2D EVENT ] Event [2E FA 80 5] [DON] [0] uom=0 prec=-1 Tue 08/04/2015 10:11:18 PM : [ 2E FA 80 5] DON 0 Tue 08/04/2015 10:11:18 PM : [D2D EVENT ] Event [2E FA 80 1] [sT] [0] uom=0 prec=-1 Tue 08/04/2015 10:11:18 PM : [ 2E FA 80 1] ST 0 Tue 08/04/2015 10:11:18 PM : [D2D EVENT ] Event [2E FA 80 2] [sT] [0] uom=0 prec=-1 Tue 08/04/2015 10:11:18 PM : [ 2E FA 80 2] ST 0 Tue 08/04/2015 10:11:19 PM : [iNST-SRX ] 02 50 2E.FA.80 2C.07.3B 41 11 05 LTONRR (05) Tue 08/04/2015 10:11:19 PM : [std-Cleanup ] 2E.FA.80-->ISY/PLM Group=5, Max Hops=1, Hops Left=0 Tue 08/04/2015 10:11:19 PM : [iNST-DUP ] Previous message ignored. Tue 08/04/2015 10:11:19 PM : [iNST-SRX ] 02 50 2E.FA.80 11.01.05 C7 06 00 (00) Tue 08/04/2015 10:11:19 PM : [std-Group ] 2E.FA.80-->11.01.05, Max Hops=3, Hops Left=1 Tue 08/04/2015 10:11:19 PM : [iNST-INFO ] Previous message ignored. The states of the nodes after pressing set go from: Smoke > On > Off CO > On > Off Low Bat > On Malfunction > On Low Bat and Malfunction do not return to off unless I Query them manually. I'm at a loss, any ideas or suggestions?? Edited August 5, 2015 by mcwxlsxn
LeeG Posted August 5, 2015 Posted August 5, 2015 mcwxlsxn The LEVEL 3 trace of the Smoke Bridge looks fine. It is normal to have to Query the two nodes to reset to Off following test. What do you see as the problem?
mcwxlsxn Posted August 5, 2015 Posted August 5, 2015 (edited) Thanks for the response LeeG I'm concerned about the states of the nodes. If I set the alarm off through manual test or actual smoke, the smoke bridge still does not change the states of any of the nodes. Edited August 5, 2015 by mcwxlsxn
Teken Posted August 5, 2015 Posted August 5, 2015 (edited) Thanks for the response LeeG I'm concerned about the states of the nodes. Why does low bat and malfunction remain "on"? And if I set the alarm off through manual test or actual smoke, the smoke bridge still does not change the states of any of the nodes. Have you confirmed you have proper coupling / bridging in your Insteon network as outlined in the users manual for the 2413 PLM? It sounds to me based on your reply you have either noise on the line or poor coupling. I would suggest you complete the coupling / bridging test and get that out of the way first. Next, move the smoke bridge to another outlet using a long extension cord. If you find one that shows proper status identify what devices are on the offending outlet and either remove / filter them. If nothing is on that circuit at all it tends to point to poor coupling but could be still noise makers / signal suckers in the home. Edited August 5, 2015 by Teken
mcwxlsxn Posted August 5, 2015 Posted August 5, 2015 Teken, I will double check the coupling/bridging but it was functioning correctly last time I tested it. I did try these tests on two separate outlets (different floors) with the bridge and detector about 6 feet away from each other in both tests. I'll try your suggestions and see what I can make of it. To me it seems there's no communication going on between the detectors and the bridge. My light never changes on the bridge when I test.
Recommended Posts