MrBill

Thanks, you see what happens. Your getting people telling you the same things in two threads, and another asking for more information that you've already provided elsewhere. I actually view the fact that the ISY allows the user to manually override light states as a feature. However if you want the outdoor lights to stay on when accidentally manually turned on my suggestion would be different than what's been offered so far. To minimize power line traffic to avoid collisions, i would suggest using 3 programs: NightLights 1 If From Sunset To Surrise (next day) And Status 'Exterior / Lights1' is Off Then Wait 10 seconds Set 'Exterior / Lights 1' 40% Else - No Actions - (To add one, press 'Action') NightLights 2 If From Sunset To Surrise (next day) And Status 'Exterior / Lights2' is Off Then Wait 20 seconds Set 'Exterior / Lights 2' 40% Else - No Actions - (To add one, press 'Action') NightLights 3 If From Sunset To Surrise (next day) And Status 'Exterior / Lights3' is Off Then Wait 30 seconds Set 'Exterior / Lights 3' 40% Else - No Actions - (To add one, press 'Action') .....the waits could also really probably also be 5,10,15 and you'd be fine....

Please don't start multiple threads that crossover. This is a relatively small community, everyone that can help reads all new posts. Creating multiple threads that cross over just create duplication and confusion. It's much easier on all of us to keep all the facts and related discussion in a single thread.

you'll note my lack of responses in these threads.... I do usually try to help new people in detail....

@ISY Newbie has two active threads and as usual when that happens the replies crossover and become convoluted and confused.

Open the Event Viewer... Tools > Diagnostics > Event Viewer. Set it to level 3 then clear it and then make a change. Are you seeing errors or retries? you can also post the output of the event viewer for additional comment if you don't understand it.

This is how, use find with Raw Text. You must be careful tho and provide an exact match... Case counts.

I use less buttons these days than I used to.

I'm surprised that I'd hadn't know of it before yesterday, but it appears documented in a developer link and in use by a number of other Insteon supporting systems. It really isn't of great use to me anymore, I have no more loads to add and for the few things I've converted to Hue moving the wire is no big deal. I'm just surprised that I've never know of this before.

I think it seems to be more of a lesser documented or undocumented feature. (that's the link with the clearest instructions, however I've found it talked about in several other locations as well). I've honestly always wished this existed, and more so now--I've rewired a couple locations for Hue bulbs wanting to be always powered, which in that case really suffices since there's no additional load that needs to be switched at that point.

I was just looking thru Home Assistant core issues on github and ran across an Insteon feature that is apparently possible with 8-button keypads. (Insteon had nothing to do with what I was looking for, this was just the newest issue and had insteon in the title so I read it.) I know we've all wished for a detached load feature before, but I never knew Insteon/Smartlabs actually implemented it. Anyone seen documentation? I'm certain it's likely not implemented within ISY, especially for a 9th button, but it would be interesting if we could just detach the load an leave it turned on. Source (Bolding by me)

@lipdoes the error log have clues? Tools > Error log What firmware version are you using? Does the UI version match? Help > About

