core: Position is not working on zwave cove

The problem

I just to add a blind device with zwave. Device is connected ok and I can close and open, but position do not works: I tried to just close at 40% (or any other %) with different options:

An automation:

action:
  - service: cover.set_cover_position
    data:
      position: 40
    target:
      entity_id: cover.persiana_6_despacho

blind card.

When I move these cards or activate the automation, de blind close or open completely.

The most curious thing is that I entity show it is opened at 40%:

I also tried to do some changes on the blind(cover) configuration. This is how it looks like now:

I have download the debug logs in case it helps

Any idea? do we need to do any kind of calibration first? how?

Thansk in advance

What version of Home Assistant Core has the issue?

core-2023.10.5

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

zWave

Link to integration documentation on our website

No response

Diagnostics information

home-assistant_zwave_js_2023-10-31T08-11-18.465Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

About this issue

Original URL
State: closed
Created 8 months ago
Comments: 23 (10 by maintainers)

Most upvoted comments

Calibration would be device specific, there’s no generic way to do it in HA.: it means i have to do outside of HA? or that could be a way to do for my device but have to find how to specifically do it for Simon devices (in my case)?

What I meant was that there’s no standard way to calibrate a Z-Wave motor control (cover) device so HA can’t provide a generic way to do it. The implementation is up to the manufacturer. That would usually be through a configuration parameter, or some on-device procedure like fully opening and closing the device one time or some button press. If config parameter is the method, you can do it via parameter 9.

I looked up the manual for this device and parameter 23 reports the calibration status, so it is currently reporting that calibration is not required. So that seems like it may not be the issue. For reference, the manual also has instructions for calibrating it by long pressing the button, or setting configuration parameter 9 to 255. HA doesn’t know what 255 means, this could be fixed by Z-Wave JS to provide a friendlier option. You can report a bug with node-zwave-js to have that enhanced. If you haven’t you could try setting parameter 9 to 255 and see if there’s any improvement.

About the support of position I understand that yes, it is supported, correct? So what could be the problem?

Your device identifies itself with Z-Wave device class Motor Control Class C. This means the device is position and endpoint aware. The manual also confirms that. The device diagnostic also shows the necessary information to set position, which is why the supported_features attribute includes SET_POSITION. So either the device is advertising the information incorrectly and does not actually support position (device bug), or it needs to be calibrated. If you can set the position in the app, it should be possible via Z-Wave.

At this point there’s nothing to suspect in HA yes, based on the given information. As I said in comment https://github.com/home-assistant/core/issues/103113#issuecomment-1788128034, you can provide debug logs if you want confirmation that HA is doing the correct thing as far as setting and reporting the position goes. Simply turn on debug logs, set a position, disable logs and attach the downloaded log file.

kpine on Nov 1, 2023