MrBill

Maybe. If his Polisy is includes it. His ISY version is 5.0.16B, which is very old. If his Polisy is old and he's never updated it, PG3 is not running. If running 300 series Z-wave OP should update ISY to 5.0.16C, if not then ISY firmware should update to 5.3.4. We need to know where he is on Polisy before being able to tell him his upgrade status there.

Best Solution is don't use email for notifications. Use Pushover, via pure Network Resources or the Notification Node server. Second best solution is create an email at your ISP or gmail and configure ISY to send FROM that address. Also send your emails TO that same address. Download a separate email client on your phone such as SPARK email and turn on notifications and exempt it from DO Not Disturb, Add the from/to email above to Spark. End result... ISY uses the address to send email TO the same email address ISY is sending FROM. You have a separate mail client on your phone that is allowed to use Push notifications anytime.

I downloaded the Spark mail client on my phone, and created a Comcast address for notification and that address only exists on Spark, this way I could let Spark mail always notify and be exempt from Do Not Disturb hours, and it has distinct sound from regular email on my regular email client.

Sending from the default mail server to a comcast email account the 'test' email will filter to spam. check the spam folder, and a because of this a better way to test is right click a program name that send a notification and choose Run Then.

if you are using the default server for email notifications you might want to shoot an email to support@universal-devices.com I'm sure @Michel Kohanim will see this thread eventually but it may add more hours until he does...

You need to order Lock Ease ... I use it for way more than locks, it gets more use than WD40 since I discovered it... Dry graphite in Alcohol base aerosol that cleans then evaporates and leaves dry lube behind. Once I've used it on a door hinge I've never had to repeat. Watch it tho, a little goes a long way and when it "runs" its hard to wipe off. Squirt it as micro-bursts.

Amen. I have versions 1 and 3, I don't think I have any 2's but I've never paid close attention. I just so some reset on there own, and some need the button to be pressed.

@CopyRon If you have 4 portal accounts that's probably not what you want. If they all appear under one account but you have 4 subscriptions that's different. If all 4 ISY devices were connected to one portal account, then in the top right choose "My Profile" then pick "Use All ISY's on account" in the dropdown.

I believe you can not migrate the licenseby unchecking the box. Then if you have a large number of months left of the old license email support with both UUID numbers and they can manually move the remaining month. Be sure to clearly state which is old UUID and which is NEW UUID.

did you migrate via the portal to a new ISY https://wiki.universal-devices.com/index.php?title=ISY_Portal_Migrate_configurations_to_a_new_ISY

@Bumbershoot I've heard we aren't supposed to use the portal update and i've asked, even recently why the function even exists if we aren't supposed to use it, but the question always goes unanswered.

It's exactly the same process. and yes it's gruesome. I've done one PLM change and my system was much smaller then. The worst of it is that every device needs updating.

this is a cool tool that i use, its similar in principle but it sucks the solder up instead of blowing all over the place randomly https://www.amazon.com/WEmake-WM-SP4-Solder-Sucker-desoldering/dp/B0002KRAAG/

I don't know if 15 hours ago is to long ago to stop you. BUT I wouldn't do that, especially if you have a lot of Insteon modules. Here's why, when you replace the modem in the system the modem has a new AB.CD.01 insteon address, and that new address must be written to EVERY LINK in EVERY DEVICE. It can take a long time, and unless your communication is perfect there will probably be at least a few broken links somewhere. Then that process must be repeated when you swap back, again opening up the possibility for communication error caused broken links. If the Insteon system is small it wouldn't be too big of a deal. If it had 150 devices like mine does, I'd never do it. As far as the best way to test it, there really isn't a best way without a second Polisy. The second best way would be to back up your polisy, unplug it from the current PLM and set it aside, then clear your Polisy and install the USB stick PLM and test it with a few random devices. You could also test the hardware with other software via a PC, I don't know what other software to recommend. There's absolutely no way that I would rewrite all the links in my insteon system without a dead modem. You're asking for trouble if you swap the device in. Again if you have a small system, like 10-12 devices, it wouldn't be hard to fix problems, in a larger system tho, the rewrites will takes hours (swap modem) and not be prefect in the end.

older modules DO alternate. I've repeated this twice above.

It doesn't actually send an OFF signal. It only sends ON and will always show ON in the admin console. It's the LACK of an ON signal that tells us the battery may be low. which is why we WAIT 24 or 26 hours to notify after not receiving. Most all Insteon devices send DON only has hearbeat. Some device firmware historically however did alternate on, off, on, off... which is why we write the programs as ON or OFF, we don't need to know which way the device sends it either on, on, on, etc or on, off, on , off.... all more modern insteon devices tho only send DON or On, as the heartbeat and never send DOFF or Off. Definition of more modern: perhaps at least the last 6 or 7 years at least... i don't know when devices last had firmware that sent on, off, on, off as hearbeat.

