Fibaro Nice Z-wave gate module still discovered as light and not a cover entity (IBT4ZWAVE)

[welo78]

The problem

Hello all, this issue has been previously discussed and "resolved" by another fork commit last year. Is it not in the master/main version yet ? Will it ever be ? I just went through the process of adding and discovering this Nice Gate dongle/module and it shows up as light still.

I am using RPI4, with Aeotec Z-stick Gen 5+. I followed the official installation from here. So the Z Wave JS UI first, then Z Wave JS. After it was setup and Aeotec showed as working I turned on the gate and paired via QR code.

I am not sure what to check/do next. The version of HA which I am using is: Home Assistant 2022.11.0 Supervisor 2022.10.0 Operating System 9.3 Frontend 20221102.1 - latest

What version of Home Assistant Core has the issue?

core-2022.11.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Z-Wave JS

Link to integration documentation on our website

No response

Diagnostics information

zwave_js-b1780598839894153663b9f2385faa8b-gate_module-bbe308732a3fb23012e42f2c66aec0da.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[kpine]

Please provide the necessary information about the device:

[kpine]

Click the ... button in that info page and download the diagnostics file, and attach (drag and drop file) here as a comment or in the original issue in that section.

[welo78]

Click the ... button in that info page and download the diagnostics file, and attach (drag and drop file) here as a comment or in the original issue in that section.

for the love of god, thank you ... I have been out of the loop with HA that I just cant keep up with the UI changes, added to OP

[kpine]

Hello all, this issue has been previously discussed and "resolved" by another fork commit last year. Is it not in the master/main version yet ? Will it ever be ?

Ok, this text was added to an edit. :) Someone needs to submit a PR, it won't be added otherwise.

[welo78]

Hello all, this issue has been previously discussed and "resolved" by another fork commit last year. Is it not in the master/main version yet ? Will it ever be ?

Ok, this text was added to an edit. :) Someone needs to submit a PR, it won't be added otherwise.

but what is it not added and approved as PR previously ? As it is stated here, Ah ok I think the guy just merged it into his own ha-core dev branch. Can anybody here create a pull request with the same code to the the main repo ? :)

[kpine]

but what is it not added and approved as PR previously ? As it is stated here,

That link is a PR to a forked repository. It was never submitted to HA. Someone needs to submit a PR to the right project.

Even if you just re-categorize the entity as a cover, it might not work properly. See my comment on the original issue. Based on the documentation, the device does not operate the way the implementation of cover is implemented. You would need to test.

[welo78]

yes I can see that now :( I would be able to test it. I also found a somewhat active thread on the PR so someone else is testing it aswell. By how it looks I would have been better off with a sonoff or shelly wifi-relay which supports 24v switching. If by your explanation all it can do is open and close and report the state if opened or closed.

Then again, this is the only thing I need from it.Basically to transform the "light" into a gate and to be able to tell Google assistant to open or close it not "turn on or off" it. Is an interminent solution to use template cover ?

I saw a similair approach here. I also think its the same developer who made the original PR. Maybe he got fed up with using it as cover ? :)

[home-assistant[bot]]

