oskrypuch

Reading the instructions is often a good idea. ? * Orest

Lutron RA3, and then access to the wide array of lighting controllers (incl. Maestros) is a very tempting scenario -- assuming that the RA3 API will be publicly available. And, love Maestros! But, it all keys on an effective and well supported PG3 node. It would be quite a nuisance if you invested heavily in RA3, and then the PG3 node crumped, either by loss of support or a proprietary closing of the RA3 interface. Does an RA3 install require a licensed installer? I presume that Lutron requires access through the cloud, another potential issue. * Orest

Yes. There is available new stock of devices! ? That is why I'm there. Made the big leap to Polisy + 700 series dongle, and added seven devices at the moment (including a light controller). Happy with them. * Orest

There are no issues with using input from one device (node) in the ISY, to control other nodes. That is the general nature of the node architecture of ISY, where it doesn't really care about the physical identity of the device. But, there are some operational issues with the Zen 32 that make it more complex to use than the good old Keylincs. You can read about it upthread. * Orest

@kzborayThanks. I have several insteoned Venstar stats now, and do use remote sensors for them. All is working well, and I do have some spares, but just looking at mitigation in the future. * Orest

@Athlon... and for control from ISY, how do you do that? * Ores

Which model? Do the Ecobees support remote sensing, IOW having more than one location drive a single zone? Also allows you to locate the stats where you like, but control other locations. Which node servers are you using? * Orest

The Honeywell T9 works on WiFi, don't believe it needs the cloud though, and there is a free PG3 node for it. It will also work with remote temperature sensors. But, I have no experience with it. * Orest

Likely, here is where it came from ... This was a bit of sandbox code testing out the text message text, before I rolled it into the actual routines. * Orest

Thanks, you are quite right. Looking at it again, that line must be a bit of old code that never got deleted, when I was reworking the routine at some time in the past. * Orest

So, after some twenty years, my venerable X-10 ding-donger is retired!

No, I haven't. Seems pretty straightforward, you use a particular format for the file name so it can recognize the file. You can both add to the sound set, and you can replace the sound that is played for the default 0 - 30 labeled standard sounds. * Orest

I have replaced two alerts, and will add some more.

Thanks, but no, actually, I only want to receive ONE nag text, preceded by the $alert email when a beat is actually sent, so that is why I send it back to IF to reset the routine. I actually won't lose track of that single text. The email alert I use more for archive. Of course if it remains without a heartbeat, there will be no further activity. * Orest

I was looking for a replacement for my venerable X-10 ding-donger that has been working for some twenty years, happened on a good one that does much more. Ecolink ISZW7-ECO Z-Wave 700 series https://products.z-wavealliance.org/products/4000?selectedFrequencyId=2 Ecolink unit arrived, added into the system, set up with four nodes, only one is required. Simple to work, you can trigger the sound directly, or set a sound as default, and play the default. You can alter the volume each time, or use the default setting. Besides the chimes there are some voice notes and there are also Alarms included. The alarms run much louder, their high volume is locked by default, but that can be unlocked and adjusted as well. This is from my sandbox, just shows how to use it. Note that they have changed the 30 included chimes, voice callouts and alarms, and as well the number labels for these have changed. That is all listed in the little booklet that comes in the box, don't throw it out. You can add another 100 or so .WAV files on an SD card if you wish. Two thumbs up! * Orest

Unit arrived, I like it. Review here: * Orest

Does that help!? ? FWIW ... Here is my heartbeat routine, it works. I don't bother repeating the warning. It sends an initial email to confirm that it is active. If a heartbeat comes within 26 hrs, then it restarts and sends another email to show it is working. I don't monitor those emails, they get filtered to a folder for reference should I need it. But, if there is no heartbeat within 26 hours, it sends a text message indicating that heartbeats have lapsed. It is also important to monitor for switched ON + switched OFF. * Orest Heartbeat Kitchen - [ID 021B][Parent 0135] If 'kitchen / LEAK - Kitchen-Heartbeat' is switched On Or 'kitchen / LEAK - Kitchen-Heartbeat' is switched Off Then Send Notification to 'xxxxxxxx - GMail' content '$my_alert' Wait 26 hours Send Notification to 'xxxxxx - Text' content 'LEAK Heartbeat MISSED' Run Program 'Heartbeat Kitchen' (If) Else - No Actions - (To add one, press 'Action')

@hart2hartAre you using an ISY994 or IoP on a Polisy? * Orest

Bear in mind that ferreting out your Station Id is not immediately obvious. It is not the printed ID on the unit, nor the ST number. Where you log into Tempest Weather (or in the app), that is where you will find the Station ID that PG is looking for. For example ... https://tempestwx.com/station/nnnnn/ nnnnn is what you need for the station ID field. * Orest

The comment was entirely tongue-in-cheek, but I suppose I'm hopeful, like everyone else. * Orest

Yes, there are cables you can buy. If you can't find one, I saw a link for one fly by here somewhere. * Orest

Well, up to seven Z-Wave items, now (in place and/or ordered). And, I'm carefully laying these out so that I build out a properly spaced RF backbone, as I'm still in a sparse array. Replacing some of my really old Insteons, one of these was a bit flaky now and one had completely failed, so some were on the list to be replaced any way. The still working pulled units, putting into inventory for possible future swap ins. Between the same-function Z-Wave replacements, a bit of inventory (in particular brand new Keylincs), and securing three 2413S as backup, I'm sure I'll weather this storm, and sail comfortably into the future. And, I'm finding all kinds of interesting Z-Wave modules, that will give me functionality I didn't have before, with a pure Insteon setup. All good. And, this forum is great. Great depth of knowledge and experience. * Orest

That is a REALLY outstanding post. That and the wiki, and really a lot of the posts in these sections, made my ISY -> IoP migration smooth, and helped me get up to speed on adopting Z-Wave. * Orest

Why? Well, there is value in redundancy, or for sandboxing. And I do have another location that I will likely be moving over to IoP/Z-Wave soon. But the big reason I ordered the second Polisy (from a local Cdn supplier) is that they bundle it with a 2413S PLM! They must have a bit of stock left, and are being rather shrewd with it. So, now I have several backups of the 2413S PLM units, including this brand new one. Any money now, expect that Michel will announce the 2413 Pro next week! ? * Orest

If you want to start from scratch, then simpler to just factory reset the PLM, and then plug it into the Polisy, rather than making deletions. But it is probably even easier to back up your ISY, make no changes or deletions nor a factory reset, move the PLM over to the Polisy and restore your setup. From there you can make any necessary changes. Be sure to carefully follow sequencing as outlined in the wiki here. * Orest