klundy

So how would we use the "is responding" to determine if a device is reachable, without sending an on or off command first? I have a circuit that keeps tripping it's GFI. I haven't been able to determine the cause. I'd like to create a program to monitor a device on that circuit to alert me the circuit has tripped. This has my beer fridge on the lanai, so it is mission critical I know I need to find the root cause of why it is tripping, and I'm hoping getting a timing alert will help in that regard as well. Kevin

That fixed it. At least for a single test. Care to educate me on that? Thanks!! Kevin

I upgraded to 3.3.4 last weekend. I thought I was seeing some strange intermittent behavior of devices coming on. I found it is not intermittent. I have programs that change the LED backlight on KPLs in bedrooms. Anytime the program ran to adust the backlights, the load comes on. Brighten or dim, doesn't matter. It also occurs if I try to manually adjust the backlights via the admin console. Interestingly, the backlights do not change anymore. Just the load comes on. KPL Dimmer v.36 KPL Relay v.36 KPL Relay v.98 all exhibit this behavior. A KPL Dimmer v.2D does NOT turn the load on, but the backlights do not adjust. Kevin

Well, I had added/ programmed 2 other RLs with the RL in the office, as well as the initial program of this very RL before I erased it. But your comment made me try a new location. I put the RL in link mode on a table outside the office and success. I'm also much happier with the correct programming now Thanks for the nudge!

I'm trying to add a new Remotelinc2. I'm getting an error: [FileOpen ] Open failed for [/CONF/1C3D5F.REC] The 1C3D5F is the correct address. The remotelinc is v1.2. I'm running 3.2.6 on my ISY. Earlier this morning, I had added the remote. I wasn't happy with the programming and thought it would be easier to delete and factory reset than to clean up the programming. So I deleted within ISY and then did the reset. since that point, I can't add it back. The full log from the attempt is: Sun 08/26/2012 10:58:22 AM : [FileOpen ] Open failed for [/CONF/1C3D5F.REC] ® Sun 08/26/2012 10:58:22 AM : DB: Cannot init 1C3D5F.REC Sun 08/26/2012 10:58:22 AM : [iNST-TX-I1 ] 02 62 1C 3D 5F 0F 0D 00 Sun 08/26/2012 10:58:22 AM : [iNST-ACK ] 02 62 1C.3D.5F 0F 0D 00 06 (00) Sun 08/26/2012 10:58:31 AM : [iNST-TX-I1 ] 02 62 1C 3D 5F 0F 0D 00 Sun 08/26/2012 10:58:31 AM : [iNST-ACK ] 02 62 1C.3D.5F 0F 0D 00 06 (00) Sun 08/26/2012 10:58:40 AM : [iNST-TX-I1 ] 02 62 1C 3D 5F 0F 0D 00 Sun 08/26/2012 10:58:40 AM : [iNST-ACK ] 02 62 1C.3D.5F 0F 0D 00 06 (00) Sun 08/26/2012 10:58:44 AM : ---- All Remaining Device Added ---- Sun 08/26/2012 10:58:44 AM : [All ] Writing 0 bytes to devices I'm no guru, but my guess is that when I deleted the RL, the ISY didn't delete the config file. I've also rebooted the ISY. Any ideas? Thanks, Kevin

got it! That will actually help me on a different scene I'm working on. Thanks for your help.

Thanks Lee and Apostolakisl, Ok, I fixed it thanks to your help. The one place I had not changed the rate, was on the KPL button under the scene hierarchy. I had only changed it at the actual scene level. To me then, that begs the question - what is the difference in ramp rates at the scene level, and then at the scene controller level? SWMBO = She Who Must Be Obeyed. Aka, the wife