Most Insteon devices send DON for heartbeat (and don't alternate DON, DOFF, DON..) but it's been said that some do, and I've never paid much attention to which do. The generally accepted, most basic, heartbeat monitoring program is close to what @Techman typed above. (in actually "is NOT switched" isn't an option.) IF Control Heartbeat is switched ON OR Control Heartbeat is switched OFF THEN wait 26 hours Send Heartbeat fail notification ELSE [nothing] The basic theory behind the program is that when the heartbeat is received, it starts the THEN block of the program which is a wait statement.. if the 'wait' expires a fail notification fires. However because ISY programs are event driven the heartbeat will be received again in less than 26 hours-- when this NEXT heartbeat arrives the wait in progress immediately stops and a new 26 hour wait begins counting down. So as you can see, the fail notification is only reached when a new heartbeat doesn't arrive in time. But we can always build a better mousetrap.. One of the problems with the above is that if for some reason the notification isn't received, or is ignored there's no nag. Another is that it's a fact sometime heartbeats are missed, missing one today doesn't matter if we know it's a reasonably fresh battery it's likely just a fluke. Also the sensors stop sending hearbeat before they are completely out of battery... meaning they actually work for a period of time after the heartbeat quits. In conclusion, failed heartbeat is not an emergency need to replace the battery, it means 'replace battery soon' as in the next days--- not it must be done now. I create 3 integer variables for each sensor, Missed Heartbeats, battery days, and transmission count. Then this is the program: hb.WhiteRefrigLeak Copy - [ID 00FB][Parent 0072] If 'Door Switches / White Refrig Leak - Dry / White Refrig Leak - Heartbeat' is switched On Or 'Door Switches / White Refrig Leak - Dry / White Refrig Leak - Heartbeat' is switched Off Then Wait 25 hours $iDoor.WhtRefrigLeak.HBmissed += 1 $iDoor.WhtRefrigLeak.HBmissed Init To $iDoor.WhtRefrigLeak.HBmissed Wait 2 seconds Resource 'NotificationNS.DoorTrouble.BarnOHD' Run Program 'hb.WhiteRefrigLeak Copy' (Then Path) Else - No Actions - (To add one, press 'Action') The key differences are: incrementing the HBmissed variable for the sensor if it was missed, I use a different message to send notifications, and then the last line re-runs the THEN portion of that program... that is if the heartbeat was missed we will for sure repeat the notification again tomorrow if it is again missed. (the original program relies on a heartbeat to be received again before it's re triggered.) It should be noted that this program should also be configured [Run at Startup], mines not because I have a separate program that starts heartbeat, so that I can used it at Daylight Saving Time switches in the spring and fall (the time change will interrupt any waits running at the time change). Like wise there is a program that counts all tranmissions for a device. Since this is a leak sensor thread this seems insignificant... the only signals a leak sensor normally sends is heartbeat. However I use the same base program for all insteon battery devices, and 15,000 open and closed or motion detects does make a difference. so to count transmissions: White Refrig Leak - [ID 007E][Parent 0033] If 'Door Switches / White Refrig Leak - Dry / White Refrig Leak - Wet' is switched On Or 'Door Switches / White Refrig Leak - Dry / White Refrig Leak - Wet' is switched Off Or 'Door Switches / White Refrig Leak - Dry' is switched On Or 'Door Switches / White Refrig Leak - Dry' is switched Off Or 'Door Switches / White Refrig Leak - Dry / White Refrig Leak - Heartbeat' is switched On Or 'Door Switches / White Refrig Leak - Dry / White Refrig Leak - Heartbeat' is switched Off Then $iDoor.UpperSlider.TransCount += 1 $iDoor.UpperSlider.TransCount Init To $iDoor.UpperSlider.TransCount Else - No Actions - (To add one, press 'Action') That counts any transmission received... again this makes more sense for door sensors or motion detectors. and finally the last value... Battery Days AddAge - [ID 003D][Parent 0034] If Time is 12:12:12AM Then [..redacted about 100 lines to make the forum post shorter..] $iDoor.RachioButtonUpper.BatteryDays Init To $iDoor.RachioButtonUpper.BatteryDays $iDoor.UpperSlider.BatteryDays += 1 $iDoor.UpperSlider.BatteryDays Init To $iDoor.UpperSlider.BatteryDays $iDoor.WhtRefrigLeak.BatteryDays += 1 $iDoor.WhtRefrigLeak.BatteryDays Init To $iDoor.WhtRefrigLeak.BatteryDays Else - No Actions - (To add one, press 'Action') At 12:12:12 every morning there is a program that adds 1 to the age of every battery in my system. and finally the failed notification includes all the data: <b>White Refrig Leak Sensor Trouble</b> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Missed Heartbeat Count: ${var.1.103} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Battery Days: ${var.1.7} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Transmission Count: ${var.1.77} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;${sys.date} ${sys.time12} Here's what the notification received looks like: (but the notification is for a different battery sensor) So as you can see in the past 162 days this sensor has missed it's heartbeat 15 times. (6 months = 180 days) I don't worry about a sensor until it's missed multiple days in a row, and even then if the counts are low sometimes i just pull the battery and wait 30 seconds and re-install it and heartbeats continue. When the counts are high then I change the battery. One more program: to reset all the counters i used a program that's manually run from my Home Assistant dashboard. LowerSlider.reset - [ID 01AB][Parent 01B5] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Resource 'NotificationNS.DoorTrouble._resetCountersBegin' Wait 1 second Resource 'NotificationNS.DoorTrouble.LowerSlider' Wait 2 seconds $iDoor.LowerSlider.HBmissed = 0 $iDoor.LowerSlider.HBmissed Init To $iDoor.LowerSlider.HBmissed $iDoor.LowerSlider.BatteryDays = 1 $iDoor.LowerSlider.BatteryDays Init To $iDoor.LowerSlider.BatteryDays $iDoor.LowerSlider.TransCount = 1 $iDoor.LowerSlider.TransCount Init To $iDoor.LowerSlider.TransCount Wait 2 seconds Resource 'NotificationNS.DoorTrouble.LowerSlider' Wait 1 second Resource 'NotificationNS.DoorTrouble._resetCountersComplete' Run Program 'hb.LowerSlider' (Then Path) Else Resource 'NotificationNS.DoorTrouble.LowerSlider' I also have an Excel spreadsheet to make creating many notification bodies much simpler, keeps track of all the variables and concatenation a string that can simply be pasted into the admin console. (if anyone's interested in the spreadsheet PM me)

