MrBill

I think you're crossing 994 instructions and trying to use it on a Polisy... not the same thing. For your issue I would recommend that that you open a ticket.. email support@universal-devices.com (they do answer on weekends although not as fast on Saturday as any other day.) UDI has amazing support!

that's subjective.... 🤣 The scene method is faster however.

The reason I made the suggestion to switch to control instead of status is because there is a wait in the program. if the program triggers via "control" it will for sure complete the THEN block, if it trips by "status" it can end prematurely if the status changes back before the THEN block is complete due to a wait.

If "control" is available so that this can say "Bedroom / Smoke Bridge-Smoke' is switched On" will probably solve it. Test that and tell me if it works, I'd try it but I don't have a smoke bridge. Also when you test, have the event viewer open on level 3.

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?

should work just fine, make sure the bulb is dimable. The dimming range at 5w may fall short, I have an 8w LED on a 2477D and it's hard to manually dim, works fine when you work out a percentage via ISY and set the on level to that.

Correct. That link should not have been published. The footer of every https://www.insteon.com/ page has a newsletter subscribe block.

oh so it's finally someone else turn to post that..... i've dumped it in a few dozen threads...lol

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.

Probably to be expected since people don't read and August 1st was the 'no longer free' deadline.

@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.

https://forum.insteon.com/

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

That's probably a recipe for going out of business to be honest. It will also anger users that 6 months later get a refund and call it exactly what you said it's not "an interest free loan". I would imagine the priorities are basic switches such as 2477D and 2477S, as well as hubs and PLMs. But those switches once existed in 5 colors each. After that there are pages and pages of old product, some further confused by color options. Do they include every last product? If not, voting by pre-order is skewed because they didn't include all the options. Further if the first wave of products take "months" as Ken has suggested it may be "a year" or even "years" before everything they have planned now to come back comes back. I do think it would be great to have a voting method, I don't think taking orders for product that may never exist is a good method. It's a sure fire way to create a group of unhappy people. "I ordered the product AND PAID but now 12 months later I'm getting a refund"... all the while forgetting there was never a guarantee the product would ever be produced" They do need wide-spread input on what the community wants to buy tho, and so far they really aren't collecting that in a constructive way. That reminds me tho, I was also going to read the insteon forum daily after it came back, but i forgot that self-pledge after just one day!

@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.

I'm sure you have an alternate email address, you might try adding that to their general list (the signup is in the footer of any Insteon.com page). If you find you receive Insteon emails there, but not at your primary address then you have a question you can ask them, your address may have bounced at some point and that address got flagged for no email. I had that happen once when my Microsoft subscription didn't auto renew due to an expired card, for some reason Microsoft rather than email that notice on my primary email they were emailing at the alternate security address only, which I wasn't monitoring. I didn't realize there was a problem until 4 months later when they actually shut off my primary paid email account. This caused all email to bounce for a few days and some email continued to bounce for a week or more for reasons I never figured out. Anyway I tell the whole story because it was hardest to get smarthome.com marketing emails restarted. The bounces got my addressed flagged in the Do Not Send black list, eventually they finally figured out what to do to resolve the problem, but it took several months of emails back and forth to customer service before they finally realized the blacklist which I needed to be removed from.

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.