MrBill

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.

If I'm reading this correctly.... you want to 1) disarm ELK 2) if it's between sunset and sunrise then turn of a specified light. You need two programs to do that. Program 1 IF Elk is disarmed then Run Program 2(if) Program 2 (DISABLED) If Sunset to Sunrise (next day) then Turn on light. Program 2 must be Disabled. A disabled program still run when run from another program. It does not Run just because the IF conditions are satisfied. -- As mentioned the best way to get programing help is to post the starting point. For future reference it's easy to do, Click and then right click the program name in the program tree, select copy to clipboard in the context menu that appeared. In a forum post click the "<>" symbol in the toolbar above a post. In the resulting sub-window click into it then type Ctrl-V to paste the contents on the clipboard.

Instead of manual linking, I'd first try bringing the devices near the ISY and doing the linking and setup there. Then put the devices at their final locations.

Which creates a new question... if your app is too old to display the sidewalk switch is it on by default even tho you can't see it, or if you can't see it does your account just not have it? Also not all devices are capable of creating the 900Mhz mesh network. I have 9 echo devices but only 1 is new enough (Echo Version 3) to participate in sidewalk. Presumably the others don't have the 900Mhz radio for it...

That appears to be the correct path. Is that an older version of the iOS app or the Android app? Asking because the center icon at the bottom changed a few versions ago on iOS, you may need to update your app...

In my app (iOS) it's: More > Settings > Account Settings > Amazon Sidewalk.

@Bspect I just edited my post above, if you've already read then recheck it.

try this: "Pump Failure": If CW Backup Pump Alert-sensor is ON, Run program "Pump Failure 2" (then) Else No Action Pump Failure 2: If (none) then disable program Pump failure wait 2 minutes run program "Pump Failure 3" (if) else (none) "Pump Failure 3": (disabled) If CW Backup Pump Alert-sensor is ON, Then Set 'CW backup Alarm ON (this is lamp link with red warning bulb) Send Notification to Brooke email content 'Cold Circ Pump Failure' Wait 10 minutes Send Notification to Brooke email content 'Cold Circ Pump Failure' enable program Pump failure Else enable program Pump Failure The problem with your version is that a retrigger of the sensor starts the 2 minute wait over again. I may actually be wrong about needing 3 programs, I'm not sure if a program can disable itself, in that case just disable the first program before the wait, but have the last program enable it both at the end of THEN and in the ELSE. Edit: I tested... you will need 3 programs, when a program disables itself it stops running. When a program is disabled, it prevents its IF statement from working automatically. However it can be run by another program. Therefor Program 3 is always disabled. Technically it doesn't matter, because it doesn't have an IF statement, but i would also disable Program 2 always. Program 1 will be disabled by Program 2 to protect the wait, and re-enabled by program 3 in both the THEN and ELSE so that the alarm doesn't end up getting left turned off.

I don't know a lot about z-wave but with Insteon I find that "Status is NOT off" works better for ON than "Status is ON", so that may be it if you followed my example of using IS NOT OFF. You might try dropping the wait and see if it works faster and correctly.

Can you watch the admin console or check the status tab to see if it's running? My guess is 1 second is too fast for zwave, or "control" isn't working with the device. You might try switching the logic to "if Status devicename is not off" and use the same then statement.

I think the switch is toast. Sounds like the memory has failed. A keypad button AFAIK can only be a controller for 1 scene, however it can exist as a responder in another scenes. (For Example All OFF) If you need to turn on two scenes set the keypad button up as a controller for the primary scene. Then create a program If status "load of primary scene" is not Off then set second scene On else set second scene Off

@GeddyYou've got my sentiment exactly. The two reasons I turned off Sidewalk is because it can use a tiny slice of a resource that has a bandwidth cap, and because it doesn't benefit me I have Alexa devices, but no Ring, No Tile, and none of the dog collars that haven't started selling yet. The resource it's using is not unlimited. We never reach our cap today, but I don't need someone else giving away a slice of the pie that I purchased, especially when the network is of no benefit to me.