Bumbershoot

From your screenshot, it appears to be related to the 'adjust scene' functionality that underwent a big rework with the upgrade to the 5.x.x firmware series. From the release notes: If you are upgrading from version 5.0.8 or earlier, you will have to manually update the Adjust Scene entries in all of your programs. Also, if you use the ISY Launcher, you won't have to worry about firmware/UI mismatches any more.

I've been running the Admin Console under all the various beta and final releases of Big Sur and I've never seen this behavior. By your description, it sounds like you're running the correct Java application (start.jnlp). Maybe you need to clear your Java cache and download the app again. I don't see any Java settings that would make this happen. It almost sounds like the app is starting from a web browser using 'http://<ISY-IP-addr>/admin.jnlp' instead of from the standalone 'start.jnlp' application? Is that possible?

The only motion sensor I'm using with a Homeseer dimmer is in a GE Enbrighten Motion Switch that shares a box with the Homeseer dimmer. The load on the GE switch is attached to a closet light that I seldom use. I have the motion sensor set to "manual" mode, meaning that it does not control the load that it's attached to. It acts instead like a fully independent Z-Wave motion sensor. I use it to control the Homeseer dimmer through ISY programs. I'm surprised at how fast the Homeseer dimmer responds to motion, since the ISY is completely involved in the process. It is discernibly slower than the Insteon MS/dimmer combo that are linked in a scene, but only just so. Sort of how the ½ second ramp rate in Insteon dimmers is discernible. But only just so. I suppose if your ISY CPU gets tied up with some process, you might notice a performance lag, but I haven't noticed that as of yet. In short, I'm really quite pleased. The only thing lacking is more granularity in the Homeseer ramp rate -- 1 second intervals. Otherwise, it works well. The program is simple (a separate program turn the lights off). Office Light On - [ID 00D4][Parent 000A] If 'Devices / dirOffice / ZW 025 On-Off Power Switch / ZW 025 Motion Sensor 1' is switched On Then Set 'Devices / dirOffice / ZW 004 Dimmer Switch' On Set 'Devices / dirOffice / lmpOfficeDeskLamp' On Else - No Actions - (To add one, press 'Action')

I'm using the Homeseer HS-WD-200+ dimmer, and it's fine, and the sentinel LEDs can be useful. Or not. I use the sentinel LEDs to reflect the status of the various doors in my house, so I'm writing parameter changes to the switch a great many times every day. It has operated flawlessly since I installed it, nearly two years ago. The biggest beef I have with it is that the ramp rate is only adjustable in seconds, not milliseconds. I'm also using GE Enbrighten Smart Motion Dimmers/Switches in order to eliminate motion sensors from the walls. They are also working fine, exactly as intended. Again, the ramp rate on the dimmers is adjustable in seconds only. Otherwise, they're fine, and the built-in motion sensors work as intended. I still prefer Insteon switches for lighting, but these Z-Wave switches are all working well. I only use Z-Wave dimmers/switches where they answer a particular requirement that Insteon can't do, so I don't have enough of them installed to be able to report how uniformly they respond in ISY scenes. I suspect you can write changes to the NV Ram on these switches many, many thousands of times without issue. https://github.com/UniversalDevicesInc/Z-Wave-Devices/issues

Sorry, I don’t use the Leviton switch, so I can’t answer your question. Here’s a switch for a competitive price. I think it’s identical to the GE switch. https://ezzwave.com/honeywell-z-wave-plus-wall-smart-fan-control

The name of the nodeserver in the Polyglot Store should provide a link to the github repository for the nodeserver, and that's where you'll find the README instructions for the nodeserver you're installing. Just click on the name. That may help provide you with some answers. https://github.com/bpaauwe/udi-climacell-poly

