bcall

I just upgraded from 3.2.4 to 3.2.5 and can no longer communicate with several devices (switchlinc, icon switch, 8 button keypadlinc...). I downgraded and some of the devices started communicating again, but not all. I have had a few devices stop communicating over the last few months (about 3 devices in 3 months). Could this be caused by a fault in the plm? I've restored the plm, restored the ISY, reverted to previous firmware, restored all devices. So far nothing helps. My plm is the original one that came with the ISY (about three years ago) - v.85. Thanks for any help.

LeeG, You are a genius! It's working again. Thank you!!!

update: I tried switching the program to trigger from another dual band switchlinc. Still not working. Tried a regular switchlinc. not working Tried an icon dimmer. not working for each, i tried faston and on. I upgraded to 3.2.4 and tried everything again. not working I downgraded to 3.1.17. not working. Ok. I'm stumped. fyi - i created a program that turned a light on at a specific time and it worked. I also created a program that triggered based on the armed status of my ELK (I have the ELK module), and it worked as well. So, as far as I can tell, it seems to be only the programs that trigger from Insteon functions. Also, the admin console does not update when I turn a light on or off. For example, if I have my kitchen light selected in the console and it's currently on, the console will show its state as on. However, if I go to the switch and turn it off, the console still shows it as off. If I right click on the device and force a query, it then shows up as off. However, I thought that previously, when I turned a switch on or off at the switch itself, the console would instantly update. Is my memory incorrect on that? Could it be that my ISY just isn't hearing the commands from the switches? I'm still able to turn the switches on and off from the console.

Hi Michel, I have 3.2.3 installed and everything seemed ok. But I just noticed that I'm not getting appropriate communication with a dual band switchlinc dimmer v.40 (2477D). The ISY is able to turn it on and off but it can't do the following: 1. i have programs triggered when FastOn is used from this switch. But, when I double click the switch, the program does not get triggered. 2. I tried restoring the device. I got no errors on the restore, but it didn't solve the problem. 3. Then I tried a couple of tests: I tried adjusting the ramp rate and the on Level. The ISY seemed to think it had made the adjustments, but the switch didn't get the changes (i.e., ramp rate and on level stayed the same as before). I believe this was working in 3.1.x. I didn't notice that it wasn't working until after I upgraded to the new beta. I didn't have a chance to install 3.2.1 or 3.2.2. I checked the error log and it has no entries related to this (or anything around the same time frame). Any help would be appreciated. bcall

Teken, You may already have considered this, but you could set up a scene with everything but the garage door relay. Then use that scene rather than all on. It's a bit of a pain, but it seems like that work around should address the problem.

Hi Michel, I installed 3.1.6 as soon as it came out and I haven't had any recurrences of the Elk crash issue since. I've been installing new devices and I just read about the backup issue with 3.1.6. Do you have an estimate on when 3.1.7 may arrive? Just wondering if I should hold off on some of my new installs. Also, just out of curiosity, any new goodies planned for 3.1.7? What can I say...I'm a geek and I get excited about things like this! Also, I noticed your post on the elk thread mentioning that the elk module is getting close. Any eta on that? Will it be in beta form when released? Again, let me repeat, I'm a geek so please forgive my eagerness. ) bcall

Hi Michel, Lol. The only reason I bought and installed the Elk at my parents was so that it could integrate with the ISY I installed there. The Elk is way overkill for their needs, but I wanted to be able to automate some things for them based on the status of alarm zones. I'll severe the connection and let you know what happens. The ISY only crashes about once every week or two, so it may be some time before I have some feedback. Also, I haven't entered programming mode on the Elk in about five months. So, if the Elk's programming mode is the only thing that hangs the ISY, maybe the Elk isn't the problem? I do communicate with the ISY using Mobilinc and also directly using HTTP commands from an app called iRule (which allows me to send HTTP commands from my iPad). But I communicate with the ISY at my house through the same two means and it doesn't ever crash. The only difference between the set up at my house and my parents is the Elk. BTW - I would have installed the ISY at their house regardless of whether it talked to the Elk (I can't imagine them living without an ISY, it just wouldn't be civilized!). Any idea when the Elk module might be ready? If this turns out to be the cause of the crashing, are there any openings in the Elk module beta program? Thanks for your help, Brad

Hi Michel, My ISY has also been freezing sporadically over the last few weeks. It's been driving me nuts. It wouldn't be that big a deal but I use it to control my EZRain and I live in Las Vegas, so the plants don't get watered and when it's over 100 degrees that can be really bad. I have two ISYs, one at my house and one at my parents'. The one at my house never crashes. It's the one at my parents' house that's been problematic. That one is connected to an Elk security system. I noticed you mentioned that in your diagnostic questions. Thanks for any help you can give. Brad

I've been working with the rest interface and I don't think I'm getting appropriate responses. 1) I send "http://username:password@ISYIPADDRESS/rest/nodes//cmd/DON". The device I'm referencing is an insteon light switch. 2) I get the following response: " 200 ". However, the light doesn't turn on. 3) I resend the command a few times, getting the same affirmative response each time, and the light eventually turns on. The same thing happens when I send "DOF" trying to turn the light off. Both commands work sporadically. I've tried sending from IE and Firefox (on a PC for each) with the same results. Also, same results for Safari on a Mac. I originally discovered the issue when trying to send from an objective C program written with xcode (compiled for a Mac). Am I missing something? If the rest response is "succeeded="true"" then shouldn't the light turn on (or off, as applicable)? I'm posting this here because I've seen some questions that relate to issues that have emerged in the 2.8.x betas, and I'm not sure if this is one of those issues. Sorry if this isn't the right place to post this. Thanks.