No watch configuration available. Open the iOS app and create your configuration in the Companion app settings.
Everything worked fine before the app update
Configuration is directly in Yaml
actions:
- name: Aqara
background_color: "#000000"
label:
text: "Aqara"
color: "#ffffff"
icon:
icon: motion-sensor
color: "#ff0000"
Looks good, but does not work on the watch
Sorry, seems to have been resolved 
Briefly went back to the iPhone, app reported like “Search server” but rather because of location always allow. Then the app opened normally on the phone and it now works on the watch 
Hey guys, thanks so much for the hard work you’re putting into this! 
Allow me to take this opportunity to mention my #1 issue with the iOS App: the fact that it doesn’t support dynamic type. The font is way too small for some people and adhering to what is configured in “Settings > Display & Brightness > Text Size” would be heaven-sent in terms of accessibility! 
The companion apps are literally the only apps on my devices, which are only updating after restart of the device. In every single update on every single device.
So I would like to ask, what is wrong with this app or deployment of updates here?
If I press update, the circle starts to run, most probably it is downloading, but the update is not starting at all. It gets stuck every time on every device on 3/4 of the circle. And even more curious is, that I still can use, shut down the app, etc. Every other up is then already in pause mode. And a prioritize download isn’t working either. And stop update (to restart it) isn’t working either.
Is is only working, if I restart the device and then start the update again.
As said, every update (at least the last 3-4) on every device (several (different) iPhones, iPads, …
2 replies
Correct, confirmation is a feature made for newer item types such as scripts.
Currently there is no way to customize server side your scripts or scenes colors, no decision has been made yet how or if this will be added, for now if you really need this flexibility, stick to iOS Actions.
1 reply
Thanks for the quick answer. Hope to see it in a future release!
First of all, thank you @bgoncal for all your hard work!
I seem to be missing or misunderstanding this. I’ve added the 5 buttons to the Control Center same as in the image in the blog post, but clicking on them doesn’t seem to do anything. The light button turns amber for a fraction, the script and scene buttons turn blue for a second and the open page does open the app
In the companion app settings, watch, and configuration, there is a toggle for show assist. I’ve got this on but I don’t see assist anywhere on the watch.
The actions on the watch do not respect the label color defined in yaml instead they are all white. The background_color and icon color do seem to work.
iOS: 2024.9 HA: 2024.9.2 iOS: 18.0
1 reply
Hey there, so, let’s go one by one:
1 - Make sure you open the App at least once after updating, then when adding a control widget, while in edit mode, you can tap on it to configure and choose script/scene/light etc.
Known issue: Scenes are not activating, I am working on a fix.
2 - Currently Assist is only showing up on watchOS 10+, it’s a beta feature and we are improving it in small steps, but good feedback, I should mention it somewhere.
3 - Can you share your yaml? How does it looks in a home screen widget?
1 reply
iOS Actions is not something we will move forward with in the future, we will keep supporting it but new features will be guided over the usage of scripts instead of iOS Actions.
“iOS Actions” is a concept that only exist in iOS (it’s actually called actions, but since HA services were renamed to actions I have to call iOS Actions 
) so we are aiming to focus our efforts on cross-platform approaches such as scripts which can also be used in Android.
Super buggy right now unfortunately in my experience.
Couldn’t choose an icon for the script, it would load list of icons then t just kept saying “couldn’t load” after scrolling even though app was open in background. It then didn’t let me add a script at all unless the app was opened. I’m used to iOS actions so gonna have to migrate them all soon I guess to keep it up to date.
Thanks for the clarification and for the great work on the app! 
Please this is important
Do permission for not admin user.
Because now if user is not admin he can get all scripts and automation, its not good.
Like CarPlay user not admin can do all on the system.
Please please fixing that issues.
Thanks for your great job
iOS and iPadOS. Different Versions (17.6.1 and below), different devices (Phone 11, 13, 15 and Pad 2021, 2023 and older Pro).
It’s not only a client feature to build.
Thanks for your quick response!
ah now I get it. Now I have an issue that the color of the control doesn’t match the actual state of the light. It seems long tap is causing this inconsistency.
in the screenshot I see it should show in the right top, but I see the time there. But would be good indeed to clarify that.
Three items are defined here: Home-Assistant-Config/packages/ios/zonnescherm.yaml at 0be6486e4e66b9683947b76e8670686ebbb01f8a · golles/Home-Assistant-Config · GitHub
On the widgets, they show correctly (except the extra large one on Mac), on the watch the text color is always white.
Please make the modular widget available for the Modular Ultra so the users of the ultra watches can have home assistant on their home screen as well!
Thanks for this! I like the idea of moving away from iOS actions to scripts. Naturally I tired that but run into a little problem. The customisation of icon colour and background doesn’t want to work. I want brown icon which I select from the menu and black background with white text. I save but the icon reverts to black. Anyone else experience that on apple watch.
1 reply
My PR above will also solve this issue
Forgot that I was listening to music at the same time. 
Ok, it’d be up to the page loaded into the Webview (the HA-Core UI I guess?) to set the appropriate CSS. I did this myself in the past with an app that was also just a Webview and it worked great. Any chance you could pass the message to the appropriate team at Nabu Casa? 
See e.g.: How to support Apple's dynamic type in your web content with CSS - DEV Community
1 reply
I just released in App Store, it should be available in a few moments
Sure, here we go: Support dynamic type on iOS (Web & App)
It’d be awesome if you could forward it
Hello @bgoncal I just installed the update v2024.9.1. It has fixed the problem with the script, great! However, in the control panel, I still can’t operate the assistant; it does nothing when I click on it, but it does work via the widget. Is this already known to you? Thanks in advance for this great update!
1 reply
Did you configure the Assist control? when in edit mode, tap on it to choose your Assist pipeline
When I put a script in the control center, I get an option to enable confirmation. However this doesn’t seem to do anything. I can only see confirmation mentioned in regards to the apple watch news. Is it not supposed to be possible to have confirmation in the regular control center or is it a bug that it’s not working?
1 reply
Those are 2 different things, Apple Watch has a “confirmation required before run”, control center has “confirmation notification after run”
You need to delete the actions itself not only their automations
After watched video that @wgumaa provided. I confirmed it is the same issue I faced. Even re-install the Home Assistant app version 2024.9.1 on my Apple Watch running on watchOS 11 and iPhone 15 pro running on iOS 18 and hit the reset button to start over configure, nothing has been changed. I notice when change the icon or background color to default blue or default green, both of them respect the color change, but when change both of them to default orange or default yellow or custom color, the color is always switched back to black.
1 reply
Yes, coming soon
In my case I use it to tell my parents and partner “hey guys, you have to “allow always” HA permission so automations work well" hahaha because iOS sometimes says “this app has been using your location in background, do you want to allow only during app usage?” and then they tap on it because well… for many apps it makes sense but not for home assistant
1 reply
This update to iOS companion up is really useful. Thank you for all the work done.
There was regression introduced by the latest iOS app update (non-preflight version). There are 2 main issues:
1 - Thats currently the expected behavior, you need to manually create a watch configuration via your iPhone. The first time you open the configuration screen it automatically migrates your actions.
2 - This issue has been fixed and should be released within iOS app v2024.9.2 (In the next week if no major issue shows up in the beta)
Nice, that works. Did not notice HA highjacks homeasisstant://, good to know.
I have a question. @bgoncal you said that the plan is to move away from iOS actions in favour of scripts. Correct?
And I have done so for Apple Watch (aside from the icon colour customisation issue). But HA for CarPlay doesn’t support scripts.
Is there going to be an option to to display scripts in CarPlay the same way we do for watch?
1 reply
Yes, that’s in progress, there will be a CarPlay configuration screen exactly like for watch
Thanks for making this so much easier to use!
I currently use the event ios.action_fired to determine which device triggered the action (using sourceDeviceName) and then send a notification back to the device. Is there a way to do this with the new method of adding scripts directly on Apple Watch instead? It doesn’t look like the script_started event knows which device triggered it.
For context, I’m doing this in order to support sub-menus via notifications. Native sub-menus would be even better of course. But since iOS Actions will eventually be deprecated I’d love to have a solution going forward.
1 reply
Currently it is not possible, but suggestion noted 
Got it, I’ll check whats happening
The new app doesn’t work with Cloudflare tunnel. It says, the browser is not supported for SSO with google.
It worked fine until now.
I think, until now, HA app used the same webview as the browser?
And now, it is different? Like on Android?
(On amdroid I forked the app, to add a request header to all http request as an API key.)
(UPDATE: I added github as authentication method to the Cloudflare Zero Acces, and I could authenticate with that. So maybe, only google auth changed somehow.)
I can’t get my icon color to stay white. Keeps changing back to black.
Here’s another vote for server-side customizations for Apple Watch. My other users will not want to set anything up manually on their side. I’d like to just have them all set the same from the server, so if iOS actions are discontinued, I’m hoping we can still have this capability for scripts and scenes.
First of all, I appreciate your work a lot! The Companion App really is getting better and better! Thank you very much for your effort!
My question is: How can I select the page, which „Open Page“ in the Lock Screen - Widget is supposed to open? I tried pressing long when adding the widget, tried to reload the widgets, but I cannot get it to the right page. I just want to Open my default Dashboard, but the current page being opened is the second dashboard.
Thanks in advance.
As discussed on this GitHub issue, users are having a problem where Apple Watch complications don’t update for several hours, rendering them all but useless. Has there been any progress on this? I have not noticed any improvements with the new version of the companion app.
Everything else is looking great, though!
@bgoncal hey, coming back to the icon colour issue for scripts on Apple Watch. The latest version of the companion app doesn’t even allow you to pick any other colour except black. The picker stays on black and if you choose another colour it still jumps to black. Would you like a screen recording?
1 reply
Having the same issue on my iPhone and iPad. Need to restart the device to complete the update
Im on it, a third party library we use was not making the conversion between hex string to swiftui Color (ironically while I was testing it was doing fine), apologies for that.
I’m not finding the Home Assitant controls in the iOS Control Center, have they been released yet?
1 reply
Are you using iOS 18? Try rebooting your device, they are released already, check if your app is updated as well
iOS 18 installed, HA Companion at 2024.09.02 (even tried with the beta), Device rebooted.
I don’t have the home assistant category in the Control Center screen. Do I need to active anything for third-party controls in iOS? 
Not really 
this is managed by Apple, perhaps it’s a bug in their side, what you can also do is to delete the app, reboot once more, install the app again (no clue if it will work but sometimes this triggers some reset on these parts of the iOS)
Uninstalled / Reinstalled the app, now I can see everything. Thanks!
So, I have only used Apple Watch for activating specific scenes, those have been originally setup as IOS Actions in the app long time ago. It seems that I still need those scenes to be selected/activated in actions view for me to see them in the watch configuration view in the companion app.
Suddenly with 2024.9.3 (2024.894) from TestFlight all those scenes started requiring confirmation before running them without me changing anything.
When I started to investigate, I found the release blog post mentioning the confirmation option and some mentions about it in this comment thread, but no reference to a real documentation anywhere. Also I can’t find the option itself anywhere in the app.
This surely can’t be intentional functionality now? I fully understand the rationale behind adding such an option and it’s an amazing addition, but don’t see why it would be the default for old actions like mine.
2 replies
I used iOS actions to toggle the gate and garage door from my wrist. Obviously I can move these actions to scripts, but I would really prefer to have a selected set of entities available in the watch menu to also see their current state (i.e. if the gate/garage is currently open or closed) prior to sending the action/activating the script.
I am aware that traffic to and from the watch is limited and complications for example are only getting updated every quater hour, but notifications are pushed through aswell, so why not entity state changes for a limited number of entities?
This would also improve the useability of Apple Car Play, where the iOS Action List is the default view, but I rather navigate to the cover sub-page to see the gates actual state.
@bgoncal Hello, I have the issue that when I try to edit something in the dashboard via the Home Assistant app on my iPhone, it refreshes the window on its own. This is not convenient, as I can’t adjust my dashboard on my phone and always have to use my laptop. I have a video of this, but I can’t upload it here?
having the same problem here: Scenes on Apple Watch now always require confirmation and no option visible on watch or in the companion app to deactivate the new behavior.
Hi,
I have noticed, that since IOS18 the location services are not updating reliably. I am using the Nabu Casa cloud and everything was working fine up and until IOS18.
Now my User is staying at home, most of the time. Occasionally, it detects me being not at home, but usually it doesn’t work anymore. I am on the latest Ha 2024.10, but no changes.
Am I the only one being affected ? Any ideas what I can do to fix this?
Thanks
Frank
Same problem (all of a sudden getting asked to confirm running an action) and nothing change (aside from the HA update Wednesday. Also nowhere to disable this confirmation request feature.
Does anyone know how to disable these confirmations? They are quite annoying
2 replies
I had the same issue. Going into ‘Settings > Companion App > Apple Watch - Configuration’ and then deleting and re-adding the items there gave me a ‘require confirmation’ toggle when adding them. The re-added entries have a new “>” option that allows you to view additional settings and change the ‘require confirmation’ toggle after the fact.
Same question. I noticed @submersedravioli remark, but that won’t work for synchronized actions. Would be nice to skip the confirmation for some actions that are not risky/harmful.
1 reply
I have neither risky nor harmful actions. And if they were deemed such, I’d really love to see the documentation stating such so that I could find a solution. Only alternative is to rewrite my all actions to scripts. However, then it seems as if I’d lose context data (about who the invoking user is) and also the name of my script would be the text shown on my watch (ie. giving it an alias is not possible)
Yeah did the trick. thx.
You are working towards replacing iOS Actions with Scripts but you are already breaking a perfectly functioning thing with something that makes sense but doesn’t work.
Releasing the app in a state where Scripts are not actually triggered implies testing is insignificant to non-existant.
With iOS Actions I could just push 15 different actions from the server to 5 different watches but now everyone at home gets to waste an hour customizing buttons and checking if every one of these buttons will actually trigger a script (they don’t). It feels like you are trying to make a sysadmin out of everyone. Most of my family doesn’t care how a button appeared on their watch and what’s under the hood. They just want to press it and open a door. Now they get to navigate annoying menus and accept endless confirmations. Zero people are excited.
Even the title “Getting ready for iOS 18” implies it is not ready. It should be beta. It should not be on my phone/watch if I don’t want to be a beta tester. Let’s not celebrate this achievement yet.
1 reply
I totally agree here. There is no reason for this sort of thing to ONLY be available to configure in the companion app. Even from a data management perspective, I’d much rather configure these things on the server and have them pushed out – that way I don’t have to muck about with reconfiguring each of the entries with the colours I want on each device.
PLEASE retain this functionality in the HA system YAML config (or, if you must, set a separate section in the system config where we can set up these actions).
With that in mind, we need the YAML config to allow us to turn off confirmations.
1 reply