416to305 Posted November 15, 2014 Share Posted November 15, 2014 Hey everyone, I'm trying to make a program where I press a KPL button, it arms Away mode (which is just a variable changing from 0 to 1) after a delay like 30 seconds or so letting us leave the house, but also beeping/flashing while the countdown happens. The KPL is on my main floor, and on the same phase is a LampLinc about 10 feet away on an outlet, 2 SwitchLinc's maybe 15 feet away, another LampLinc one floor up directly above the KPL, and another KPL maybe 40 feet away on the same floor also on the same phase. Below is a quick program I did mostly as a test: If Control 'Front Foyer.G' is switched On Then Repeat 8 times Set Scene 'Front Foyer KPL G' On Set 'Front Foyer Light' 100 (Beep Duration) Wait 2 seconds Set Scene 'Front Foyer KPL G' Off Wait 2 seconds Repeat 1 times $s.HouseStatus = 1 Set Scene 'Front Foyer KPL G' On Set Scene 'Kitchen KPL D' On Set 'Front Foyer Light' 100 (Beep Duration) Set 'Front Foyer Light' 100 (Beep Duration) Set 'Front Foyer Light' 100 (Beep Duration) Else - No Actions - (To add one, press 'Action') So few things, I have it as 2 seconds because 1 was giving issues but seems to be similar issue with 2 seconds. Also I'm not sure how to make something happen after a repeat, so that's why the last stage is Repeat 1 time as Repeat 0 doesn't make any of that trigger and Repeat 1 time seems to do it only once. Anyway the problem is that it's not consistent. Like I'll press the KPL button, it lights up and a second later it beeps, maybe 2 seconds later it beeps and flashes again, then it might sit there for 3 seconds and do nothing, and then flash twice and beep twice fast, then do the final few properly 2 seconds apart etc. I moved a LampLinc literally 2 feet away from it but it does the same thing, so I don't think it's an issue with range or coverage as there's so many devices near by. Seems like it can't keep up with beeping and what not. Not sure if the beep duration means time? Like is 100 1 second, 250 2.5 seconds etc? Could try to play with that but wanted to see first if this was the best way to make something beep, flash and repeat or if there's a more efficient way to do it, as ideally I'd like the kitchen KPL to also do the same thing and vice versa. As a side question, does anyone have any good examples of an "Arm AWAY" type program with an exit delay, that ideally shows feedback like flashing or beeping etc? Mine does work, but always feel like I'm reinventing the wheel lol. Thanks! Link to comment
LeeG Posted November 15, 2014 Share Posted November 15, 2014 The Program should not produce the varying results. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Trace the activity when KPL button pressed and post trace. Repeat 1 brackets the above Repeat and statements after Repeat 1 execute once. Link to comment
416to305 Posted November 15, 2014 Author Share Posted November 15, 2014 Here's from a couple days ago, note that the program wasn't the same, I had it flashing for 1 second and a few other differences, but when it was really slow I captured this. I'll do it again when I get home, but figured this might help a little for now if it shows errors etc. No idea how to read this lol. Fri 11/14/2014 12:42:43 PM : [iNST-ACK ] 02 62 00.00.1B CF 13 00 06 LTOFFRR(00) Fri 11/14/2014 12:42:43 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [0] uom=0 prec=-1 Fri 11/14/2014 12:42:43 PM : [ 2B FF F9 7] ST 0 Fri 11/14/2014 12:42:43 PM : [iNST-ACK ] 02 62 00.00.1B CF 11 00 06 LTONRR (00) Fri 11/14/2014 12:42:43 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [255] uom=0 prec=-1 Fri 11/14/2014 12:42:43 PM : [ 2B FF F9 7] ST 255 Fri 11/14/2014 12:42:44 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 13 00 Fri 11/14/2014 12:42:44 PM : [iNST-ACK ] 02 62 2B.FF.F9 0F 30 64 06 BEEP (64) Fri 11/14/2014 12:42:44 PM : [iNST-SRX ] 02 50 2B.FF.F9 2C.08.F8 2B 30 64 BEEP (64) Fri 11/14/2014 12:42:44 PM : [std-Direct Ack] 2B.FF.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 11/14/2014 12:42:44 PM : [iNST-DUP ] Previous message ignored. Fri 11/14/2014 12:42:44 PM : [iNST-ACK ] 02 62 00.00.1B CF 13 00 06 LTOFFRR(00) Fri 11/14/2014 12:42:44 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [0] uom=0 prec=-1 Fri 11/14/2014 12:42:44 PM : [ 2B FF F9 7] ST 0 Fri 11/14/2014 12:42:45 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 11 00 Fri 11/14/2014 12:42:45 PM : [iNST-TX-I1 ] 02 62 2B FF F9 0F 30 64 Fri 11/14/2014 12:42:45 PM : [iNST-ACK ] 02 62 00.00.1B CF 11 00 06 LTONRR (00) Fri 11/14/2014 12:42:45 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [255] uom=0 prec=-1 Fri 11/14/2014 12:42:45 PM : [ 2B FF F9 7] ST 255 Fri 11/14/2014 12:42:45 PM : [iNST-ACK ] 02 62 00.00.1B CF 13 00 06 LTOFFRR(00) Fri 11/14/2014 12:42:45 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [0] uom=0 prec=-1 Fri 11/14/2014 12:42:45 PM : [ 2B FF F9 7] ST 0 Fri 11/14/2014 12:42:46 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 13 00 Fri 11/14/2014 12:42:46 PM : [iNST-ACK ] 02 62 00.00.1B CF 11 00 06 LTONRR (00) Fri 11/14/2014 12:42:46 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [255] uom=0 prec=-1 Fri 11/14/2014 12:42:46 PM : [ 2B FF F9 7] ST 255 Fri 11/14/2014 12:42:46 PM : [iNST-ACK ] 02 62 2B.FF.F9 0F 30 64 06 BEEP (64) Fri 11/14/2014 12:42:47 PM : [iNST-SRX ] 02 50 2B.FF.F9 2C.08.F8 2B 30 64 BEEP (64) Fri 11/14/2014 12:42:47 PM : [std-Direct Ack] 2B.FF.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 11/14/2014 12:42:47 PM : [iNST-ACK ] 02 62 00.00.1B CF 13 00 06 LTOFFRR(00) Fri 11/14/2014 12:42:47 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 11 00 Fri 11/14/2014 12:42:47 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [0] uom=0 prec=-1 Fri 11/14/2014 12:42:47 PM : [ 2B FF F9 7] ST 0 Fri 11/14/2014 12:42:47 PM : [iNST-ACK ] 02 62 00.00.1B CF 11 00 06 LTONRR (00) Fri 11/14/2014 12:42:48 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 13 00 Fri 11/14/2014 12:42:48 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [255] uom=0 prec=-1 Fri 11/14/2014 12:42:48 PM : [ 2B FF F9 7] ST 255 Fri 11/14/2014 12:42:48 PM : [iNST-ACK ] 02 62 00.00.1B CF 13 00 06 LTOFFRR(00) Fri 11/14/2014 12:42:48 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [0] uom=0 prec=-1 Fri 11/14/2014 12:42:48 PM : [ 2B FF F9 7] ST 0 Fri 11/14/2014 12:42:49 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 11 00 Fri 11/14/2014 12:42:49 PM : [iNST-TX-I1 ] 02 62 2B FF F9 0F 30 64 Fri 11/14/2014 12:42:49 PM : [iNST-ACK ] 02 62 00.00.1B CF 11 00 06 LTONRR (00) Fri 11/14/2014 12:42:49 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [255] uom=0 prec=-1 Fri 11/14/2014 12:42:49 PM : [ 2B FF F9 7] ST 255 Fri 11/14/2014 12:42:49 PM : [iNST-ACK ] 02 62 2B.FF.F9 0F 30 64 06 BEEP (64) Fri 11/14/2014 12:42:50 PM : [iNST-SRX ] 02 50 2B.FF.F9 2C.08.F8 2B 30 64 BEEP (64) Fri 11/14/2014 12:42:50 PM : [std-Direct Ack] 2B.FF.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 11/14/2014 12:42:50 PM : [iNST-DUP ] Previous message ignored. Fri 11/14/2014 12:42:50 PM : [iNST-SRX ] 02 50 2B.FF.F9 2C.08.F8 23 30 64 BEEP (64) Fri 11/14/2014 12:42:50 PM : [std-Direct Ack] 2B.FF.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 11/14/2014 12:42:50 PM : [iNST-SRX ] 02 50 2B.FF.F9 2C.08.F8 23 30 64 BEEP (64) Fri 11/14/2014 12:42:50 PM : [std-Direct Ack] 2B.FF.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 11/14/2014 12:42:50 PM : [iNST-DUP ] Previous message ignored. Fri 11/14/2014 12:42:50 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 13 00 Fri 11/14/2014 12:42:50 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 11 00 Fri 11/14/2014 12:42:50 PM : [iNST-ACK ] 02 62 00.00.1B CF 13 00 06 LTOFFRR(00) Fri 11/14/2014 12:42:50 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [0] uom=0 prec=-1 Fri 11/14/2014 12:42:50 PM : [ 2B FF F9 7] ST 0 Fri 11/14/2014 12:42:51 PM : [iNST-ACK ] 02 62 00.00.1B CF 11 00 06 LTONRR (00) Fri 11/14/2014 12:42:51 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [255] uom=0 prec=-1 Fri 11/14/2014 12:42:51 PM : [ 2B FF F9 7] ST 255 Fri 11/14/2014 12:42:52 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 13 00 Fri 11/14/2014 12:42:52 PM : [iNST-ACK ] 02 62 00.00.1B CF 13 00 06 LTOFFRR(00) Fri 11/14/2014 12:42:52 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [0] uom=0 prec=-1 Fri 11/14/2014 12:42:52 PM : [ 2B FF F9 7] ST 0 Fri 11/14/2014 12:42:53 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 11 00 Fri 11/14/2014 12:42:53 PM : [iNST-TX-I1 ] 02 62 2B FF F9 0F 30 64 Fri 11/14/2014 12:42:53 PM : [iNST-ACK ] 02 62 00.00.1B CF 11 00 06 LTONRR (00) Fri 11/14/2014 12:42:53 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [255] uom=0 prec=-1 Fri 11/14/2014 12:42:53 PM : [ 2B FF F9 7] ST 255 Fri 11/14/2014 12:42:53 PM : [iNST-ACK ] 02 62 2B.FF.F9 0F 30 64 06 BEEP (64) Fri 11/14/2014 12:42:54 PM : [iNST-SRX ] 02 50 2B.FF.F9 2C.08.F8 2B 30 64 BEEP (64) Fri 11/14/2014 12:42:54 PM : [std-Direct Ack] 2B.FF.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 11/14/2014 12:42:54 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 13 00 Fri 11/14/2014 12:42:54 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 11 00 Fri 11/14/2014 12:42:54 PM : [iNST-ACK ] 02 62 00.00.1B CF 13 00 06 LTOFFRR(00) Fri 11/14/2014 12:42:54 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [0] uom=0 prec=-1 Fri 11/14/2014 12:42:54 PM : [ 2B FF F9 7] ST 0 Fri 11/14/2014 12:42:55 PM : [iNST-ACK ] 02 62 00.00.1B CF 11 00 06 LTONRR (00) Fri 11/14/2014 12:42:55 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [255] uom=0 prec=-1 Fri 11/14/2014 12:42:55 PM : [ 2B FF F9 7] ST 255 Fri 11/14/2014 12:42:56 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 13 00 Fri 11/14/2014 12:42:56 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 11 00 Fri 11/14/2014 12:42:56 PM : [iNST-ACK ] 02 62 00.00.1B CF 13 00 06 LTOFFRR(00) Fri 11/14/2014 12:42:56 PM : [VAR 2 10 ] 1 Fri 11/14/2014 12:42:56 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [0] uom=0 prec=-1 Fri 11/14/2014 12:42:56 PM : [ 2B FF F9 7] ST 0 Fri 11/14/2014 12:42:56 PM : [iNST-ACK ] 02 62 00.00.1B CF 11 00 06 LTONRR (00) Fri 11/14/2014 12:42:56 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [255] uom=0 prec=-1 Fri 11/14/2014 12:42:56 PM : [ 2B FF F9 7] ST 255 Link to comment
LeeG Posted November 15, 2014 Share Posted November 15, 2014 There looks like an issue between the Scene On to turn the KPL button On and the Beep to the SwitchLinc. The Scene On does not get an ACK from the KPL (normal) so the Scene On may not have worked. The Beep gets multiple ACKs which is not normal. Fri 11/14/2014 12:42:49 PM : [iNST-TX-I1 ] 02 62 00 00 1B CF 11 00 Fri 11/14/2014 12:42:49 PM : [iNST-TX-I1 ] 02 62 2B FF F9 0F 30 64 Fri 11/14/2014 12:42:49 PM : [iNST-ACK ] 02 62 00.00.1B CF 11 00 06 LTONRR (00) Fri 11/14/2014 12:42:49 PM : [D2D EVENT ] Event [2B FF F9 7] [sT] [255] uom=0 prec=-1 Fri 11/14/2014 12:42:49 PM : [ 2B FF F9 7] ST 255 Fri 11/14/2014 12:42:49 PM : [iNST-ACK ] 02 62 2B.FF.F9 0F 30 64 06 BEEP (64) Fri 11/14/2014 12:42:50 PM : [iNST-SRX ] 02 50 2B.FF.F9 2C.08.F8 2B 30 64 BEEP (64) Fri 11/14/2014 12:42:50 PM : [std-Direct Ack] 2B.FF.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 11/14/2014 12:42:50 PM : [iNST-DUP ] Previous message ignored. Fri 11/14/2014 12:42:50 PM : [iNST-SRX ] 02 50 2B.FF.F9 2C.08.F8 23 30 64 BEEP (64) Fri 11/14/2014 12:42:50 PM : [std-Direct Ack] 2B.FF.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 11/14/2014 12:42:50 PM : [iNST-SRX ] 02 50 2B.FF.F9 2C.08.F8 23 30 64 BEEP (64) Fri 11/14/2014 12:42:50 PM : [std-Direct Ack] 2B.FF.F9-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 11/14/2014 12:42:50 PM : [iNST-DUP ] Previous message ignored. What ISY firmware was in use when this trace was run? Link to comment
416to305 Posted November 16, 2014 Author Share Posted November 16, 2014 It's firmware 4.2.18. I'll try to do it again later and post the results again, just got home but I'll test it again after and see what happens. Link to comment
larryllix Posted November 17, 2014 Share Posted November 17, 2014 I have a similar situation. The Insteon traffic is just swamped with activity and you cannot depend on anything getting through. When I arrive home I press a sequence to turn off a beeping X10 module. Sometimes it continues to beep for another 60 seconds after. You may need to spread those beeps out even more to get reliable responses. The beep variable is a dummy and has no bearing on time length. The syntax of the Repeat is incorrect. "REPEAT 1" means do not repeat at all. Should have been "REPEAT END" Link to comment
apostolakisl Posted November 17, 2014 Share Posted November 17, 2014 I have a similar situation. The Insteon traffic is just swamped with activity and you cannot depend on anything getting through. When I arrive home I press a sequence to turn off a beeping X10 module. Sometimes it continues to beep for another 60 seconds after. You may need to spread those beeps out even more to get reliable responses. The beep variable is a dummy and has no bearing on time length. The syntax of the Repeat is incorrect. "REPEAT 1" means do not repeat at all. Should have been "REPEAT END" Unless something has changed since 4.2.8, there is no "repeat end" and using "repeat 1" is the proper way to end a repeat. Though "repeat end" would be more logical and a "repeat 0" would not even be an option. Link to comment
Teken Posted November 17, 2014 Share Posted November 17, 2014 There is a post in the new Insteon forum under the wish list sub group. Requesting that all future devices have a native beep / LED feature. This would in essence allow the end user to initiate the beep, LED blink, set the duration & frequency. What the OP is doing is simply sending a broadcast message that fills the power line with endless messages. Which everyone knows is very bad for COM's and is not consistent in its end result. Please consider lending your voice to that thread and perhaps this feature will be added in later iterations. Encrypted By: Phoenix Security Solutions Link to comment
416to305 Posted November 17, 2014 Author Share Posted November 17, 2014 Well in fairness, I'm not sure why they would have a Beep feature or option and then not expect people to actually want to make something beep a few times. I can't see any reason that having it beep just once would ever be beneficial. It seems more that it's the ISY that can't keep up as if you have the admin console open all it does is pop up a progress bar saying System Busy every time it makes it beep or flash. My Z-Wave light switches can beep as long as you want, so I just ended up changing it to have the Vera make my bathroom light switch beep every second when the door opens and it seems to work. Link to comment
Teken Posted November 17, 2014 Share Posted November 17, 2014 Well in fairness, I'm not sure why they would have a Beep feature or option and then not expect people to actually want to make something beep a few times. I can't see any reason that having it beep just once would ever be beneficial. It seems more that it's the ISY that can't keep up as if you have the admin console open all it does is pop up a progress bar saying System Busy every time it makes it beep or flash. My Z-Wave light switches can beep as long as you want, so I just ended up changing it to have the Vera make my bathroom light switch beep every second when the door opens and it seems to work. You have to keep in mind the maker included the beeper / LED solely as a hardware confirmation and error detection. It was not provided to the end user as a means of self automating and controlling its native behaviour. Hence why I suggested that Smartlabs reconsider these hardware aspects to allow an end user to control and manipulate both LED's and beep functions. The latter does not rely on continuous COM's to be sent over the line as its done now. With the new feature the device could be programmed to beep / LED pulse set by the user as it would be native and not requested externally as it is done now. Encrypted By: Phoenix Security Solutions Link to comment
Teken Posted November 17, 2014 Share Posted November 17, 2014 For the benefit of others this is the reference link asking this feature be included in the next generation Insteon product line: http://forum.insteon.com/forum/main-category/new-insteon-device-wish-list/16482-native-beep-flash Please select the *Like* and add your voice. As this is the ONLY method to show demand and bring this feature to market. Link to comment
larryllix Posted November 17, 2014 Share Posted November 17, 2014 I could see the LED flash (pardon the pun), for the few devices that aren't behind furniture, but the beepers (for me) are a waste of time. None of my 25 or so can be heard more than about 3 feet away even with all audio devices off and our home is extremely quiet to outside noise. Perhaps the KPL units make louder sounds. It would seem the units have blinking built in to accommodate the setting table being implemented in some versions, so the control of it would be an easy addition. Just have the beep length function converted to a beep count instead. The protocol with the passed parameter should already be in place. Link to comment
Teken Posted November 17, 2014 Share Posted November 17, 2014 I could see the LED flash (pardon the pun), for the few devices that aren't behind furniture, but the beepers (for me) are a waste of time. None of my 25 or so can be heard more than about 3 feet away even with all audio devices off and our home is extremely quiet to outside noise. Perhaps the KPL units make louder sounds. It would seem the units have blinking built in to accommodate the setting table being implemented in some versions, so the control of it would be an easy addition. Just have the beep length function converted to a beep count instead. The protocol with the passed parameter should already be in place. The above suggestions should be indicated in the linked thread and "Like" the suggestion so Smartlabs can see public support of said feature. Many people are quick to say, but rarely act. Encrypted By: Phoenix Security Solutions Link to comment
larryllix Posted November 17, 2014 Share Posted November 17, 2014 You should to start a new thread with something about "support" in the title. Many here report using this beep successfully. The quest is hidden here and probably a hijack of the thread. The forum also requires an account that some may not prefer. Link to comment
apostolakisl Posted November 17, 2014 Share Posted November 17, 2014 I don't see where this particular program would flood the lines. It is just a single command every 2 seconds. I have several programs that operate exactly the same except I only have a 1 second wait on the loop and I don't have any issues with them running. The only thing close to calling a problem is that the beep is not perfectly at 1 second intervals, presumably the reason is varying number of hops from one PLC to the next. Link to comment
416to305 Posted November 17, 2014 Author Share Posted November 17, 2014 I have no problem hearing any of my KPLs or SwitchLinc's. If the TV was blasting them probably not, but I'd say it's just as loud as a cell phone text message tone or whatever, to the point that I can hear it from 2 floors down. Mostly given up on it though, not really that huge of a deal for me so ended up changing most of my programs like the enable away mode, to just light up when I press the KPL button, not flash, but only activate away mode after 60 seconds vs beeping and flashing a countdown. Link to comment
Xathros Posted November 20, 2014 Share Posted November 20, 2014 I use the beep for three functions: 1) Single beep a scene with many devices whenever and exterior door opens. 2) 30 second countdown with a beep every second before an auto off timer expires in a few locations (single device scene) 3) Confirmation beep in places where I trigger a program with a FastOn, FastOff or Fade control. In general these all work just fine. Like others, i see variation in timing with a sequence of beeps. I attribute this to variations in comms quality / other traffic from motion sensors etc. I exclusively use scenes for the beep as I believe there is less traffic involved than when addressing a device directly. (Maybe LeeG can confirm or bust me bubble on that). I completely agree that a variable duration beep and blink capability should be built into certain devices (KPLs and Switchlincs and Toggleincs mostly). -Xathros Link to comment
LeeG Posted November 20, 2014 Share Posted November 20, 2014 Xathros An ISY Scene name used in a Program or invoked from Admin Console or App using ISY Scene name is a single outbound command from the PLM. No ACKs from the Responder(s). The same ISY Scene invoked from a Red node Controller below Scene name is handled by that Red node Controller as a normal Insteon Scene. A Group Broadcast message (not ACKed) followed by a Group Cleanup Direct message to each Scene Responder with the Group Cleanup Direct message ACKed by each Responder. I2CS devices have some control over the number of retries of the Group Cleanup Direct message. Link to comment
Xathros Posted November 20, 2014 Share Posted November 20, 2014 LeeG- Thanks. So then by utilizing an ISY scene to beep a device, rather than a direct command, I am reducing overall traffic by roughly 50% correct? -Xathros Link to comment
LeeG Posted November 20, 2014 Share Posted November 20, 2014 That's right on. From Scene Beep a single command is sent and no ACK. Thu 11/20/2014 05:37:07 PM : [iNST-TX-I1 ] 02 62 00 00 6E CF 30 00 Thu 11/20/2014 05:37:07 PM : [iNST-ACK ] 02 62 00.00.6E CF 30 00 06 BEEP (00) From a Direct Beep a single command is sent with an associated ACK received. Thu 11/20/2014 05:38:15 PM : [iNST-TX-I1 ] 02 62 1D 23 6B 0F 30 64 Thu 11/20/2014 05:38:15 PM : [iNST-ACK ] 02 62 1D.23.6B 0F 30 64 06 BEEP (64) Thu 11/20/2014 05:38:16 PM : [iNST-SRX ] 02 50 1D.23.6B 22.80.0B 2B 30 64 BEEP (64) The only downside is if the Insteon network is marginal the Scene Beep could be missed due to lack of ACK. Should not be an issue for those who have a functional Insteon network. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.