waffles

Hmm, I disabled the windows firewall, but no joy. In the meantime I also found a post about this issue: Unfortunately, the suggested steps from the Wiki don't seem to work for me here. (These are the steps I followed whenever I upgraded ISY's f/w before.)

Since I upgraded from RC1 I keep getting this error message whenever I try to log into the ISY the second time (first launch is OK): The same happens on another PC. I tried clearing java cache, re-installed java and ISY f/w to no avail. How can I fix this?

Mine now also. I did not have to reboot again.?

Same here. Still no joy.

Same here:

I did restart today AFTER I had lost connection.

Same here, ever since it was released. (I am also offline as of an hour or so ago.)

not sure about the restarted ISYs. My ISY was working fine until about an hour ago, incl. Alexa connection. First I thought the issue was on my end, so I rebooted my ISY as well as the switch it is connected to.

I believe the Maintenance scheduled for earlier today has not yet been completed:

Just found this thread, as my ISY has gone offline a little while ago (green dot in ISY portal still there, but lost connection to Amazon, Google, etc. @bmercier; I believe the thread title should say 04 (April), not 03 (March), correct?

From the limited testing I have done thus far, it seems that newly created scenes assign 'defined' Actions, e.g. '100% in 0.1 seconds' with Link Type 'Insteon' to Responders and only Controllers get the 'default', 'default'. This makes sense to me. However, I have numerous old/existing scenes where the Responders still show 'default', 'default'. Often these devices are dimmers , like shown in my initial screenshot, and are tasked to dim to 30% w/in 4 seconds. Most of them appear to be working still fine (basically still doing what they were supposed to do, even though the 'default' would suggest otherwise. It seems that these different 'Scene support' features were only introduced with V5, going by the title in the wiki. Since most of my scenes were created during V4, I wondering if I am seeing some migration issues here. Maybe I will need to go through each scene to make sure Responders no longer show 'default'/'default'. Thoughts?

Still trying to wrap my head around it.... @lilyoyo1, I think I understand your kpl example. Coming back to my initial screenshot: all the HT-LED-xx shown there are Lamplinc devices. What is their 'default', as these are dimmers and in this case, Responders?

Thanks @lilyoyo1! The choices in my drop down menu don't show 'Native', but 'Insteon' instead. I think I can live with that :-). More importantly, how does 'Default' fit into it? I have currently most of my scenes with mix of 'Insteon' and 'Default', like shown in my initial screenshot. Most of these scenes are triggered by the ISY (via Alexa or my Crestron) and occasionally via KP. Would/Should I change them and if so to what? Also, why is there a mix of them in the first place? Again, probably pretty dumb questions, so please bear with me. Thanks!

Thanks, @Chris Jahn . I found some additional references here and here. Unfortunately, even after reading it a several times, I have to admit, I don't really understand it. Would it be possible to dumb it down for me, please? In particular, I would like to know if there is a preference/best practice which 'flavor' to use for Scenes controlled by ISY (e.g. through a program or 3rd party (Alexa or external control system via REST), as well as Insteon devices, e.g. keypads. Thanks!

Happy New Year! I came across this 'default' in most of my scenes and have been trying to figure out what this means or does. I had never noticed it before. I seemed to have always 'concrete' Actions, like '100% in 2.0 seconds'....and to be honest I never paid attention to the Link Type before. I would appreciate if anyone enlighten me. My search came up empty. (ISY994i with v5.0.16b)

@Michel Kohanim Thanks for the confirmation!

@Michel Kohanim I don't think so, unless you are referring to the Network Resources.

@Michel Kohanim Funny! That's actually that's what I just did Before that I had installed the brand new 16GB SD card, as well as doing a factory reset of the ISY. This did not do the trick, e.g. no access to Portal. Then I noticed that there was a difference between F/W and UI version: v5.0.16B vs. v5.0.16, so I decided to reinstall the F/W. While the versions have not changed (=> is this correct?), the ISY is now connected to the Portal. I also noticed: Logon credentials had reverted to default (admin, admin) and had not been retained System location settings had not been retained. => Is this normal after a config restore? This is a fresh error log, after an ISY reboot: 2019/12/27 12:17:28 System -5 Start 2019/12/27 12:17:34 System -110022 /DEF/F6/I1/NLS/EN_US.TXT 2019/12/27 12:17:35 System -110022 /CONF/UXT.BIN 2019/12/27 12:17:35 System -110012 /CONF/UXT.BIN 2019/12/27 12:17:37 System -170001 [Network] Established -110012: SD DRIVE CONFIG FILE OPEN READ FAILED -110022: OPEN FILE FAILED So it seems there are still file errors, correct? => How do I address this?

Hello Michel; Here is are the recent error log entries existing setup (the forgetful one): 2019/12/25 13:51:21 System -5 Start 2019/12/25 13:51:28 System -110022 /DEF/F6/I1/NLS/EN_US.TXT 2019/12/25 13:51:29 System -110022 /CONF/UXT.BIN 2019/12/25 13:51:29 System -110012 /CONF/UXT.BIN 2019/12/25 13:51:31 System -170001 [Network] Established 2019/12/25 14:06:06 System -5011 uuid:0 2019/12/26 01:51:37 System -100 [DHCP] state=RENEW 2019/12/26 07:23:54 System -5 Start 2019/12/26 07:24:01 System -110022 /DEF/F6/I1/NLS/EN_US.TXT 2019/12/26 07:24:01 System -110022 /CONF/UXT.BIN 2019/12/26 07:24:01 System -110012 /CONF/UXT.BIN 2019/12/26 07:24:04 System -170001 [Network] Established 2019/12/26 07:28:52 System -5006 uuid:28 and my lookup of the messages: -5: no error message found in wiki -5006: no error message found in wiki -5011: PROCESS DEVICE STATE CHANGE SID NOT FOUND -110012: SD DRIVE CONFIG FILE OPEN READ FAILED -110022: OPEN FILE FAILED -170001: no error message found in wiki with replacement SD card setup (the one I cannot connect to the portal): This is the complete log after another fresh restore just now with my most recent backup file: Time User Code Message Thu 2019/12/26 07:45:16 AM System -5 Start Thu 2019/12/26 07:45:17 AM System -110022 /CONF/INSTENG.OPT Thu 2019/12/26 07:45:17 AM System -110012 /CONF/INSTENG.OPT Thu 2019/12/26 07:45:17 AM System -110022 /DEF/F1/I1/NLS/EN_US.TXT Thu 2019/12/26 07:45:17 AM System -110022 /CONF/UXT.BIN Thu 2019/12/26 07:45:17 AM System -110012 /CONF/UXT.BIN Thu 2019/12/26 07:45:17 AM System -110022 /WEB/ELKNLS.XML Thu 2019/12/26 07:45:17 AM System -170001 [Network] Established Thu 2019/12/26 07:45:17 AM System -110022 /CONF/PORTALS.PSF Thu 2019/12/26 07:45:17 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:45:46 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:45:58 AM System -110022 /WEB/DRIVER.XML Thu 2019/12/26 04:45:58 AM System -110022 /WEB/DRIVER.XML Thu 2019/12/26 04:46:16 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:46:46 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:47:17 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:47:47 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:48:17 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:48:47 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:49:17 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:49:47 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:50:17 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:50:39 AM System -5 Start Thu 2019/12/26 04:50:41 AM System -110022 /DEF/F1/I1/NLS/EN_US.TXT Thu 2019/12/26 04:50:41 AM System -110022 /DEF/F4/I1/NLS/EN_US.TXT Thu 2019/12/26 04:50:41 AM System -110022 /DEF/F6/I1/NLS/EN_US.TXT Thu 2019/12/26 04:50:41 AM System -110022 /CONF/UXT.BIN Thu 2019/12/26 04:50:41 AM System -110012 /CONF/UXT.BIN Thu 2019/12/26 04:50:41 AM System -110022 /WEB/ELKNLS.XML Thu 2019/12/26 04:50:43 AM System -170001 [Network] Established Thu 2019/12/26 04:50:44 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:51:14 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:51:44 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:51:55 AM System -110022 /WEB/DRIVER.XML Thu 2019/12/26 04:51:55 AM System -110022 /WEB/DRIVER.XML Thu 2019/12/26 04:52:00 AM System -10011 n/a Thu 2019/12/26 04:52:14 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:52:44 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:53:03 AM System -110022 /WEB/DRIVER.XML Thu 2019/12/26 04:53:03 AM System -110022 /WEB/DRIVER.XML Thu 2019/12/26 04:53:14 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:55:13 AM System -5 Start Thu 2019/12/26 04:55:15 AM System -110022 /DEF/F1/I1/NLS/EN_US.TXT Thu 2019/12/26 04:55:15 AM System -110022 /DEF/F4/I1/NLS/EN_US.TXT Thu 2019/12/26 04:55:15 AM System -110022 /DEF/F6/I1/NLS/EN_US.TXT Thu 2019/12/26 04:55:16 AM System -110022 /CONF/UXT.BIN Thu 2019/12/26 04:55:16 AM System -110012 /CONF/UXT.BIN Thu 2019/12/26 04:55:16 AM System -110022 /WEB/ELKNLS.XML Thu 2019/12/26 04:55:17 AM System -170001 [Network] Established Thu 2019/12/26 04:55:17 AM System -170001 [TCP-Conn] -256/-140002, Portal-Dispatch Thu 2019/12/26 04:55:28 AM System -5006 uuid:27 Thu 2019/12/26 04:55:37 AM System -110022 /WEB/DRIVER.XML Thu 2019/12/26 04:55:37 AM System -110022 /WEB/DRIVER.XML Thu 2019/12/26 04:55:45 AM System -10011 n/a No SMTP errrors, but a bunch of System messages/errors. Where should I go from here?

No devices. The trigger comes from Alexa, setting a Variable to trigger the notification. This works fine: in the ISY I can see the variable changing and the program icon flip to green. I can currently get messages, even though the Recipients field is empty and the Notifications are being sent to "3", which technically should no longer exist (I had this set up during earlier troubleshooting). In the meantime I was able to find an old 2GB SD card which I formatted with my Win10 PC (I tried formatting it through the ISY (telnet and FS per wiki), but it never completed). Unfortunately, this was also unsuccessful: while the Recipients were visible again and everything else seemingly was there, I kept getting LIB_ERRORS-403 during log-on though the admin console. Also I was not able to connect to the ISY through the Portal (it showed the device as offline). I tried reformatting the 2 GB SD card several times, as well as restoring from different, in part rather old back up versions, but all to no avail. Not sure if this is caused by a bad SD card, but I have now a brand new one (16GB) on order.

Thanks apostolakisl. The responses are not in regards to a PLM. They are basically notifications about timers, so it's all 'w/in' the ISY. (Even though I had several PLMs failing on me in the past and the symptoms were as you said (loosing touch).) I did not see any error messages, also the logs did not mention anything (that said, I have not found the build in ISY logs under Tools very useful). I think I'll try a new SD card next. A new one is only a few $$.

As of recent my ISY 994i has started acting a bit weird. I have noticed it with some programs where all of a sudden Notifications are no longer being sent. This despite no code or any other apparent changes to the set up. I had been using F/W 5.0.16 RC1 for several months and very recently updated to 5.0.16B RC1. It has happened with both versions. Using the Test feature to test the SMTP settings (Default, as well as my own ones) are successful. Creating new test programs to trigger notifications work also. Here is what I did to fix this issue - all methods worked, but only for some time. 1. Restore ISY and Devices (first time it worked, the second time it did not fix the issue) 2. Rebuilding my recipient Group and Customizations (Name/Customized Cotent), basically by copy/pasting the old ones. This morning I noticed that the entry for the recipients under Groups is empty, i.e. there are no longer any Recipients listed. However, my ISY just sent me an email as it should have based on the program that has been running.? The ISY seems to be working fine otherwise, e.g. Scenes are all working as far as I can tell. I wonder what the root cause could be. Is the SD card is failing or corrupted? ISY and card are 1/2 dozen + years old. Looking forward to your thoughts and suggestions.... Thanks!

I think I have to study up a bit more on these features to figure out the best way to utilize them. Thanks much!

That's a good idea. This way I have at least one 'simple' command per room. Thanks!

Thank you for your reply, Scott! Hmm, these are pretty severe limitations for my application. I have about 10 dimmable lights in each room, with numerous scenes. A simple 'Lights' doesn't cut it for me. Guess, I have to be patient until such feature becomes available. Could you please help me understand the differences are between Alexa Categories Devices and Scenes? They seem to behave pretty much the same when imported as such through the ISY Portal. Thanks!