Node Red automation broken with Hassio 0.116 update

[jakedawson18]

I’ve got a flow in node red with an event state node that’s triggered when my media player is “playing”. It then flows through to a switch node which was reading the “msg.data.new_state.attributes.media_duration” to extract the media duration attribute. And then based on the length of the media it was triggering different lighting. The switch node created two paths one for >5100 secs the other for <5100 secs i.e a movie length show would have different lighting to a tv show.

This was all working a dream until I updated Hassio and now the node has stopped worked. I’ve used debug nodes and determined that all nodes in the flow are still working except for the switch node where the message becomes blocked.

Does anyone have any ideas of what changed with the update and how I can fix the switch node so it works again?

[bastero (Juan Carlos)]

The following link may be relevant

Breaking Change for Events State Node - Or just me?

After updating either to 116.1 or the NodeRed Addon I just realized that some of my automations dont work anymore. When I checked why, I found that all the messages from event state nodes look different now. While before the data for a new state was i.e.: msg.data.new_state.XXX now it is: msg.data.event.new_state.XXX Was that mentioned somewhere? I don’t remember seeing that change in any changelog. Took me sometime to change it now for all the nodes, and would like to avoid similar trouble…

[jakedawson18]

Thanks for sharing that link. I tried that new code but it didn’t work. Interestingly I just updated to Hassio version 116.2 and now its fixed. Whatever the breaking change was must have been addressed.