cdneh

No program triggers the IOlinc. Manually turned ON to open garage door from MobiLinc (thru portal). The offending programs simply return the relay to OFF state to simplify the next ON/opening request. Option settings are identical for all three IOlincs: - LED on TX - Monentary (ON or OFF) Thx, - Chris

v4.5.1 for both firmware and UI - Chris

Done and done. As I mentioned, I even recreated the programs with random gibberish names to eliminate any potential for another program disabling them. No change. Thx. - Chris

Yeah, I save and I save and I save, and I save. That's not it. Thx, though. Good thought. - Chris Edit: Moreover, if I go back into the Console,say, 30 minutes after enabling or creating the programs, they show as "enabled". When I check back, say, the next morning, they are disabled. Saving changes isn't the issue.

Ok, this is driving me crazy... I have three simple programs that, when an IOLink relay is switched ON, wait 50 seconds and then switch it OFF. One of the programs for one of the IOLinks runs flawlessly. The other two are repeatedly being set to 'disabled' (i.e., not "enabled") and, as a result, do not execute. I've have deleted and recreated the offending programs multiple times without any change, A few hours after I create them and check "enable", I'll return to the Admin Console and find them disabled. I have no programs that are disabling them. I am not disabling them. I've even tried giving the programs random names and the behaviour is exactly the same: disabled within a few hours. Sample program attached. What the heck am I missing? Thx, - Chris

Michel, Brilliant. Problem solved by having ISY use DHCP and having router assign a predetermined IP. Not sure why it works, but happy it does. Thanks for the super quick response. - Chris

I'm totally stuck. Long time ISY user (ISY 994irPRO f/w v4.2.30). I have dozens of notifications set up -- using Gmail SMTP/TLS -- which have been happily running for a few years. We changed Cdn ISPs (from Rogers to Teksavvy, both over cable) on June 23 and suddenly notifications went dead. Test messages elicit error messages in the form: "Mail Server DNS Error / [[sMTP_ERRORS-smtp.gmail.com]]" For timeouts below 10,000, I'm also seeing: "TCP client DNS error / [api.areisapi.com] My initial thought was the ISP was the culprit but I've been back and forth with them trying different DNS targets without change. Then it dawned on me that my Synology NAS also sends notifications utilizing exactly the same Gmail SMTP service and credentials. It continues to function perfectly. I've also tried an alternative -- i.e., not Gmail -- SMTP server with exactly the same error results. Finally, I just realized my climate module is also dead and will not connect to any of the multiple local and remote sources I've tried. However, I cannot be sure that the climate module failure began with the ISP change or arose subsequent to my update to 4.2.30 a few days ago. So, apart from concluding that at least part of the problem is the ISY, I'm completely stumped. Ideas anyone? Thanks, - Chris

Michel, Thanks for the response and the guidance. Much appreciated. I actually have submitted a couple of tickets request using your contacts page. First was Tuesday AM (EST) and again late Thursday evening. So, not sure why you're not seeing them. Regardless, your multiple reboot suggestion was successful. It actually took 8 consecutive reboots before the the ISY became partially responsive, although after 3 or 4, the LED flash patterns began to change from what I had described above. For what it's worth, after 8 reboots the unit became network accessible, but not otherwise functional. My config had disappeared leaving only the ID and PWD at the HTML level intact. Unit initially would not restore from backup and reported a variety of errors over multiple attempts (e.g., null or bad pointer; will not accept upgrade (??); and several other I wasn't quick to note). After about 4-5 attempts at a restore, I succeeded. All devices, scenes and programs back! WooHoo. At this stage, the only functionality still absent (of which I'm aware, anyway) is internet access. Using the menu option "Enable Internet Access" either elicits an error ("Failed Enabling ...") or no response. Prior to the PLM failure, I had enabled Internet Access without issue. Any suggestions on that score? By the way, for the few weeks I had your product running, I was generally very impressed. Also, your proactive user support so visible on this forum is superb. Thanks, - Chris

Hoping one of y'all ISY brains can point me in the right direction. I tried some days ago contacting UD's tech supp but have not received any response. Some weeks ago, my ISY (IR Pro)new in 09Nov, f/w 2.7.0 as shipped) stopped communication with my Insteon devices. Was able to access ISY HTTP/Java interface but it always displayed 'system busy" or some similar message and would not report the status of any devices. RX led was steady on. Docs indicate that likely means a PLM problem. Indeed the PLM (2412S) could not be reset. Concluded I had a bad PLM (same age as the ISY) and chased a replacement. Finally received the PLM replacement several days ago. Made connections and fired up the ISY. Immediately the TX and RX leds are steady on and the MEM led flashing. No network access to ISY. Router logs show no attempt by the ISY to connect to the network. Basically the ISY is totally unresponsive. Tried resetting the PLM; no change in ISY symptoms. So, back to the fine manual to read that a flashing MEM led may indicate a bad or poorly seated SD card. Removed, re-seated the SD card. No improvement. Tried looking at SD card using card reader and PC. SD card seems absolutely fine. Can read it fine. OK, having fun now... tried ISY factory reset. ISY will not reset as described in the fine manual - i.e., it never reaches the point described in the manual of the MEM led flashing. Inspected the SD card post factory reset attempt: absolutely unchanged; all files exactly as they were prior to reset attempt. This seems to confirm that the reset is not executing properly. Not sure that matters a hoot, however. So, I have a new PLM and an almost new ISY brick. Any ideas out there? Thanks much, - Chris

Michel thanks I'll take a run at 2.7.7. jcip...thanks, I also saw the button missing from scenes. I'll let you both know how 2.2.7 plays out here. Thanks again, - Chris

Michel, I'm having exactly the same issues with a new v5.0 KPL-8 button acquired last week - i.e., had to 'brute force' the initial linking of the device to the ISY and am unable to get subsidiary buttons on the KPL to link/control to the KPL main button (from the ISY). FYI, the ISY auto discovery (run multiple times) will only recognize the main button of the v5.0 KPL and listed it as an "unrecognized device v0.00). Brute forcing it identified the sub buttons but still did not pick up the KPL version at all. Based on what I read above, I'm guessing (hoping) that ISY firmware versions subsequent to 2.7.0 should resolve this. So if this is a KPL version support issue, will the 2.7.7 beta support KPL v5.0's? Thanks much, -Chris