Replies: 2 comments 5 replies
-
Pretty sure you can use an inject node with I hadn't before seen that you needed to create definitions before using them in iOS. So I did a little reading and stumbled upon this.
This then leads me to home-assistant/iOS#1588. From my quick scan of that commit looks like you'll be able to do actionable notifications for iOS without having to define them prior. For now, though you could add another field to the config of the subflow called |
Beta Was this translation helpful? Give feedback.
-
|
Great! RE: unique identifer - I borrowed your code for the tag, so I could just use that. My concern there was that if someone copies this subflow multiple times for the same notification, it'd create a new YAML file for each copy of the flow, and they'd have the same category name - which isn't allowed. But I could put that in the documentation. I'm trying to imagine a flow where I'd want the same actionable notifications but have the actions do different things...but I think I'm overthinking it. It's more likely a user could have many triggers for a notification, but have the actions do the same thing. You can pass in an alternate message into the flow with an environment variable, so that should suffice I think... RE: 2021.5, looks like quite a few changes are coming out. I also just saw an issue close for cancelling iOS notifications, which is HUGE. Previously we could only replace the message with another one. Message 1 - Please close the back patio door |
Beta Was this translation helpful? Give feedback.
-
|
I think I'll table this for now and revisit once 2021.5 drops. I'm super excited about being able to create actionable notifications dynamically - and it should be relatively easy to adjust this flow once the new changes are in place. It'd also simplify the setup and drop the YAML file creation, though that was fun to figure out... :) |
Beta Was this translation helpful? Give feedback.
-
|
Looks like I can join the beta test in testflight. |
Beta Was this translation helpful? Give feedback.
-
|
@zachowj I downloaded the beta, and the new version of my subflow is working great. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, just create a PR for the documentation. You should be able to follow the format of the existing examples. If you need more info just let me know I can try and get a better write-up. If you're a VS Code and docker user, you can clone this repo, and after starting the dev container you can run |
Beta Was this translation helpful? Give feedback.
-
|
Here is my latest gist, @zachowj https://gist.github.com/sstratoti/8021c5a4ee8e34313c3f59ba20c4a83a Still working on the documentation. I just need to come up with some sample use cases. I'll be working on a PR and will try to get it submitted by this weekend. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Using your Android Actionable Notification example in the cookbook, I worked on an iOS version over the weekend.
However, I could use some input on how to optimize it. Since iOS actionable notifications need to exist as YAML in the HA config files before they're called, I need to generate the YAML for the notification and restart HA for them to take effect.
The config is also pretty long. I tried to incorporate as many of the options from the HA-Companion docs that I could find.
Generating the file is done via JSON -> YAML conversion -> write file to disk. Where it writes is configurable, so you could map a folder to your HA-config directory and just drop the YAML files there. However I think it writes each time the node is called. I'm not sure how to get it to "write once" per deploy of node red.
The filename is based off off the category name, so if you were to have multiple of these nodes with the same category, it would just overwrite the yaml file each time. :/ Any ideas for this?
Otherwise my testing last night so far was excellent!
Beta Was this translation helpful? Give feedback.
All reactions