paulbates

There are a number of moving parts here. Did you recenlty replace the routers? The router provides the ISY with its IP address which is how it gets out to the portal. It could be as simple as restarting the ISYs Do you have other internet services on the ISYs that are functioning, like notifications? Are you able to access the admin consoles? If you go to the config tab Does the IP config look right vs the subnet the unity's are providing.. the first three octets of the router and iSYs need to match eg 192.168.x, 10.10.1.x, etc Is it set up for DHCP or manual address?... if you have manual addresses, that is likely the problem.. the new routers could be providing a different local subnet and the iSYs can't talk any more. There are other possibilities like firewall but I'd start by looking at those basics

You probably did this but the write up doesn't say... did you power down / power up the policy after updating the static DHCP address for the policy in the router? Typically the router will hold the IP address for X amount of time. Many iot appliances need to be restarted and ask again for their network info.

One thing to think about in simplifying is; which plugin (node server) are you going to use? There are 2 completely separate and unrelated plugins that can send notifications to pushover and you reference and appear to have them both, but using only one in your program sample ..push Notifications plugin - this one is more "Swiss army knife". It's more flexible, but a little more learning curve IMO. Its the one I use Note: when you use the "resource" example in your program, you're not using the notifications plugin.. see my screen shot at the end of your previous thread for how a "notifcations" plugin statement looks Push plugin. This one does pushover specifically. When your program statements say "push" and not "notification", you are using the push plugin Summary, 2 plugins are creating confusion. Pick one and uninstall the other. I'd stay high level now and pick the plugin based on what you want to do With the notifications pluginI can do what i want fairly easily to use pushover Use the pushover "app" feature which lets me put my notifications in folders Operations - simple daily reports, no sound notification, just updates I can review when I want to. When did the dusk sensor work, sump pump cycles, hvac vent cycles beyond normal furnace cycles,.... Warnings - Battery alerts, filter alerts, something like the sump pump operating outside of its normal range. Plugins or devices like thermostat going off line. emergency - water on a floor, sump depth too high substitute ISY variables in my messages so that they are quantitative and meaningful to think about and compare to previous days Here's an example, the pushover folders are on the left, and individual messages in the folders are to the right Maybe you just want to send simple fixed messages. Based on a response I saw to one of your previous threads, someone showed a screen shot of push doing just that. If that's all you want, all you'll ever want, .. push plugin is the way to go, and remove the notifications plugin Or, If you think you'll want more in the future like I describe, and others do much more than I do with the 'notifications' plugin, you'll want to start there

They are two different references to the same eisy: Doesn't matter which one you choose.

At first look you could do most if not all of this with one command using one scene with all devices in that scene: -Set the variables - add all devices to one scene, including the devices that are in other scenes - set specific behaviors for the devices in that scene - remove all of the 'set <device> off' commands with one for that new scene No more 'popcorn' lights, they all go of together

To add to @DennisC's answer, if you use Jimbo's paid Notification plugin, and setup piushover nodes using the Notification Server's pg3 page, yes.. you can have long messages AND variable substitution AND tweak which sounds are used AND priority of the message in pushover

The light in the first post is being set by a scene. Your image shows the switch and what happens when you activate manually & loally. Open the scene and see what the on level for that device is. Change that to 25%. The drop down over the percentage setting will say insteon, then make sure to hit update to write it to the device(s), like the following

This is not exactly what you're asking, but there are other ways to debug Put notifications in key spots in programs to alert you and then remove them once the program is working. I've recently completed several programs and notifications got me around my "bugs" As an alternative to notifications, set a variable, If your program is setting variables this is a good method and also recently used this method. To see these changes, open the event viewer (as opposed to the log) and look for entries something like VAR[ 2 7]... where 2 = state variable, and 7= variable number on the list of variables.

If you plan to bring nothing with you, I would start fresh with a new account on a new eisy and let the old one go after you're sure you're done. Any chance the new buyer will want it? I sold my last house recently and left the ISY and a gmail account that went with the ISY and any iot. They didn't want the portal though

Two different things Use Control instead of Status Test the notification in its own: What happens when you right-click on the program name on the left and pick "Run Then"... does the notification get sent?

Thanks Bob.. that is the case and I agree that its a very low priority

I am really happy with the paid version of the notification plugin.. makes setting up and classifying notifications much easier with pushover vs network resources. When I look at plugin purchases in pg3x, I see the below. In iox I see ecobee in slot 1 and notification in slot 2, that's it & as it should be. The question is why is line 3 there, a second instance that can be reinstalled? Everything's working and maybe this is a "don't worry about it".

I suggest submitting a ticket .. and remove the specific-to-you URLs in the post above. Those should not be out in public

I'm guessing that you're Insteon. If so I'm thinking something happened to the PLM. If I'm right about Insteon: Did you migrate your existing PLM, or buy a new one? If you go to tools/diagnostic/plm info and status, what does it say?

I'm setting up notifications in pushover, and I want all notifications to go there and not UDM. For my own notifications, I know what to do. For PG3 and plugin notifications, I see both places in pg3 to uncheck pg3 and plugin notifications from going to udM, and remove the UDM node. Halfway there I want is to have pg3 and plugin notifications go to a pushover "app" I've set up for UD messages. When I look at program options for "if", I see how to check the notification service For my remaining plugins, like ecobee, I create a message for each one, like below Question: UDM notifications appeared to "bundle" any/all iox, pg3, system and plugin notifications, I saw them come there... is there any iox/pg3/system messaging I'm missing doing it the above way, provided that I correctly write a handler for each of my plugins like above? any special handler need for iox/pg3/system errors/messages, if so how to write the if?

@Jimbo.Automates I bought the notification ns and setup pushover, the pushover apps I want and added them in pg3. I'm ready to add notifications with the new 'devices', per app, that it gave me. I've been through the manual, and want to be sure I'm on the intended path here with the below example I want to send a message to pushover, have it go in my 'house operations' app in pushover. I want it silent in pushover. I should pick 'Send sys custom with params' and content should be a custom notification with variable substitution as I did in the past on my 994 with network resources?

Another option, which I use, is to add a comment where the line should go and either type the line in, or a short reminder of what should be there. This helps me during final 'tweaking' which I'm doing that now on several programs

https://www.java.com/en/download/help/other_jreversions.html

When you run the admin console for the first time it should put a new UD icon on the desktop... that's my recollection

SD cards do not live forever. I had a 994 at my previous house and proactively changed the SD card. I also had gotten automation to a point there where it worked and I hardly logged in or looked at it. You may want to get a replacement card and follow the steps (there was a recent post here on how to)

Have you replaced the 994's micro SD card?

A certificate error indicated you might have virus scanning package on that PC (notion, McAfee, et al) that's blocking Java or the admin console. If true, See if you can disable the scanning/protection for the admin console

What you describe is a recurring problem with replacing SD cards, the detailed steps have to be followed exactly. Review this post, especially the solution

Another suggestion is to consider your insteon network by function and/or room. Start with some simple function like a 3 way switch in a room... Remove the devices from the insteon hub Factory reset them Add them to the polisy Set up programs if necessary Pick another room or function and move at a pace that you can support Another way to say it is Do not attempt an "big bang" conversion Tempting as it is, do not use the admin console function to crawl and discover your existing insteon network.. it's better to proceed at a pace you can manage

The above was the easier way, if it doesn't fix it... remove the device from scenes, delete the device and add it back in. This way likely means some wrench work on any programs it was part of