https://wiki.universal-devices.com/UD_Mobile#Network_Resources_Setup

Is there another way to call out for eISY?

Edited Friday at 02:04 PM2 days by awysocki

Just skimming over that it looks like it is referring to using it for push notifications through the portal.

Edit I just noticed this is in the notification section of the forum and I assume they want you to use the notification plugin. Are you trying to send from eisy get a notification from somewhere else through the Mobil app?

Edited Friday at 02:23 PM2 days by tazman

@Javi @bmercier

Could we get some clarification on the use of Network Resources for notifications?

Is this just for adding notifications through UD Mobile?

Does this have anything to do with eisy-ui?

If so, what is the recommended method for adding notifications?

If it is recommended not to use Network Resources for notifications, then what should we continue to use them for, and what does the future of Network Resources look like?

That is the example they use, I use it to send data to my DB server for history. Just a simple post of some data points I want to record on my local lan.

Beside my use of the Network Resource method I described above. It sounds like they are reigning in Notifications to only their paid service, Where you have to buy the notification plug in and only get some phone notifications with UD Mobile unless you have the plug-in. There are a few other services like PushOver, NTFY.SH that give you notifications to your phone along with history and other options. But eISY is removing those other options, other than the ones they chose.

I only got UD Mobile notification to work, and it works, but I can't run it on my desktop (Windows, Apple, Linus) to get notifications, where those other apps do have desktop versions along with your phone. I was not able to get PushOver working consistently using the notification plugin/node server ($15) to work

My wish list is to have from within a program Dynamic msg text ie: => SEND MSG ("This is is my message => light $light.name is $light.status") . Along with a UD Mobile desktop version. (the $ are variables and not valid in eISY just that they are variables of some sort)

Nothing changed, the API exists for all portal users. It is simply difficult to use Network Resources and causes too many support tickets, so deprecated only in support.

Network resources also has a disadvantage from plugins when using variables. Plugins get the variable as it was when the program was triggered. Network resources query a variable which may have changed since the trigger

Jim's plugin was not created by universal. He was the first developer to make a Great Notification Plugin. It has many advantages over Network Resources, like retry and error logging. Network resources is fire and forget.

Anyone can create their own Notifications plugin. I have one for testing APIs.

In short, you can spend a day of your time recreating the proverbial wheel or tip jim once for making things easier.

34 minutes ago, awysocki said:

I was not able to get PushOver working consistently using the notification plugin/node server ($15) to work

I can confirm that the Notification Plugin works great with Pushover on all UD devices. I currently have both running on two eisy's without issues.

Describe the difficulty you are having in detail and any errors you see in the Notification Debug Log page and let's see if we can get you running without issues. You might need to post a screenshot of your configuration page (depending on exactly what your issue is), but redact any sensitive information first.

Your other option is to download a complete log package, with debug enabled and send it to the author of the Plugin.

On 10/24/2026 at 6:34 AM, DennisC said:

I can confirm that the Notification Plugin works great with Pushover on all UD devices. I currently have both running on two eisy's without issues.

Thanks, but I closed my PushOver account. it was just spotty for me on UD and for my TeslaFi account. Just seemed like I would only get a portion of the messages. I may just make my own notification server for UD Mobile and ntfy, like @Javi i suggested. being a very very very old HTTP server coder I understand headers so happy that Network Resourses are sticking around.

Thanks

Edited 18 hours ago18 hr by awysocki

10 minutes ago, awysocki said:

Thanks, but I closed my PushOver account. it was just spotty for me on UD and for my TeslaFi account. Just seemed like I would only get a portion of the messages. I may just make my own notification server for UD Mobile and ntfy, like @Javi i suggested. being a very very very old HTTP server coder I understand headers so happy that Network Resourses are sticking around.

Thanks

I still recommend Jim's Plugin, unless you just want to own your own creation. Before AI, I estimated it would take me 1-2 weeks to create the same with all of the redundancy (retires/loops/group lookups/non-indexed group stabilization) . With AI, it would likely take a day maybe 2 when accounting for bug fixes plus ~$30 in credits. Much more expensive in both time and money than the ready made solution.

On 10/24/2026 at 9:31 AM, Javi said:

Nothing changed, the API exists for all portal users. It is simply difficult to use Network Resources and causes too many support tickets, so deprecated only in support.

Network resources also has a disadvantage from plugins when using variables. Plugins get the variable as it was when the program was triggered. Network resources query a variable which may have changed since the trigger

Jim's plugin was not created by universal. He was the first developer to make a Great Notification Plugin. It has many advantages over Network Resources, like retry and error logging. Network resources is fire and forget.

Anyone can create their own Notifications plugin. I have one for testing APIs.

In short, you can spend a day of your time recreating the proverbial wheel or tip jim once for making things easier.

Just to confirm...Network Resources will continue to be available on EISY-UI, but technical support will no longer address Network Resource tickets?

I use Network Resources to communicate with a GlobalCache IP2IR device, not for notifications as described above. I use Jim's Plugin for message notification.

This topic is specifically for The notification API. All support tickets are referred to the Notification Plugin.

Network Resources are included in eisy-ui but are, and have always been, self managed. The issue with the notification API and the deprecated concern, is that our wiki shows the method as deprecated only to be used with 994, as 994 doesn't support plugins. This is only in the context of the notification API