This is a bit of a noob question but I just got a notification when opening the app (because I was expecting a notification and didn’t get one!) and saw this:
Breaking Change: TTS and notification commands have new formats, refer to the companion docs for updated format.
But I’m not sure where I can see the companion docs it refers to…
Can someone direct me?
Thanks
Thanks. Does it call out what the specific breaking changes are anywhere (and how to fix them?)
There are tables that list the old parameter and the new one, not all have changed just a few
Ah, so it’s only the TTS (which I assume is text to speech) commands that have changed, the way it read I was concerned all my notifications we’re going to break!
All notification command will/have changed.
Meaning notifications that does something on the phone
Yeah it’s definitely more than TTS, I don’t have any TTS but had to make changes
I’m confused. The only item that seems to have an Old value table is TTS, and I’m not using TTS in any of my commands?
Either way, I think if a breaking change is being introduced it should be top and center with clear details of what has changed, because I’m a bit in the dark right now!!
There is a breaking change and the change is part of the documentations.
What more can be done?
Look at the type of notifications that is listed as beta format that is the format you should use.
If you do not make the changes all you get is the notifications as clear text, so that makes it easy to find them
What more can be done?
As a new user, this is a really really bad experience that things can simply break from one day to the next - I only created my mobile notifications yesterday and I had to learn a lot to do that
Now I’m blind to what has actually changed and how to fix it
Add to that that I’m away from home for the week and the notifications I created were to notify on events away from home and it destroys faith in my smart home system
In the absence of the above I’d really appreciate it if someone could point out what the breaking change is and what I need to change to fix it
The link to the docs are in companion app settings and each settings page has it’s own direct link to the corresponding docs page.
As the change impacted a few different areas it made more sense to keep the changes specific to what had changed. The examples have been updated so you can follow them to see what changed. There is also a note on each impacted section mentioning this. This is why the change log said to check the docs.
Check GitHub PR
Not possible to control Google play store settings like that. You as a user need to disable that on your Android device.
Just look at the updated examples and compare to your own that no longer work.
This is very difficult to test with events that only occur infrequently…
Maybe I’m stupid but I only see one mention of 2022 in the document.
My setup uses node red so the examples are not all that useful (and really only useful if you’re setting something up for the first time even if I wasn’t!)
Without going through every single one of my notifications and manually triggering to test, is there really no way to fix?
I’m still unclear what the fix would be anyway!
Why doesn’t every variable have a table like the TTS one - then at least I could search for a variable to change
All your notifications are actions and they can be tested separately.
We can’t possibly help you if you just keep making such a big deal of it without showing us any of your automations.
Here i one table of changes:
Please see the below table for new parameters to use after updating the Android app to 2022.8+:
Old Parameter New Parameter
channel intent_package_name
group intent_extras
subject intent_type
tag intent_action
title intent_uri
Do you see any other official HA documentation that uses Node Red? No so as a user of Node Red you should be comfortable with converting yaml examples to the format that Node Red uses. A lot of new users jump to Node Red without understanding how things work and they end up getting confused.
Perfect. Where did that come from? Because it isn’t in the linked article above?
From the documentations page.
That was from the notification commands.
But the breaking change might not even be applicable for you if you don’t use any advanced notifications.
One thing I would like to add to this topic is that (it’s too late I understand that) but it would be nice if breaking changes would have a period of time where both formats are accepted.
Especially for those who are on beta versions.
I had the issue that I’m on beta and the other phones are not.
Since I got the change first and is the administrator of HA then I made the changes in the automations and forgot that all the other phones got a breaking change in the other way.
Due to the nature of htis change it was not feasible to support both formats so it was decided to make it a one time breaking change to keep the parameter names in line with everything else. We did have a discussion on this as normally we would support it just like when sensors were split up from their attributes a while back.
This example appears wrong?
automation:
- alias: Command volume level
trigger:
...
action:
- service: notify.mobile_app_<your_device_id_here>
data:
message: "command_volume_level"
title: 20
data:
media_stream: "music_stream"
command: 20
It still uses title?
for others this is correct:
automation:
- alias: Command volume level
trigger:
...
action:
- service: notify.mobile_app_<your_device_id_here>
data:
message: "command_volume_level"
data:
media_stream: "music_stream"
command: 20