If it doesn’t work in an HA automation, it’s not going to work in NR. By any chance are you using notify to file in the group? Afaik that was the only notification change.
Have you confirmed the names of the individual services in the group hasn’t changed? You can confirm that in developer tools as well. Also test the individual services to narrow down where the problem lies.
I have - both work independently
(it actually doesn’t correctly create the group if they’re wrong - I tried adding notify. to the front of each of them on the off chance and it didn’t create the group)
Doesn’t make a difference tho - perfectly valid. See note above - the group is being created - it exists to select in developer tools. If something doesn’t match it fails to create the group
Thanks - tried that change but no difference sadly
Some further troubleshooting - I’ve reduced the group to a single item… just my phone and it STILL doesn’t send.
However sending to the phone on it’s own does
Hmm - okay. So I think I’ve found the issue - it is actually 2 issues
My phone, the name of the notify entity didn’t match the name of the phone device… so now I’m getting them. No idea how that changed but d’oh
It’s actually pretty weird - my device is AndyPocoX5Pro (removed the name in original post but really doesn’t matter) and even in the dropdowns that are prepopulated that’s what shows.
However, if you check the notify in developer options it drops the “pro” - no idea why… all the sensors from the app still have the pro, just the notify does not
Kinda frustrating actually as now a single naming node needs a separate one for sensors and notifications
My wife’s phone however is all good. They’re appearing in the log but weren’t appearing on the phone… because she’s disabled the general notification categon