Sending HASS notifications from MSR
-
Hello anyone,
is there a simple trick to send native HASS notifications from MSR? I guess I could call a scene or something with some parameters but I have little experience so would need some clear pointers on this. Thanks in advance!
@hansw Can you give more info? An example? Do you mean push messages to your phone?
I have all scenes/automations in MSR. Most of my devices comes from HA and Vera, but they are more like radio transmitters (and HA have a nice and useable UI, which I use), and MSR is the brain, where all the good shit happens...
Everything the entities can do in HA, they can do in MSR. So why would anyone in their right senses use anything else? -
Yes I mean HASS native push messages to my iPhone. I would ;ike to stay with MSR for my automation instead of diving into the complexity of HASS automation, templates and blueprints but the notify action of MSR is limited to alert, email, prowl, pushover, syslog, callmebot and telegram. I would like to use the native messages and its different interruption levels
-
Looking into this...
-
Yes I mean HASS native push messages to my iPhone. I would ;ike to stay with MSR for my automation instead of diving into the complexity of HASS automation, templates and blueprints but the notify action of MSR is limited to alert, email, prowl, pushover, syslog, callmebot and telegram. I would like to use the native messages and its different interruption levels
@hansw OK. Latest docker images...
The system entity for your Hass controller will have an action
x_hass_system.call_service. This action lets you call any service. You pass the service data as a JSON string. Here, for example, is how a persistent notification can be sent:
You can call any service, but you have to know what the service data for that service needs to contain, and you have to supply it (in properly formed JSON).
-
@toggledbits holy cow, you are fast! I am going to try this out!
-
@toggledbits, I tried but the hass>system entity is not there. I do have a hass>controller entity but no action to choose from. I am running your container on a qnap though so maybe selecting the latest build had no effect since you didn't rebuild that version? Or I did not manage to update the image in the right way. What I did was stopping the image, creating a new one using the latest-genereric-amd64 build and than starting that new image. It reports: Reactor (Multi-hub) latest-21243-a5028fc
-
@toggledbits And as an addition question on this new feature, is there any way to get for instance the friendly name of the trigger into the parameter section? I have for instance 9 doors which I would like to combine into one rule where, if one of them opens or closes, I get a message which tells me which door was opened/closed. It is not a big deal of course, I could easily have 9 rules but still would be nice also for other situations reporting temperatures and such.
-
@toggledbits, I tried but the hass>system entity is not there. I do have a hass>controller entity but no action to choose from. I am running your container on a qnap though so maybe selecting the latest build had no effect since you didn't rebuild that version? Or I did not manage to update the image in the right way. What I did was stopping the image, creating a new one using the latest-genereric-amd64 build and than starting that new image. It reports: Reactor (Multi-hub) latest-21243-a5028fc
@hansw said in Sending HASS notifications from MSR:
It reports: Reactor (Multi-hub) latest-21243-a5028fc
It should be 21257
@hansw said in Sending HASS notifications from MSR:
is there any way to get for instance the friendly name of the trigger into the parameter section? I have for instance 9 doors which I would like to combine into one rule where, if one of them opens or closes, I get a message which tells me which door was opened/closed.
You can do it, but it's an exercise for the reader. You'll need expressions. The roots of it would be similar to what is described in this post.
-
@hansw said in Sending HASS notifications from MSR:
It reports: Reactor (Multi-hub) latest-21243-a5028fc
It should be 21257
@hansw said in Sending HASS notifications from MSR:
is there any way to get for instance the friendly name of the trigger into the parameter section? I have for instance 9 doors which I would like to combine into one rule where, if one of them opens or closes, I get a message which tells me which door was opened/closed.
You can do it, but it's an exercise for the reader. You'll need expressions. The roots of it would be similar to what is described in this post.
@toggledbits said in Sending HASS notifications from MSR:
It should be 21257
Thanks. It turns out that to upgrade a container on a QNAP you need to delete the old container first, than delete the image (which is locally stored as well) through the image menu and after that you can create a new image which will than all the real latest from the docker hub. Just specifying to get it from docker hub like I did the first time did not work, it used the locally stored image anyway.
-
@toggledbits Well, I have 21257 running now but still no hass>system entity... Only hass>controller. Should I enable something somewhere?
-
Go to the Entities list, clear the filters, then choose "hass" from the controller filter, and
sys_systemfrom the capabilities filter. You should have exactly one entity listed, and that's it.
-
Go to the Entities list, clear the filters, then choose "hass" from the controller filter, and
sys_systemfrom the capabilities filter. You should have exactly one entity listed, and that's it.@toggledbits said in Sending HASS notifications from MSR:
and sys_system from the capabilities
Thanks, that did it!
-
T toggledbits locked this topic on