I'm confused on how to use the ramp rate with the ISY. I have a bed lamp plugged into a LampLinc (v.33). I control it with a non load key on a KPL Dimmer (v.36). A year ago, I had programmed this with HouseLinc to have a 8.5 second ramp rate. This is in a scene as I also have a remotelinc to turn this light on/off. Houselinc was deinstalled when I bought the ISY. SWMBO suggested that the ramp rate should be a few seconds longer. No problem I thought. Came into the ISY, looked at the scene and it shows an 8.5 second ramp rate. I drag the indicator over to 30 seconds. Go test, and it takes only 8.5. I then right clicked the KPL button and did a "write updates" just to be sure, and no affect on the ramp rate. So how do I increase the ramp rate? Then a follow up question - is it possible to have a ramp rate only on "off"? In other words, instant on, 30 second off. I'm sure I can do it with multiple ISY programs, but can it be done natively? ISY is at 3.1.15. Thanks Kevin

Could there be a bad link to the download? When I downloaded, the file was 417k. Previous betas were 4.6M. I haven't tried to load the 417k version yet. Kevin

What is the purpose of checking for both "On" and "not Off"? If the device is a relay and not a dimmer, doesn't "on" = "not off"? (I'm still new to the ISY programming, so I am just reading threads to learn) Thanks Kevin

I believe there is some bug in the 3.1.6 backup process. See this thread I started as a separate topic since I wasn't sure where the problem was at first. viewtopic.php?f=25&t=6807 After H2R reported a similar problem as I was having, I went back to a 3.1.5 backup I had and after that restore, everything was fine. Kevin

I concur with Sanders. Update went fine and alerts using a TLS server appear to be working much better. 100% of a small sample set (10). Kevin

