paulbates

https://www.theverge.com/23820078/matters-biggest-problem-apple-google-thread-border-router-interoperability This article from this summer gives a detailed description of the state of affairs. UDI is not the bottle neck. They're suffering, like other integrators, from the governing bodies decision to let Apple, Google, Samsung et. al. mutually agree and cooperate on proprietary products & border routers. Going to need to let the dust created from the dust settle😒.

I went back and reviewed the intro thread for system notifications via UDM UDM system notifications work for me and not suggesting removing them from UDM. The question is, is there a way for them to also be provided to the the Notification Plugin? Not a hight priority; but it would be nice to have all notifications in one spot. I can see an "order of events" problem in this request; in that system notifications can't be sent to a plugin that hasn't loaded yet... and which notification plugin to pick when there is more than one iox device.

+1 This is something good to do on your terms, not when the card finally gives up

One more idea.. the common element of the problem is the program - you're sure every thing is good in the program? .. maybe open and resave it

Just to clarify a few things You did "Restore Device" for both, and that ran successfully? A lot gets communicated from the PLM to the devices for that to complete, which suggests the PLM can talk to the devices The eisy PLM is plugged into the same outlet as the ISY? One more thing, easy to try through I'm not sure it works with scenes. I used it at my last house that had problem areas and it helped... adjust the individual device retries: Right click on the device Pick advanced / PLM Communications Bump the Retries up to 2 or 3 and retest

My understanding is you substitute the Group key where you would have used the User Key

My understanding of pushover is that phones are associated with one account. You could put that to the test by going to pushover and trying to add your wife's number to your account to see if that works.... if it does, make a group on pushover with both devices They do offer pushover for teams at a cost which I believe would meet the requirement but seems pricey to me for what it gives for you requirement, Something else to try, a workaround of sorts: Jimbo's plugin defines the User Key and application key for each node.. so you can define similar notifications nodes for each account for the same type notification, and send them back to back in a program.

I believe the program is actually firing when you turn 'Office / OnOff-9.1 On-Off Module' on. The reason you're not seeing any notifications is because your "Then" statements either aren't doing anything, or erroring out. Before writing a program, test the notifications individually to make sure they are working Edit.. to prove this theory right (or wrong) add the following statement in the then Your devices 'Office / OnOff-9.1 On-Off Module' pick "Beep" from the drop down as the action When you turn the device on, it will beep at the device, showing that "Control" is actually working

Based on recent threads, I'm guessing that the notifications are new... have you tested them? What happens if you right-click on the program and select "run then" to force the program to run?

The. I ink for the device direct is different than the links for the scene. I would right click on one of the devices and pick "Restore device" and then retest the scene. This may not be it, but important to eliminate and doesn't take long to do.

If I read the first post right, you should be able to set the on levels for the local switch behaviors (first post) and each/every scene (;ast post) and have those 2 things be different. If there are multiple scenes associated with keypad buttons, you'll have to open each scene and change all of the members, including the second entry on the second graphic - foyerrecessed 1st floor. You can do a lot with variables but my understanding of what you want should be solvable with scenes... just a lot of detail work for every "moving part" in the setup

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?