MrBill

here is Michel's entire post, while the nuts and bolts were quoted above, the entire post is much more riveting:

as mentioned by @Techman X10 is still very much alive: https://www.x10.com/ If you haven't noticed the nokia product is only sold by smartlabs... i.e. insteon / smarthome's parent company and it's delivery has also been delayed to "nobody knows when". It's completely unclear what is really going on at insteon / smarthome / smartlabs, but someone posted yesterday they hear product may again be available in the spring. I've also heard the company is again for sale. so who knows.... You compared it to X-10.... they went bankrupt and sold a few times in the 50 year history of x-10.... Insteon could follow the same path....

Sadly if you're at that point likely the most logical thing to do is log into (via computer browser) https://alexa.amazon.com (its easier/faster this way than the app) and delete all the devices and scenes.... good and bad, then once all are gone say "Alexa, Discover devices" which is very destructive.

bookmarked... I don't need the info myself but I'm certain this will be a popular question over the next year or so.

You're confusing "Export to Clipboard" with "copy to clipboard" or "copy folder to clipboard". the Export option is XML both of the COPY options are plain text programs views.

The program logic is as described by @hart2hart I would however make a suggested improvement to your program. Add one line to loop back to the then block of the same program. The problem with the current program is the notification is only sent once. If you forget that it arrived or for some reason the notification gets lost on the way you are never notified again. To solve the problem add one more line to restart the THEN block meaning that every 25 hours the notification will repeat until a new heartbeat is received. hb.BarnOHD - [ID 0063][Parent 0072] If 'Door Switches / Barn OHD / Barn OHD-Heartbeat' is switched On Then Wait 25 hours Resource 'NotificationNS.DoorTrouble.BarnOHD' Run Program 'hb.BarnOHD' (Then Path) Else - No Actions - (To add one, press 'Action')

You're correct... setting "preferred ISY" doesn't work the way I thought it did, i just tried to do what your asking with a test ISY that I have. With the upcoming migration tool for Polisy I would think there would be a simpler method.

Are you setting the new up from scratch? or are you restoring a backup? If restoring a backup the "address" column should not be changing, meaning that to swap from old to new you would simply change which ISY the portal is pointing to.

Top Right hand corner of the screen there is a "Profile" tab. Select that and choose which ISY you want to use for Alexa and google, or "all on account". If you are restoring a backup on the new ISY the addresses shouldn't change, so you would just add pointing Alexa to the correct ISY to your list of things to do during changeover to the clone.

Did you try step 1... that is "reboot the ISY"?

If it's a 500 series board (if it was recently purchased it is) you may find that standing the ISY up on it's end gives better Z-wave range.

+1 That's probably the issue, if it's not you will hit the non-pro limit quickly with z-wave. If you have Polyglot on Polisy or Pi there is a nodeserver called ISY Inventory that accurately counts nodes.

I've found that pasting into the body you sometimes end up with an extra CR (or Enter) character at the end of the string.... that might not matter.... but it might in some cases too. Arrow forward or down and then backspace to get rid of extra character at the end of the string. I paste from Excel into NR Body's frequently.

I've got AT&T also and the delays are from the AT&T email gateway... some days its fine, some days it's hours later.... One batch of texts actually arrived months later (i guess stuck in a queue somewhere). I've pretty much quit using text messages for notifications. A much better solution is the service pushover.net that allows push notifications. On both V4 and V5 ISY's you can use Network Resources to send notifications. For version 5 there are 2 nodeservers available: Notification: requires polyglot running on Polisy/Pi. It's more feature rich than "push" and also is higher reliability as it retires on certain failure conditions. Push: is available both for local polyglot on Polisy/Pi and polyglot cloud with a more basic feature set. Notable tho because of it has a cloud version which doesn't require Polyglot on Polisy/Pi. Another viable option if you want to stick to email based notifications is to download a second mail client for your phone like Spark Mail (free) on iOS. Create an email address just to use there and turn on notifications for that email client. With this option you could continue sending from UDI's default mail server --or-- in my case I created a Comcast email address that the ISY sends from... and have it send TO the same email address which is configured in Spark Mail.

Question #1... if you open the admin conole to node for Button C do you see button C turning on and off in the admin console? Questions#2.. did you test your network resource to ensure that it's set up correctly? Additional info: remeber that you can select the program name in the program tree and then right click and pick Run THen or Run Else to test your program. Also remember that you must SAVE the program before it will work, or save to apply changes before they will take effect.

I can't tell by your steps... but the proper proceedure to change a PLM is to unplug both the ISY and the PLM. Then swap the PLM, plug it in and wait 30 seconds, the green light should be on steady. THEN plug in the ISY. If your are changing a PLM without re-starting the ISY then the ISY will never realize the PLM has been changed... during the startup procedure is the ONLY time the ISY interrogates the PLM for it's device address. Therefor if you hotswap a PLM then do restore PLM it THINKS its restoring the old PLM, not the new. When a PLM is actually swapped and the AA.BB.CC address changes then "restore PLM" will take a long time... because the PLM address change and needs to be written to every single link in every device in the house.

correct ${sys.node.n006_rain.XXX} To figure out what XXX should be replaced with follow the guide below.... NOTE: I'm using a different nodesever, you need to figure the out for the nodeserver you are using. from the admin console: I just forced 1/100 of an inch for this demo. Now go to the node server node listing: and locate the matching node in the node listings: The value I'm looking for is either GV1 or GV2 (note the 0.01 values) I'd make the educated guess that it's probably GV1 that I'm looking for, but then next time it rains I'd watch for which value is which. so if GV1 was the "Driver" value that yours returned you would use ${sys.node.n006_rain.GV1} See also this wiki page for more substitution information.

I read too fast, I see you stated that now, but I read it the other way the first time... but if the power light on the front is NOT on that is also indicative of a bad power supply. The blue LED on the front is pretty much attached directly to the power entry point.

From the Wiki: 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 This most definitely sounds like a bad power supply, and there was an apparent bad batch of them shipped at some point, because it's not uncommon for users to report the power supply replacement solved the issue. The good news is you can use a WIDE variety of power supplies.

tagging @glarsen

@Javi... thanks for that, it makes more sense to me now... I passed the info along.

I use Home Assistant and I believe you are correct that it uses PyISY... that said... I have no problem... HA works perfectly even when its rebooted which should close the subscription. (I may or may not have a method to get the PR some attention.... I'll try and see what happens...)

And one more comment.... Another method is to drop the motion sensor from the scene, and then add the line that turns the light on back to the program..... and "adjust scene" the root level controller. The drawback is that it takes an extra few seconds after motion detection for the light to come on.

You're going to need to open a ticket.... the fix for that was in 5.3.2: my guess is that they missed that particular device in the fix.

You can't and shouldn't need to for this. That said, "Adjust scene when used with a wireless controller" was broken in many versions of 5.x... I can't remember exactly which recent release fixed the bug but to use adjust scene with a wireless controller you should not need to put the device in setup mode-- the link that needs to change is actually in the responder. Your first post says you're on 5.3.4 so you should be good.