Aha! That was a bit of information I did not know, and very possibly explains the behaviour. When I have time, I'l have to capture some data to see if there are retransmissions. The other thing that dawned on me, I still have my HL2 PLM plugged in, with HL2 shut down. I see another thread where you are helping someone remove the HL2 PLM. I'll read that and follow that advice as well. (That PLM is behind a heavy file cabinet, so I'vee been lazy about unplugging in) Thanks again for your help Lee. Kevin

Obviously, something is not clicking ... I created a scene with 2 toggle links and 1 button on a KPL: New Scene, drag and drop the 2 toggles and button. I noticed intermittent behaviour in my rule. So I just tried turning the scene on and off from within the ISY console. I did that 10 times. It fully worked 3 times, 1 time it just turned on the button, and 6 times nothing happened. That makes me think it is just a communication issue. So I then go to the individual devices within the ISY console. I turned them each on/off at least 20 times. 100%. No issues at all. That seems to indicate communication is fine. I also assume I created the scene correctly, otherwise it wouldn't have worked those 3 times. This is not making any sense to me. Kevin

This is one of those that I think the KISS principle applies. Use your regular garage door opener. Add a garagelinc (I/O linc) to monitor the door. When the door opens, trigger your other scenes. You could determine the home/away based on how the door is opened. If opened via a button in the house, then you must be leaving, set status away, if opened without a button, then you must be coming home. Now having said that, I wish someone would create a receiver for Homelink (I think that is what it is called) that is built into most newer cars to replace garage door openers. My Honda has 3 built in buttons, I use one for the neighbor hood gate, one for the garage door, which would leave one for something else. Kevin

With 750, 7 out of ten went through. With 875, 6 out of ten. With 1000 it was 6 out of ten. I still see 1 server error and the rest were password errors. With "use default" it was 10 out of ten. I also think I identified a GUI bug. When just changing the timeout, the save button doesn't seem active. I had to click on another field in order to get the save button to save. I found another thread similar to my IR messages and you indicated to that user it sounded like a bad IR module. Should I contact support for a replacement (I purchased directly from the UD store). Last I checked, today is Sunday, shouldn't you be off today?

Changing the timeout to 500 improved my results, but still not 100%. I just did 10 test mails from the configuration screen. 1 every 10 seconds or so. 7 were successful (with the body timeout error), but 3 gave me a password error. Note that I wasn't changing the password during this test Also, any thoughts on the IR messages I am receiving? Thanks!!! Kevin

Michel - What he said Exactly. When I got the body timed out, the test messages went through. Like Jim, I then tried another server (yours via "use default"). So far today, that has been 100% - although 2 test messages still through an error on the console even though I received the email. I'm quite content to "use default". But it appears that the smtp code is not properly closing the connection and gmail appears more sensitive to that issue. Are the IR button presses I mentioned earlier in the system log anything I need to worry about? Right now I'm only using 2 IR codes, so I guess as long as the spurious codes don't overlap with my live ones, it's no big deal. Thanks Kevin

Since installing 3.1.5 my email notifications have been intermittent. In the previous release version (non-beta), the notifications were 100%. I know the programs are triggering by looking at the last run time. I also added a variable that I increment every run. Today, it incremented 5 times (which is right), but I only received 2 emails. But the fact that I received 2 shows that the email properties are correct. I just now triggered the program 4 times (opening a door). Variable incremented 4 times, so Insteon connectivity is fine. I received 3 out of 4 emails. The error log indicates no network connectivity, but yet i was logged into the admin interface over the network. No new Insteon devices. No new network devices or changes to the network. The problem definitely started with the upgrade. Now, this next part may or may not be related. In trying to find clues to the email problem, I opened the event viewer. The thing is receiving some sort of IR event about every few seconds. I covered the front ISY to ensure it wasn't picking up some wild IR light. Fri 07/22/2011 07:47:18 PM : [ IR] 02AA Press Fri 07/22/2011 07:47:18 PM : [ IR] 015A Press Fri 07/22/2011 07:47:21 PM : [ IR] 0152 Press Fri 07/22/2011 07:47:22 PM : [ IR] 0092 Press Fri 07/22/2011 07:47:29 PM : [ 10 E4 37 1] ST 0 Fri 07/22/2011 07:47:34 PM : [ IR] 0295 Press Fri 07/22/2011 07:47:38 PM : [ IR] 02A9 Press Fri 07/22/2011 07:47:40 PM : [ IR] 00AA Press I can't say that I looked at the event viewer in the previous version, so I don't know if this is a new problem related to the beta, or if I have a possible hardware problem. Thanks for any pointers Kevin

Thanks Lee. I'm still thinking about your response ... I'm not sure yet, but I think you highlighted that I was creating a problem when there was no problem, and that was my problem Kevin

Hi all - i think I need a sanity check or a kick in the right direction. I've read through a lot of the forum as well as the wiki. I suspect the answer is there, but I have confused myself. Background - I've got 40 something Insteon devices. Lots of direct controller/responder links. I had been using Houselinc. I bought the ISY several months ago, installed it and then got busy with work. I'm back to having some free time. I upgraded to the latest beta (why start with the old) I don't recall how all the devices and scenes got into the ISY, but they are all there and I know I didn't do it manually. A simple example that leads to my confusion: I have 2 sets of front lights, each on a toggle linc. On a KPL in another room, I linked a button as a controller for both toggles. I also set the toggles as controllers of that button so the button comes on if either toggle is on. When the ISY did it's crawl, it created 2 scenes - one for each toggle linc. So I decide I was going to create a rule (involving garage door and light status, etc). I was thinking that rather than controlling both toggles and KPL button individually within the rule, I should create a single scene (e.g. "all front lights"). That would also let me re-use the scene in other rules if appropriate. I create the scene, drag and drop the devices and the ISY complains (something to the effect that those are already controller/responders). I let it create anyway, but it now lists all 3 devices in blue. I fully expect to have a "doh" moment when someone answers. I expected to be able to have multiple scenes with re-used controller/responders. E.g. Porch lights=toggleA and KPL button. Garage lights=toggleB and KPL button. All front lights=toggleA, toggleB and KPL button. So with the ISY, should I be doing those 3 scenes independantly? Or the 2 individual scenes within the ALL scene? Do I need to think of ISY scenes any different from Insteon or HL scenes? Or maybe it's because the ISY is reusing scenes either from the devices themselves or the HL PLM and I need to nuke all links/scenes and start clean with the ISY? I'm hesitant to go that route as all the direct control links of devices are working the way I want (and importantly the way my wife accepts ) Thanks for reading this far and I hope my rambling makes sense. Kevin