johnmsch

Will do Teken. At this point, I'd be very surprised (and flummoxed) it the switch is then recognized by the ISY994i. Not sure how to check the warranty though. With all the Insteon switches I have, I don't know how to trace back when I purchased this particular one.

I removed the bulbs and started the console. Still get the error. I tried a query and see the progress bar, but nothing else happens. Then tried to restore the device, but again, nothing appears to happen. Then removed the device and tried to re-add it. That gave the error: New Device Errors The following devices could not be added: xx.yy.zz Cannot determine Insteon Engine Oh well, I have an order coming tomorrow in fact, with 6 new switches and another 8 button keypad. I'll replace this switch with one of the new ones. Thanks, as always, for all the quick replies!!!!

Hope I'm not being dense here, but isn't the device restore done from the Admin Console, which still can't communicate with the switch? There are actually 4 bulbs on this switch. I'll unscrew them and try again. BTW, just took off the coverplate for that switch, and the switch itself is pretty hot. I know these switches run a little warm, but don't remember ever feeling one that was as hot as this one.

For the reset, I pulled out the set button and waited about 15 seconds. Then pushed it in all the way and held it. Within a second or two, it beeped twice. I kept holding it in for about 10 seconds, but it didn't make any more beeps. I then released it and it still works the same (manually works fine, but ISY994i still has the error). By "removing the load", I assume you mean to disconnect the red wire?

I have an older Insteon 2466SW On/Off switch v5.05 that the ISY Admin console can no longer communicate with. When I start the console, it throws the error "Cannot Communicate With ... Please check connections." This has been working fine for a few years and I haven't made any changes to my electrical wiring/switches in at least 6-7 months. The switch itself looks fine and works manually. When its off, the LED is on, and when its on, the LED is off and all the lights it controls come on. I tried the factory reset procedure and also turned off the breaker that switch is on for about a minute. Can't think of anything else to try. Has this switch just gone bad?

Ok, looks like going to 5.x is the easiest way. Is v5 still in Beta? I usually keep fairly current with the firmware, but it looks like 4.5.4 is the most recent release. BTW apostolakisl, very impressive code in your programs. Having spent 40+ years in development, I do appreciate all the effort you put into that!

I'm looking for a way to save the boot time of the ISY to a variable. I have a couple of push/email notifications that when sent, I'd like to add a line with the timestamp of the last time the ISY booted. I'm running v4.5.4. Thanks for any tips/ideas.

Thanks guys. Looks like I'm getting a new toy.

Very cool. Thanks for the info. I've been wanting to play with a RPi, so now I have a good excuse. Would you be so kind as to explain what a "wc8" is?

Actually found some posts that got me started down the right path. Will update everyone once this is done.

Ouch. Sounds like there's not going to be some straightforward way to do this.

Got a new wrinkle to this issue. Last night we had some brief heavy storms/winds that rolled through and knocked down a bunch of trees, which took some power/cable/phone lines with them. The power is not a problem, as I have a backup generator that restores full power within a few seconds. However, it took hours for the cable (Comcast) to be restored. That prevented me from getting the ISY reboot notification, as my internet connectivity was down. Is there some way to get the ISY to check to see if it has an internet connection before attempting to send the message? The only thing I can think of right now would be some way to ping a site, such as Google and check to see if it got a response. This would have to be in a loop, or something that would execute every minute or two until successful, then send the notification. Any ideas would be appreciated.

Got this all setup and ran a test. Works like a charm. Just one nitpick. The message should say "The following is the uptime hours the ISY had been operating before ${sys.time} reboot: ${var.1.330} Hours." Technically, when the ISY reboots, its been operating 0 hours since the reboot. The variable will hold the number of hours before (i.e. previous to) the reboot. Also, how the heck do you have at least 330 variables? Wow!!!

Thanks again Teken. That's just the info I needed. larryllix - That gives me something to look forward to whenever I decide to upgrade to a 5.x release.

Got it. Thanks. Couple more questions please. For the Time Check program, how does sending that notification confirm the NTP sync was successful? I'm assuming your "GMX" notification is an email? Would you mind sharing the contents of your 'ISY - Clock Check' and 'ISY - Uptime Counter' notifications? Just wondering how they were setup. Always love learning new things about the ISY and the tips/tricks I learn here.

