Bumbershoot

It looks like I got it on the 7th just by updating normally. The front end still says version 2.2.9-5, however. For some reason, this upgrade didn't fix the log issue.

FWIW, I concur with @Teken regarding the fixtures he describes above. I've put two of them in a closet, driven by an Insteon SwitchLink Dimmer, and they work very nicely at the dim levels I set them to -- 30% brightness late at night and early in the morning, and 80% brightness during the day and evening. 80% is plenty bright, way brighter than the 4 LED tubes that preceded them, which were brighter than the 4 florescent tubes that were originally installed in the fixtures. No hum or flicker, and they ramp up or down smoothly.

I'm on 5.3.2 firmware/UI and I have the same options as @oberkc shows in his screenshot above. The additional thing that comes to mind is that you might clear the Java cache on the computer you're using to connect to your ISY, and make sure you're using the ISY Launcher (start.jnlp) to start the Admin Console. Something is preventing your UI from correctly loading the interface to your ISY.

I didn't actually answer your questions. Answers in red.

I would use the "adjust scene" functionality, which is what I think you're asking for. Here's an example program that uses it: West Hall On-Level - [ID 00B7][Parent 000A] If From Sunset + 1 hour To Sunrise (next day) Then In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallEntrance' To 25% in 0.5 seconds, 1 retry In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallLaundry' To 25% in 0.5 seconds, 1 retry In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallOffice' To 25% in 0.5 seconds, 1 retry Else In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallLaundry' To 50% in 0.5 seconds, 1 retry In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallEntrance' To 50% in 0.5 seconds, 1 retry In 'Devices / dirWestHall / msWestHallNorth-Sensor' Set 'Devices / dirWestHall / sldWestHallOffice' To 50% in 0.5 seconds, 1 retry EDIT: A screenshot might help you find the "adjust scene" functionality. ISY firmware and UI at version 5.3.2.

This doesn't directly answer your question, but I'd write multiple programs, one for each month using the Time-Data program, and one program using the ISY's built in scheduling for the time. Way easier to write, understand and debug. November Deck Lights - [ID 007B][Parent 00A7] If 'Devices / dirNodeServers / ISY Time Data / ISY Time Data' Month is November And 'Devices / dirNodeServers / ISY Time Data / ISY Time Data' Day of Week is Thursday And 'Devices / dirNodeServers / ISY Time Data / ISY Time Data' Day of Month > 7 days Then Enable Program 'Deck Lights' Else Disable Program 'Deck Lights' This might work for turning on/off the lights using the ISY internal scheduler: Deck Lights - [ID 007B][Parent 00A7] If From Sunrise - 1 hour To Sunrise (same day) Or From Sunset - 1 hour To 11:00:00PM (same day) Then Set 'Devices / dirExterior / sldDeckEast' On Else Set 'Devices / dirExterior / sldDeckEast' Off

No apparent issues here, either.

Nope, you haven't been had, and the interface does look the same. That's old alpha firmware, so I'd install 5.3.1 first thing.

@larryllix is right. Here's a screenshot from Windows 10.

I can't help you with a more precise motion sensor, but my setup is still working. I currently have two original Insteon motion sensors outside (one for each irrigation zone I'm interested in), and they're active. My sprinkler system has been winterized, so it's not currently in use, but the motion sensors still work, and I plan on running this setup into the future. I may very well expand this setup to more irrigation zones this coming spring. I have a Rainmachine irrigation controller, and use the Rainmachine nodeserver and ISY, along with a few simple programs to control the setup. It's easy to set a schedule for the programs to not run when your landscapers are around. Upon activation, I run the zone for one minute, which is sufficient for deer (or golfers retrieving their ball from my back yard) to get the idea and move on. I think the noise and water startle the deer, and just the water works with the golfers. I'm not currently using this setup for dogs and their walkers, so I can't speak as to how effective this will be in that use case. I've considered buying the Zooz Outdoor Motion Sensor, but until my old Insteon sensors give up the ghost, I probably won't.

Three thing to check: Are you using the ISY Launcher to start the AC Did you clear your Java cache when you upgraded If no to #1, do your firmware and UI versions match

