![]() ![]() In any case, it's a lot more convenient than hitting allow on the screen. Perhaps the crown is interpreted as "allow" rather than "cancel" in this context, or perhaps it's a bug. I was then surprised when the shortcut ran anyway. When trying to run the original shortcut that used Home Assistant actions, one time instead of hitting allow I just pressed the crown to dismiss the dialog quickly. However, I may have discovered another workaround of sorts. (How about the one I asked you to run? The one you asked permission to run?) Actually, it's worse now, since after hitting allow my watch then asked which shortcut I'd like to run. I converted a shortcut from Home Assistant actions to the REST API, but now instead of asking for permission to access Home Assistant, my watch just asks permission to access my HA server's domain name. ![]() This workaround appears to no longer work as of iOS 16.2 / watchOS 9.2. The only workaround I have found is to do an HTTP POST request using the native shortcuts action There are a few threads on reddit and mac forums of others having the same issues on other apps. Running the shortcut on the phone works fine without any prompting except for the first time. The shortcut should be initiated without a prompt it asks to "allow" or "don't allow" but selecting "allow" does not prevent the prompt next time.Ĭreate a shortcut that calls a script (or service) and attempt to use siri to launch the shortcut from the watch IOS device model, version and app versionĪfter the ios 15 update every time i try to initiate a shortcut that interacts with home assistant from my watch i am prompted "Allow " to access "(null)"?".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |