MrBill

I nominate the Kasa Smart plug: https://www.amazon.com/TP-Link-Kasa-Smart-Wifi-Plug/dp/B07RCNB2L3/ (there's also a slightly more expensive model with load sensing built in.) The local API is undocumented, but @Jimbo figured it out and wrote a node server. I'm certain if you're not interested in running the nodeserver that you could in fact peak at his code get what you need to craft a NR, just be sure to reserve IP addresses so they can't jump IP's. Can't beat the price either. I've purchased 12 and finally had enough devices to automate christmas last year.

I started typing one reply then I realized you said the above.... so I googled and found out that they use "IT-36002 QuietCool RF Wireless Control Kit" as the operational controls. Products that might allow you to control the fan via faking the remote controls are the Bond Bridge and the Broadlink RM4 Pro. There is a Bond Bridge node server. I thought there was a Broadlink node server too but I'm not seeing it in the list. Disclaimer: I didn't research the frequency of the "IT-36002 QuietCool RF Wireless Control Kit" and have no idea if it's compatible... I'm just pointing out possibilities.

Try using https://alexa.amazon.com (using your wife credentials) to delete all references again and then let her discover devices again. If that doesn't work I would disconnect the Skill and try the above again, then re-add the skill.

Open a ticket. support@universal-devices.com They are fast to respond although slower on weekends that weekdays.

@LarryCRetired Let me know when you have more questions.

You're absolutely correct, it's not quick and easy. I try to stay on top of it but it seems like later I always find things no longer in use that I forgot to delete. At the beginning of this year I took the time to do a comprehensive ISY cleaning Project. For variables I copied and pasted the list into excel. You can select all rows of the variable screens by clicking the top entry and holding and dragging down. then type Ctrl-c to copy and click into cell A1 of a spreadsheet and paste. Then delete: I deleted all the extra columns value columns because they paste as garbage, then I could resize the rows back to single line. Then i deleted rows where I knew with out looking the variable was still in use. At the end with the remaining row I used Find to search programs for that variable... I ended up deleting like 25 state variables from either not being used or as I went through this process either saying "Hmm, I know better now, I really don't need this variable" or "that really should just be an integer variable". Then rinse and repeat with the other variable type. Network resources I didn't have as nice of luck with making an external list. I ended up making screenshots of the list and actually PRINTING (uggh), then the same method as above, I crossed off the rows that i knew where still in use without looking then used Find > Raw Text to search programs for all or part the name. In the end I had quite a few to delete, I wasn't very good with ongoing maintenance of this list. There is an Export button the the NR page that i hoped to use to Export all and craft a list from whatever it exported.. I never figured out how to make it export anything tho, the file created always seems to be empty.

Follow the directions in the first post of the thread linked below to use the launcher: If you were upgrading from a V4 release to 5.3.0 some of your programs may require manual intervention or fixing. Basically fix the above issue first. make it so that your firmware and UI revisions are the same. then go back to the Programs summary tab and recheck for yellow errors, if you find any look at the program... where you see Green text that's a comment that the upgrader added in place of a programming line that couldn't be automatically updated. Add the missing program line back and resave. You can leave the green text comment or remove it, it doesn't matter.

Effectively you're asking how to make a 3-way switch setup with ISY and Insteon, so that when one switch is turn on the LED indicators on the other follows. This is very easy to do with the ISY. Create a scene, add both Insteon devices as a controller. Boom you should be done. If that's not working for you, Start over, delete the devices and scene from the ISY, then Factory reset both switches (pull out the air gap/programming button, wait 10 seconds, press in and HOLD until the beep stops or ends, then release). Create a scene, add both Insteon devices as a controller. Boom you should be done.

there are 3 ways to compose messages in the notification nodeserver.... 1) Short messages. Link 2) Notify Nodes. Link 3) creating Network Resources on the ISY and sending them to the nodesever. Link. Short messages could be "Good Morning" or any repetitive text. Personally I didn't find much use for them. The notify nodes are good a couple of ways, they can actually be added to a scene and send a message anytime the scene turns on or off. That could be good with a door sensor for example BUT ONLY IF you always want to know when the door opens and closes, for me that doesn't work out because I only want to know if a door opens or closes when another variable = 1 (or true). So then you could use that same notify node in a program, and set the messages and fire it from the program. The method I use most often is 3) which is alot like i used to do it when i was using Pushover strictly from Network Resources. It's a little easier to create the Network resources needed for the nodesever tho. without the nodesever the strings you need are a bit complicated and unforgiving... with the node server there's less formating required. This is also the method that can be used to send data... such as variables or temperatures. Because you can include any of the substitutions. Most of my notifications are this type "Kitchen Refrigerator 36.2F" or "Kitchen Freezer Low battery 2.56V" I also like adding a timestamp to my messages even tho I don't really need to but I just want to know especially back when i was using Text messages so most of my notifications end in "[${sys.time12} ${sys.date}]" on it's own line so i know when the notification left the ISY and how long it took to get to me. I did warn you this was probably one of the more complicated nodeservers to get going.... but if you understand wireless tags (and I know you do) you've got the ability for sure. BTW... I'm a little bit younger than you but not too much...

Do you mean you upgraded the firmware via the portal? Like this.... That probably updates to 5.3.0 since that's the official release.... I wish that tool didn't exist, people seem to have problems with it.....

@Michel Kohanim Just noting... the Locative version of the portal node server does work, and please don't get rid of it.

