Remotec ZRC-90 Scene Master 8 button remote (zwave-js)

Hello,
I am trying to do the same on Zwave.
The automation is triggerred but the button does not do anything.
Do you spot any issue ?

blueprint:
  name: Remotec ZRC-90 Blueprint
  description: Create an automation for the Remotec ZRC-90 8 button remote using ZWAVE
  domain: automation
  input:
     remote:
      name: Remotec ZRC-90
      description: The Remotec ZRC-90 to interact with.
      selector:
        entity:
          integration: zwave
    button_1_1:
      name: Press Button One 1x
      description: Action to run on button press once.
      default: []
      selector:
        action: {}
    button_1_2:
      name: Press Button One 2x
      description: Action to run on button press twice.
      default: []
      selector:
        action: {}
    button_1_held:
      name: Hold Button One
      description: Action to run on button hold.
      default: []
      selector:
        action: {}
    button_2_1:
      name: Press Button Two 1x
      description: Action to run on button press once.
      default: []
      selector:
        action: {}
    button_2_2:
      name: Press Button Two 2x
      description: Action to run on button press twice.
      default: []
      selector:
        action: {}
    button_2_held:
      name: Hold Button Two
      description: Action to run on button hold.
      default: []
      selector:
        action: {}
    button_3_1:
      name: Press Button Three 1x
      description: Action to run on button press once.
      default: []
      selector:
        action: {}
    button_3_2:
      name: Press Button Three 2x
      description: Action to run on button press twice.
      default: []
      selector:
        action: {}
    button_3_held:
      name: Hold Button Three
      description: Action to run on button hold.
      default: []
      selector:
        action: {}
    button_4_1:
      name: Press Button Four 1x
      description: Action to run on button press once.
      default: []
      selector:
        action: {}
    button_4_2:
      name: Press Button Four 2x
      description: Action to run on button press twice.
      default: []
      selector:
        action: {}
    button_4_held:
      name: Hold Button Four
      description: Action to run on button hold.
      default: []
      selector:
        action: {}
    button_5_1:
      name: Press Button Five 1x
      description: Action to run on button press once.
      default: []
      selector:
        action: {}
    button_5_2:
      name: Press Button Five 2x
      description: Action to run on button press twice.
      default: []
      selector:
        action: {}
    button_5_held:
      name: Hold Button Five
      description: Action to run on button hold.
      default: []
      selector:
        action: {}
    button_6_1:
      name: Press Button Six 1x
      description: Action to run on button press once.
      default: []
      selector:
        action: {}
    button_6_2:
      name: Press Button Six 2x
      description: Action to run on button press twice.
      default: []
      selector:
        action: {}
    button_6_held:
      name: Hold Button Six
      description: Action to run on button hold.
      default: []
      selector:
        action: {}
    button_7_1:
      name: Press Button Seven 1x
      description: Action to run on button press once.
      default: []
      selector:
        action: {}
    button_7_2:
      name: Press Button Seven 2x
      description: Action to run on button press twice.
      default: []
      selector:
        action: {}
    button_7_held:
      name: Hold Button Seven
      description: Action to run on button hold.
      default: []
      selector:
        action: {}
    button_8_1:
      name: Press Button Eight 1x
      description: Action to run on button press once.
      default: []
      selector:
        action: {}
    button_8_2:
      name: Press Button Eight 2x
      description: Action to run on button press twice.
      default: []
      selector:
        action: {}
    button_8_held:
      name: Hold Button Eight
      description: Action to run on button hold.
      default: []
      selector:
        action: {}
  source_url: https://www.home-assistant.io/docs/z-wave/device-specific/
mode: single
max_exceeded: silent
trigger:
  platform: event
  event_type: zwave.scene_activated
  event_data:
    entity_id: !input 'remote'
action:
- variables:
    scene_id: '{{ trigger.event.data.scene_id }}'
    scene_value_id: '{{ trigger.event.data.scene_data }}'
- choose:
  - conditions: '{{ scene_id == ''1'' and scene_value_id == ''0'' }}'
    sequence: !input 'button_1_1'
  - conditions: '{{ scene_id == ''1'' and scene_value_id == ''3'' }}'
    sequence: !input 'button_1_2'
  - conditions: '{{ scene_id == ''1'' and scene_value_id == ''1'' }}'
    sequence: !input 'button_1_held'
  - conditions: '{{ scene_id == ''2'' and scene_value_id == ''0'' }}'
    sequence: !input 'button_2_1'
  - conditions: '{{ scene_id == ''2'' and scene_value_id == ''3'' }}'
    sequence: !input 'button_2_2'
  - conditions: '{{ scene_id == ''2'' and scene_value_id == ''1'' }}'
    sequence: !input 'button_2_held'
  - conditions: '{{ scene_id == ''3'' and scene_value_id == ''9'' }}'
    sequence: !input 'button_3_1'
  - conditions: '{{ scene_id == ''3'' and scene_value_id == ''3'' }}'
    sequence: !input 'button_3_2'
  - conditions: '{{ scene_id == ''3'' and scene_value_id == ''1'' }}'
    sequence: !input 'button_3_held'
  - conditions: '{{ scene_id == ''4'' and scene_value_id == ''0'' }}'
    sequence: !input 'button_4_1'
  - conditions: '{{ scene_id == ''4'' and scene_value_id == ''3'' }}'
    sequence: !input 'button_4_2'
  - conditions: '{{ scene_id == ''4'' and scene_value_id == ''1'' }}'
    sequence: !input 'button_4_held'
  - conditions: '{{ scene_id == ''5'' and scene_value_id == ''0'' }}'
    sequence: !input 'button_5_1'
  - conditions: '{{ scene_id == ''5'' and scene_value_id == ''3'' }}'
    sequence: !input 'button_5_2'
  - conditions: '{{ scene_id == ''5'' and scene_value_id == ''1'' }}'
    sequence: !input 'button_5_held'
  - conditions: '{{ scene_id == ''6'' and scene_value_id == ''0'' }}'
    sequence: !input 'button_6_1'
  - conditions: '{{ scene_id == ''6'' and scene_value_id == ''3'' }}'
    sequence: !input 'button_6_2'
  - conditions: '{{ scene_id == ''6'' and scene_value_id == ''1'' }}'
    sequence: !input 'button_6_held'
  - conditions: '{{ scene_id == ''7'' and scene_value_id == ''0'' }}'
    sequence: !input 'button_7_1'
  - conditions: '{{ scene_id == ''7'' and scene_value_id == ''3'' }}'
    sequence: !input 'button_7_2'
  - conditions: '{{ scene_id == ''7'' and scene_value_id == ''1'' }}'
    sequence: !input 'button_7_held'
  - conditions: '{{ scene_id == ''8'' and scene_value_id == ''0'' }}'
    sequence: !input 'button_8_1'
  - conditions: '{{ scene_id == ''8'' and scene_value_id == ''3'' }}'
    sequence: !input 'button_8_2'
  - conditions: '{{ scene_id == ''8'' and scene_value_id == ''1'' }}'
    sequence: !input 'button_8_held'

{
    "event_type": "zwave.scene_activated",
    "data": {
        "entity_id": "zwave.living_remote",
        "node_id": 25,
        "scene_id": 5,
        "scene_data": 0
    },
    "origin": "LOCAL",
    "time_fired": "2021-05-26T14:28:58.425320+00:00",
    "context": {
        "id": "2fb387bcfb4f696b92c89e3cf79a2f61",
        "parent_id": null,
        "user_id": null
    }
}

Hi @TheDarthFather, are you using the deprecated z-wave integration?

Yes,
Found the issue as well. Integer on the deprecated version vs string on the new one.
I replaced ‘{{ scene_id == ‘‘1’’ and scene_value_id == ‘‘0’’ }}’ with ‘{{ scene_id == 1 and scene_value_id == 0 }}’.
PS: I tried this before, but it seems I have to re-create the automation as well :slight_smile:

Stupid question: Why is the Remotec ZRC-90 not available as a device with entities in the Zwave-JS integration? And how to get it in?

Hi,

Nice feature! But I am still struggling with this device. Can’t seem to get it work in Homeassistant.

My Z-wave in HA is managed by my Fibaro Home Center 2, which I added in HA/ configuration.yaml.
All other Fibaro Z-wave devices show up as entities in Home Assistant. Except this Remotec Panel…

I managed to include it in Fibaro Home center, but I want to use it in HA…

Are there any people who sorted this out?

Regards,
Ludwig

Hi Ludwig, this blueprint only works if you use the zwave-js integration in HA. I’m afraid I can’t test it for you in combination with a HC2. I used to own a Fibaro HC2 in the past but moved everything to HA (including an Aeotec Z-Wave USB stick) to manage my zwave network. It will take some time to rebuild your network, scenes and (LUA) scripts but once I did I never looked back.

Thanks Rule!

I think I have to look for an alternative panel :slight_smile:
Switching everything to Aetoec does not sound like an inviting idea :wink:

Regards,
Ludwig

Has anyone else tried using the HELD buttons for doing repeating actions like Brightness on a light entity?

Setting one of the buttons Held state to Increase or Decrease Brightness on a Zooz Zen22 dimmer causes HA to go off the rails and report the dimmer as dead. I can bring back the dimmer after turning it off or on at the physical switch.

I have no idea what’s causing the issue, but otherwise sending extra single-press increase or decrease brightness commands to this dimmer don’t cause such an issue (example sending decrease when the dimmer is already at 0 or increase when at 100). It also seems to work well with media control volume increase for my AVR.

This was working nicely for me till the upgrade of Z-Wave JS to 0.1.56. Other people facing this issue? Ideas how to solve this?

