Bumbershoot

I can't really answer the first part of your question with any authority, as I have my own PWS (WeatherFlow), but prior to getting that, I used Climacell node server and found it very useful at my location. Regarding using substitution variables in your notification: The values that appear in your notification can be derived from the Polyglot installation. My WeatherFlow node server is installed in slot 12 (which is why you see .../node012... in the URL below). I use the REST interface to look up the values, and I do this using this URL in a browser: http://192.168.1.19:8080/rest/nodes/n012_forecast_0 This returns XML that looks like this: <nodeInfo> <node flag="0" nodeDefId="forecast"> <address>n012_forecast_0</address> <name>Forecast 0</name> <family instance="12">10</family> <parent type="1">n012_controller</parent> <type>0.0.0.0</type> <enabled>true</enabled> <deviceClass>0</deviceClass> <wattage>0</wattage> <dcPeriod>0</dcPeriod> <startDelay>0</startDelay> <endDelay>0</endDelay> <pnode>n012_controller</pnode> </node> <properties> <property id="GV0" value="32" formatted="32°F" uom="17" prec="1"/> <property id="GV1" value="212" formatted="21.2°F" uom="17" prec="1"/> <property id="GV13" value="4" formatted="Snow Possible" uom="25"/> <property id="POP" value="30" formatted="30%" uom="51"/> <property id="ST" value="0" formatted="Sunday" uom="75"/> </properties> </nodeInfo> Just match up the "property id" with the "value" you're looking for, and it's pretty easy to figure out. It's pretty easy to figure out the <address>n012_forecast_0</address> you want by looking at the AC (screenshot). EDIT: See the wiki on Substitution Variables here: https://wiki.universal-devices.com/index.php?title=ISY-994i_Series:EMail_and_Networking_Substitution_Variables

Here’s a good place to buy in the US: https://www.supplyhouse.com/Sensors-14422000

The VenstarCT node server has a default shortpoll value of 20 seconds, though that’s user configurable. I believe the temperature granularity is one degree.

I only have one stat, but I have sensors in remote parts of the house. There are both wired and wireless (WiFi) sensors available. There is a utility from Venstar that you use to provision the wireless sensors (don’t know about the wired ones). The wireless sensors can be wall mounted, though they’re kinda big. See if they meet the WAF before purchasing. I set them up as fixed IP addresses (IP reservations) and with Lithium batteries, they seem to run forever. I just put them on shelves where the Mrs. doesn’t notice them, and she’s never been more comfortable.

It might be possible to do something interesting. If you have a window sensor that indicates the window is open, then set mode to “Off” until the remote sensor drops below “X”. That ought to work.

I don’t see anything in the API to suggest that functionality you’re looking for is available outside of the app or the Skyport website (which seems odd — maybe that functionality is undocumented). You do have sensor data available to the ISY through the node server, so you could possibly write some programs that manage setpoints based on individual sensor data of your choosing.

I may have used too much poetic license by saying “instantaneous”. Some values are updated in the ISY using the “short poll” value in the node server. I believe the default is 20 seconds, though you can set it to suit your needs.

Venstar ColorTouch T5900 thermostats provide a local API and there is a very good node server to control them from your ISY. There is a cloud based app to control them as well, but connecting to your ISY is entirely on your local WiFi network, and instantaneous, as far as I can tell. Heat pumps are supported. I believe the temperature granularity is one degree, and I use two remote temperature sensors to provide input. The sensors are supported by the node server. https://files.venstar.com/thermostats/colortouch/documents/T5900_manual_rev4.pdf

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.

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.

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.