MrBill

to get a specific answer you'll need to open a ticket, support@universal-devices.com thing is @bmercier will be the one that has to look, and he was paying attention above but went silent.

I'd try deleting the other device in the amazon website, then add the correct device for the gate in the portal, then say "Alexa, discover devices". It's possible the device has already been deleted from the portal.

In "scenes", click the scene to open to scene details and there is a trashcan in the Upper right (iOS). If that doesn't help try using a computer browser at https://alexa.amazon.com I find it's much easier to delete things there.

Tools > Diagnostics > Event Viewer then in the window that pops up change the "Level" drop-down to "3. Device Communication Events."

Another way to think about it..... "Status" is what the ISY already knows, it's not based on a current event, but the value stored in memory (even if that value just changed to it's current value). "Control" is actual events being listened for and reported to the program as they occur. real-time events.

Yes. You do need a portal subscription however: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Node_Server_Occupancy_V2_%26_UDI_Mobile_app_Instructions Also @Javi will need to confirm if this works with the iOS version, I'm certain it will get added to the iOS version but it actually may not be there yet. If it doesn't there is a version that does, that I've been using for a long time: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Node_Server_Occupancy_%26_Locative_app_Instructions for this one you need a portal subscription and the 3rd party app called Locative. (free version)

With the information you're providing there is no hope in helping you in this forum. Please open a ticket with UDI support. email support@universal-devices.com to get started.

Are you using iOS? (you did post in an iOS thread) I just tried enabling/disabling a program, I had no trouble doing so--it works for me, although it uses a "dialog box" rather than "dropdown", so I wondered if you meant iOS or confused the terminology.

@Javi Just to follow up... whatever was causing my crashes you apparently fixed. You'll remember I never had reproducible steps to fail, but whatever was causing is appears to be gone.

A more secure solution than port forwarding (and more reliable) is to subscribe to the ISY portal... It works out to $1/month--paid intially at $23 for 2 years then renewable per 12 or 24 month. Other benefits it allows interface with Alexa/Google Home and access to polyglot in the cloud. While only a subset of nodeservers (36) are available in the cloud (as opposed to local). As well as a bonus Occupancy portal nodeserver than can be used as a geofence, so the ISY can know who's home. For Clarity: If you subscribe to the portal, no port forwarding is needed. Is your Spectrum external IP route-able? If it's in the range 100.64.0.0 to 100.127.255.255 then it's not. (Also 10.x.y.z but most carriers use 100.x.y.z. for carrier grade NAT). Here's an article that explains public vs private IP addresses.

Hopefully you created a separate gmail account just for the ISY to send from. If 10dig@vtext isn't working, but you can send the same elsewhere then the problem is likely on verizon's side. You can also try number@vzwpix.com which is the MMS gateway as opposed to the SMS gateway. The MMS gateway will still accept just text.... (and I don't know how it is at verizon but at @att it's better to use the MMS gateway).

what error message are you getting?

it's not a bot, but it's definitely a pre-spaming spammer post... that's why I asked one invalid question along with some he probably can't answer ?

That's odd. Which model controller? What software version? Is the node turned on or off? what error message are you getting, it can't be the one shown above, that's something else.

Before I wrote yesterday I scanned the nodeserver list.... I missed Ping (it's not one I use), that's likely exactly what you're looking for.

I'd still put something in the ELSE of the last program in the daisy chain.... In theory you will never see that message, but without it you could in theory miss an event if something weird happen to the user. You could include the ${sys.node.XXXX.YYYY} replacement for the user number just so if you ever do see it, troubleshooting is instantly easier.... The end result of an empty ELSE at the end of the daisy chain of users is that Murphy Law will apply when you desire it least.....

As I recall you have Polisy, you could note that wireless tags aren't updating AND something else isn't updating or some combination and the program could perhaps assume that the internet has disconnected, but maybe that only means Polisy froze up (which doesn't often occur). Maybe tell us more about why or what programs need to disable and there might be a better answer? There's also another route you could take... it's not cheap tho, I use a Ubiquiti Edgemax router with a failover Wan... if the cable internet goes offline it switches over automatically to an LTE modem. I don't have a backup plan for if that connection fails also, but so far it's never happened and if conditions are such that it did we might want to put our head between our knees and prepare to .........

@mangoIf you didn't think of it, I would recommend you create a NR for "user unknown" and fire a notification using it in the last Else at the end of the daisy chain of users. Without it, if for some reason there is not a user match, there is no notification.

Thinking about this more, the double trip likely comes anytime the user number is changing. When the same user that last operated the lock the User isn't changing. If both change you get the double.... Implementing as I suggested above should resolve the problem.

The problem is that both conditions are Status, any status change causes the program IF block to be re-evaluated. The double notification likely comes when one updates before the other, but not when the other updates before the one. One way to solve the issue (Disclaimer, someone else might have a better idea.. I'm flying a bit blind because I don't have any z-wave....or locks...) is to use one program to catch the trigger then send it through a series of DISABLED programs to catch the user.... If 'Front Door / ZW 002 Front Door Lock' Status is Locked Then Run Program 'Door User 10' (If) Else - No Actions - (To add one, press 'Action') ------------------ [Door User 10] Locked Guest - (DISABLED) If 'Front Door / ZW 002 Front Door Lock' User Number is 10 Then Resource '[FrontDoor U10] Locked Guest' Else Run Program 'Door User 11(If) ------------------------------- etc.... so the First program is enabled and it catches the lock or unlock... then just daisy chain together a string of disabled programs to figure out which user it was..... If you're not familiar, a disabled program will still run when called by another program, it however won't run itself based on the conditions in the IF statement changing.

Post your ISY program, click the name in the tree, then right click it and choose copy to clipboard, then paste it into a forum message.

I guess I am missing missing. I should have said:

Just email support@universal-devices.com they will fix you up. I’m pretty sure adding that two years for a polisy is a manual entry. Some users have multiple ISY’s, there would be no way to guess which account should be credited.

Scene editing did change a little bit between v4 and v5, but not substantially (except a ‘copy’ button for scene attributes). I suspect your problem is that you don’t realize there are multiple places to configure the scene attributes. The root level of the scene (when you click the scene name itself on the tree) are the scene attributes when the ISY (admin or program) is the controller. Now click each red controller name, these are the scene attributes when the selected controller is used to activate the scene. Check each controller to ensure the attributes are configured as you expect the scene to operate. This is actually a great advanced feature, scenes can behave differently based on which controller was used. For all off did you also change the button attributes to non-toggle off only?

With @Brian H's comment, the two programs below should work. If 'Fireplace-Sensor' shows up in the 'control' menu, I'd use that rather than Status for the first line of the If. If Status 'Fireplace-Sensor' is On AND Status 'Fireplace-Relay' Off Then Set 'Fireplace-Relay' On Else (nothing) If Status 'Fireplace-Sensor' is On AND Status 'Fireplace-Relay' On Then Set 'Fireplace-Relay' Off Else (nothing)