I have a feeling the repeat/loop issue I mentioned above may be related to the issues of 700-series Z-Wave sticks reported earlier in the year, as I just noticed my stick has firmware 7.15 and not 7.17 (issues fixed) as I thought.

As an aside, is there any chance this blueprint can be upgraded to allow turning ON/OFF looping/repeating for long-presses on a per-button basis? It won’t address my issue above, but it allows a number of other automation possibilities.

Hi!
I just keep getting
Error: UndefinedError: ‘dict object’ has no attribute ‘event’

Any idea?

Regards
Johan

been having issues ,i tried to cheat ,delete and re-add but keep getting this

Logger: homeassistant.config
Source: components/blueprint/models.py:259
First occurred: 08:32:09 (1 occurrences)
Last logged: 08:32:09

Invalid config for [automation]: Failed to load blueprint: Unable to find rule/remotec-zrc-90-scene-master-8-button-remote-zwave-js.yaml (See /config/configuration.yaml, line 17).
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/components/automation/config.py”, line 103, in _try_async_validate_config_item
config = await async_validate_config_item(hass, config, full_config)
File “/usr/src/homeassistant/homeassistant/components/automation/config.py”, line 70, in async_validate_config_item
return await blueprints.async_inputs_from_config(config)
File “/usr/src/homeassistant/homeassistant/components/blueprint/models.py”, line 297, in async_inputs_from_config
blueprint = await self.async_get_blueprint(bp_conf[CONF_PATH])
File “/usr/src/homeassistant/homeassistant/components/blueprint/models.py”, line 272, in async_get_blueprint
return load_from_cache()
File “/usr/src/homeassistant/homeassistant/components/blueprint/models.py”, line 259, in load_from_cache
raise FailedToLoad(
homeassistant.components.blueprint.errors.FailedToLoad: Failed to load blueprint: Unable to find rule/remotec-zrc-90-scene-master-8-button-remote-zwave-js.yaml

config line 17

Hi,

I’m trying to use a ZRC-90 with this blueprint but I’m having a few issues.

Initially, I was getting ‘no matching devices found’ when I tried to select the remote device. I guessed that this was because the blueprint looks for the remote under the integration ‘zwave_js’ and mine are via MQTT, so I tried ‘integration: mqtt’ and ‘integration: MQTT’ but neither worked, still ‘no matching devices found’.

According to the device diagnostics (will try to attach if I can work out how to upload a text file!), the device appears to be:
integration: MQTT
manufacturer: Remotec
model: Scene master 8 button remote (BW8510)

I’ve now been able to get the remotes to show up by removing ‘integration’ from the selector clause. No idea what the MQTT integration is called if it’s not ‘MQTT’ or ‘mqtt’!

… but …
The automation isn’t doing anything. I see the scene state change event for whichever button I press, but the automation isn’t triggered.

I’m not sure exactly what the blueprint looks for from the remote; for a single press of the button, mine are logging “Remotec remote 1_scene_state_scene_003 changed to 0” and then “Remotec remote 1_scene_state_scene_003”. That looks like a scene controller message vs a blueprint expecting buttons… am I right?

I’m new to blueprints and indeed to HA; can anyone help me to diagnose this one, please?

Okay, so… after looking at some debug logs, I think it’s a case of catching ‘state_changed’ events, but they don’t seem to be carrying the attributes that are needed.

I will look again into doing this with MQTT, but for now I’ve opted to do the hard work to move my zwavejs onto the websockets integration, where the original blueprint works!

I get the same error when I look at the ‘Trace Timeline’

Triggered manually at August 20, 2023 at 3:08:38 PM

Define variables scene_id and scene_value_id
Stopped because an error was encountered at August 20, 2023 at 3:08:38 PM (runtime: 0.11 seconds)

UndefinedError: 'dict object' has no attribute 'event'

I updated the blueprint to use filters (since direct selection is now deprecated)
And also added “KeyReleased”, which triggers after long hold on release.
It only triggers once, while KeyHeldDown triggers continuously while being held.

So remember when you want to use the hold:

  • Hold triggers multiple times
  • Hold & Release will be triggered as well

I hope it can help someone.

2 Likes

Thanks @magnobe !

Not sure if this is ‘user error’, but this blueprint doesn’t work for me either?

My best guess as to what’s going wrong - I see that the Blueprint is looking for ‘KeyPressed’, ‘KeyPressed2x’, etc. But when I look at the Logbook for my Remotec, it shows that a single press is represented by ‘0’, a double press is ‘3’, etc. It makes me wonder if I should edit the Blueprint and replace ‘KeyPressed’ with ‘0’, and so on?

image

That’s weird.
I believe so far that everyone had the named events.
Maybe it’s because of a different firmware or something.

Do you have a list of all of them. I can update the blueprint to support both of them.

1 Like

That would be awesome, thank you! Yeah I agree, I’m not sure why it’s different

0 - single press
3 - double press
2 - hold
1 - release