I have to disagree, the problems are rare. Yes there are a number of threads here in the forum that illustrate the problem, when it occurs. But there are also 10 million other times that the problem didn't occur, people don't post about that tho. I agree that it's frustrating when java problems occur. You can read about the single time it happened to me here, but other than that single event I open the admin console across multiple ISY's many times everyday and other than that one time... I never struggle.

@cdave1252 Are you using Java 8 from https://www.java.com ? or some other version like 11 or 17? You need Oracle Java 8 from www.java.com

It's the same thing! unless you are selecting Dashboard from Finder. You must select either of the Admin Console selections: (cloud is faster but either should work).

Here's the troubleshooting lights from the WIKI, and yes if the connector fits you can use Polisy's, seems like my polisy has an adapter for the power connector. I added RED to this... Front Panel LEDs/Lights Boot up sequence: Power, RX&TX, momentary blink of Memory/RX and TX, and then Power only Only Power Light Is On: Most probably power supply related. You can try any power supply that outputs anywhere between 5 volt and 30 volts,center positive, 2mm barrel connector Error light and Memory light blinking simultaneously: ISY is not able to get on the network.Please ensure: The Network jack on the back of ISY is connected to your router The lights on the Network jack have one steady on and the other one blinking. If not, check cable and connectivity to the router Your router provides DHCP There are no other devices on the network with the same IP address (IP Conflict) If you have configured your ISY to use DHCP, then you will have to search your network for devices that might be in the same DHCP range as your router is providing If you have configured your ISY with a static IP address, and as long as you have a good backup, you can Factory Reset your ISY and then restore a good backup (File | Restore ISY). Once prompted to change the network settings, choose No Only Error light blinking: ISY cannot communicate with the SD Card. Please ensure: The micro SD Card (on the front) is seated properly. Unplug ISY, remove the rubber cap, using a sharp object, push the micro SD Card in so that it pops out. Push it back in so it clicks in. Apply power to ISY If reseating the micro SD Card does not work, you probably have a defective SD Card. Please consult Replacing/Formatting SD Card

I change most of the mini-remotes to 4 device controllers for exactly that reason, but yes you can do exactly what you suggest. YMMV with dimming tho and programs tho, you'll find there is a definite lag on releasing the button, you need to anticipate the level and release the button a split second sooner. I actually have this set up in a couple places, but the mini-remotes are in 4 button mode, but use a button to toggle a couple things, so that i could squeeze more devices on to one remote. My wife prefers the on / off scenario of the 4 device configuration because the button can be a scene controller and scenes are faster, the same button to toggle, always confused her, even when it's not the scenarios you mention with the 8-scene mode.

Shift and click the refresh does the same as well.

This is abnormal behavior, you should open a ticket with support@universal-devices.com Many of us do the same. During Polisy boot, Polisy asks PLM for it's Insteon ID and software version, if the PLM becomes unavailable due to power failure an ISY994 never realizes, when power is restored communication happily continues because it's the same PLM... that is specifically the Insteon ID hasn't changed. I assume Polisy is the same but haven't specifically tested that at this point.

A good place to start is the ISY Home Automation Cookbook http://www.universal-devices.com/docs/production/The+ISY994+Home+Automation+Cookbook.pdf The size of the PDF is intimidating, but there is a lot of explaining done from the very basic level to the more advanced.