MrBill

does the program summary time show the program running via "last run time"? Is the ISY a Polisy or 994? it's possible the data/time for last variable update isn't getting updated due to a bug, I'd expect that more from a Polisy than a 994.

if the variable is never getting set to 1, then something else is triggering the node to send message while that message is still set as the message for the node. in other words, the first three lines are setting dropdowns on the node, the 4th is actually sending. If another program just calls send message without changing anything then you get the message for the dropdowns that are already set. One thing you could do to debug this is have this program do one more thing. Perhaps turn on a light. Or perhaps set up a counter using an interger variable and have this program increment the counter as it runs so that you can see if this program is actually being tripped.

paste the exact program, right click the name and pick the bottom item, copy to clipboard then paste it into a forum post. it sounds like you've got it exactly correct already. also how does the variable get set back to 0? and are there any other values used anywhere?

But they won't from AT&T when sent thru the email gateway because segment 1 will be from 1410100173 and segment 2 might be from 1410100179, etc. Just use @mms.att.net.... you'll be happier.

you're using 10digitnumber@txt.att.net change that to 10digitnumber@mms.att.net and it will come thru with the From email address. Another benefit is that txt.att.net will break up long messages longer than 160 character into multiple messages, wheres mms.att.net accepts long messages without truncating them into smaller messages.

i think some of mine are from https://www.flaticon.com the rest are favicons from Ubiquiti, wireless tags etc. Other than Mickey and Goofy but that's another story 🤣 this is true, however i have a very small handfall that the ISY sends with out the notification node server. On is an ISY boot message that's sent both ways ISY -> Pushover direct and thru the Node server -> Pushover... if I don't get both then something is wrong and I need to investigate. Another is I watch the heartbeat of the notification Node server, and if it fails send a message directly from the ISY because the node server is down. hb.NotificationController - [ID 0028][Parent 016D] If 'Node Servers / Notification Controller' is switched On Or 'Node Servers / Notification Controller' is switched Off Then Wait 11 minutes Resource 'ISYnotification.NotificationNS.Missed Heartbeat' Else - No Actions - (To add one, press 'Action')

Nice to know it's been expanded for PG3. I haven't gone there yet....

I'm not certain whether this will trigger once per false value, or whether the query potentially returning a new false would retrigger and immediately cause the buffer to fill and overflow. You might add a wait as the first statement of the Then block just to prevent the queue being filled. Wait 1 min, or even 30 seconds should let some other traffic thru if it's "hammering away".

Here's how I do it. For starters I don't use subject at all with Pushover. Instead using the Pushover website I created multiple "Applications". One for each "type" of notifications I send. This will group the notifications like this in the app: The first two are miscellaneous type messages from ISY and Polisy that don't fit into one of the other categories below. and Home Assistant and Router Status don't even originate from Notification node server. To do this you create multiple Service nodes in the Node server, once service node for each message "type" Then under the Notification Controller Node, you will see each message category listed: now to route messages to each category use a simple /send command such as /send?node=po_wtag on the Network Resource. Again I don't use subject, so nothing to include there. As far as the other parameters such as Sound, priority etc.. I don't set those via the /send command... instead I use the node... remember that after setting a drop-down you MUST press the button to the LEFT of the drop-down. now that those are set, for the message category I also create a program to keep them set that way, which is essentially making them defaults. ServiceNode.wtag - [ID 01CB][Parent 016D] If '{hide}Node Servers / Notification Controller / Service Pushover wtag' Device is not all Or '{hide}Node Servers / Notification Controller / Service Pushover wtag' Priority is not Normal Or '{hide}Node Servers / Notification Controller / Service Pushover wtag' Format is not HTML Or '{hide}Node Servers / Notification Controller / Service Pushover wtag' Sound is not Quack Then Wait 3 seconds Set '{hide}Node Servers / Notification Controller / Service Pushover wtag' Device all Set '{hide}Node Servers / Notification Controller / Service Pushover wtag' Priority Normal Set '{hide}Node Servers / Notification Controller / Service Pushover wtag' Format HTML Set '{hide}Node Servers / Notification Controller / Service Pushover wtag' Sound Quack Else - No Actions - (To add one, press 'Action') So this program says if any of the defaults get changed then wait 3 seconds and change them back. ---- With some of the categories, I actually want to be able to change the sound and/or priority at the time of sending. For with Door Control so I expand the wait to change back to defaults to 30 seconds: ServiceNode.doordc - [ID 01C6][Parent 016D] If '{hide}Node Servers / Notification Controller / Service Pushover doordc' Device is not all Or '{hide}Node Servers / Notification Controller / Service Pushover doordc' Priority is not Normal Or '{hide}Node Servers / Notification Controller / Service Pushover doordc' Format is not HTML Or '{hide}Node Servers / Notification Controller / Service Pushover doordc' Sound is not Door Open Then Wait 30 seconds Set '{hide}Node Servers / Notification Controller / Service Pushover doordc' Device all Set '{hide}Node Servers / Notification Controller / Service Pushover doordc' Priority Normal Set '{hide}Node Servers / Notification Controller / Service Pushover doordc' Format HTML Set '{hide}Node Servers / Notification Controller / Service Pushover doordc' Sound Door Open Else - No Actions - (To add one, press 'Action') //Door Check Tally does do 15 second sound overrides at the end of the cycle. then in the program "Door Check Tally" which is part of the "goodnight" routine Then Set '{hide}Node Servers / Notification Controller / Service Pushover doordc' Sound Magic Wait 2 seconds Resource 'NotificationNS.doordc._TallyZero' Wait 10 seconds Set '{hide}Node Servers / Notification Controller / Service Pushover doordc' Sound Door Open Enable Program 'dc00._trigger.0' Else Run Program 'dc16._tally1' (If) the sound actually changes based on it being a "good" result that we can ignore, or a "bad"result that means we need to physically intervene. So the above program segment changes the sound, sends the notification then changes the sound back. If we failed to change the sound back, the ServiceNode.doordc program would do it at the end of 30 seconds.

