"Doesn't work" covers a lot of things. Can you give is a specific issue, or is it for ANY new rule?
Seriously!? I am using Chrome, and the website clearly says you can only set automation rules in the app. On my iPhone, I am using the COMCAST app. Tap on automation, tap on the oval button, 'Add a Rule' then some sample rule suggestions come up on the bottom half (top half says 'Good Morning'). Tap on 'arm or disarm security system at a certain time', then those same sample rules now list on the entire screen. Tap on the same bar again, and nothing happens.
Foiden, bonner3988, Lanny_Dietz --
I was able to pull up your accounts & share with engineering so they can troubleshoot. Can you please provide us screenshots of the issue you are experiencing?
I’m having the same problem. I sign out and back in and I can see the rules I set up in the past. If I say I want to add a rule it takes me to a couple of screens to select a template, such as “take a video if motion is detected”. However I cannot choose an action and I cannot move out of thaat screen. I must close the app.
I have seen on other forums where people cannot create rules in Xfinity Home on either IOS or Android devices. I can log in and see my existing rules and can turn them off or delete them but if I tap the button to add a rule I am sent to a page with several options to create new ones but tapping on any of them does nothing and the only way out of the screen is to close the app. And if I want to see my existing rules again I must log out and log back in. Please fix this problem now. I am not able to use the system fully and feel I am not able to get what I am paying for. And add my voice to the many that are demanding that rule management be returned to the desktop access.
dngolden & JimDH --
Thank you both for reaching out. From the details shared by you & other users in this thread, we were about to reproduce this issue on our end. We believe that we have identified the issue & are including a fix in an upcoming release.
Hi all --
We recently made a change on our end that we believe should correct this problem. Can you please let me know if you still continue to experience this issue?