GMalezis

well, looks like after the upgrade the user id is reset to admin and admin... With that I was able to log in and reset to the appropriate id and pass. thanks - gus

Hello - probably a rookie mistake - but hoping someone can help. I have an ISY 994i/RF PRO that was running 4.9.0 - working well. Upgraded it to 5.0.16, cleared the Java cache, and now I find the ISY but can no longer log into the Admin Console. On the windows PC I get "Failed. Retry Authenticating Home Lighting". On the Android app I get "Invalid credentials 401". Seems my login id got blown away somehow? thanks in advance for any help on this.

yes, thank you - there must be some noise on one of the phases, which i'll have to track down. Device Current state is not however reflecting properly, except when I force a manual query of the devices. I can switch on and off all the devices from the admin console so the comms is happening. What is the issue with the PLM not picking up the state changes? Any ideas on how to troubleshoot that?

I have about 50 insteon devices (mostly 2477D, and a few Keypadlincs all managed by an ISY 994i. The system had been working reasonably well, but had some intermittent comms issues, which manifested themselves in timer programs not running properly. Still the system had settled and was working mostly well. In order to improve comms I installed a signalinc (2406H) and as of the install comms went from ok to horrific. Most if not all the switches were not accessible, however I could communicate and update the switches but only one at a time. I restored the PLM; no improvement. Restore Devices; device access errors. I removed the signalinc and just trying to get back to the prior state...and still struggling. No other change had occurred on the system. ANy ideas?

thank you for the feedback on the "Fade Down". I understand the issue with the Fade-down part of the program, but that was not giving me any state problems. The issue was that the state was not being recognized by ISY. That said, I will look into phase coupling...and report back. thanks in advance.

I have an ISY994i/IR Pro (4.0.5 fw) with about a dozen programs of two general categories; (1) on/off on time, and (2) timers (off on time elapsed). The first group - the on/off on time programs - all work fine. The second - the timers - are a little inconsistent and am interested in some insights, advice or help. The issue is the timer program are not running consistently. Some times the programs run, others times they do not. I've noticed the ISY Programs/Summary page does not always recognize the correct status, and does not execute the program. For example this occurs in a number of locations, including a box with two switches, each of which control lights (incandescent and halogen pot lights respectively). Note the attached Summary screen capture, switches 1 and 2 ("office light", "office pots") were turned on at the same time by hitting the respective switch, yet only one is running the program. The program in both cases is identical, and relatively simple. Example below, and Summary screen capture attached. Any insights? Is there any more detail on programming issues and troubleshooting guide(s)? thanks in advance. If Status 'Office / Office chandelier' is not Off Then Wait 1 minute Set 'Office / Office chandelier' Fade Down Else - No Actions - (To add one, press 'Action')

thank you much - the restore function worked.

thank you - that did it! Now, is there an automated script I can instrument to do this on a weekly basis?

I am a little new at this, have an ISY 994i IR Pro (4.0.5), with insteon switches and it has all be running well. I have a number of simple programs running for the past two weeks without issue. However recently I noticed that the "timer programs" are not running. By Timer I mean if light/fan is on, wait one minute, turn off...that sort of thing. I use these for washroom fans, closet lights etc. No changed were made to the programs between the time they worked and then failed. This may have coincided with the series of power failures in the Ontario region. Tried updating the programs, re-saving etc...same issue. Any ideas on how to troubleshoot? Attached is a sample program. thanks in advance for any thoughts or insights.