I currently send almost every notification via 2 or 3 methods, that's how I know how many get dropped. Lost one just yesterday, the email arrived but the pushover didn't. I use an excel spreadsheet to make concatenated strings like this one: token=<redacated>&user=<redacted>&html=1&message=Tag Trouble:\n<b>${sys.node.n004_f693ed5a5dff50.name}:</b> ${sys.node.n004_f693ed5a5dff50.CLITEMP}\nBattery: ${sys.node.n004_f693ed5a5dff50.CV}\n\nTrouble Code: ${var.2.69}\n1-Temp, 2-No Update, 8-Low Battery\n\n[${sys.date} ${sys.time12}]\n from a data block like this: Node Name Node Addr trbl variable Extra(usb) n004_f693ed5a5dff50 69 Living Room Fireplace n004_1d3698bae66c5e 53 Downstairs Fireplace n004_b40c6d12d303cc 54 Kitchen refrig n004_47a90b787eeef5 57 Kitchen Freezer n004_84e7b435fe8785 59 I can speedily make 12 Network Resources and the reason that I choose to do that this time is because Network Resources are simpler to use in programs with just a single program line. I could do the same type of spreadsheet with nodeserver custom messages, I've just never set up the simplified version. I also save the spreadsheet so if I ever need the body strings again or need to update node addresses it's fairly simple. Since you want to understand how to make the nodeserver better, my suggestion would be have a place for the user to set Custom Message default attribute values for "device", "priority" and whatever other attributes need a default value, so that they do not have to be called out each time they are used. For the majority of the notifications I send I never change those value, however priority is bumped in certain cases and it would be relevant to add an additional preface program line to override the default value to 'high'. On the topic of Notify Nodes and Short Messages, I'm not currently using any of them. I started out with a lot of Notify nodes for wireless tag failures, but rather than just a verb/action message such as "Low Battery" or "not responding", I kinda like the status report variety of notification, as you can see in my example above, that includes data. I also had notify nodes for door openings, but ended up deleting them since I couldn't use them in scenes, they are sent only when the $away variable is set, meaning they all needed individual programs anyway. Notify nodes would work out great for some, but personally I prefer and will stick with Custom Messages. Same thing with short messages I don't have much use for them, even my mailbox notification contains a variable "Mailbox opened {$var.1.22} times today." so that it's easier to figure out if the mail is being delivered or one of us has already gotten it from the box. On a new topic, Pushover introduced Custom Sounds with today's app update. If you made that attribute available in the nodeserver I would definitely make use of it. From the way I understand it https://api.pushover.net/1/sounds.json?token=(your app token) should return a list of the 21 default sound names, plus whatever sound names the user has uploaded as custom sounds. So to Summarize all of the above, my suggestions for making the nodeserver better: Retry send on http fail. default attributes for Custom Messages that can be over-ridden on a per use basis. ability to change the sound attribute, including new custom sounds. Thank you for providing the nodeserver, I realize nodeserver developer is your unpaid side job, I've written this message as feedback since you said you're trying to understand how to make the nodeserver better, and those are my thoughts. I'm also quite certain that I don't always convey my thoughts as thoughtfully as I might like... I might even come across the wrong way from time to time ?, for that I apologize, it's never my intent to sound demanding and/or complaining and I'm positive that I don't always write with the big picture in mind. ?

did you try replacing the SD card? https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card as far as step by step, it depends? what firmware version are you on now? and what do you want to be on V4.x or V5.x? do you have z-wave? Insteon?

I have no idea what the alarm.com controller is, how it works, or how it interfaces to other controllers. The ISY has a strong API however, and with Polisy you can add nodeservers (... yet another reason to use the ISY portal....) to interface with other devices via their API's whether local or cloud.

The original mobilic product family of apps is a one time purchase, adding Mobilinc Connect adds a monthly subscription. The newer "Mobilinc X" is a monthly subscription for both the app and the connectivity service. I have the ISY portal personally and that's what I would recommend. You can use the ISY portal with the original mobilinc's, with the newer Moblinc X there is a fee to unlock being able to use it with the ISY Portal. Personally I've owned and used all the apps made by 3rd parties for the ISY...Mobilinc, eKeypad, Agave, and another that is now defunct. I don't actually care for any of them for one reason or another.... I do fall back and use Mobilinc Pro on rare occasions, but what I actually use now as my ISY remote from the phone is Home Assistant. I like it the best because I can organize as many screens as I want, and ordered the way I want.... Further the Universal-Devices Integration for Home Assistant has a very active developer. Now after pumping it up, I've gotta let some air back out.... 1) there is a learning curve 2) it takes some time to build it like you want it. For me that was worth it-- if you need a turnkey solution tho.... it's not for you. I'm not familiar with alarm.com's protocols, but if you can hit a url based on an event you can control anything you want on the ISY.... if you have that ability from alarm.com I would definitely push you to the ISY Portal instead of Mobilinc Connect.

If you delete it from the ISY and then factory reset, yes it will need to be re-linked as if it was a new device. And there might be a time and place to try that method. If on the other hand you think the switch has just memory has just become corrupt, you can leave it set up in the ISY.... Factory reset the switch, then tell then ISY to restore device which will put the links back in the switch. Another confusion that I think comes up, is that some people don't HOLD the reset until until the long beep stops.