Hey there @home-assistant/z-wave, mind taking a look at this issue as it has been labeled with an integration (zwave_js) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `zwave_js` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zwave_js` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation zwave_js source _{^{(message by IssueLinks)}}

[welo78]

Well if this does not get implemented. Here is a workaround from the same person who made the PR for his own fork.

I just created a proper gate cover entity using a set of configurations.

1. Find the device ID for your IBT4ZWAVE. Open the device page, and copy the last chunk of the URL. That’s the device ID.
2. Under Devices / Helpers create a new text input. Mine is called: input_text.gate_state
3. In the following snippets, always replace the device id and the input id with your values.
4. Create a set of automations that change the value of the text input when the value of the BiDi ZWave changes. You’ll need to add the following to your automations.yaml file.

- alias: Set gate=open
  trigger:
    - platform: zwave_js.value_updated
      id: The gate is open
      # At least one `device_id` or `entity_id` must be provided
      device_id: bbe308732a3fb23012e42f2c66aec0da # Garage Door Lock device ID
      entity_id:
        - light.gate_module
      # `property` and `command_class` are required
      command_class: 38 # Door Lock CC
      property: "currentValue"
      # `property_key` and `endpoint` are optional
      #property_key: null
      #endpoint: 0
      # `from` and `to` will both accept lists of values and the trigger will fire if the value update matches any of the listed values
      to: "99"
  action:
    - service: input_text.set_value
      target:
        entity_id: input_text.gate_state
      data:
        value: "open"
- alias: Set gate=closed
  trigger:
    - platform: zwave_js.value_updated
      id: The gate closed
      # At least one `device_id` or `entity_id` must be provided
      device_id: bbe308732a3fb23012e42f2c66aec0da # Garage Door Lock device ID
      entity_id:
        - light.gate_module
      # `property` and `command_class` are required
      command_class: 38 # Door Lock CC
      property: "currentValue"
      # `property_key` and `endpoint` are optional
      #property_key: null
      #endpoint: 0
      # `from` and `to` will both accept lists of values and the trigger will fire if the value update matches any of the listed values
      to: "0"
  action:
    - service: input_text.set_value
      target:
        entity_id: input_text.gate_state
      data:
        value: "closed"
- alias: Set gate=opening
  trigger:
    - platform: zwave_js.value_updated
      id: The gate is opening
      # At least one `device_id` or `entity_id` must be provided
      device_id: bbe308732a3fb23012e42f2c66aec0da # Garage Door Lock device ID
      entity_id:
        - light.gate_module
      # `property` and `command_class` are required
      command_class: 38 # Door Lock CC
      property: "targetValue"
      # `property_key` and `endpoint` are optional
      #property_key: null
      #endpoint: 0
      # `from` and `to` will both accept lists of values and the trigger will fire if the value update matches any of the listed values
      to: "99"
  action:
    - service: input_text.set_value
      target:
        entity_id: input_text.gate_state
      data:
        value: "opening"
- alias: Set gate=closing
  trigger:
    - platform: zwave_js.value_updated
      id: The gate is closing
      # At least one `device_id` or `entity_id` must be provided
      device_id: bbe308732a3fb23012e42f2c66aec0da # Garage Door Lock device ID
      entity_id:
        - light.gate_module
      # `property` and `command_class` are required
      command_class: 38 # Door Lock CC
      property: "targetValue"
      # `property_key` and `endpoint` are optional
      #property_key: null
      #endpoint: 0
      # `from` and `to` will both accept lists of values and the trigger will fire if the value update matches any of the listed values
      to: "0"
  action:
    - service: input_text.set_value
      target:
        entity_id: input_text.gate_state
      data:
        value: "closing"

Create the cover by adding to your configuration.yaml

cover:
  - platform: template
    covers:
      gate:
        device_class: gate
        friendly_name: "Main gate"
        value_template: "{{ states('input_text.gate_state') }}"
        open_cover:
          service: zwave_js.set_value
          data:
            command_class: 38
            #endpoint: 0
            device_id: bbe308732a3fb23012e42f2c66aec0da
            property: targetValue
            value: 99
        close_cover:
          service: zwave_js.set_value
          data:
            command_class: 38
            #endpoint: 0
            device_id: bbe308732a3fb23012e42f2c66aec0da
            property: targetValue
            value: 0

That’s it. As an extra benefit, I wanted to add a button card 3 to my dashboard as well. For this I created an “Open/Close the gate script” under Automations / Scripts. The YAML is the following:

open_close_the_gate:
  alias: Open/Close the gate
  sequence:
    - choose:
        - conditions:
            - condition: state
              entity_id: input_text.gate_state
              state: closed
          sequence:
            - service: zwave_js.set_value
              data:
                command_class: 38
                device_id: bbe308732a3fb23012e42f2c66aec0da
                property: targetValue
                value: 99
        - conditions:
            - condition: state
              entity_id: input_text.gate_state
              state: opening
          sequence:
            - service: zwave_js.set_value
              data:
                command_class: 38
                device_id: bbe308732a3fb23012e42f2c66aec0da
                property: targetValue
                value: 0
        - conditions:
            - condition: state
              entity_id: input_text.gate_state
              state: open
          sequence:
            - service: zwave_js.set_value
              data:
                command_class: 38
                device_id: bbe308732a3fb23012e42f2c66aec0da
                property: targetValue
                value: 0
        - conditions:
            - condition: state
              entity_id: input_text.gate_state
              state: closing
          sequence:
            - service: zwave_js.set_value
              data:
                command_class: 38
                device_id: bbe308732a3fb23012e42f2c66aec0da
                property: targetValue
                value: 99
      default: []
  mode: queued
  icon: mdi:gate
  max: 5

Finally, the dashboard button is configured as an entity.

          - entity: cover.gate
            type: custom:button-card
            name: Gate
            show_state: true
            color_type: icon
            tap_action:
              action: call-service
              service: script.open_close_the_gate
            triggers_update:
              - cover.gate
            state_display: |
              [[[
              states["input_text.gate_state"].state
              ]]]
            state:
              - value: closed
                color: var(--paper-item-icon-color)
                icon: mdi:gate
              - value: open
                color: var(--paper-item-icon-color)
                icon: mdi:gate-open
              - value: opening
                icon: mdi:gate-arrow-left
                color: rgb(100,255,100)
              - value: closing
                icon: mdi:gate-arrow-right
                color: rgb(100,255,100)
            style:
              left: 69.5%
              top: 64.5%
              size: 50%

It’s a bit complicated to set up, but in the end, it works without any issues.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Loic691]

Hi all Any update of this issue for native integration ?