Oakland Jeff

And that's what I did... delete them, factory reset them, and start from scratch. Everything is working perfectly. The new ISY Links table has only 17 entries in it.

Yes, both of my problem new KPLs are replacements for failed devices. I did a Replace With operation after the new KPL was installed, and restored each device too. This left them in a perma 1011 state, and unable to read the device link table. Here is what eisy thinks the link table should be. No idea how to tell if this is corrupt or not. I may just try to delete it and re-link it anyway.

Thanks lilyoyo1, I looked into that, and while it does indeed seem possible, I don't really want to add and maintain a completely different home automation solution (which seems like a bear to spin up) just to use it as an in-between, nor do I want to re-flash the cams and bulbs with new firmware. I mean, I suspect I could maybe pull it off, but I was really hoping for something way simpler. I also learned in my travels on the interwebs that Wyze is more or less hostile to the hobbyist community and thus makes it very difficult if not impossible to write integrations, and I don't think Feit was much friendlier. I now understand why integrations don't exist for these very common, cheap, and in my experience reliable brands. Bummer! And again, thanks for the pointer to a valid solution. It's just not for me.

I love these bulbs and these cams. They're cheap and they get the job done. I wish I could control the bulbs from my new eisy, and I wish I could use motion detection notifications from my wyze cams to trigger programs. I wish I had the skill to write these myself but I do not. Does anyone have a solution for either of these?

This is the result of me trying to do a Show Device Links Table for one of troublesome KPLs. I should note that the Failed dialog appeared only about halfway through generating the coms in the Event Viewer.

Hmmmmm... Identical, but still not triggering "control is switched on" in the IF of my programs like they used to before migrating...

So most of my motion sensors are the 2420Ms, and they fast flash when they are having comm problems. They are ALL fast flashing when they detect motion. When I watch the event viewer and I manually trigger the sensor by tapping the set button, the event viewer just sits there, silent, blank. To compare, I got my remoteLinc working, and I see 15 lines of events instantly when I tap a button on it. So while motion is not triggering events, the AC successfully writes updates when I do so on the Motions when they are in linking mode, according to the event viewer. So what's happening here? Why doesn't PLM/eisy see motion triggers, but they can communicate with the motion otherwise?

Techman, thanks, great insight! Those two programs both referenced a 2-wire dimmer that hadn't changed in forever, but for whatever reason its record was corrupted during the migration so the lines to beep it, turn it on, and turn it off were replaced by comments that said that node ###### was missing or something like that and that the desired action could not be taken. I restored those lines and the program now works, but none of the sensors are triggering the programs. I'm just bench testing by executing the Thens & Elses by hand.

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.