How odd to have all of my comments and contributions ripped from the original thread/discussion and segrigated here for some reason. Seems strange for me to leave them here, lonely and lacking context and the flow of the original topic and conversation.
Strange as it may seem, Routines use a different version of Rules to the ‘Rules API’.
One of the obvious differences is the type that appears throughout the Routines. This looks completely unnecessary. However one of the quirky things about Routines is that what you see in the Routine editor is (or at least always was) recreated from the JSON of the Rule. My assumption is that the type helped with this process. There is also a metadata section that clearly helps where the Routine is a preset or uses a template.
However even if you get rid of those bits you find that the Rules API is still a subset of what is available to Routines and one of the things that is missing is notifications. I have been bemoaning this for years and eventually lost hope. The only good thing is that Routines handle deleted devices relatively sensibly these days so I can tolerate their existence, even if I don’t like having to use the mobile app to access them (I don’t like the mobile app being the only way of doing anything at all).
I don’t particularly care that the idea that the Rules API would develop to webCoRE level of functionality came to absolutely nothing, and indeed I can’t see how it ever could have done. However, while I never like to assume things are ‘easy’, it doesn’t seem a big ask for the Rules API to at least have feature parity with Routines.
I shall qualify my above comments by reiterating that I abandoned hope for the Rules API a long time ago and so I no longer closely track what is going on.
Audio notifications on a Sonos is precisely what I particularly wanted too.
See above.
Hi, @JKnight
Sorry for the delay, I was checking some details with the engineering team.
I believe the original post was about sending push notifications to users.
And, you’re trying to use the TTS (Text-to-Speech) functionality, in that case, the team mentioned it is a feature available only through the app but we’re wondering why you need to use the API instead, could you provide more details, please?
See above.
See above.
Hi, sorry, I shared your comment with the engineering team but haven’t received a reply so far. In case I have more information, I’ll let you know but currently, this is the expected behavior.
See above.