The reaction stopped working (Google Nest max playing a video)

[Fanan]

Hi!
I've have had a mp4 (video) file playing on my Google Nest Max at specific times. A few weeks ago it stopped working. I´ve tried everything but the correct way...
I've changed the boxes above countless times. What is the correct info in each box?
I can do it within Home Assistant, but not in MSR.
My MSR installation is on version 25208-c53e8513, my HA is 2025.9.4.

I´m grateful for any pointers and help.
/Fanan

[toggledbits]

The action you are using is created from data passed from Home Assistant for that service. It looks like they changed the definition of that service since you created the Reaction. When did you upgrade your Home Assistant install, and what revision was running before? It looks like they haven't even yet updated their documentation to coincide with the revised service data, either.

Edit/update:

The fields that have (extension) in the value are Reactor telling you that it has parameter data for the action in this reaction that the action definition now doesn't define. It preserves that data so you can copy it to the correct fields in HA's expected (new) format. Based on what I see in my installation (HA 2025.9.3), it looks like they moved the media_content_... fields into an object supplied by a new media field. Using your preserved data, the media field should now contain:

{ "media_scontent_id": "http://192.../fredag.mp4", "media_content_type": "video" }

Once you make that change, clear out the extension fields and exit the editor, and they will go away (not appear next time you edit this reaction).

That's a pretty nasty breaking change. And I'm still trying to find where HA documented it. So far, no luck. This is why I track HA version numbers and have the UI complain when it sees something unexpected, but in this case, there's so far no telling when this change happened.

They also introduced a new data type in their service definition data for that media field, so I'll make sure the next version of HassController supports it and gives you a more appropriate field size for entering/editing that data.

Edit 2: FOUND IT! It's listed only as "Use media_selector for media_player.play_media" on this pull request, marked as a breaking change, but... not called out as such in their general release notes. My biggest issue with HA has always been the frequency of breaking changes, and like this, that they often miss spelling them out. Sometimes, we're just going to discover these things by accidents like this.

By the way, if you recently upgraded your HA install and something stops working, it's probably a good idea to mention that upgrade in your post.

[Fanan]

@toggledbits Thank you for the hard work!
I can´t get it to work just yet, but maybe it get easier after the next update.
Right now I only get the Runtime error: "[object Object]", no matter what I do. I´ll keep on trying.
/Fanan

[gwp1]

@Fanan Ok, I'm gonna jump in here now. I just added a Switchbot Tilt Blind to my system and it is giving me the same

[object Object]

response when I go to Entities > Perform to test position.set.

Wasn't gonna say anything as @toggledbits is focused on the above items and it seemed a distraction.

I am on HA 2025.9.4 but installed the Switchbot just in the last 48 hours so didn't draw the line between them connecting the dots.

[toggledbits]

Odds are there's something logged. This is why I always say, go look at the log files when something isn't working. When you find it, post with context, don't just post the one or two line error message.

@gwp1 in your case I would also like to see posted the attributes of the new device (using the Copy Attributes button, not a screen shot).

I'll be away all weekend, unfortunately, so this won't get more attention until Monday.

[gwp1]

@toggledbits

cover.state=true
position.step=0.1
position.value=1
x_hass.domain="cover"
x_hass.entity_id="cover.living_room_right_blind"
x_hass.services=["cover","switchbot_cloud"]
x_hass.source="switchbot_cloud"
x_hass.state="open"
x_hass_attr.current_position=100
x_hass_attr.current_tilt_position=100
x_hass_attr.device_class="blind"
x_hass_attr.friendly_name="Living Room Right Blind"
x_hass_attr.supported_features=176

And there's absolutely no rush on this specific item. The blind is opening and closing, just opposite of what I want it to and I'm fighting with learning HA templates to try and achieve this. Switchbot approaches tilting in a unique way.

[toggledbits]

Logs will definitely be your friend right now. If HA is returning an error on a request, the detail of that error is logged, along with the request that was sent to HA and the full response from HA. There are rules for fields that HA doesn't publish in its service data APIs, and that can vary by device and even firmware, so sometimes, you just have to "go low" to figure out how to talk to them.

[CatmanV2]

Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off

Cheers

C