@Bill Morrow As @Brian H is explaining the firmware needs to be installed on a fresh MicroSD card. The ISY has a shortened and older version that exists as a default boot-loader to get the machine online. After that the next important step is to download and install the latest firmware, which is Step 3 in the link provided by Brian.

@CPrince this is what I believe you're looking for: If 'DN Back Door Recessed' Responding is False Then Else Created like this:

@Dub aka WHaas Are you using this with Pushover or one of the other options? With Pushover I don't use subject lines, but do have a few unique methods. I haven't moved over to PG3 yet tho, and I know the PG3 has more options that just Pushover.

https://smartenit.com/shop/plm-serial-cable/

At some point I've learned a 3rd party company manages at least some of the mobile carries email to sms gateways. I know for a fact (US) AT&T uses a third party. That came to light a few years when suddenly 168,000's text messages sent on valentines day were suddenly delivered 8 months late. I was surprised when I googled that this occurred 2019, it seems like it was more recent. In the 8 month late text messages, I received some from the ISY. Fortunately I add ${sys.date} ${sys.time12} to the bottom of every notification i send, so I knew immediately they were old messages. I don't send much email to text anymore, certain alarms are sent by multiple paths tho and those do still go by text as well.

Maybe. If his Polisy is includes it. His ISY version is 5.0.16B, which is very old. If his Polisy is old and he's never updated it, PG3 is not running. If running 300 series Z-wave OP should update ISY to 5.0.16C, if not then ISY firmware should update to 5.3.4. We need to know where he is on Polisy before being able to tell him his upgrade status there.

Best Solution is don't use email for notifications. Use Pushover, via pure Network Resources or the Notification Node server. Second best solution is create an email at your ISP or gmail and configure ISY to send FROM that address. Also send your emails TO that same address. Download a separate email client on your phone such as SPARK email and turn on notifications and exempt it from DO Not Disturb, Add the from/to email above to Spark. End result... ISY uses the address to send email TO the same email address ISY is sending FROM. You have a separate mail client on your phone that is allowed to use Push notifications anytime.

I downloaded the Spark mail client on my phone, and created a Comcast address for notification and that address only exists on Spark, this way I could let Spark mail always notify and be exempt from Do Not Disturb hours, and it has distinct sound from regular email on my regular email client.

Sending from the default mail server to a comcast email account the 'test' email will filter to spam. check the spam folder, and a because of this a better way to test is right click a program name that send a notification and choose Run Then.

if you are using the default server for email notifications you might want to shoot an email to support@universal-devices.com I'm sure @Michel Kohanim will see this thread eventually but it may add more hours until he does...

@CopyRon If you have 4 portal accounts that's probably not what you want. If they all appear under one account but you have 4 subscriptions that's different. If all 4 ISY devices were connected to one portal account, then in the top right choose "My Profile" then pick "Use All ISY's on account" in the dropdown.

I believe you can not migrate the licenseby unchecking the box. Then if you have a large number of months left of the old license email support with both UUID numbers and they can manually move the remaining month. Be sure to clearly state which is old UUID and which is NEW UUID.

did you migrate via the portal to a new ISY https://wiki.universal-devices.com/index.php?title=ISY_Portal_Migrate_configurations_to_a_new_ISY

@Bumbershoot I've heard we aren't supposed to use the portal update and i've asked, even recently why the function even exists if we aren't supposed to use it, but the question always goes unanswered.

It's exactly the same process. and yes it's gruesome. I've done one PLM change and my system was much smaller then. The worst of it is that every device needs updating.

this is a cool tool that i use, its similar in principle but it sucks the solder up instead of blowing all over the place randomly https://www.amazon.com/WEmake-WM-SP4-Solder-Sucker-desoldering/dp/B0002KRAAG/