As pointed out there are a lot of possibilities here.... tell us more about what is going on. There is a method to convert 8 button to 6 button and vice versa (the faceplate also gets changed when it's done on purpose, but I've done it by accident once too) Generally factory reset is painless. Don't delete it from the ISY first, just pull the air gap/programming tab out, wait 30 seconds...push in AND HOLD depressed until the long beep stops. Once it's factory reset go back to the admin console and run Restore Device.

there is the ISY Cookbook but then again asking questions to get pointed in the right direction is pretty simple too. The most important things to grasp are how event based IF statements work, and the difference between State and Integer variables. When a state variables value changes it causes programs whose IF statements contain them to be run. When run the entire IF statement is evaluated down to a single True or False. If True the THEN statements are executed, If False the ELSE statements are executed. You must be careful because something like IF STATE_A > 3 AND STATE_B < 99 AND STATE_C = 100 AND TIME IS 3:00PM means that the THEN block will ONLY run at 3pm when all 3 of the other conditions are ALL true. On the other hand if this program has an ELSE statement it will get run anytime A, B, or C changes and at 3pm. the ELSE portion often bites unsuspecting people in the butt.... because the ELSE lines run way more often than they expect them too. Integer variables on the other hand, when used in an IF statement will not cause the program to run, but might be used to change the outcome. For example: IF INTEGER_A > 100 THEN .... ELSE.... will never be triggered. Integer variables don't have the magic property that State variables have that trigger IF statements. An Integer variable could be used in conjunction with something else in an IF statement tho to change the outcome. IF STATE_A > 100 AND INTEGER_C = 5 THEN... ELSE.... in that case anytime STATE_A changes the IF will be evaluated, INTEGER_C can change millions of times and nothing will happen tho. BUT when STATE_A changes the value of INTEGER_C is important because if it's 5 AND STATE_A > 100 then the THEN clause will run, but if STATE_A <= 100 or INTEGER_C is anything but 5 then the ELSE is going to run. In conclusion, a change to a State variables can be used to trigger things happening, Integer variables don't trigger things but instead can change the outcome when the trigger occurred by another event. Confused yet? feel free to ask questions until you understand things....

Yes. In the first program create conditions that will always be true to catch when the values change. I'll use State1, State2, State3 in this example. we also need a temporay integer variable for math. IF State1 > 0 (something always true) or state2 > 0 (also always true) then Integer_temp = State1 Integer_temp -= State2 State3 = Integer_temp --- anytime either state1 or state2 change in value state3 will be computed. in a second program: If State3 > 4 then (increase flow) in the third program If State3 < 2 then (decrease flow) anytime state3 is updated by the first program, programs 2 and 3 will be evaluated.

two possible suggestions: both involve the bottom or OFF light only. take the paddle off by removing the 4 itty bitty screws, either add a piece of tape the the very bottom OFF LED and/or remove the section of the light pipe on the paddle. (the light pipe is two piece, OFF is a separate piece from the others, gripe it with pliers and just pull it out.) Now put the paddle back on.

I think OP's question is about back lights and side LEDs. I agree with @carealtor backlight set to 0 on/0 off turns the backlighting off for 6 and 8 button keypads. Normal switches even 0% leaves the side LEDs very dim for whatever reason. I used to have ridiculously complicated programs that turned off the backlights on 6 button keypads when all buttons were off (It never made sense to me why OFF lit up... The programs were kludgly and created lots of traffic. Ultimately I got rid of such programming and used a dot of gorilla tape to block all the LEDs on 6 button keypad OFF buttons-- this solution has been much more effective than the original programmatic solution.

