actionable-notifications-subflow-for-ios
actionable-notifications-subflow-for-ios copied to clipboard
sstratoti
clear_notification not working externaly
Hello,
i have an issue, i use your subflow sometimes to only send an notification without any action. when i do that i want clear the notification after an x amount of time.
when i call the clear_notification with an automation, it doesnt delete the notification at my iphone. i set the tag message in your subflow to the tag i use in the data of the automation
when i use your subflow with an action and i select clear notification at action recieved it work as expected. so it only doesnt work when i send clear_notification externaly. could it be possible that the tag option in your subflow is not working correctly?
data: message: clear_notification data: tag: Oven
sorry for my bad english and thanks in advance.
Hi! I've noticed an issue with clearing notifications as well, but I thought it only had to do with clearing "critical" notifications.
I'll need to experiment with this a bit.
- Is your subflow updated to the latest version from this repo?
- What version of iOS and the App are you using?
Thanks!
Updated to the last version, but stil nog working. I have the lateste ios app version.
When i tag the message send bij the subflow it doesnt work, maybe there is the problem i can not check if the message really gets taged with the tag "oven"
then i fire the automation below and the notification doesnt get removed from my phone.
When i fire the below notification i can remove it with the above automation.
https://companion.home-assistant.io/docs/notifications/notifications-basic#clearing
Platform limitations may require the companion app to have been recently used to clear the notification: this applies for all iOS notifications, and any Android notifications not marked as critical.
Perhaps its that you haven't opened the app recently?
Hi @bjornmorsman - is this issue still present?
I'm about to push up a new version of this subflow. Wondering if you could give it a try and report back?
Hi @sstratoti
i installed the update via import and then checked the replace box. When i test the subflow i get the next message:
31-8-2024, 07:31:26node: Send Notifications msg : error "ValidationError: "service" is not allowed to be empty"
did i do something wrong?
Edit: if i install v0.0.3 the same way i as i installed v0.0.4 everything works again.
Ah - Did you update HA to 2024.8? This is the fix for them renaming services -> actions.
@sstratoti This isn't because of HA 2024.8, it's because of the nodered companion. They misinterpreted the change from using service calls in home assistant (lovelace and automations). The HA rest API still uses the term "service" and this wasn't a part of the change. NR Companion didn't have to enforce such a breaking change. But They did...
Ah - Did you update HA to 2024.8? This is the fix for them renaming services -> actions.
Yes i have 2024.8.3, so that shouldnt be the problem.
@okets what do you mean by that? Do i need to wait for an update of NR companion?
Thanks, I need coffee. I'll adjust my release notes. I don't see a way to check the version of a palette.
@bjornmorsman - at least v0.66.0, released 2024-08-16 https://github.com/zachowj/node-red-contrib-home-assistant-websocket/releases/tag/v0.66.0
I meant that in order to reproduce the bug, he had to update the NodeRed Companion, it wasn't HA 2024.8 that caused it.
Can you use .66 without upgrading Home Assistant to 2024.8? I see the service -> actions announcement in this latest release, but is that when it first came available?
Thanks guys, after updating the pallettes of node red your update seems to work🥳
Great, let me know if the issue seems resolved?
I still suspect that the subflow isn't doing anything wrong, I think it's the companion app behavior that is producing this issue. But maybe they've fixed it since you reported this issue?
I will check this week if de bug still exists, i will let you know if ik works. Thanks for the update btw and keep up the great work!