Jump to content

Notifications


beninsteon

Recommended Posts

Posted

The ISY itself does not currently have the ability to send notifications to a device unless you create a program to email or text msg. I have plans to create a system for this, but it may be a while before it is ready.

Does agave support notifications from the isy yet? I'd like a notification on my phone if, for example, a variable becomes a certain number.


Sent from my Pixel 3 using Tapatalk

Posted

It’s perhaps worth noting for others that may read this (and I don’t use Agave yet so please excuse my interruption here) but the ISY can send text messages and emails. You can set a unique notification sound in iOS for any messages received from the email associated with / sent by the ISY (so get a text and hear a specific sound notification). Others use a service called pushover for iOS that creates the pop up alerts on an iPhone. Not sure about Android although I suspect there may be a few options there for alerts.


Sent from my iPhone using Tapatalk

Posted

Thanks.

I am using email for certain notifications but I find the delay to be a limiting factor.

Text notifications (with xxx@sms.rogers.com) are a pain with my service provider who blocks these by default and receiving a message requires actually accepting it each time.

I've been meaning to look into pushover for android...

Posted
Thanks.
I am using email for certain notifications but I find the delay to be a limiting factor.
Text notifications (with xxx@sms.rogers.com) are a pain with my service provider who blocks these by default and receiving a message requires actually accepting it each time.
I've been meaning to look into pushover for android...


I second using Pushover (been using it for quite a while now, after testing most other options out there). I put together this wiki page to describe them.. https://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Mobile_Notification
Posted

I've been using Pushbullet for a few years for notifications from the ISY. I got tired of having to change 80+ network resources whenever my API token is invalidated, as well as the limitations of the ISY network resources. So, I've been working on a message relay service, running on an RPi.

Sample network resource:

{"title":"<< AwayHome : ${var.2.13} >> mode",
"body":"<<AwayHome:${var.2.13}>> mode active. Garage is <<OpenClosed:${var.2.24}>>",
"importance":"info"} 

No more authentication headers in network resources. Don't need several network resources for readable notifications anymore. Eventually, I will add the option to configure other notification services (SMS, email, …), for fallback and recipient preference.

Posted
On 1/29/2019 at 10:31 AM, Jimbo said:

I started working on a simple Polyglot nodeserver for this as well, just haven't had the spare time to complete it.

Let me know if you need a beta tester!

Posted
1 hour ago, beninsteon said:

Let me know if you need a beta tester!

So how I was thinking this would work.

- In the polyglot config you will be able to set:
  - pushover user & app keys
  - simple phrases you want to send with title & message

- The main controller node would allow selecting one of those simple phrases

- There will be a node for each service, like pushover, and in that node you select it's options, like Importance, sound, device, ...
  - with a "Send" button to send the current selected phrase from the main controller

It will also have a simple REST server where you can send it the service, message and title for passing custom messages.

This way configuring a bunch of common phrases is simple, and sending those from ISY programs is easy.  But if you want more info and device status or variables then the using a network resource is necessary.  My main reason for the simple phrases is for sending things to assistant-relay to speak, which will be another service. :)  Also, the REST server will accept http GET and POST since NR POSTS allow you to format the body a lot easier.  I'm assuming I can make that work.

Does that make sense, or does anyone have any better ideas?

Posted

I got all of that working using NRs. Substitution rules for tokens can be configured in a service configuration file and also per request. 