I see the documentation on the error flag. I had read that before and forgotten it existed because unless I'm missing something it's not that helpful. Let's use a made up example: the Mail arrives which is something I get notified for, I'm at Costco an hour away and won't be home for awhile, the notification fails to send. OK so I have another program in the ISY that detects the notification fails to send, it sends me a notification that the Notification node server failed to send a notification.... Now what? I don't have my laptop to investigate logs... I might poke around in a mobile app and determine there no doors open, or water on the basement floor, then check the wireless tags and see if any of them them are in odd states. There really isn't anyway that I'm aware of to take a Send error and figure which message to try to resend? I assume that you a referencing this portion of a sentence that I made above: Unless there are short cut's that I'm unaware of the documentation says that to send one of the "short messages defined by user" to use a then body like this: Then Set 'Notification Controller' Message Good Morning Set 'Notification Controller / Service Pushover homeisy' Device JimsPhone Set 'Notification Controller / Service Pushover homeisy' Priority Normal Set 'Notification Controller / Service Pushover homeisy' Send Which is my reference to adding 4 program lines above. To send the ISY Network Resource type of message, the documentation says to use a THEN body that looks like this: Then Set 'Notification Controller / Service Pushover WIND' Priority Normal Set 'Notification Controller / Service Pushover WIND' Device JimsPhone Resource 'Test.1' which is my reference to adding 3 program lines to send a message.

I have back up power and failover internet.. I've tried to cover all bases 6 ways to Sunday... the only problem is when the notification times out, nothing retries and there isn't a method to detect failure. most get thru, but enough don't (1 maybe 2 a month) that I send most notifications by more than one method and that seems to mostly solve the problem, its just ridiculous tho to have to get 3 notifications when the better solution is "If not '200 Ok' then queue for retry" but it's not implemented in the system and there is no way to detect failure at the user programming level.

I guess no world is perfect, I have a mix of ISY based NR and also use @Jimbo's Notification Node Server, most of the NR's came before the Notification Node Server, but I actually just created 10 new notifications as ISY NR's because It's easier to add one line to a program than the 3 or 4 it takes with the nodeserver. My biggest problem with all of the above tho is that neither the ISY nor the nodeserver do anything on fail, the message is just lost. It doesn't happen often, but it happens often enough that I'm aware of it but some notifications just vanish. I live in a rural where my only broadband option is brought to us by a gigantic cable company made with love in philadelphia and dropped packets and service drops in my RURAL area are a thing I deal with. I have a dual WAN router with LTE backup. The router notifies me when cable drops and it fails over to LTE, it notifies me when it falls back. If the ISY or the notification nodeserver either one try to fire a notification during the roughly 12 second failover (failback works cleaner) and doesn't get a "200 Ok" back...the notification is just dropped. Further, I just checked the router stats in the last 225 days I've averaged 28 dropped packets a day... most of the time the avg user would never notice a single dropped packet, at the worst they would just reload the page etc. but again when the dropped packet happens and its either the ISY or the notification nodeserver trying to send a notification it just poofs into the netherworld. To build a better mousetrap most of my notifications are sent via multiple methods, usually pushover and email, email is often sent to email and AT&T's SMS gateway because the AT&T is another weak link... the silly part is open the mailbox and I get 3 notifications if none are lost. Pushover isn't immune from occasional DOS attacks either, again it doesn't happen often but it does happen and I was aware they were getting DOS'd at least twice in the several years I've used the service. So the endgame is that I'm just really looking for ways to build more reliance into the system, no system is perfect... but then again when it comes to notifications the weakest link is something that the only thing I can do something about is send the notifications via multiple routes.... which is also why I'm aware of how often failure occurs. I always look for the root cause, from the ISY that hunt usually ends in finding a Timeout in the error log because it doesn't retry. In another forum thread I asked Jimbo if the notification node server retries on fail and he added it to the wish list. Oh and if you think I don't blame the cable giant, I do.... when it starts getting really bad I call and call, I pay for premium service and pay their option inside wiring maintenance even tho the problem is never there. Level 3 tells me my error rates are within tolerance for residential service, so my next question is can I get business service and an SLA? "I'm sorry sir, but that's not available at your address."

There is not. I send important messages by multiple methods at this point. @Jimbo's node server called "Notification" doesn't have it yet, but someday it may retry when on fails. I'm also hoping that UDI Mobile will allow us to send push notifications, including critical notifications, without using a 3rd party service like we must now... no idea if that's in the roadmap tho and @Javi isn't yet taking feature requests, so we must wait and see how that evolves.