I read somewhere on this forum that the Polisy will update itself upon boot. I ran across this same issue recently (possibly with the same package, I don't recall) so I tested this by rebooting my Polisy. The issue went away. My guess is that it's probably fine to choose "y", but I stayed within the UDI web interface (by rebooting from the menu). EDIT: I just checked, it was the same package.

I’m a big fan of the Philips Warm Glow bulbs. No flickering, they dim nicely and the Mrs. loves the color temperature at low light levels.

Apparently, this isn't a global issue with 5.3.0. I just crawled through my AC (5.3.0) and I don't see that artifact in any of my 211 Insteon devices, most of which support the Beep.

Yes. This is how it should look.

@Kentinada, I found a couple of examples of this "Out of memory" issue caused by deleted devices. Below is a program that produces this, with the text of the program in which you see where the ISY inserts comments in the "If" stanza where the device was specified. MotionSensorLowBattery - [ID 000C][Parent 0004] If // Warning: Unrecognized Condition (program may not run) // <control OP="IS" NODE="36 84 1 3" ID="DON"/> // Or 'Devices / dirWestHall / msWestHallNorth-Sensor / msWestHallNorth-Low Bat' is switched On Or // Warning: Unrecognized Condition (program may not run) // <control OP="IS" NODE="4A 56 56 3" ID="DON"/> // Or 'Devices / dirMasterBath / Master Closet Motion Sensor.1 / 4A.54.9E.3 Low Battery' is switched On Or 'Devices / dirGarage / msGarage / msGarage Low Battery' is switched On Then Send Notification to 'Brad' content 'Motion Sensor - Low Battery' Else - No Actions - (To add one, press 'Action')

Normally you need to edit/save or delete the programs that show their status as "Out of memory". In my experience, this happens when a device is removed from the ISY that is referenced in a program and the program isn't edited to reflect the absence of the device (mostly in the "IF" stanza, if my memory serves correctly). Your ISY isn't out of memory, you just need to edit/save or delete the programs.

It doesn't appear that you're running the latest and greatest on your box. You may need to have all your packages on the latest version. I've upgraded and this is the version that's reported at the prompt: FreeBSD 12.1-RELEASE-p10 r365882 POLISY You might try running this: sudo pkg update && sudo pkg upgrade Reboot upon successful completion of the upgrade.

I've only got one, but I excluded and included it when I installed 5.3.0 on the day of release. I also changed the batteries at that time. I probably use the lock 5-6 times a day, and the batteries are still showing at 100% this morning, so I'm not seeing any unusual battery drain.

For the simple purpose you have, you might give a thought to LiFX White to Warm bulbs. They have an astonishing range of color temperatures, from 1500K to 9000K. You can connect them to your ISY if you want with the LiFX nodeserver, but there's really no need (the API is local, no cloud involved, just your WiFi). The LiFX app will let you manage the color temperature changes, so the bulbs can automatically change temperature based on your requirements.

In an effort to eliminate motion sensors (barnacles, as my wife calls them), either Z-Wave or Insteon from the walls of our house, I bought one of these in order to see if it could be a useful alternative. My ISY is running the current 5.3.0 firmware/AC with the 500 series Z-Wave dongle installed. Installation was easy enough, though the device is roughly the same size as an Insteon SwitchLinc or a HomeSeer WD 200+. I was happy to note that I was able to include the switch from the junction box it was installed in, which is roughly 60' from my ISY. It does, however, share that junction box with a HomeSeer WD 200+, which acts as a Z-Wave repeater, so that may have helped. The installation created 5 nodes (screenshot), though only two are really useful in my installation (On-Off Power Switch and Motion Sensor 1). I have this device installed where it load it controls is a closet light, but that's not the device that I want the motion sensor to activate. I have the switch set to Manual Mode (there are three operational modes for this device 1) - Occupancy - the motion detector directly controls the load 2) - Vacancy - the motion detector will not turn the load on, but will turn it off 3) - Manual - the motion detector will not turn the load on or off) which makes it operate exactly like any other Z-Wave motion detector I've owned. With the sensitivity turned to "high", the motion detector triggers very quickly, which is good, as the light turns on in the room nearly instantly upon entering (and this is using a program on my ISY to turn on the lights, the load being controlled by a Z-Wave HomeSeer WD 200+). The motion detector is advertised as having a 180 degree detection area, and so far, it seems close to that. Ergonomically, the switch looks quite good, and the button presses have a solid feel, with the usual click of an on/off switch. These switches don't have anywhere near the adjustability of the HomeSeer switches and dimmers through parameters, but there are a few. Here's a link to the dimmer manual, and here's another link to the advanced configuration page that's available for these products. Below is what appears in the event viewer when the motion sensor turns off, then ten seconds later, turns back on, followed by node details in the event viewer. So far, one Insteon MS II (barnacle) removed from my walls. I have five others that I can very reasonably replace with either these switches or dimmers. It seems that they work very well, are easy to setup and configure, and have nice ergonomics. Fri 10/16/2020 05:39:13 : [ ZW025_308] ALARM 0 (uom=25 prec=0) Fri 10/16/2020 05:39:13 : [ ZW025_308] DOF 0 (uom=78 prec=0) Fri 10/16/2020 05:39:13 : [ ZW025_155] ST 0 (uom=78 prec=0) Fri 10/16/2020 05:39:13 : [ ZW025_155] DOF 0 (uom=78 prec=0) Fri 10/16/2020 05:39:23 : [ ZW025_308] ALARM 8 (uom=25 prec=0) Fri 10/16/2020 05:39:23 : [ ZW025_308] DON 100 (uom=78 prec=0) Fri 10/16/2020 05:39:23 : [ ZW025_155] ST 100 (uom=78 prec=0) Fri 10/16/2020 05:39:23 : [ ZW025_155] DON 100 (uom=78 prec=0) Fri 10/16/2020 05:36:17 : [ZW-SHOW ] ---------------------------------------------- Fri 10/16/2020 05:36:17 : [ZW-SHOW ] ZW 025 On-Off Power Switch Fri 10/16/2020 05:36:17 : [ZW-SHOW ] ZW025_1 uid=25 security=None type=4.16.1 mid=99 tid=18765 pid=12338 Fri 10/16/2020 05:36:17 : [ZW-SHOW ] Association Group ID 1 Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x20 V1 BASIC Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x5E V2 ZWAVEPLUS_INFO Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x72 V2 MANUFACTURER_SPECIFIC Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x5A V1 DEVICE_RESET_LOCALLY Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x73 V1 POWERLEVEL Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x27 V1 SWITCH_ALL Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x25 V1 SWITCH_BINARY Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x2B V1 SCENE_ACTIVATION Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x2C V1 SCENE_ACTUATOR_CONF Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x70 V1 CONFIGURATION Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x86 V2 VERSION Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x71 V4 NOTIFICATION Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x60 V4 MULTI_CHANNEL Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x8E V3 MULTI_CHANNEL_ASSOCIATION Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x85 V2 ASSOCIATION Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x59 V1 ASSOCIATION_GROUP_INFO Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x7A V2 FIRMWARE_UPDATE_MD Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - x56 V1 CRC_16_ENCAP Fri 10/16/2020 05:36:17 : [ZW-SHOW ] - Secure Fri 10/16/2020 05:36:17 : [ZW-SHOW ] Fri 10/16/2020 05:36:17 : [ZW-SHOW ] ----------------------------------------------

