Athlon

Thank you. I tried a new cable and still no joy. So, to recap, I've tried two different PLMs (including one that's never been used before) and I'm still in safe mode. What can I test next, if anything? By the way, the ISY finder works and I can log in.

Thank you for replying so quickly. By the way, we had a very brief power outage yesterday - less than 2 seconds - and that's when my ISY stopped communicating with the PLM. I unplugged both the PLM and the ISY. I first plugged in the PLM (the 'new' one) and waited about 3 or 4 minutes, then I plugged in the ISY. I still get the message about no communication with the PLM on my admin console. How do I know the PLM is fully powered up? The green light comes on immediately. Also - I have not tried a new cable yet - my wife and I are going out shortly - will try that in the AM and report back here. I have to say though that the cable on there has been on there since day one, and the ISY is in a very protected area.

My ISY is in Safe Mode. I rebooted it and the PLM a few times. I then installed a new PLM I ordered and received about a year and rebooted the ISY. The ISY still in safe mode. What do I do next?

@johnstonf I'm not going to presume to answer for larryllix, but my guess is the lesson is we are all at the mercy of any cloud services we use (in this case AWS). That's all he meant to say, I believe. UD is relying on AWS for the portal, and obviously by extension so are we. When AWS has issues, so will we. Thank goodness it does not happen very often. I use Gmail and even they 'went down' for a short time last week. It happens - that's the lesson. There is not much you can do about it except to minimize the number of cloud services you rely on. I'm sure UD did everything they could if AWS needed them to repair the issue. EDIT: I'm mentioning AWS because someone else did in this thread - I don't know exactly what caused this issue. I believe larryllix's comment was directed toward cloud services such as AWS, however.

I believe by 'we' he means all of us.

All is well here as well.

Ditto - since 6:30am Sunday

Thanks to you both. I'm not opposed to a little soldering. I'll just have to figure out where... Each shade came with it's own remote, and they can each be programmed to any other shade. So, I can 'pair' two shades to one remote so I'll have an extra remote. Is there a node server that will tell my RPi to activate the relay?

We just had a new roof installed along with new skylights with solar battery operated shades for the skylights. The shades are made by Velux - their Velux Integra series. They use the io-homecontrol protocol to operate. They came with battery operated remotes (one for each), their model KLI 312. They did not come with a Velux KLF 200 - those are currently not available because of the chip shortage, although I don't think it would be a solution for me anyway. My goal is to be able to operate the shades with both my ISY and Alexa. The Velux website is very frustrating - it's very difficult to get specs on their stuff and many links take you to broken pages. Their online store is closed because of the current chip shortage. Google searches lead me to mostly European sites that do not ship here to the states. I have discovered an io-homecontrol hub that may operate my shades - the Somfy 1870600. It's new and available on Ebay from a reliable vendor. (It's not for sale in the US yet.) The protocols include io-homecontrol, RTS, Zigbee 3.0 and it works with Alexa. My question is this - is there an easy to control the Somfy with my ISY because of it's Zigbee compatibility? (My model ISY has Z-wave.) I'm also running Polisy on a Raspberry Pi.

Oh wait - I don't have a Polisy - sorry about that.

Hmmm - I wonder why I don't see it...

How did you do that? I don't see it listed in the Polyglot Store...

I've been using TP-Link plugs for years (since right after they came out) for mostly Christmas lights and candles in the windows (about 20 of them). None have failed yet, nor have any failed to receive and execute a signal. They've been rock solid even though I box then up at the end of every January and bring them back out in late November. I don't even have to re-program them. I have a strip of masking tape labeled with a Sharpie on the back of each one telling me which window or spot in the house (like the Christmas tree, village under tree etc.) they go to. Because of their reliability and low cost, I have about 6 of them in year round use as well - all of which are in spots that are hidden from view.

I have a TP-Link plug connected to a lamp in my 94 year old mother-in-law's house 125 miles away. I can program it from here very easily with their free Kasa app. That would easily solve their problem

Love our Ooma. We have the original one and it's still going strong.

[[Is anyone here afraid of Insteon disapearing?]] Nope - All of mine are screwed in tight. ?

Been whispering to mine for a while - love the voice. ?

Woot! Congrats guys!! ?

Perhaps when we can change to Sam's voice she won't be so sensitive... ? https://www.theverge.com/2019/9/25/20883751/amazon-alexa-voice-languages-natural-bi-lingual-frustration-support-new-features

Here's a thread I started a few months ago where I show how I get Alexa to make announcements: I've since made a change because IFTTT changed their texting policies. I now have my ISY text me directly. (This part of my program has nothing to do with the Alexa part of the program.)

Thumbs up for Agave here as well. Although my phone is an iPhone, I use Agave on my Amazon HD Fire when outside by the pool.

I use TP-Link devices. They work great. Read through this thread for how to use them with your ISY:

What brand of WiFi plug are you considering?

Great!

You're welcome. I did the following three times in the Portal, one for each of the three Routines in my Alexa app. Each of the three uses one of the three State Variables I refer to in my post above. Here is how I set up the one for 'JoAnn_Garage_Door_Is_Open_1st_Announcement' Go to your portal, then go to Select tool/Connectivity/Amazon Echo Click 'Variable' My state variable: Use the drop down box to choose your 'State Variable' ('JoAnn_Garage_Door_Is_Open_1st_Announcement' in my case) Room is optional Alexa Category: choose 'Contact Sensor' Contact closed value: for me, 0 works Spoken: I used 'J Gar Dr One' Click 'Save' +++ I created four Routines in my Alexa app, one for each of the State Variables, and one for when her door closes. Here's how I did the Routine for the first announcement. In your Alexa app choose 'Routines' Click the + button to create a new Routine Click the + button to choose a 'When This Happens' Click 'Device' In my case, I chose 'J Gar Dr One' (created above) Finishing the 'When This Happens' section is self explanatory In the 'Add Action' section, choose 'Messaging', then 'Send Announcement' Finishing the 'Add Action' section is self explanatory I did one of these for each of the three announcements triggered by the 'JoAnn's Garage Door Is Open program' detailed in my previous post. I also did one for when the door closes. A State Variable is not needed for that one because Alexa 'sees' the sensor directly, in my case 'Joann Door Sensor' (see images in my previous post). One last thing, when testing the program 'JoAnn's Garage Door Is Open', rather than use 20 minutes between actions, I used 45 seconds so I didn't have to wait 40 minutes to see if it all worked together like I hoped, especially the text sent after the second announcement. The reason for 45 seconds is that you have to let Alexa rest at least 30 seconds between announcements or they risk being delayed.