Thanks Teken/Xathros! That's pretty slick. While I will add that program, I'm still back to my original question. How to get it to run at startup? I see in the example above "[Run At Startup]", but I can't see where that would be declared. No doubt I'm missing something obvious...

I'd like to setup a notification whenever my ISY994i boots, like after a power failure. I'm assuming I can create a program that will activate at boot time, but just can't figure out what the "If" statement should be checking for. Thanks

Ah, ok, I see what you're saying. I just never saw the need to do any purging in the NC, since the latest stuff is always at the top and it auto purges after 7 days. I did file a support request with Pushover to ask that they at least give us the option to keep notifications in the NC.

Just wondering what you guys mean by clearing out the notifications in the Notification Center. At least on my iPhone 6s, it only keeps the past 7 days worth of notifications. Anything older than that is automatically purged. Also, and please understand I'm not intentionally being dense here, but I don't understand the statement "Notifications usually disappear when you read them in the originating app (like email)". I'm not aware of any other apps that perform that way, especially email. Are you referring to the email client on the iPhone? If so, my emails do not disappear once they are flagged as having been read. Just to provide a screenshot and explanation of what I'm talking about: Keeping all notifications in the Notification Center is especially important to me when I'm messing around with ISY programs/settings/devices. I like to be able to see the sequence of events as they happen. Whenever I make any changes in the ISY, I like having this log (even though its in reverse-chronological order) of things that are/were happening just to be sure I have everything setup the way I want. I really appreciate all the replies. I guess it just comes down to a personal preference, but as I said before, none of the other notifications I get (in this case, specifically the Arlo and MobiLinc) are deleted from the Notification Center. I'm really struggling to understand why only Pushover would do that.

Hey Paul, I'm not following what you're saying. I too have unique sounds for certain notifications and get new events normally. Don't see what that has to do with the iOS notification center.

Been using Pushover for about a week now, and its working fine, except for (what I consider) to be a big flaw. When I get a push notification to my iPhone, I can then go to the Notification Center (swipe down from most any screen) and see it in reverse chronological order with all the other notifications from other apps. However, if you open up the Pushover app, it then erases all it's notifications from the Notification Center! I posted this compliant on their support forum (https://www.reddit.com/r/pushover/comments/4yjadz/ios_notifications_disappear/?sort=old). Someone who appears to be a developer for Pushover said this is intentional. BTW, never seen any company use reddit as a support forum. According to him, this is by design. I just can't understand what their reasoning is behind that decision. Is it just me, or does anyone else using Pushover find this annoying? The whole purpose of the Notification Center is to keep a few days worth of history of notifications. Why would any app purposely remove them?

Thanks Paul/Michael. I was aware of the Wiki page with all the built-in variables that can be used, but as you can see from my example scenario in post #20, that's not what I was looking for. Is there somewhere I can promote the idea of string variables in the ISY to the folks at UD? I would really love to see that feature!

Thanks so much guys. This forum is an absolute gold mine of information. Michael - could you please expand on what you mean by substitutions, or point me to some documentation? Hopefully, the following is a better explanation of what I'm looking for... Let's say that I want a push message whenever a few lights come on. Call them Barn, Shed and Outhouse. For each of these, I have to go to the Admin Console -> Configuration tab -> Networking tab -> Network Resources tab and create a resource for each one. The first one will have the hardcoded message "Barn light is on". I then make a copy of that one and change the message to "Shed light is on", then another copy and change the message to "Outhouse light (and exhaust fan) is on". I then create 3 programs, one for each of the lights, and use the corresponding resource to get the push message when that particular light switch is turned on. It would be nice if I could just create one resource, and in the message use something like a string variable such as %MessageString%. Then, from each one of those 3 programs, I somehow set that variable to the appropriate message I want pushed, or pass it like a command line parameter when I call the resource. This way, you actually could have just one resource defined and use it by multiple programs/scenes.

Ok, all setup and the first test push went fine. Can someone please post an example of where you are calling the Push notification from an ISY program? Also, do we have to "hardcode" each push message? In other words, can we setup a generic push, and in the program that calls it, pass it the message to send, or does each message have to be specifically defined in Network Resources?

Nevermind. Finally figured it out.