-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Siri shortcuts stopped working #34
Comments
BTW, I tried deleting Watt and reinstalling, including having to re-enter all of my spaces (and confirming them in Shortcuts). For whatever reason, one space (Living room, if it matters) now works, but none of the others do. I also tried force-quitting Shortcuts (and Watt), with no effect. |
Hey @dan7769 do you have more than one iPhone or iPad with the same Apple user? Are your devices Kasa Smart or are Tapo? Using the app can you turn on and off all devices from space? (click ▲, then click "space", then slide to "Turn on") |
I have one iPhone and one iPad with the same Apple user. My devices are Kasa. In the Watt app, yes, I can turn those spaces on & off. In the Shortcuts app, no, I cannot. Thanks! |
I think that the error maybe be related to the same Apple User Did you create some shortcuts using the iPad? Or using the iPad the voice requested work? |
I did install Watt on the iPad, but I'm pretty sure I made all of the Shortcuts on the iPhone. I may have made them again on the iPad - I don't remember. I didn't experience any problems until iOS 14. If this is the issue, will deleting Watt on the iPad fix it? |
So my suggestion to you is to open the apple app "Shortcuts" and delete all the shortcuts that are related to Watt. |
Unfortunately, this did not work. |
So now I'm out of ideas of what it could be ¯_(ツ)_/¯ I will leave this issue open to see if anyone else complains about this |
My Siri shortcuts have stopped working. She tells me "something's gone wrong." When I try to do it from the Shortcuts app, it says "There was a problem communicating with the app." Is this a known issue, or unique to me? Using an iPhone 12, iOS 14.6. Thanks!
The text was updated successfully, but these errors were encountered: