rick.curl Posted February 21, 2013 Share Posted February 21, 2013 I know you haven't had the opportunity to try a real Smoke Bridge yet, so I am not surprised that there seems to be a problem...but it could be a misconfiguration on my part. I have an ISY994i and am running 4.0.1 beta. I have the Smoke bridge linked to a SCO500 Smoke /CO detector and to the ISY. When I press the test button on the smoke detector the LED on the Smoke Bridge changes from solid green to blinking red, but the ISY does not respond. I have three programs- one for smoke, one for CO, and one for low battery. The smoke program looks like this: If Control 'Smoke Alarms /23.4E.6B-Smoke' is switched On Then Send notification to 'Default' content 'Smoke Detector' Set Scene 'Living room / Living room Overhead' On Set Scene 'Bedroom / Bedroom Overhead' On Else -No Actions What should happen when I press the test button on a smoke detector? What should happen if I tap the SET button on the Smoke Bridge? (nothing is happening). Any suggestions? Thanks! -Rick Link to comment
Michel Kohanim Posted February 21, 2013 Share Posted February 21, 2013 Hi Rick, Nothing should happen in either case. What you need to happen to test is actual smoke/C02 ... With kind regards, Michel Link to comment
rick.curl Posted February 21, 2013 Author Share Posted February 21, 2013 In that case it may be working fine. I'll get a can of smoke detector tester spray form the local burglar alarm supply house and give it a try. BTW- there is a small typo in your software when it refers to Carbon Monoxide. I't's CO- not CO2. If that's all I've got to complain about then things must be pretty good!!!! -Rick Link to comment
jjp076 Posted February 23, 2013 Share Posted February 23, 2013 I received my smoke bridge yesterday and have successfully added the device to ISY 994i ver 3.3.10. I also linked the smoke bridge to an I/O Linc that triggers an autodailer. I tested the smoke bridge by blowing smoke into the smoke detector. The smoke detector alarmed, notified the smoke bridge, and the smoke bridge triggered the I/O Linc causing the autdialer to activate. The problem is that the ISY never recognized the smoke bridge alarm. I wrote a program for the ISY that activates when the smoke bridge alarms and turn on lights, sends email, etc.. The ISY recognizes the device but alarms are not being seen by the ISY. I also linked a light to the smoke bridge manually and it turns on during an alarm condition. The smoke bridge is communicating over the system. It just appears that the ISY is not seeing the messages. The link table for the smoke bridge shows it linked to the PLM, I/O Linc and light. Not sure what to try next. Any help would be greatly appreciated. Link to comment
LeeG Posted February 23, 2013 Share Posted February 23, 2013 jjp076 Do a Show Device Links Table for the Smoke Bridge and the device that was Set button linked with the Smoke Bridge. Post the Show images if you have the means of hosting an image. I don't think the forum is accepting .jpg files yet. If unable to post the Show images, Save the Show display results which will be an .XML file and post the XML file as text meaning the xml tags need to be included in the post text. Need to see what the links look like that the ISY established versus what the Smoke Bridge established with Set button linking. Link to comment
rick.curl Posted February 24, 2013 Author Share Posted February 24, 2013 I've got the same problem as jjp076. I blew some smoke into the detector. The detector went into alarm, the LED on the smoke bridge changed to red, and then nothing happened. I don't have any devices linked directly to the smoke bridge- I am using a program to switch some lights on and to send an email. The device links table for the smoke bridge looks like this: Device links table: 23.4E.6B-Smoke / 23 4E 6B 1 0 : 0FF8 : A2 00 1E.49.6C FF 1F 01 1 : 0FF0 : E2 01 1E.49.6C FF 1F 01 2 : 0FE8 : E2 02 1E.49.6C FF 1F 02 3 : 0FE0 : E2 06 1E.49.6C FF 1F 06 4 : 0FD8 : 00 00 00.00.00 00 00 00 The program that is supposed to be triggering some devices is shown in the first post in this thread. Am I doing something wrong? Thanks. -Rick Link to comment
LeeG Posted February 24, 2013 Share Posted February 24, 2013 Not that I know of. The Show Device Links Tables by the previous user will/would show any differences between the link records created by the ISY and those created by the Smoke Bridge itself. The Leak Sensor creates a link record with information that is not currently described in the Developer information. It could result in the PLM not seeing messages from the Smoke Bridge if it also generates these undocumented link records and the comm. between the Smoke Bridge and the PLM plug points is marginal. There is a possibility the Smoke Bridge plug point is not able to communicate with the PLM location. One test would be to move the Smoke Bridge to the PLM plug point. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Trip the smoke detector with smoke and see if the event viewer traces any messages from the Smoke Bridge when plugged into the PLM location. Link to comment
rick.curl Posted February 24, 2013 Author Share Posted February 24, 2013 Thanks- Here's the event log: Sat 02/23/2013 08:23:24 PM : [ Time] 20:23:24 3(0) Sat 02/23/2013 08:24:42 PM : [iNST-SRX ] 02 50 23.4E.6B 00.00.01 C7 11 80 LTONRR (80) Sat 02/23/2013 08:24:42 PM : [std-Group ] 23.4E.6B-->Group=1, Max Hops=3, Hops Left=1 Sat 02/23/2013 08:24:42 PM : [iNST-SRX ] 02 50 23.4E.6B 11.00.01 C7 06 00 (00) Sat 02/23/2013 08:24:42 PM : [std-Group ] 23.4E.6B-->11.00.01, Max Hops=3, Hops Left=1 Sat 02/23/2013 08:24:53 PM : [iNST-SRX ] 02 50 23.4E.6B 00.00.01 C7 11 80 LTONRR (80) Sat 02/23/2013 08:24:53 PM : [std-Group ] 23.4E.6B-->Group=1, Max Hops=3, Hops Left=1 Sat 02/23/2013 08:24:53 PM : [iNST-SRX ] 02 50 23.4E.6B 11.00.01 C7 06 00 (00) Sat 02/23/2013 08:24:53 PM : [std-Group ] 23.4E.6B-->11.00.01, Max Hops=3, Hops Left=1 So I take it that the ISY is seeing the messages from the smoke bridge? -Rick Link to comment
LeeG Posted February 24, 2013 Share Posted February 24, 2013 rick.curl Thanks for that trace. Messages are reaching the ISY/PLM but they have an unusual data content. The Insteon architecture calls for the byte containing the 80 to be a Group number which for a Smoke Alarm would normally be expected to be a 01. I suspect that is why the ISY is not reacting to the Smoke Alarm message because it is not the expected Group 1 On Group Broadcast message. Will have to wait for UDI to confirm that. Sat 02/23/2013 08:24:42 PM : [iNST-SRX ] 02 50 23.4E.6B 00.00.01 C7 11 80 LTONRR (80) Sat 02/23/2013 08:24:42 PM : [std-Group ] 23.4E.6B-->Group=1, Max Hops=3, Hops Left=1 This is what the Leak Sensor sends for a Group 1 On message. Note the expected 01 in the message below where the 80 is in the Smoke Bridge message. Sat 02/23/2013 09:36:38 PM : [iNST-SRX ] 02 50 21.7A.CC 00.00.01 CB 11 01 LTONRR (01) Sat 02/23/2013 09:36:38 PM : [std-Group ] 21.7A.CC-->Group=1, Max Hops=3, Hops Left=2 Link to comment
rick.curl Posted February 24, 2013 Author Share Posted February 24, 2013 Thanks, Lee- I appreciate your thoughts on this. Do I need to do anything to call this to UDI's attention? -Rick Link to comment
LeeG Posted February 24, 2013 Share Posted February 24, 2013 rick.curl No. I emailed tech support with a reference to this forum topic. Link to comment
Michel Kohanim Posted February 25, 2013 Share Posted February 25, 2013 Hi Rick and LeeG, Thanks so very much for the trace and apologies for tardy reply. As always, I am seeing some discrepancies that were not in the API guide. We'll review and keep you posted with whatever we find. With kind regards, Michel Link to comment
DigitalAnvil Posted February 25, 2013 Share Posted February 25, 2013 I am also not having any success with the ISY with Smoke Bridge. (currently on the most stable ISY firmware, not the beta like the original post). Should I also be using the beta version? Link to comment
Michel Kohanim Posted February 25, 2013 Share Posted February 25, 2013 Hello DigitalAnvil, Please hold off on the upgrade since it's not going to fix the issue. We are trying to figure out what needs to be done. With kind regards, Michel Link to comment
Michel Kohanim Posted February 26, 2013 Share Posted February 26, 2013 Hello everyone, Just wanted to let everyone know that we are waiting for a response from SmartHome. As LeeG pointed out, 80 is an unknown value which ISY does not understand. The values on that byte are limited to 1 through 7. Furthermore, this specific device does NOT send an OFF message for any of these events. There's only one Clear event and we do not really know what it clears (for instance, does it clear Test, Malfunction, and Bad Message events?). Once we have more information, we would like to ask those who can actually test for Smoke/Fire to test our code before we go to the next beta cycle. Volunteers are welcome. With kind regards, Michel Link to comment
Joe B Posted February 26, 2013 Share Posted February 26, 2013 I have the smoke bridge and am seeing the same issue. However, I have an ISY99i running 3.3.10, so am I out of luck for any future fix via a firmware upgrade? Link to comment
LeeG Posted February 26, 2013 Share Posted February 26, 2013 Joe B There is an upgrade offer for those who want to move to a 994i. viewtopic.php?f=44&t=10771 However, you are correct, the features and fixes in 4.0.1 (which do not include fix for Smoke Bridge), those coming in future 4.0.x, 4.1.x and so on will not be in 3.3.10. The Smoke Bridge is only first of what will likely be a long line of new Smarthome devices that will not be in 3.3.10. Link to comment
rick.curl Posted February 27, 2013 Author Share Posted February 27, 2013 If you need a Beta tester, count me in. I'm really eager to see this all working. -Rick Link to comment
Michel Kohanim Posted February 27, 2013 Share Posted February 27, 2013 Hi Joe B, LeeG is 100% correct. I am so very sorry but we really cannot do anything without actually gutting existing functionality out of 99 to support additional features. We do try to accommodate all those whose 99s are in/around 1 year old. Please do contact sales@universal-devices.com and perhaps we can help more. Hi Rick, I think we finally got enough information from SmartHome to have an initial stab at it. Please do be kind enough to send an email to support@universal-devices.com and we'll send you an early release. Since this device is a safety device, we have decided not to let customers clear faults (such as malfunction, bad messages, test, low bat) for now till we figure out the safest way. In all cases, you will need to remove Smoke Sensor from your ISY, factory reset and then add it back. With kind regards, Michel Link to comment
rick.curl Posted March 6, 2013 Author Share Posted March 6, 2013 I just wanted to let everyone know that the Smoke Bridge is working fine now since I updated to 4.0.2 beta. Nice work, guys! Thanks for fixing it quickly! -Rick Link to comment
JamesB Posted April 26, 2013 Share Posted April 26, 2013 Any updates on this?? I've got my bridge working .. but I was curious to see others' experiences. Link to comment
LeeG Posted April 27, 2013 Share Posted April 27, 2013 What kind of update are you looking for? rick.curl reports the Smoke Bridge is working. Link to comment
rick.curl Posted April 27, 2013 Author Share Posted April 27, 2013 Still OK here. Have three smoke detectors linked to it. I would be curious to know if others are running OK. -Rick Link to comment
Teken Posted May 10, 2013 Share Posted May 10, 2013 Still OK here. Have three smoke detectors linked to it.I would be curious to know if others are running OK. -Rick I finally got a chance to install and test the smoke bridge. So far it looks like the alert notification for Smoke, CO, Low Battery, Malfunction come in while pressing the Set button on the device itself. I have been able to link all the required lights and sirens I want during these events. It appears to activate all things linked as I would hope. I know others have wondered about the Low Battery alert notification. As of this writing one of my smoke alarms began to chirp. It did not initiate a signal to the Smoke Bridge, I am guessing the voltage is too high? Both AA batteries measured 1.375 VDC for the device in question. I would be interested to know from First Alert / Smarthome as to when the low battery signal is sent off? As the device does in fact sound off indicating the battery is low. I gather this threshold is much higher than what the Smoke Bridge considers low? Since I was already going to change out the battery I decided to complete the review. I performed a *Test* on the First Alert One Link module. It did in fact signal the Smoke Bridge and I received all the e-mails & text sms to all the phones I had programmed. It looks like this product is very solid and does perform as advertised. Teken . . . Link to comment
rick.curl Posted May 10, 2013 Author Share Posted May 10, 2013 Thanks for the update. I'm very curious about the low battery indication. Please let us know if you get more information about this. -Rick Link to comment
Recommended Posts