Oakland Jeff

OK, I saved all of my programs but got little dialogs each time that nothing had changed, so I'm not sure if anything was actually accomplished or not. Anyway, I rebooted and notice that 2 of my 97 programs say "Not Loaded" in the activity column and Out of Memory in the status column.

Sadly, both KPLs are in a state of 1011, needing updates. By the way, in this state, with green 1011s, if I try to use AC to turn on or off the light, I get a Cannot Communicate error and the green 1011s are replace with a red "!".

Thanks Techman, I tried that, but no joy. I just replaced another previously failed KPL and I'll see if I have any better luck with that one. I'll keep you posted.

Thanks Techman, I migrated from ISY994i. Attached are my current eisy versions. I want to make sure I understand what you are suggesting in the last sentence... Select My Programs from the tree, select Export from the context menu and save to a file. Then reboot the eisy and import all those programs again?

The KPL that I replaced after upgrading to eisy is pretty much unreachable. The old one, before it died, worked just fine with the old ISY. I did a "Replace <device> with" and in AC at least it seemed to take on all the properties of its predecessor... except for the persistent unwritten updates "1011" icon.

I can write updates to my wireless motion sensors, but when they are tripped, none of my auto-off programs are triggered like they used to trigger. Even my RemoteLinc 2 won't trigger the scene it's part of... pic attached of scene test results. It also seems relevant that in my main device overview screen, the status of my lights is not accurately reflected. If I do a manual query, they will update correctly, but I used to see real-time changes before I migrated. Any ideas?

Thanks Mr. Bill. Yes, it's checked. I've been following all the guides. A few minutes before you posted though, the PLM started to update as I had gone through all the steps a third time. I think my mistake was that I didn't know if/when the Update Packages step was complete so I was when the PLM failed I tried to reboot the eisy and bunch of other flailing type things that were not productive. When I went through all the steps for like the 3rd time, I got a message that said the packages were updated and to reboot the eisy. From there is was smooth sailing.

I have an ISY994i with dying serial PLM. I got shiny new eisy and new USB PLM. I restored by ISY backup to the eisy. That seemed to work. Then I tried to restore the new PLM from the newly restored eisy. I got a "Failed resetting PLM [-200000/-30]" What in the world is going on?

My UD Mobile just started giving me a stream of UD Portal disconnect and reconnect events every couple of minutes. Not sure where to see the error log that OP shared.

Thank you lilyoyo1 and larryllix. I did a bunch of googling and it seems that the FEIT bulbs can be controlled via Tuya, I'm not sure yet how that helps me control them via UDI, but I'll keep researching! Cheers, Jeff

Just got notified of the eminent EOL of my ISY994. I guess I'll migrate to eISY in time. I was looking forward to control over my FEIT bulbs via a node server, but it seems none exists? Is this correct, or is there some other way to control these bulbs (brightness, color) that I'm missing? Cheers, Jeff

TLDR; The On Level showed up mysteriously! Thank you for your responses! How and why? I don't know. Here are the things that happened this morning prior to it working... I clicked on my shortcut to launch the admin console. I got an error about the file not being found or something. I navigated to the Start.jnlp file instead and launched it. I had been using Start.jnlp the whole time prior to today, but last night I created a shortcut to admin.jnlp and was going to try that directly. I took screen shots of the version numbers and device type, as seen below. I tried to see if On Level was there for other devices. HA, it WAS. Thinking that this might be the issue, I went back to the bathroom light and it was there now too! I noticed that the last 4 actions on that list though, including On Level, were now different. They used to be all about setting temperatures, as if my switch was a thermostat? But now all the actions in the list are relevant to a light switch! Is there some cache that I should have cleared or something that may have cause the ISY to get confused about what type of device it was working with?

Trying to write a program to set the on level for a bathroom light to 8% at night, and 40% during the day for when I physically use the paddle. I don't see "on level" as a choice in my drop down list for Your Devices with my switch selected. I also see old posts from 7 years ago showing pictures of "on level" being in the list!! Where did it go? How do I currently accomplish this? Seems simple but I'm baffled. Thanks in advance!

AH, OK, thanks MrBill, that makes perfect sense about the grey buttons being on hold from my new Pro button. Oh, and regarding restoring the PLM, no confusion. This was the thing that I needed to do from the beginning, since a brown out pretty much seemed to erase most everything on it and none of my programs were getting triggered or taking effect (e.g. turn off the lights 20 minutes after someone hits the paddle to turn them on; turn on my accent lights at dusk; etc.) The good news is that everything seems to be working fine now, despite all the grey "write needed" buttons. And those concern me because it just seems like something is broken and those effects will surface later.

Also, what's the difference between the grey "1011" and the green "1011" icons? FWIW, I am using "adjust scene" in my programs to: Lower the on level of motion triggered scenes at night to something less blinding Set many lights in motion activated scenes to "Ignore" during the day so they don't come on at all when it's light out I started to use this methodology after it was reported that the bug you mentioned was fixed. I'm currently on v.5.3.3.

