Aeotec Minimote Stopped working - 47.1 SOLVED

My minimote had been working under the previous Z-Wave setup with the following action:

- alias: "Minimote Button 1 Radio 2"
  trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
      object_id: minimote_23
      scene_id: 1
  action:
    service: script.turn_on
    entity_id: script.play_all_speakers
    data:
      variables:
        what: 'hls-radio://a.files.bbci.co.uk/media/live/manifesto/audio/simulcast/hls/uk/sbr_high/llnw/bbc_radio_two.m3u8'

I have updated all my Z-Wave object id’s as per the blog and everything is working apart from the minimote. The only thing I have changed is the name so it now looks like this:

- alias: "Minimote Button 1 Radio 2"
  trigger:
    platform: event
    event_type: zwave.scene_activated
    event_data:
      object_id: aeon_minimote_dr
      scene_id: 1
  action:
    service: script.turn_on
    entity_id: script.play_all_speakers
    data:
      variables:
        what: 'hls-radio://a.files.bbci.co.uk/media/live/manifesto/audio/simulcast/hls/uk/sbr_high/llnw/bbc_radio_two.m3u8'

But for some reason, the action doesn’t work. I have tried changing the action to a pushover notification which also failed to trigger so I know it is not the Sonos part.

My Z-Wave log captures:

Info, Node023, Received Scene Activation set from node 23: scene id=1 now. Sending event notification.
Detail, Node023, Notification: SceneEvent

So it looks like it is detecting the button press ok.

I have not renamed entities or looked into this heavily yet - but updated mine to 47.1 as well and now my minimote doesn’t work either - OZW log looks like it’s getting events - will investigate, but wanted to note I’m having the same issue.

1 Like

You now need to be using the entity_id rather than object_id. So, replace:

  object_id: minimote_23

with

  entity_id: zwave.minimote_23

The HA logs (not OZW_Log) do report that object_id is deprecated, and it was mentioned in the release notes. It’s always worth reading the release notes for any notes tagged breaking change (I was bit by this too, until I re-read the release notes).

2 Likes

Thanks! I had a feeling it was something like this but had not had time to dig. I did note the deprecation errors in the log when HASS starts, but have not had the time to fix. Appreciate the help - will see if I can get this fixed soon!

Again, thank you.

I love the pace that Homeassistant is developing but so many release notes to read :smile:

All working now.