I do see where @Jimbo states in the requirements that > 2.2.6 I have no idea tho what won't work correctly because you're using 2.2.3. I also have no idea what's wrong after you upgrade where it won't save your ISY's credentials. When it comes to how polyglot works under the hood, I really have no idea.

I was going off the fact that OP says Vera sends commands to the ISY. Later on he also says Vera doesn't speak to Insteaon.

try it on one first and make sure it works like you expect.

That sounds very likely. (disclaimer: I know nothing about Vera, but if I was was turning on a scene then the other switches should be responding also.) you could try this program as a workaround: If Status switch1 is not off then set hallway scene on else set hallway scene off

You should have a pre-formed blocks to save everything, you won't need the custom block like your screenshot shows. The place that you put your User Key and Application Key looks like this: For the name blank you can use anything. I used the numbers out of my street address, another idea for name is "Pushover" or anything up to 8 characters that you want to type. If you don't see those fields look for the "Add Pushover Service Nodes" and click that area and see if it expands. All the prefilled block appear after you get the "I understand and agree" blank filled in an saved. Also I can't help with the fact that Polyglot isn't saving your ISY credentials, I'm using a Polisy and you have a Pi. Only thing I can suggest is have you tried restarting the Pi? I think that fixed it for me once when I had that problem with the Polisy. Anyone else have any suggestions for @LarryCRetired and his Polyglot not saving the ISY credentials?

OP doesn't have Pro....

I'm not going to lie, it's a little complicated getting this going, but once you do you'll have more or less instant notifications. Here's the big steps that should prevent much of the confusion. Set up an account on pushover.net first on your computer. download the app on your phone and sign into the same account. Now go back to the Pushover.net on the computer. On the page that shows "Your User Key" on the top right corner scroll down to the section titled "Your Applications", click the link that says "(Create an Application/API Token)" Type a name, "ISY" would be a good choice, No Description needed or you could just type ISY again, No URL needed, check the box at the bottom, then click the Create Application button. Now when your logged into https://pushover.net/ on the computer you'll always see the USER key on the top right corner of that page, you can get to your application key by scrolling down to the bottom and clicking on "ISY" which will be in the "Your applications" section. You need both during nodeserver setup. Note it's best to copy and paste those values into the nodeserver. When you click into the field on the pushover.net webpage it will assume your about to copy the value and select the whole thing for you, type Ctrl-c to copy it, then in the node server click into the empty field and press Ctrl-v to paste it. The node server readme file is here and there are also on-screen configuration instructions for help setting it up the first time. If you run into trouble or have a question just post again... once you get it going I'm pretty sure you'll be very happy. It is one of the more complicated nodeservers to set up tho.

You're not the first to complain about vtext lately. (I can't say I have AT&T which also gets bad from time to time). What makes email to text bad, is the spammers that flood the gateways with spam. The solution is to move away from SMS as your means of notification. I can't remember if you have Polisy (or Pi running polyglot), but if you do look at using Jimbo's "Notification" nodeserver instead. It uses the service called Pushover. Pushover is a one-time 4.99 fee for the app and no per message charges. If you don't have Polisy, there is a cloud nodeserver called Push that also works with Pushover. I've tried both nodeservers and would recommend Jimbo's Notification over the cloud Push choice).

@Brian R., As @larryllix mentions Pro vs standard is a feature level update, primary Pro has more node capacity, more program capacity, and the added two buttons on the toolbar allowing you to turn off writes (one button for battery devices, one button for non-battery devices), being able to do so makes setting up programs faster. Your programs are likely using a feature called "adjust scene" which is causing the extra writes to be queued for battery devices, this was a bug in firmware prior to 5.3.2. What you should do now is upgrade to v5.3.3 firmware, it's the latest and greatest and very stable. The upgrade process will likely take you less than 10 minutes. The 5.3.3 firmware is located here. (yes 5.3.3 is labeled as a "test build". However it's been out since March 8th and is stable without any issues. The actual most current official release is 5.3.0, but don't use that one because it still has the bug you're fighting now.) After you've upgraded you will need to get the queued device writes written out to the module. Find the modules with the little green 1101 icon, then put that module in set or program mode by pushing its button then right click the name of the device and pick "writes changes to device". Then move on to the next one and do they same thing. As you get towards the end the process will get much faster. When you've gotten rid of all of them you'll be back to a speedy process overall again. Pro vs Standard is a different upgrade. You have to pay for that one. If you're interested in the admin console go to Help > Purchase Modules. (you don't need it tho, if

Both of mine upgraded successfully... I did have to do the step 2 upgrade. ?? Many thanks to all the make it work awesomely!

You're looking for this button on the toolbar: It normally the last button (on the right end). It does only exist in the "pro" version Also, please tell us what firmware version you are using (Help > About). Firmware v5.x had a longstanding bug that was finally fixed in v5.3.2 that caused battery device writes to be queued when programs executed "adjust scene". If this is your issue the solution is to update your firmware to v5.3.3 and then work through the device writes by waking up each device with the set/programming button and letting the currently queued writes to occur. If that isn't your issue then we need to figure out why you have so many queued battery device writes.

Nobody seems to do it, but you can build custom dashboards. Search the wiki for HAD. (Home Automation Dashboard).

agree with, you must be using the launcher... it does require internet. as @gzahar points out admin.jnlp is available anytime from the ISY itself, but people struggle more with it than the launcher, so most of the time the launcher is the better choice.

as @hart2hart indicates the scenes live as links in the devices (and the plm). I just want to add that creating scene in the ISY is the equivalent of manual linking. If you want to test the theory... after everything is linked and working just unplug the PLM and retest.