OK, well, after that detour, I'm still back to my original problem... here is the level 3 com log when I tried to update a motion sensor that needed writes (as indicated by the gray 1011 icon)... Thu 11/18/2021 10:13:56 AM : [INST-TX-I1 ] 02 62 14 BF 3B 0F 0D 00 Thu 11/18/2021 10:13:56 AM : [INST-ACK ] 02 62 14.BF.3B 0F 0D 00 06 (00) Thu 11/18/2021 10:14:05 AM : [INST-TX-I1 ] 02 62 14 BF 3B 0F 0D 00 Thu 11/18/2021 10:14:14 AM : [INST-TX-I1 ] 02 62 14 BF 3B 0F 0D 00 Thu 11/18/2021 10:14:18 AM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 Thu 11/18/2021 10:14:27 AM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 Thu 11/18/2021 10:14:30 AM : [INST-SRX ] 02 50 14.BF.3B 00.00.01 CF 13 01 LTOFFRR(01) Thu 11/18/2021 10:14:30 AM : [Std-Group ] 14.BF.3B-->Group=1, Max Hops=3, Hops Left=3 Thu 11/18/2021 10:14:30 AM : [D2D EVENT ] Event [14 BF 3B 1] [DOF] [1] uom=0 prec=-1 Thu 11/18/2021 10:14:30 AM : [ 14 BF 3B 1] DOF 1 Thu 11/18/2021 10:14:30 AM : [D2D EVENT ] Event [14 BF 3B 1] [ST] [0] uom=100 prec=0 Thu 11/18/2021 10:14:30 AM : [ 14 BF 3B 1] ST 0 (uom=100 prec=0) Thu 11/18/2021 10:14:30 AM : [INST-SRX ] 02 50 14.BF.3B 00.00.01 CF 13 01 LTOFFRR(01) Thu 11/18/2021 10:14:30 AM : [Std-Group ] 14.BF.3B-->Group=1, Max Hops=3, Hops Left=3 Thu 11/18/2021 10:14:30 AM : [INST-DUP ] Previous message ignored. Thu 11/18/2021 10:14:31 AM : [INST-SRX ] 02 50 14.BF.3B 44.CD.0D 2F 0D 02 (02) Thu 11/18/2021 10:14:31 AM : [Std-Direct Ack] 14.BF.3B-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Thu 11/18/2021 10:14:40 AM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 Thu 11/18/2021 10:14:40 AM : [INST-ACK ] 02 62 14.BF.3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 06 (00) Thu 11/18/2021 10:14:44 AM : [D2D EVENT ] Event [14 BF 3B 1] [ERR] [1] uom=0 prec=-1 Thu 11/18/2021 10:14:44 AM : [ 14 BF 3B 1] ERR 1 After this completes, I get an error message that pops up that says the ISY can't communicate with the Motion Sensor and the icon is now a red "!" instead of the needs-write "1011". After a few minutes, the red "!" reverts to the gray needs-write "1011".

MrBill, thank your for all your help! Best $30 bucks I spent all year. With Pro now, I turned off the wireless writes and auto writes and did my Restore Modem (PLM) which went smoothly. With 71 total devices in my house (many keypads and sensors that have sub-nodes) the PLM now has 280 links in it's table, which seems about right.

OK, I found it. Thanks! Turns out I had 3 ISY's listed under my products and the one I'm currently using didn't have a valid serial number so clicking on modules showed nothing but an error message.

When I select Help > Purchase Modules... this is what I get. Even when I go to the Store menu there are no software modules to be found.

Yes, I cleared browser cache and it's back. Oh, I thought Pro was a hardware thing, given that it supports more nodes and programs (i.e. eats up more memory). Well in any case I don't have those buttons

