Bumbershoot

Yes, it's the BATLVL property. Something like this should fetch the value into a report: ${sys.node.ZW024_1.BATLVL}

@mango, I don't think there's an elegant way to do what you're trying to do. You have to work around ISY limitations with regards to STRINGS. The first thing I did is create a program that puts user # into an INTEGER variable, and the lock status into a STATE variable. When the status of the STATE variable changes, I have another program that will evaluate a couple of conditions, and if the conditions are met, it will use both variables in the body of an email. I put a small static table (for user lookup information) in the body of an email customization. Below is an example of what the email look like: The Garage Door lock status is ${var.2.27} 0 = Unlocked 1 = Locked Person making this change is ${var.1.5} 0 = Manual or programmatic unlock 1 = Lori 2 = Brad 3 = Zak 4 = Katherine 5 = Wally 6 = Norman 7 = Ann

Try the bottom of the Z-Wave menu: Z-Wave | Z-Wave Version Selecting this option should produce a pop-up window that looks something like this (screenshot).

Alfred Locks makes their DB2-B, which comes in gold and has an optional Z-Wave module, which gets you above your price point, but the locks seem very full featured. https://alfredinc.com/collections/products/products/db2b

I've fiddled with my older lock (non Z-Wave +) a few times, and network wide inclusion doesn't seem to work with it, no matter how close/many repeaters are present. I've just had to remove it from the door at take it to the ISY (within 10 feet or so, if memory serves me correctly) and include it. I believe you can exclude it in place, however, just not include it. This was explained to me as being part of the "S0" security that the lock/ISY employ (as a way to defeat packet sniffers, man-in-the-middle attacks, etc., during setup). My lock is probably 75' away from my ISY. I don't have a Z-Wave + lock, so I can't report on that. All of my Z-Wave device that have security use "S0", so they all had to be included close to the ISY.

I think this will be important. My ISY gets pounded by Polyglot/Z-Wave/Insteon data, which I think will only get worse. My hope has always been that the Polisy will chew through all the data, basically instantaneously. Modern wired/wireless networks can handle higher speeds, the question for me is if my Insteon and Z-Wave networks can handle higher data throughput. I hope so. I've got spares of every Insteon device I have installed (save the SyncroLinc), and a couple spare PLMs. I've never had an Insteon device fail, so I think I'm good for as long as I stay in this house. That said, all my new devices have been either Polyglot devices or Z-Wave. I'm not looking to grow my Insteon installation, but am hoping instead that Z-Wave and Polyglot device performance improves so I can replace Insteon if need be (though I'd miss the KPLs). I hope/suspect that performance improvements across all device types will become realized on the Polisy platform.

An observation/perception with Z-Wave performance on 5.3.3: I'm perceiving that my ISY is handling Z-Wave device updates faster than it has in the past. I don't know if this is true, as I don't have data to back this assertion up. This is perceptible in a couple of device types in my installation: Z-Wave motion sensors, my single Z-Wave lock and the state changes in my garage doors. None of my Z-Wave motion sensors are battery powered, but with this firmware, it very much seems that the ISY turns on the lights upon motion being sensed quicker than previously, which is nice. Also, when I open/close my garage doors, I notice that the firmware shows the transition from closed/opening/open almost exactly when the tilt sensor changes state. This has never been this quick or reliable. Additionally, my single Schlage lock displays changes of state in the AC immediately instead of a few seconds later. This just makes me think that UDI is getting their Z-Wave code optimized in their firmware. Not a big deal (and maybe not even true), but I'm liking my Z-Wave devices a little more with this release.

The 2477D is in 5.3.3 (see screenshot). Also the MS II can be added from the menu tree: "Link Management | Link a Sensor | Motion Sensor II"

FWIW, they fixed this issue with Adjust Scene in 5.3.2, which has indeed worked with my battery powered scene controllers. From the notes: 0000774 - Green icon appears on Insteon Controller Node after using Adjust Scene

@fasttimes, these dialogue boxes are what the "Options" and "Users" buttons at the bottom of the pane produce.

Installed. No apparent issues. The first thing I did is exercise my Schlage Z-Wave lock from the AC, and it operated as designed. EDIT: Are these new icons in the context menu in program details pane? Maybe I didn't notice them before...

No metal doors here. Stick frame house, probably 4 walls and 30' between the siren and lock, and the siren is probably 25' from the ISY. EDIT: The door the lock is installed in is metal clad. I just checked.

It's an old product, an Aeotec Gen 5 Siren, which I got in early 2016.

These locks do work with repeaters. I only have one older Schlage BE469, and it successfully uses an Aeotec Siren as a repeater. With the latest ISY firmware, it operates reliably. Thu 02/25/2021 06:57:32 : [ZW-SHOW ] ---------------------------------------------- Thu 02/25/2021 06:57:32 : [ZW-SHOW ] ZW 024 Schlage Door Lock Thu 02/25/2021 06:57:32 : [ZW-SHOW ] ZW024_1 uid=24 security=S0 type=4.64.3 mid=59 tid=25409 pid=20548 model=2 Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x22 V1 APPLICATION_STATUS Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x72 V1 MANUFACTURER_SPECIFIC Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x7A V2 FIRMWARE_UPDATE_MD Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x98 V1 SECURITY Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x86 V1 VERSION Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - Secure Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x5D V2 ANTITHEFT Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x85 V1 ASSOCIATION Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x20 V1 BASIC Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x80 V1 BATTERY Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x70 V1 CONFIGURATION Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x62 V2 DOOR_LOCK Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x71 V3 NOTIFICATION Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - x63 V1 USER_CODE Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - xEF V0 MARK Thu 02/25/2021 06:57:32 : [ZW-SHOW ] Thu 02/25/2021 06:57:32 : [ZW-SHOW ] Last working route from ISY to Node 24 - ZW 024 Schlage Door Lock Thu 02/25/2021 06:57:32 : [ZW-SHOW ] - Node 7 - ZW 007 Siren Thu 02/25/2021 06:57:32 : [ZW-SHOW ] Thu 02/25/2021 06:57:33 : [ZW-SHOW ] Node 24 - ZW 024 Schlage Door Lock has the following neighbors ... Thu 02/25/2021 06:57:54 : [ZW-SHOW ] Thu 02/25/2021 06:57:54 : [ZW-SHOW ] ----------------------------------------------

I don't think I'm directly responding to your question, so I apologize if this isn't any help. I use the "adjust scene" functionality in a program to achieve something like what you describe. I have a 4-way in a dark hallway that I want to turn on at different levels depending on sunrise/sunset. This scene is kicked off by a motion sensor, but you could easily have a state variable kick it off, or just run it from Agave if you like. The beauty is that the lights (and all the switches in the scene) turn on at the proper level at the proper time. When this program is run, it takes a few seconds to write the changes to the switches, so it's not instantly effective. 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

I've never had to do this, but I suspect that you need to simply add you new ISY to the Portal. Then, turn off your old ISY, or switch the Portal connection to the new one.

I've got 2.2.13 running, and the logging is back. The new version came through the regular update process.

This is the area where I've found Insteon motion sensors linked to Insteon switches to be the best solution available. Nearly instantaneous lighting upon motion being sensed, so there's no stumbling around in the dark. There are reported shortages of Insteon modules these days, apparently due to supply chain issues related to the pandemic.

@paulw, can you ping your ISY from your new computer? If you can, then keep looking at Java and firewall issues. If you can't, then there may be something incorrect about your network setup.

It sounds like you're trying to access your ISY through your browser. Most up-to-date browsers have eliminated the ability to start Java applets due to security. Along with what @MrBill advises you above, be sure to use the ISY Launcher to access your AC.

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.