Athlon

Perhaps I misspoke. When I said iRobot's cloud grabbed control from your ISY - I meant the PG3 Node Server. Assuming your schedule was created using your iRobot app, that's perhaps why the Node server is losing it's connection. I'm wondering if you were to delete all programs in the iRobot app and recreate them in your ISY if the issue you and wmcneil are having would go away. By the way, I have no programs in my iRobot app and never have. I also never lose Node server connection with either of my robots.

Who put it in there? I'm sure it didn't start vacuuming at 1am everyday when you first set it up. The reason I'm asking is if you used the app to create that schedule, then perhaps the iRobot cloud is grabbing control form your ISY once in a while.

I've been watching this thread - I have a Roomba Mop & Vacuum. Is your 'schedule' in your ISY or in your iRobot app?

My portal is working fine.

I'm using the Kasa Node server with great success. It treats my Kasa devices pretty much like they are Insteon devices. I have to believe you should be able to easily use their new $10 smart bulb with no problem at all.

IoP looks just like the ISY you are used to. You use a web browser to connect Node servers you want to add from your Polisy. EDIT: @MrBillPosted at the exact same time ?

Agreed - which is why i suggested he do so.

Wouldn't using Alexa to open your doors be a security risk? (Someone could yell the command from outside?)

I don't have the garage door opener, so someone with more knowledge on those may chime in here. I'm gonna guess you didn't reset anything before installing your new Polisy, so there are likely links in those openers from your old installation still present.

For the buttons (A - D) I like to put them in a 'Scene' and then control the scene. Here's a couple of mine for example: e:

I believe he is saying none of the buttons at the KPL are working and that he must use the app to turn the lights on and off. I thought I'd help to at least get the lights working with the switch and then show him how to program the buttons A to D.

You will likely be asked to furnish these before we can help: Please include Firmware Version (FW) and User Interface (UI) version found in the Help -> About section of Admin Console. Having said that, my 6 button switch looks like this in my AC: Are you moving to your Polisy from a previous installation? If so, did you 'reset' the switch? If not, try that and then add it back using your AC.

I don't want to complicate this, but I run something similar when we are done watching TV for the night. In our family room we way 'Alexa, Turn Off The TV'. It's an Alexa routine that executes two actions: 1) Turns off my TV and associated gear every time. My Harmony Hub takes care of that. 2) Runs the following ISY program for lights and thermostat control: If From Sunset To Sunrise (next day) Then Set 'Fireplace Lights' On Set 'Speaker Lights' Off Set 'Fan' Off Set 'Fan Light' Off Set 'Kasa Controller / Mantle' Off Set 'Kasa Controller / Kitchen Counter Light 1' On Set 'Ecobee - Family Room' to Sleep, Hold Type Hold Next Wait 10 seconds Set 'Ecobee - Living Room' to Sleep, Hold Type Hold Next Wait 10 seconds Set 'Ecobee - Bedroom' to Sleep, Hold Type Hold Next Wait 10 minutes Set 'Fireplace Lights' Off Set 'Kasa Controller / Kitchen Counter Light 1' Off Else Set 'Fan' Off Set 'Speaker Lights' Off Set 'Fireplace Lights' Off Set 'Fan Light' Off Set 'Kasa Controller / Mantle' Off The differences between the 'night' and 'day' actions are: The thermostats are not altered during the day, and the Kitchen Counter Light is not turned on during the day because we don't need it to light the way to the bedroom during the day. The wait 10 seconds to change the thermostat settings was added because they weren't all getting the 'signal' until I added that. The wait 10 minutes on the two lights is there in case we forget to turn them off on the way to the bedroom. You might be able to pull elements (ideas) from this program to do what you are trying to do. Substitute your outside lights where I have my thermostats and/or Kitchen Counter Light.

Guessing here a little, isn't it your programs you want backed up? If so, you should back up your ISY. If you have to 'reconnect' to PG2 coming from a different server (Polisy instead of an RPi), just be sure to put each Node server on the same node. That's what I did and it worked fine. I checked each program that looks at a node, and I had to make very few changes if I recall correctly.

Thank you.

Can you provide a link to the ones you are using? A search for 'zigbee shades' turns up a zillion (well, almost a zillion) responses.

The second link in the second post here will show you how to fix the issue. Did you read that? EDIT: Actually - read the info at both of those links. Before I bought my Policy, I installed PG2 on an RPi and had the same problem until I found those posts.

That's all it does? (I don't have it installed) If so, guess that won't help you on a Policy.

Exactly what we do (a program dims and brightens the lights when turning on/off the AV equipment), except for overriding lighting or drapes - that we do with voice. By the way - you can add Universal Devices / ISYxxx as a device in your 'My Harmony' app.

Rather than 'Status', try 'if Master Bed Light.D is switched On'.

Sounds like I have a similar setup. When I moved to Policy when my ISY was fried by a lightning strike I started using an Alexa device to control the lights in my home theater room - when said lights need to be changed outside of the ISY program I created. So, I still use the Harmony Hub in there (have the Node Server for that). We tell Alexa to 'turn on the TV' (or 'turn off the TV) and it executes an ISY program. Depending on the time of day that program (besides turning on my AV equipment) will adjust the lights and drapes in the room. If we want to 'override' the program, we'll issue a spoken 'turn on the speaker lights' or 'turn on the fan light' for example. At first I missed the hard buttons on my Elite for the lights and fan, but now I no longer do. YMMV.

You 'da Man! Thank you!!

I didn't know that version # bug was a thing. Log PM'd.

Two of my programs are not communicating with IFTTT. It may have started when I upgraded to 3.0.3 on Saturday. Two things I've noticed: 1) When I restart the Node server it says 'Current Version: 3.0.3 [Production]' for about one second, then changes to 'Current Version: 3.0.0 [Production]'. So, right now it's saying 3.0.0 2) This error in the log over and over: 2022-04-18 08:43:53,966 Command udi_interface.node ERROR node:runCmd: command DOFF not defined 2022-04-18 08:48:54,404 Command udi_interface.node ERROR node:runCmd: command DOFF not defined I have 4 programs running in ISY using this node server, 2 of them turn on my A/C units, and 2 of them off (upstairs/downstairs). What's strange is they turn on when they are supposed to, but they no longer turn off. Even when I run the 'Then' part of the program they don't fire the webhook at IFTTT. Also - the history of the 'Turn Off' applets at IFTTT ends on Saturday - right about the time I restarted the node server to do the upgrade. The 'Turn On' applets show activity even today. (I manually turned off the A/C.) By the way, these A/C units are mini-splits (inverters), so I'm trying to use them to augment my oil heat to save on these crazy high oil prices.

Just updated to 3.0.10 - I'm able to add them to programs now. Your Node server has many more options than the Kasa app has! One notable one is it looks like I may be able to set a color by RGB - and that's not in the app for these. I needed that because I've installed two of them and would very much like to match the two color-wise. Awesome work - thanks again! I won't have time to completely test everything until Friday as we leave tomorrow morning for the day, but if you would like me to test anything in particular, just let me know.