Teken, unfortunately I do not have pro. Waiting for Polisy to fully support ISY and be out of Beta and then I'll buy one and be totally up to date with the latest and greatest. MrBill, this is the com log when I try to Restore Device: Hey, why won't the forum let me enter a code formatted section in my response like I did in my original post? Well, here it is, formatted poorly: Wed 11/17/2021 02:39:28 PM : [ 14 BF 3B 1] Preparing Device '~Main Hall - Entry-S' for Restore Wed 11/17/2021 02:39:28 PM : [ 14 BF 3B 1] Device '~Main Hall - Entry-S' ready for Full Restore Wed 11/17/2021 02:39:28 PM : [All ] Writing 99 bytes to devices Wed 11/17/2021 02:39:28 PM : [INST-TX-I2CS] 02 62 14 BE B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/17/2021 02:39:28 PM : [INST-ACK ] 02 62 14.BE.B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Wed 11/17/2021 02:39:37 PM : [INST-TX-I2CS] 02 62 14 BE B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/17/2021 02:39:46 PM : [INST-TX-I2CS] 02 62 14 BE B1 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/17/2021 02:39:50 PM : [INST-TX-I1 ] 02 62 14 BF 3B 0F 0D 00 Wed 11/17/2021 02:39:59 PM : [INST-TX-I1 ] 02 62 14 BF 3B 0F 0D 00 Wed 11/17/2021 02:40:08 PM : [INST-TX-I1 ] 02 62 14 BF 3B 0F 0D 00 Wed 11/17/2021 02:40:12 PM : [INST-TX-I1 ] 02 62 1C B3 F8 0F 13 00 Wed 11/17/2021 02:40:16 PM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 Wed 11/17/2021 02:40:24 PM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 Wed 11/17/2021 02:40:33 PM : [INST-TX-I2CS] 02 62 14 BF 3B 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 C9 Wed 11/17/2021 02:40:37 PM : [D2D EVENT ] Event [14 BF 3B 1] [ERR] [1] uom=0 prec=-1 Wed 11/17/2021 02:40:37 PM : [ 14 BF 3B 1] ERR 1 It continues to try to write stuff, but I don't think it's related to the restore. I suspect it's related to all the other queued writes for other devices?... Wed 11/17/2021 02:40:38 PM : [INST-TX-I2CS] 02 62 21 D0 FD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/17/2021 02:40:41 PM : [INST-TX-I1 ] 02 62 1C B3 C6 0F 13 00 Wed 11/17/2021 02:40:50 PM : [INST-TX-I2CS] 02 62 21 D0 FD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/17/2021 02:40:59 PM : [INST-TX-I2CS] 02 62 21 D0 FD 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Wed 11/17/2021 02:41:03 PM : [14 D6 91 1 ] Link 2 : 0FE8 [62011BBF93000001] Writing [62011BBF93000001] Wed 11/17/2021 02:41:03 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 02:41:11 PM : [INST-TX-I1 ] 02 62 30 67 B0 0F 13 00 Wed 11/17/2021 02:41:12 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 02:41:21 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 02:41:25 PM : [14 D6 91 1 ] Link 2 : 0FE8 [62011BBF93000001] *Failed Writing [62011BBF93000001] Wed 11/17/2021 02:41:26 PM : [31 AE CD 1 ] Link 3 : 0FE0 [62011A673A000001] Writing [62..............] Wed 11/17/2021 02:41:26 PM : [INST-TX-I2CS] 02 62 31 AE CD 1F 2F 00 00 02 0F E7 08 62 01 1A 67 3A 00 00 01 B2 Wed 11/17/2021 02:41:34 PM : [INST-TX-I2CS] 02 62 31 AE CD 1F 2F 00 00 02 0F E7 08 62 01 1A 67 3A 00 00 01 B2 Wed 11/17/2021 02:41:41 PM : [INST-TX-I1 ] 02 62 1A 69 5A 0F 13 00 Wed 11/17/2021 02:41:43 PM : [INST-TX-I2CS] 02 62 31 AE CD 1F 2F 00 00 02 0F E7 08 62 01 1A 67 3A 00 00 01 B2 Wed 11/17/2021 02:41:47 PM : [31 AE CD 1 ] Link 3 : 0FE0 [62011A673A000001] *Failed Writing [62..............] Wed 11/17/2021 02:41:48 PM : [31 B6 54 1 ] Link 3 : 0FE0 [E2011A66E1000001] Writing [E2011A66E1000001] Wed 11/17/2021 02:41:48 PM : [INST-TX-I2CS] 02 62 31 B6 54 1F 2F 00 00 02 0F E7 08 E2 01 1A 66 E1 00 00 01 8C Wed 11/17/2021 02:41:57 PM : [INST-TX-I2CS] 02 62 31 B6 54 1F 2F 00 00 02 0F E7 08 E2 01 1A 66 E1 00 00 01 8C <Truncated because it went on and on>

I put the open/close sensor into linking mode and do "Write Updates to Device"... it fails. All my wireless devices are like this now. Yea, the batteries have all just been replaced... I wish it were that simple. Here is the Device Communications Events log when I tried to write updates: Wed 11/17/2021 01:53:25 PM : [14 D6 91 1 ] Link 2 : 0FE8 [62011BBF93000001] Writing [62011BBF93000001] Wed 11/17/2021 01:53:25 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 01:53:34 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 01:53:42 PM : [INST-TX-I2CS] 02 62 14 D6 91 1F 2F 00 00 02 0F EF 08 62 01 1B BF 93 00 00 01 F8 Wed 11/17/2021 01:53:46 PM : [14 D6 91 1 ] Link 2 : 0FE8 [62011BBF93000001] *Failed Writing [62011BBF93000001] What's the way forward?

Thank you MrBill, you put me on the right track!!! The first step on this page is to look at the PLM link table making sure that there isn't more than about 900 links. HA! I only had 6 links in mine!!! I restored my PLM (back to around 300 links) and it solved everything. Thank you!

Other bits of if info... Yes, I can control all the lights using the admin console. No, using my RemoteLinc 2 turns on the lights that it is in a scene with, but does NOT initiate the program that automatically turns the lights off after an hour.

Yea, batteries all good on all my sensors. AND remember they are still triggering the scenes they are part of. The ISY just seems to be blind to them... they are not triggering programs and I'm not able to get status from them.