Wow, you've had a rough go! All the best to you in 2021! I've never done this, so there may be steps I haven't thought of. Hopefully, this will simply get the conversation started with those who know more... Keep in mind that you can always open a support ticket with UDI, which I'm certain would be the most reliable way performing this upgrade. It doesn't appear that you have any Z-Wave installed (from your forum signature), so that should make upgrading pretty easy. First things first: install the latest/greatest firmware on your new ISY (I'd use version 5.3.1) if you actually have Z-Wave devices installed and running on your current ISY, perform a Z-Wave backup (use menu Z-Wave | Backup) backup your current ISY (use the menu File | Backup ISY) I would power down the current ISY (just in case), and I'd leave the PLM still connected to it (I don't know how any current Z-Wave devices would react to having two ISY's competing for control -- maybe nothing, maybe chaos). Now, all you have to do is to perform a File | Restore ISY on your new ISY, using the backup you just made of your current ISY. You may need to reset your login credentials on your new ISY after the restore is complete, as they may reset to the defaults of admin | admin. I don't believe you'll need to perform a Z-Wave | Restore on your new ISY, as the backup of the Z-Wave dongle will be included in the recent ISY backup of your current ISY. Inspect the programs on your new ISY (most should come across fine, but the programs that use the "adjust scene" functionality will need to be looked at, maybe others). Satisfy yourself that your programs are good and saved. Backup your new ISY when done. At this point, I'd think you could simply power down your new ISY, and connect it to your PLM (which should be powered on), and turn it on. Magic will ensue... If you don't like the looks of your programs on your new ISY, power up your current ISY, and either seek help here, or open a support ticket with UDI.

Here's a link to the wiki page that talks about OSX. https://wiki.universal-devices.com/index.php?title=Main_Page#MAC_OSX First, it appears that you're running Big Sur, which means that you should see the very first item on the link: On Big Sur, Admin Console is no longer a separate Window System Preference | General | Prefer Tabs - set it to "in full screen" (not "always") Otherwise, you might find something helpful in the wiki.

I don't know how to resolve the "Send queue full" issue, but you may consider installing the test firmware 5.3.1, specifically for this fix: 0000770 - Support old lock notification values I've only got one Schlage lock (an older lock, not Z-Wave +), and it's functionality is much improved over how it functioned on 5.3.0. Additionally, I've got quite a few Z-Wave devices, and none of them show the need to write updates anymore, specifically since I installed 5.3.1.

Have you used the Event Viewer? The menu items: Tools | Diagnostics | Event Viewer is probably not what you're looking for, but I don't know of any memory profilers or other tools (like a shared memory viewer) that would let you observe the event queue, etc. UDI may have tools like that, but AFAIF, they don't release or support them.

Yes, there are various threads about this problem. For me, the solution was to replace the LEDs with a different brand. I understand that you're using the same LEDs elsewhere in your house, but the cheapest/easiest test might be to try a different brand of LED where you have the flicker. I've had good luck with Phillips Warm Glow bulbs, but there are other brands that work well. Search around the forum (type "flicker" in the search box) and you'll see other recommendations.

I think the PLM table can maintain something on the order of 1000 links, though I'm not entirely certain. These errors may not mean that you've exceeded the number of links. Folks who've recently migrated to a recent firmware version who've used the "adjust scene" functionality in programs run into this as well. You can try to open one of the affected programs, inspect it and re-save it.

@ddimit, this has been reported earlier in this thread. In this previous post, it's suggested that you may have an SD card going bad or some firewall issue. You can always submit a ticket with UDI.

Dollars to doughnuts, unless you're running an ancient Windows machine (i386 or something, which I'll bet Windows 10 won't run on), then shouldn't you be using the 64 bit version of Java? I'd give it a try.

The Launcher is the current specified best method to get into the AC.

This?

This doodad in the FCC database intrigues me a bit. It's apparently a spread spectrum transmitter, and it's licensed on 915MHz as well as on Bluetooth LE and WiFi 2.4 GHz.

I only have one, but it functions under 5.3.1 better than any firmware version to date (it's an old lock, not Z-Wave +). I wish I understood why there's such a wide variability with peoples experience.

@btreinders, apologies if you aren't running any Polyglot nodeservers, but if you are, the ISY-Inventory nodeserver would have saved you some hassle. See screenshot.