rpsa Posted February 17, 2013 Posted February 17, 2013 I'm having problems getting my ISY to see changes in the Smoke Bridge. OK…To set the stage: I have a commercial fire detection and alarm system in my house with 16 smoke detectors, 12 heat detectors and a sprinkler (fire) waterflow switch – yes the whole house and garage have fire sprinklers. (I’m a fire protection engineers – have to take my own advice.) I chose the First Alert One Link to be able to wirelessly add CO and link it into my Insteon system with the new Smoke Bridge. I bought three combination CO/Photoelectric smoke alarms (alarms are stand alone, detectors connect to a panel), one for each level. I was able to set each up with the “voice†to announce the location. I was able to link each with the others so they all go off when one goes off. I plug in the Smoke Bridge, enter linking mode and then press the test button on one of the CO/smoke alarms. The linking LED changes from blinking green to blinking red, then goes to steady green. I assume this means a successful link. I have an ISY99i running version 3.3.10. I use the New Insteon Device to manually add the Smoke Bridge. I enter the address and select “Insteon Smoke Sensor†from the Device Type dropdown box. Click ok and it finds the Smoke Bridge. Three nodes get added to my network, each with a flame for an icon and each without anything to distinguish what each means. Are they the three CO/Smoke alarms? Or, could one be smoke, one CO and one trouble? The current state for each of three nodes is blank. I Query and the state stays blank. I do >Diagnostics>Query Insteon Engine and each of the three nodes shows “writing†for a second and then goes back to the flame icon. I wrote three programs to notify me by email and text if any of the three nodes is “Onâ€. Using the test button on any of three I do NOT get any change in Current State for any of the three nodes. Hey, maybe a Test does not pass through the Smoke Bridge. Being the consummate pro, I use canned smoke to test the CO/Smoke alarms. No change in state, no notification, no entries in my event log. Soooo, I manually linked the Smoke Bridge to a light. The test button does not cause the light to respond. Testing with canned smoke caused the light to respond. But, no status changes on my ISY network. Regarding the test button, the manual says that this is normal: “Using the Set button to create a link to a responder links it to the Smoke Detected group only. To link to the test button group, you must use software or a smart device (iOS or Android) app.†That made me think that the Smoke Bridge and CO/Smoke alarms are working and linking fine. The problem must be in the ISY99i. So, I deleted the Smoke Bridge from my network and re-linked it. This time I used >Link Management>Start Linking and manually pressed the set button on the Smoke Bridge. It gets found and linked and three new nodes are added. This time though one node is Smoke, one is CO and the last is Low Bat. Actually the CO node came up incorrectly with a default name using the address and “CO2â€, which is carbon dioxide, not carbon monoxide (CO). Success? Let do some testing…. Nope. Still no response when I query the three nodes and no response when the smoke alarm is activated using simulated smoke. The Smoke Bridge does blink red when the smoke alarm activates, it’s just not updating the ISY. The Event Viewer shows that the address was successfully added. But that’s it. Any ideas?
arw01 Posted February 17, 2013 Posted February 17, 2013 post some level 3 event logs for people to digest. Michael said they only got the add support from the developer documentation, they did not get to test anything. The level 3 details should give the excellent people here on the forums something to digest and have you test various theories. Alan
rpsa Posted February 17, 2013 Author Posted February 17, 2013 post some level 3 event logs for people to digest. Michael said they only got the add support from the developer documentation, they did not get to test anything. The level 3 details should give the excellent people here on the forums something to digest and have you test various theories. Alan OK - Before I do that, is there a way I should format the txt file to make it easier to read? And then just copy and paste in the reply? And, do I have to set the Event Log to level 3 before I run all those tests all over again? I had it set to 1 before when I was setting up. Bob
LeeG Posted February 17, 2013 Posted February 17, 2013 Must set to LEVEL 3 before creating the activity. There will not be that much activity if any when testing for each condition. Edit the event trace with WordPad. Copy/Paste the records to the a forum post.
Michel Kohanim Posted February 17, 2013 Posted February 17, 2013 Please also note that this device is NOT queryable and thus you actually need to have actual events trigger events back into ISY. The only thing we could test was the Test button and even that was not 100% consistent in its behavior. As such, care should be taken when using this device/ISY for safety ... With kind regards, Michel
rpsa Posted February 18, 2013 Author Posted February 18, 2013 Please also note that this device is NOT queryable and thus you actually need to have actual events trigger events back into ISY. The only thing we could test was the Test button and even that was not 100% consistent in its behavior. As such, care should be taken when using this device/ISY for safety ... With kind regards, Michel Thanks all. The safety side is covered - the smoke/co alarms work and I'm not relying on the interface to ISY for anything more than reporting and info logging. But, as you say, others, with different circumstances and needs, might be cautious about relying on that link/response until the details are worked out. I'll do some additional testing to try and narrow down - or at least document - the connectivity and reporting problem/issues. It might be a few days before I can take the time to do some systematic playing and before I can post the results. Bob
rpsa Posted February 18, 2013 Author Posted February 18, 2013 Must set to LEVEL 3 before creating the activity. There will not be that much activity if any when testing for each condition. Edit the event trace with WordPad. Copy/Paste the records to the a forum post. OK - BTW, until I get some canned CO, I won't be able to generate a "real" CO test since the test button, by default, will NOT actually generate a state change for Insteon to respond to. I have access to some CO test gas and will get some this week to test. Bob
LeeG Posted February 18, 2013 Posted February 18, 2013 Start with what you have available. Set off the smoke alarm and let’s see what the Smoke Bridge generates for messages. Very likely the other detection nodes will do the same thing. No sense going to the trouble of testing the others until Smoke is working.
rpsa Posted March 3, 2013 Author Posted March 3, 2013 OK – I ran some controlled tests: Set Event Viewer to Level 3 and cleared the log. Activated smoke alarm with canned smoke. Four lines were entered for the Smoke Bridge address (23.4E.5B) in the log before the units even started sounding. Then four more lines were logged up as they started sounding the alarm. I then operated the silence button and cleared the unit with canned air. Saved log to file: ISY-Events-Log.v3.3.10__Sun 2013.03.03 01.29.49 PM.txt ++++++++++++++ First Smoke Alarm Test Sun 3/3/2013 1:25:36 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.01 CB 11 80 LTONRR (80) Sun 3/3/2013 1:25:36 PM : [std-Group ] 23.4E.5B-->Group=1, Max Hops=3, Hops Left=2 Sun 3/3/2013 1:25:36 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.01 CB 06 00 (00) Sun 3/3/2013 1:25:36 PM : [std-Group ] 23.4E.5B-->11.00.01, Max Hops=3, Hops Left=2 Sun 3/3/2013 1:25:48 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.01 C7 11 80 LTONRR (80) Sun 3/3/2013 1:25:48 PM : [std-Group ] 23.4E.5B-->Group=1, Max Hops=3, Hops Left=1 Sun 3/3/2013 1:25:48 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.01 C7 06 00 (00) Sun 3/3/2013 1:25:48 PM : [std-Group ] 23.4E.5B-->11.00.01, Max Hops=3, Hops Left=1 Sun 3/3/2013 1:28:39 PM : [ Time] 13:28:39 28(0) +++++++++++++++ The first four entries are identical to the 2nd set of four entries 12 seconds later EXCEPT for one minor difference in the last line. In the 1st set the last line has Hope Left = 2, in the 2nd set, the last line has Hops Left = 1. I don’t know what that means. (I added the blank rows to make it easier to read.) Throughout the test there was no change in the Current State of my network for that node. A light that I Iinked to the Smoke Bridge did turn on, but did not log in the Event Viewer. Was this because I linked it manually, not using the ISY – and because it was done after adding it to the network so the link was not imported? I mentioned previously that I have a program set to send an email and a text when the node is “Onâ€. I added another to send the same message if the node was “Responding†– just in case the Smoke Bridge is acting as a responder to the actual smoke alarms. I then ran the same test again. The first four lines show up immediately upon activation of the Smoke Bridge (LED changes from steady green to steady red). The second set of four lines get logged when the units start sounding. This time, all entries were identical, including Hops Left = 2. No changes in the Current State and no emails or text messages sent. I then manually removed the link to the light. I cleared the Event Viewer and tried tapping the set button on the Smoke Bridge. According to the manual this should cause it to cycle through the following five notifications: Smoke detected; Carbon Monoxide detected; Low battery detected; Error; All Clear. The Event Viewer responded by logging 12 lines. They came in as three groups of four lines separated by a couple of seconds time. (I added the blank rows to make it easier to read.) +++++++++++++++ Sun 3/3/2013 2:25:49 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.01 CB 11 80 LTONRR (80) Sun 3/3/2013 2:25:49 PM : [std-Group ] 23.4E.5B-->Group=1, Max Hops=3, Hops Left=2 Sun 3/3/2013 2:25:50 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.01 CB 06 00 (00) Sun 3/3/2013 2:25:50 PM : [std-Group ] 23.4E.5B-->11.00.01, Max Hops=3, Hops Left=2 Sun 3/3/2013 2:25:51 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.02 CB 11 40 LTONRR (40) Sun 3/3/2013 2:25:51 PM : [std-Group ] 23.4E.5B-->Group=2, Max Hops=3, Hops Left=2 Sun 3/3/2013 2:25:52 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.02 CB 06 00 (00) Sun 3/3/2013 2:25:52 PM : [std-Group ] 23.4E.5B-->11.00.02, Max Hops=3, Hops Left=2 Sun 3/3/2013 2:25:56 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.06 CB 11 10 LTONRR (10) Sun 3/3/2013 2:25:56 PM : [std-Group ] 23.4E.5B-->Group=6, Max Hops=3, Hops Left=2 Sun 3/3/2013 2:25:57 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.06 CB 06 00 (00) Sun 3/3/2013 2:25:57 PM : [std-Group ] 23.4E.5B-->11.00.06, Max Hops=3, Hops Left=2 +++++++++++++++ I then created a test scene using the Admin Console with a single light as a responder and the smoke node as a controller. I instantly got my notification text message and email!!!!! But I did not see any changes in Current State. I also received the following error message: “Failed Communicating With, Cannot Communicate with 23.4E.5B 1) Please check connections.†I assume this is because it cannot be queried. ++++++++++++++ Sun 3/3/2013 2:46:23 PM : [23.4E.5B-Smok e] Start : Adding to scene 'test sconces' Sun 3/3/2013 2:46:23 PM : [23.4E.5B-Smok e] Making 'test sconces' a Controller Sun 3/3/2013 2:46:23 PM : [MNG-LNK-RSP ] 02 6F 40 E2 13 23 4E 5B 10 0A 43 06 Sun 3/3/2013 2:46:23 PM : [23.4E.5B-Smok e] Making '1st S1-2 Sun Rm Sconces' a Responder Sun 3/3/2013 2:46:24 PM : [23.4E.5B-Smok e] Finish : Adding to scene 'test sconces' was Successful Sun 3/3/2013 2:46:24 PM : [iNST-TX-I2CS] 02 62 1D E5 5A 1F 2F 00 00 02 0F E7 08 A2 01 23 4E 5B FF 1F 01 43 Sun 3/3/2013 2:46:24 PM : [iNST-ACK ] 02 62 1D.E5.5A 1F 2F 00 00 02 0F E7 08 A2 01 23 4E 5B FF 1F 01 43 06 (00) Sun 3/3/2013 2:46:25 PM : [ 23 4E 5B 1] ERR 0 Sun 3/3/2013 2:46:25 PM : [iNST-SRX ] 02 50 1D.E5.5A 0D.FD.11 2B 2F 00 (00) Sun 3/3/2013 2:46:25 PM : [std-Direct Ac k] 1D.E5.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sun 3/3/2013 2:46:25 PM : [iNST-TX-I2CS] 02 62 23 4E 5B 1F 2F 00 00 02 0F DF 08 A2 13 0D FD 11 FF 1F 01 EA Sun 3/3/2013 2:46:25 PM : [iNST-ACK ] 02 62 23.4E.5B 1F 2F 00 00 02 0F DF 08 A2 13 0D FD 11 FF 1F 01 EA 06 (00) Sun 3/3/2013 2:46:34 PM : [iNST-TX-I2CS] 02 62 23 4E 5B 1F 2F 00 00 02 0F DF 08 A2 13 0D FD 11 FF 1F 01 EA Sun 3/3/2013 2:46:34 PM : [iNST-ACK ] 02 62 23.4E.5B 1F 2F 00 00 02 0F DF 08 A2 13 0D FD 11 FF 1F 01 EA 06 (00) Sun 3/3/2013 2:46:43 PM : [iNST-TX-I2CS] 02 62 23 4E 5B 1F 2F 00 00 02 0F DF 08 A2 13 0D FD 11 FF 1F 01 EA Sun 3/3/2013 2:46:43 PM : [iNST-ACK ] 02 62 23.4E.5B 1F 2F 00 00 02 0F DF 08 A2 13 0D FD 11 FF 1F 01 EA 06 (00) Sun 3/3/2013 2:46:47 PM : [ 23 4E 5B 1] ERR 1 Sun 3/3/2013 2:46:47 PM : [iNST-TX-I2CS] 02 62 1D E5 5A 1F 2F 00 00 02 0F E7 08 A2 01 23 4E 5B FF 1F 01 43 Sun 3/3/2013 2:46:47 PM : [iNST-ACK ] 02 62 1D.E5.5A 1F 2F 00 00 02 0F E7 08 A2 01 23 4E 5B FF 1F 01 43 06 (00) Sun 3/3/2013 2:46:48 PM : [iNST-SRX ] 02 50 1D.E5.5A 0D.FD.11 2B 2F 00 (00) Sun 3/3/2013 2:46:48 PM : [std-Direct Ac k] 1D.E5.5A-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 ++++++++++++++ I ran another smoke test and got the same eight entries in the Event Viewer as before. But, no changes in state, no text/email and NO activation of the scene to turn the light on. I tried tapping the set button again to run a test. Same 12 entries (three groups of four) but NO scene activation and NO notifications. Next I removed the Smoke Bridge as a controller of the scene then added it back in. I got my email and text notifications. I don’t think the scene was triggered – I did not see the light’s status change and am too far away to watch the actual lights. I’m not sure what is happening. Any help would be appreciated. I’d be willing to do some more testing if you have ideas that might lead to a solution or that might help the ISY developer’s. Bob S.
LeeG Posted March 3, 2013 Posted March 3, 2013 rpsa The Smoke Bridge is sending Scene/Group messages with an unexpected/undocumented Scene/Group number. For sure 3.3.10 and 4.0.1 will not work. The 4.0.2 release indicates the Smoke Bridge has to be deleted and added back to the ISY. Assume that means 4.0.2 has a fix but I do not have a Smoke Bridge to confirm.
Michel Kohanim Posted March 4, 2013 Posted March 4, 2013 Hi rpsa, LeeG is 100% correct. Please remove the bridge, upgrade to 4.0.2, link it back. With kind regards, Michel
az1324 Posted March 4, 2013 Posted March 4, 2013 Seems like this was another case of inactive group cleanups. Have the links been fixed for this (and the leak sensor) so that cleanups are sent? Are there any other devices out there that aren't sending cleanups due to link parameters?
Michel Kohanim Posted March 4, 2013 Posted March 4, 2013 az1324, As I mentioned before, we cannot implement anything that's NOT in the developers guide. What's in ISY is precisely what should be there based on the documentation (or will be). With kind regards, Michel
rpsa Posted March 4, 2013 Author Posted March 4, 2013 LeeG is 100% correct. Please remove the bridge, upgrade to 4.0.2, link it back. With kind regards, Michel OK. But to do that I understand that I first have to change out my ISY 99i/IR PRO for a ISY994i/IR PRO. Somehow I knew the solution would not be fast and easy. I don’t know about “inactive group cleanupsâ€, but my leak sensors, which were also a challenge to get working, are now working consistently. See my “set-up instructions†in the SH forum at: http://www.smarthome.com/forum/topic.asp?TOPIC_ID=12166 (posted 2/2/13). Thanks for your help. Bob S.
az1324 Posted March 4, 2013 Posted March 4, 2013 az1324, As I mentioned before, we cannot implement anything that's NOT in the developers guide. What's in ISY is precisely what should be there based on the documentation (or will be). With kind regards, Michel Well it is true that the information is not specified, but it seems the dev docs assume that you are going to use the built in All-Linking mechanisms to let the devices negotiate links with each other. So by choosing to manually write links, you are responsible for making sure those links contain the same parameters that would arise from the negotiated links. Of course it is disappointing that detailed information is not provided for those using this method. For some reason it seems that at least these two devices (Leak Sensor, Smoke Bridge) only send cleanups when the Data 1 parameter is a certain value (or possibly a valid range) but NOT the default value ISY uses of 0xFF. Now as long as you have a sample of the device in your possession, it is straightforward to create some auto-negotiated links and observe the Data 1 values and use them in your links. We know that a valid value for the Leak Sensor is 0x03. I would also think that as a valued partner you have a high-level contact at Smarthome that can provide better information on this and hopefully you would encourage them to add documentation to the developer's site as well for those who want to manually write links into devices. I suspect this problem may apply to other devices and will continue to apply to newly released devices. I think it is necessary to resolve this issue including examining what existing devices this applies to and put a policy in place for future device support. Presumably, this all ties back into the fact that status messages from these devices were labeled as broadcast messages but implemented as group broadcast messages. So I guess one could make the argument as to whether group cleanups are necessary, but it seems like if the functionality is available to improve the chances of message success then it should be used. As a side note, I have seen repeated references (including this thread) to unexpected values in the Cmd 2 parameter of group broadcast messages that imply this should contain the group number when from my understanding this is not true. The Cmd 2 parameter only contains the group number in group cleanup messages. In group broadcast messages the Cmd 2 parameter is specified to contain a default value of zero but in more recent devices it seems to contain extra information. However, that extra information is usually not necessary for interpreting the message correctly. Finally, could you please clarify which of the 7 possible status messages are supported for the Smoke Bridge in the latest ISY firmware?
Michel Kohanim Posted March 6, 2013 Posted March 6, 2013 Hi az1324, All 7 are supported in the new firmware version. This said, just because two devices exhibit this behavior does not make a compelling case for implementing something ESPECIALLY since 99.9% of other INSTEON devices do NOT (regardless of whatever they "assume" the linking method is). In short, without verification from SmartHome, this is VERY risky for us and not something I would like to entertain without more empirical data from more devices and their characteristics. As such, and at the moment, the only think I can do is to send a link to this post to our contacts at SmartHome. Whatever is their recommendation shall be done. With kind regards, Michel
az1324 Posted March 6, 2013 Posted March 6, 2013 Well I don't see how it is risky to make sure the links you write are the same as what the device would write into its own database if it was sent a start linking command. In fact the opposite is true: writing a link that the device would NOT have written into its own database is risky, if anything. The fact that these are the two newest devices and they exhibit this means future devices could also do so. It's pretty simple to maintain an array of default link data values by dev cat and say if the dev cat is found in the array then replace the link values with the new defaults. Otherwise, do the same old same old. I do think the fact that these devices happen to be critical sensors makes it compelling to make sure the cleanups are sent. But I am interested to see what SH says on the issue of why the cleanups do not occur.
Michel Kohanim Posted March 7, 2013 Posted March 7, 2013 az1324, With all due respect, I strongly disagree with you but I am not going to try and persuade you one way or another. I will post back as soon as I hear back from SmartHome. With kind regards, Michel
az1324 Posted March 8, 2013 Posted March 8, 2013 UPDATE: I was just looking at the I2CS dev note and it actually says that the value 0xFF in the Data 1 parameter means cleanups are disabled. Please refer to page 7. So there is the official documentation. Now the question is do you believe cleanups should be disabled (not sure why you would)? If not then maybe the value 0x03 should be used for all I2CS device controller records from now on. Or at least 0x01 for non-critical devices and 0x03 for critical sensors. Interested to hear your thoughts. This probably means none of the I2CS devices out there managed by ISY are sending cleanups, right? Thanks.
Michel Kohanim Posted March 8, 2013 Posted March 8, 2013 Hello az1324, Thank you. We'll revisit through the documentation, consult with SmartHome, and will get back to you. As of now, I have categorized this as bug ID#78. With kind regards, Michel
rpsa Posted March 24, 2013 Author Posted March 24, 2013 Hi rpsa, LeeG is 100% correct. Please remove the bridge, upgrade to 4.0.2, link it back. With kind regards, Michel OK - I upgraded.... First I removed the smoke bridge from the 99i. Backed up. Removed the 99i and installed the 994i. Restored my backup. Upgraded to v 4.0.2. Cleared Java cache, etc. Added the smoke bridge back to isy network. It now links seven nodes: Smoke CO2 (Note – should be CO, not CO2) Clear Low Bat Malfunction Test Unknown Message I created custom notifications for each event when “Onâ€. Tested with the test button. The Test node changes state to “On†and I get my notification. Tested with the canned smoke. The Smoke node changes state to “On†and I get my notification. When I cleared the smoke and the smoke alarm returned to normal, I expected the Clear state to change to “onâ€. Nope. Tried again, but this time I There is no way for me test low bat, malfunction and CO. I have no idea what “Unknown Message†is. Interestingly, I can right click and query each of the nodes and they all show “Off†except the Clear node. It shows nothing. I’m guessing you would like to see a level 3 event log. So, I tested again after clearing the Event Log. Here it is. By the way, there are 4 CO/Smoke alarm units interconnected to each other. I’m hoping it does not matter which gets tested or activated since I used different ones for different tests – to test their interconnection to each other at the same time. I would think that does not matter and that the smoke bridge is simply activated the same regardless of the originating unit. Here it is: After upgrade to ISY 994i/IR Pro and v 4.0.2 First I used the Test button (12:43:32 and :12:43:44) Sun 3/24/2013 12:43:32 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.03 CB 11 00 LTONRR (00) Sun 3/24/2013 12:43:32 PM : [std-Group ] 23.4E.5B-->Group=3, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:43:32 PM : [ 23 4E 5B 3] DON 0 Sun 3/24/2013 12:43:32 PM : [ 23 4E 5B 3] ST 255 Sun 3/24/2013 12:43:32 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.03 CB 06 00 (00) Sun 3/24/2013 12:43:32 PM : [std-Group ] 23.4E.5B-->11.00.03, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:43:44 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.03 CB 11 00 LTONRR (00) Sun 3/24/2013 12:43:44 PM : [std-Group ] 23.4E.5B-->Group=3, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:43:44 PM : [ 23 4E 5B 3] DON 0 Sun 3/24/2013 12:43:44 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.03 CB 06 00 (00) Sun 3/24/2013 12:43:44 PM : [std-Group ] 23.4E.5B-->11.00.03, Max Hops=3, Hops Left=2 Next I used canned smoke (12:45:56 and 12:46:07). Sun 3/24/2013 12:45:56 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.01 CB 11 80 LTONRR (80) Sun 3/24/2013 12:45:56 PM : [std-Group ] 23.4E.5B-->Group=1, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:45:56 PM : [ 23 4E 5B 1] DON 128 Sun 3/24/2013 12:45:56 PM : [ 23 4E 5B 1] ST 255 Sun 3/24/2013 12:45:56 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.01 CB 06 00 (00) Sun 3/24/2013 12:45:56 PM : [std-Group ] 23.4E.5B-->11.00.01, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:46:07 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.01 CB 11 80 LTONRR (80) Sun 3/24/2013 12:46:07 PM : [std-Group ] 23.4E.5B-->Group=1, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:46:07 PM : [ 23 4E 5B 1] DON 128 Sun 3/24/2013 12:46:07 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.01 CB 06 00 (00) Sun 3/24/2013 12:46:07 PM : [std-Group ] 23.4E.5B-->11.00.01, Max Hops=3, Hops Left=2 "I used the hush button, and I got events at 12:48:18 through 12:49:06 but never got a “Clear†change in state or associated notification. " Sun 3/24/2013 12:48:18 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.05 CB 11 00 LTONRR (00) Sun 3/24/2013 12:48:18 PM : [std-Group ] 23.4E.5B-->Group=5, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:48:18 PM : [ 23 4E 5B 5] DON 0 Sun 3/24/2013 12:48:18 PM : [ 23 4E 5B 1] ST 0 Sun 3/24/2013 12:48:18 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.05 CB 06 00 (00) Sun 3/24/2013 12:48:18 PM : [std-Group ] 23.4E.5B-->11.00.05, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:48:30 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.05 CB 11 00 LTONRR (00) Sun 3/24/2013 12:48:30 PM : [std-Group ] 23.4E.5B-->Group=5, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:48:30 PM : [ 23 4E 5B 5] DON 0 Sun 3/24/2013 12:48:30 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.05 CB 06 00 (00) Sun 3/24/2013 12:48:30 PM : [std-Group ] 23.4E.5B-->11.00.05, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:48:42 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.05 CB 11 00 LTONRR (00) Sun 3/24/2013 12:48:42 PM : [std-Group ] 23.4E.5B-->Group=5, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:48:42 PM : [ 23 4E 5B 5] DON 0 Sun 3/24/2013 12:48:42 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.05 CB 06 00 (00) Sun 3/24/2013 12:48:42 PM : [std-Group ] 23.4E.5B-->11.00.05, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:48:54 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.05 CB 11 00 LTONRR (00) Sun 3/24/2013 12:48:54 PM : [std-Group ] 23.4E.5B-->Group=5, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:48:54 PM : [ 23 4E 5B 5] DON 0 Sun 3/24/2013 12:48:54 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.05 CB 06 00 (00) Sun 3/24/2013 12:48:54 PM : [std-Group ] 23.4E.5B-->11.00.05, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:49:06 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.05 CB 11 00 LTONRR (00) Sun 3/24/2013 12:49:06 PM : [std-Group ] 23.4E.5B-->Group=5, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:49:06 PM : [ 23 4E 5B 5] DON 0 Sun 3/24/2013 12:49:06 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.05 CB 06 00 (00) Sun 3/24/2013 12:49:06 PM : [std-Group ] 23.4E.5B-->11.00.05, Max Hops=3, Hops Left=2 So, I tried smoke again, but allowed the smoke to clear without using the hush button (the smoke alarms are non-latching. Events 12:52:32 through 12:52:45. Sun 3/24/2013 12:52:32 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.01 CB 11 80 LTONRR (80) Sun 3/24/2013 12:52:32 PM : [std-Group ] 23.4E.5B-->Group=1, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:52:32 PM : [ 23 4E 5B 1] DON 128 Sun 3/24/2013 12:52:32 PM : [ 23 4E 5B 1] ST 255 Sun 3/24/2013 12:52:33 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.01 CB 06 00 (00) Sun 3/24/2013 12:52:33 PM : [std-Group ] 23.4E.5B-->11.00.01, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:52:44 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.01 CB 11 80 LTONRR (80) Sun 3/24/2013 12:52:44 PM : [std-Group ] 23.4E.5B-->Group=1, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:52:44 PM : [ 23 4E 5B 1] DON 128 Sun 3/24/2013 12:52:45 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.01 CB 06 00 (00) Sun 3/24/2013 12:52:45 PM : [std-Group ] 23.4E.5B-->11.00.01, Max Hops=3, Hops Left=2 "When the smoke cleared (pardon the pun) I got events 12:55:17 through 12:55:41. Again, no change in “Clear†state and no notifications." Sun 3/24/2013 12:55:17 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.05 CB 11 00 LTONRR (00) Sun 3/24/2013 12:55:17 PM : [std-Group ] 23.4E.5B-->Group=5, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:55:17 PM : [ 23 4E 5B 5] DON 0 Sun 3/24/2013 12:55:17 PM : [ 23 4E 5B 1] ST 0 Sun 3/24/2013 12:55:18 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.05 CB 06 00 (00) Sun 3/24/2013 12:55:18 PM : [std-Group ] 23.4E.5B-->11.00.05, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:55:28 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.05 CB 11 00 LTONRR (00) Sun 3/24/2013 12:55:28 PM : [std-Group ] 23.4E.5B-->Group=5, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:55:28 PM : [ 23 4E 5B 5] DON 0 Sun 3/24/2013 12:55:29 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.05 CB 06 00 (00) Sun 3/24/2013 12:55:29 PM : [std-Group ] 23.4E.5B-->11.00.05, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:55:40 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.05 CB 11 00 LTONRR (00) Sun 3/24/2013 12:55:40 PM : [std-Group ] 23.4E.5B-->Group=5, Max Hops=3, Hops Left=2 Sun 3/24/2013 12:55:40 PM : [ 23 4E 5B 5] DON 0 Sun 3/24/2013 12:55:41 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.05 CB 06 00 (00) Sun 3/24/2013 12:55:41 PM : [std-Group ] 23.4E.5B-->11.00.05, Max Hops=3, Hops Left=2 Is there some way to find out what these nodes are supposed be for? (Clear, Malfunction and Unknown Message). Bob S.
Michel Kohanim Posted March 24, 2013 Posted March 24, 2013 Hi Bob, Thanks so very much! Clear is the group command sent when the event has been cleared (either smoke or fire). The only thing you can do with this node is to either put them in a scene as a controller so that when clear is sent, you turn on/off something. Or, you can put them in a program based on Switched-On. I am not sure what malfunction and unknown messages do. With kind regards, Michel
rpsa Posted March 24, 2013 Author Posted March 24, 2013 Hi Bob, Thanks so very much! Clear is the group command sent when the event has been cleared (either smoke or fire). The only thing you can do with this node is to either put them in a scene as a controller so that when clear is sent, you turn on/off something. Or, you can put them in a program based on Switched-On. I am not sure what malfunction and unknown messages do. With kind regards, Michel Thanks. I do have Clear in a program to send me a notification - BUT I just noticed I had the condition set to "Respond" instead of "On". I changed it but can not test until tomorrow - after my wife goes to work I can make all the noise I want. I'll post an update if I get it to work - or not. I would guess that Malfunction is just that. But, it would be nice if the mfg would let you know what "Unknown Message" is. p.s. - Is the incorrect node label - CO2 which should be CO - something that is in the Insteon program or does that come from the smoke bridge? And, who would change it?
Michel Kohanim Posted March 25, 2013 Posted March 25, 2013 Hi rpsa, Thank you. The incorrect label comes from us and it has already been rectified. Please do be kind enough to rename it manually. With kind regards, Michel
rpsa Posted March 25, 2013 Author Posted March 25, 2013 2013 03 25 Michel - Thanks for looking at these for me. More testing of the Smoke Bridge and ISY. Here is one set test Events. If I’m reading this correct, the Smoke alarm is Group 1 for the address. And, Clear is Group 5. I just figured out that to know the group number, I have to right click and choose rename to the see the full address and group number. (Is there some other way?) 2013 03 25 Smoke Alerm Test allowed to clear itself. Mon 3/25/2013 12:40:55 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.01 CB 11 80 LTONRR (80) Mon 3/25/2013 12:40:55 PM : [std-Group ] 23.4E.5B-->Group=1, Max Hops=3, Hops Left=2 Mon 3/25/2013 12:40:55 PM : [ 23 4E 5B 1] DON 128 Mon 3/25/2013 12:40:55 PM : [ 23 4E 5B 1] ST 255 Mon 3/25/2013 12:40:55 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.01 CB 06 00 (00) Mon 3/25/2013 12:40:55 PM : [std-Group ] 23.4E.5B-->11.00.01, Max Hops=3, Hops Left=2 Mon 3/25/2013 12:41:07 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.01 CB 11 80 LTONRR (80) Mon 3/25/2013 12:41:07 PM : [std-Group ] 23.4E.5B-->Group=1, Max Hops=3, Hops Left=2 Mon 3/25/2013 12:41:07 PM : [ 23 4E 5B 1] DON 128 Mon 3/25/2013 12:41:07 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.01 CB 06 00 (00) Mon 3/25/2013 12:41:07 PM : [std-Group ] 23.4E.5B-->11.00.01, Max Hops=3, Hops Left=2 This must be the Clear signal. Mon 3/25/2013 12:41:24 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.05 CB 11 00 LTONRR (00) Mon 3/25/2013 12:41:24 PM : [std-Group ] 23.4E.5B-->Group=5, Max Hops=3, Hops Left=2 Mon 3/25/2013 12:41:24 PM : [ 23 4E 5B 5] DON 0 Mon 3/25/2013 12:41:24 PM : [ 23 4E 5B 1] ST 0 Mon 3/25/2013 12:41:24 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.05 CB 06 00 (00) Mon 3/25/2013 12:41:24 PM : [std-Group ] 23.4E.5B-->11.00.05, Max Hops=3, Hops Left=2 Mon 3/25/2013 12:41:36 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.05 CB 11 00 LTONRR (00) Mon 3/25/2013 12:41:36 PM : [std-Group ] 23.4E.5B-->Group=5, Max Hops=3, Hops Left=2 Mon 3/25/2013 12:41:36 PM : [ 23 4E 5B 5] DON 0 Mon 3/25/2013 12:41:36 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.05 CB 06 00 (00) Mon 3/25/2013 12:41:36 PM : [std-Group ] 23.4E.5B-->11.00.05, Max Hops=3, Hops Left=2 Mon 3/25/2013 12:41:48 PM : [iNST-SRX ] 02 50 23.4E.5B 00.00.05 CB 11 00 LTONRR (00) Mon 3/25/2013 12:41:48 PM : [std-Group ] 23.4E.5B-->Group=5, Max Hops=3, Hops Left=2 Mon 3/25/2013 12:41:48 PM : [ 23 4E 5B 5] DON 0 Mon 3/25/2013 12:41:48 PM : [iNST-SRX ] 02 50 23.4E.5B 11.00.05 CB 06 00 (00) Mon 3/25/2013 12:41:48 PM : [std-Group ] 23.4E.5B-->11.00.05, Max Hops=3, Hops Left=2 I can get notifications for activation of the Smoke node (Group 1) and the Test node (Group3). I cannot test CO (yet), Malfunction, Low Bat. or Unknown Message nodes. I have not been able to get notifications for Clear, even though the alarm does clear and does seem to send some communications. I even tried creating programs to notify for Clear On and for Clear Off. Is there something in the Event log that hints at why the event is not triggering the program? Here is the Clear On program: +++++++++++++++++++++++++++++++++++ If Status '23.4E.5B-Smoke / 23.4E.5B-Clear' is On Then Send Notification to 'Default' content 'First Alert Clear On' Else - No Actions - (To add one, press 'Action') +++++++++++++++++++++++++++++++++++ 'Default' has my special “Alert†email address and my phone for getting texts – and it works for all other notifications I have set up. Thanks for your help. Bob S.
Recommended Posts