Glad to see that the update fixed the issue.
Very strange as none of my HA notifications are going to my apple watch now. I think it is related to upgrading to 2204.5.1 but I donât know for sure. I have rebooted both the watch and iphone and still my notifications from HA are not working. So frustrating.
I think the problem is in spaces in the phone name. Try renaming to something without spaces (Settings > General > About > Name). Either replace spaces with underscores, or just simply - use your name alone.
1 Like
Well⌠i guess iâm an outlier, but, how can I disable these annoying confirmation alerts that pop up now?
This topic is not about âAre you sure you want to run âŚ?â automatic confirmation that was added to the iOS actions recently.
Itâs about intentionally sending notification with confirmation to an iOS client.
@n6ham is right, but: You should just be able to turn off âRequire confirmationâ in the companion app watch settings. Itâs mentioned here.
But that doesnât work for me! @dmgd, if it also doesnât work for you, I would recommend you file an issue here.
Thereâs no such option in iOS companion app Actions (which are pending deprecation). Itâs only available for the Scripts. But when you trigger a script from the watch - thereâs no DeviceID to send confirmation to.
Did you find a work around for the custom confirmation via script?
Iâm not sure what you mean by finding a work around. Iâve sort of abandoned the approach in my blueprint, given the pending deprecation of actions. Iâm not using the blueprint any more.
Iâm just saying that for scripts in the new Watch version, turning off ârequiring confirmationâ doesnât seem to do anything. Running a script with it off still prompts a confirmation request.
Oh, interesting. I added a script with Require confirmation off and the script is triggered immediately as soon as I tap it on a watch.
What I meant by workaround is to find a way to identify which device called a script, to send a notification with a custom action to that device.
It used to work (and still does) with actions, since I have sourceDeviceId there, but not in the script. It seems like thereâs no way to know what device is calling a script.
To mate it clearer - hereâs my use case.
I have a âGarage Doorâ iOS action which is triggering an automation on a server side.
The automation checks the garage door state, and sends a notification with a custom action button back to the device that triggered the automation. If the door is closed - notification contains button âOpenâ. If itâs already open - âCloseâ.
Then automation waits for the action confirmation from the triggering device. Basically, it allowed me to get the garage door state and open/close it, or just check the state without any action.
I didnât use your blueprint, but rather its idea of sending notification with a custom action button back to the caller. This worked beautifully until I tried to migrate to a script, which lacks the caller device id
I see the âRequire Confirmationâ switch for scripts and scenes, but not for iOS Actions. I have about 10 actions set up in configuration.yaml so they populate on two iPhones, carplay, ipads, macbooks etc. I have trouble using scenes with my Daikin Aircon, when i set a scene for a certain temp, other paramaters like fan speed, mode etc will be set randomly and inconsistently, iOS actions (automations really) are reliable.
I havenât looked into scripts before, i assume theres probably a way to run an automation from there and then I can set the ârequire confirmationâ toggle to âoffâ.
Thanks for your help!
I think you should look into replacing your actions with scripts. Scripts are very simple! Should be easier to set up than scenes, actions, and automations.