I believe this behavior changed in 5.1.0. From the release notes: New – Some changes to the Admin Console o You now have to press the button when issuing a command for a node on the device page (rather than just change a parameter for the command to automatically be submitted) o All commands are now shown on the device page

I can't answer if you have something wrong, and I don't know how to correct it, but my AC shows an "Options" button between "Write Changes" and "Users". Maybe you need to use the "Z-Wave | Synchronize" menu items (that's a guess...)?

You can always go to the Z-Wave | Z-Wave Version menu in your Admin Console. If the popup window looks like the attached screenshot, then you have the current 500 series board.

Congratulation on reaching certified status with Z-Wave! The one issue I was having (Schlage Z-Wave lock showing pending writes) appears to be now resolved, at least for now...

My Echo's have are operational, and have been since the last hiccup by my ISP. Is your ISP unable to route the traffic? Maybe unplug the Echo's for a minute and let them rejoin your network.

It looks like the "Write Updates to Device" icon is back on my lock this morning. I can confirm that the functionality works -- I can change users, options, etc., successfully, so it appears to be operationally unaffected.

That means that there are updates waiting to be written to the lock. It will have to be woken up in order for the updates to be written. I have a 500 series board, and I had updates that needed to be written to the lock, for which the "Write Updates to Device" command always failed. This morning I excluded the lock, factory reset it, included it, and it's back to working normally running 5.2.0.

Outstanding! Thank you, that worked!

Same issue for me with the old lock, it won't include securely. It excludes okay, but the secure include fails. This post indicates that the newer locks behave better, but I don't have one to test at the moment: