Bumbershoot

I think your original request is provoking. I'm no engineer, but it's easy enough to imagine that Insteon could build a new PLM that also functioned as a Matter controller, which might get them closer to solving their problem of obsolescence.

I don't know if this is what you want, but in the program builder, if you select Schedule, and uncheck the Daily check box, you get access to a calendar.

Ken Fairbanks, in the Insteon Webinar on 11/04 indicated that Matter support is very much on the radar for Insteon. I'll believe it when I see it.

My station ID is simply five digits. No leading 000's or text.

@larryllix, in the areas where I use "adjust scene" (only in multi-way setups), I've never had an issue with any devices getting messed up, but I understand the concern. It takes a few seconds to write the new values to each device. @GQuack, I do set some light on-levels to a variable, but I set the values individually to each device in a scene. The program below actually contains two 3-way scenes, but the scene members are controlled individually - which I don't think it's strictly necessary to do - you can just set the on-level of the device that carries the load, though your switches will appear out of sync. KitchenLights - [ID 0077][Parent 000A] If $s.KitchenLights is not 1000 Then Set 'Devices / dirKitchen / sldKitchenSink' On '$s.KitchenLights %' Set 'Devices / dirKitchen / sldDining' On '$s.KitchenLights %' Set 'Devices / dirKitchen / sldKitchenIslandSouth' On '$s.KitchenLights %' Set 'Devices / dirKitchen / sldKitchenIslandNorth' On '$s.KitchenLights %' Set 'Devices / dirKitchen / sldTrackLightSouth' On '$s.KitchenLights %' Set 'Devices / dirKitchen / sldTrackLightNorth' On '$s.KitchenLights %' Set 'Devices / dirKitchen / sldUnderCounter' On '$s.KitchenLights %' Else - No Actions - (To add one, press 'Action') This program is used to interface with Alexa, and uses a STATE variable ($s.KitchenLights) to set a brightness value for the lights in the kitchen. "Alexa, set the kitchen lights to 50" will set the STATE variable to 50, which causes this program to run.

@GQuack, I'm not certain that you can do what you're trying to do without using the "adjust scene" functionality (which you'll find in the dropdown menu in the "Action" pane in the AC). I do something similar with the "adjust scene" functionality. Below is some code for a scene (this is for a 4-way setup) using an Insteon motion sensor as a controller (this program sets the on-level to 25% or 50%, based on time): 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 Any time the scene is run, the lights turn on at the correct on-level. If you don't use "adjust scene", then the scene will remain static at the on-level values it was set up with.

I think Philips folded the Warm Glow bulbs into the "Eye Comfort" series. These have the Warm Glow feature: https://www.usa.lighting.philips.com/consumer/p/led-candle---lustre--dimmable-/046677566654

First thing to look for: does your Polisy (with an IPv6 address) appear with a ✔️ beside it when you select the ISYs menu option on your Polyglot V3 installation?

@Snibley, the Station ID is a five digit number (you can find it under the "Status" menu), and you have to use that value in a Custom Parameter in the node server configuration, "Add Custom Parameter": Key <your five digit station id> Value local

I use Elk for security and fire as well. I use a different node server for my thermostat.

It's running okay for me, but it's possible that the developer isn't getting notified when there's activity in this forum. The developer is @simplextech, and you might consider sending him a DM.

@kzboray, if you haven't noticed, FanLincs are back in stock.

In the conference call a couple of weeks ago, the Insteon CEO complained that the bankruptcy custodian sold off the etching machine. He did indicate that he wanted to bring that service back, IIRC.

You set this value in the node server configuration page. In the Custom Configuration Parameters section, set Rapid Wind to true or false. FWIW, I wrote a program identical to yours quoted above, and the variable updates as expected. Maybe there's something specific with your installation of the node server.

You have to have a IS Portal account for the voice commands to work, so the migration is easy. Log into your ISY Portal account, then go to the "Select Tool" button, then go to the "Maintenance | Migrate to" menu options, select the ISY you're migrating to, and things will migrate automatically. I did this and didn't loose any voice commands at all. Quick and painless, in my case.

I thought about this for a second. If you're able to successfully install Z-Wave switches/dimmers, then you have all the skills you need to install the board. Decent motor controls in your hands and decent eyesight are all that's likely to be required, and an ability to follow directions. I have no doubt that this will NOT be a perilous operation. You'll probably need a small philips screwdriver, a table, and 15 minutes of your time. These little computers are not made of eggshells, and you won't need a soldering iron or a sledgehammer.

If you have the "Upgrade Packages" button in the System Configuration tab on your ISY software, then you likely don't have to worry about it. Clicking on the button should upgrade your Polisy to the latest/greatest and you're good to go. Otherwise, if you log into your Polisy with PuTTY, then the command 'uname -a' should get you the information you seek. [admin@polisy ~]$ uname -a FreeBSD polisy 13.1-RELEASE-p2 FreeBSD 13.1-RELEASE-p2 releng/13.1-n250158-752f813d6ccc POLISY amd64

Personally, I would just wait for the eisy. It apparently is nearing readiness, and the ISY software shipping with it will have all new Z-Wave code/hardware that UDI licensed from a 3rd party. Michel has stated that both the Polisy and the eisy will use FreeBSD as the host OS, so the functionality of both should be identical or close to it. You’ll have the latest/greatest with only one migration step.

I'm doing this from memory as I'm not at home, so I might get this a little bit wrong. Open System Preferences, click on the Privacy & Security tab, and select "App store and unidentified developers", and start.jnlp will run.

You shouldn’t need an API key, which is one of the great things about a local API. I’d make a static reservation for these lights in your routing table, and search for “devlist.yaml” in this forum. Sorry I can’t help you more, but I’m traveling out of the country for a while.

I’ve never seen that. Something is in an odd state. I’ll be surprised if you get a satisfying answer to your question. First thing I would do is to take out the batteries, wait a few heartbeats, then put them back in, and hope for the best. Reboot it. Kinda like running Windows 98.

I assume the clock on your Polisy is beginning to drift... Since your Polisy runs FreeBSD, the ntpd service should be running by default (it is on mine). ntpd is both a client and server, so you could just edit /etc/ntp.conf to have it point to a server location that's not blocked by your firewall. Also, commercial network switches provide NTP services, so if you've got one of those you can get to (your internet provider, for example), you should be able to use it. I don't know how UDI would respond to a support ticket for something like this. If you can find a local NTP server that you that you can ping, then UDI might help you edit ntp.conf. This might become an ongoing support issue for them, as local NTP servers can come and go. Also, UDI might take a dim view of users trying to edit system files... It's your property, but they provide support. I'd ask them in a ticket: support@universal-devices.com

You can certainly append the values to a file in the web space on your ISY. I put them in comma delimited format, making a file that can be imported into a spreadsheet and graphed from there. https://wiki.universal-devices.com/index.php?title=ISY-994i_Series_INSTEON:Networking#Dynamic/Custom_Page_Creation

There's been various discussion about this on this forum, but it's my understanding that if the device isn't used in the path back to the controller (and as a battery device, it isn't a repeater), there should be no effect. I have a similar situation with a 300 series device (which isn't in to path of any other device), and it doesn't seem to interfere with later Z-Wave enhancements, such as network wide inclusion.

Presumably, once the Polisy/eisy have Matter on board (also presuming border router functionality), then one can easily imagine the Polisy/eisy providing the glue between native Matter devices and any devices in the UD universe (legacy Insteon/Z-Wave/Node server devices). Performance might be a question mark, but there's no reason to think it would be much slower than any other node servers.