I am considering exposing the message relay service as a node server, but Polyglot is Python (AFAIK), which is a turn-off for me (it's been a while). I don't know if there is a binding for JS/Node. If I remember correctly, ISY and node servers communicate over a web socket, so conceptually there shouldn't be any technical hurdle. I'm am busy, so a node server would take a while...

Posted

Polyglot-V2 is Node.JS and communicates with nodeservers via mqtt. Most nodeservers are written in Python, but there is a template to create them directly in node and someone did one, I can't remember who now, but there were a few issues....  I have all that working as well in a standalone script, but moving to polyglot will allow setting most configuration in nodes, then just pushing the message in an NR instead of all settings being in the NR like priority, devices, ...  And I want to support assistant-relay so the ISY can speak thru Google Home's.  Also, moving to polyglot handles the distribution and updates instead of users manually doing.

I still would prefer @Michel Kohanim just add pushover to the standard notifications!  But last time I asked he wasn't interested, if I remember correctly.

Also, if you are good at Node, we (meaning @einstein.42) could use help with Polyglot development!

 

Posted

I really like the ideas here.  I little different then the approach I am attempting with Agave, but good to see some attempts.  I don't understands the in/outs of the polyglot system so I am not sure how a NS will be able to monitor the ISY for device updates?  Can someone explain this to me.

Posted
I really like the ideas here.  I little different then the approach I am attempting with Agave, but good to see some attempts.  I don't understands the in/outs of the polyglot system so I am not sure how a NS will be able to monitor the ISY for device updates?  Can someone explain this to me.
I wasn't planning on monitoring the ISY, I could by running pyISY like my Hue emulator nodeserver does, but building the rules would be the more difficult part. This will allow programs and network resources to send notifications from the ISY.

Sent from my Pixel 3 XL using Tapatalk

Posted

Ok. I understand know.

I wasn't planning on monitoring the ISY, I could by running pyISY like my Hue emulator nodeserver does, but building the rules would be the more difficult part. This will allow programs and network resources to send notifications from the ISY.

Sent from my Pixel 3 XL using Tapatalk



Sent from my Pixel 3 using Tapatalk

Posted

Before I get too far on my little project I'd like to get a few opinions.  See attached video.  

Notice Agave does not need to be running.  The messaging is all handled on a remote server.   I have not added a way to create the rules yet,  the rules I used in the video are just manually created on the server for testing. 

But the gist is this:  <Device> <Condition> <value>

11 22 33 1 > 10%

Conditions are [ > , < , >= , <= , == , != , ANY ]

Posted
On 2/1/2019 at 7:55 PM, Jimbo said:

So how I was thinking this would work.

Thanks Jimbo. Your description sounds good, but complicated and still relies on another service (pushover)....thus when that service starts charging or goes down these notifications won't work.

It seems to me like this ISY portal which we all subscribe to anyways would be a good place to integrate this. I wonder what @Michel Kohanim thoughts are.

@James Peterson your agave service also looks great. Let me know when it's ready for mass consumption. I would also be happy to be a beta tester here. I'm looking for notifications on variables (leak sensor tripped, fire alarm on, garage door left open, etc).

Ben

Posted
8 minutes ago, beninsteon said:

Thanks Jimbo. Your description sounds good, but complicated and still relies on another service (pushover)....thus when that service starts charging or goes down these notifications won't work.

It seems to me like this ISY portal which we all subscribe to anyways would be a good place to integrate this. I wonder what @Michel Kohanim thoughts are.

@James Peterson your agave service also looks great. Let me know when it's ready for mass consumption. I would also be happy to be a beta tester here. I'm looking for notifications on variables (leak sensor tripped, fire alarm on, garage door left open, etc).

Ben

Those were my original thoughts as well.  I have spoken with Michel about this and from what I got, it is not something they want to pursue.  for one) the ISY portal is not subscribed to the your ISY at all times, just when you are connected and this defeats the purpose.   

Posted
17 minutes ago, James Peterson said:

Those were my original thoughts as well.  I have spoken with Michel about this and from what I got, it is not something they want to pursue.  for one) the ISY portal is not subscribed to the your ISY at all times, just when you are connected and this defeats the purpose.   

Is there a way to use Polyglot, Polyglot Cloud and Nodelink  with your new Mobilinc Connect ?

Posted
47 minutes ago, James Peterson said:

for one) the ISY portal is not subscribed to the your ISY at all times

Interesting. I don't see why the portal would have to monitor/subscribe to the ISY in this case. The user can identify certain variabels/states they want monitored then the ISY notifies the portal when that occurs. Tthe portal can send a notification to an app ...

B

Posted

All, need more clarification and requirements as my conversations with James are not entirely related. Just for clarity, all ISY Portal accounts that have links to Echo and Google Home do subscribe to ISY at all times and keep the subscription open.

With kind regards,

Michel

Posted

@Michel Kohanim, thanks so much for coming into the fore here!

I think the functionality we're discussing is notifications from the ISY to a mobile phone (via an app).

This is currently being done with email and third party solutions but there are shortcomings here. For example with pushover having to make many complicated network resources and having to redo them when api key changes for whatever reason. Relying on another third party interface also is not fantastic if for example services gets shut down. Email is problematic because even "push" email can be slow when phones are dozed.

A (relatively) simple ISY phone app that can receive notifications from the ISY portal for certain device/variable states would be a very welcome feature, I think, for a lot of users. I know there are probably many things on UDI's plate so understand if this is not a priority, but perhaps it can be discussed & added to roadmap.

Sincerely,

Ben

Posted
3 hours ago, beninsteon said:

Thanks Jimbo. Your description sounds good, but complicated and still relies on another service (pushover)....thus when that service starts charging or goes down these notifications won't work.

It seems to me like this ISY portal which we all subscribe to anyways would be a good place to integrate this. I wonder what @Michel Kohanim thoughts are.

@James Peterson your agave service also looks great. Let me know when it's ready for mass consumption. I would also be happy to be a beta tester here. I'm looking for notifications on variables (leak sensor tripped, fire alarm on, garage door left open, etc).

Ben

Yes, that's been peoples reason for years now, but once you purchase the app you get 7500 messages for free a month for each 'app', it's been working great for many years.  It uses the Google Messaging service FCM which does have a cost, so they could start charging at some point.  I think @James Peterson is planning to use FCM as well, but would be best to include that as part of the portal and allow ISY to send FCM messages directly and Agave could receive them.  Everything will rely on a service that supports push messaging so it doesn't kill your devices battery.

 

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...