Core: set_cover_position does not workt correctly with Fibaro FGR-223

Created on 16 Apr 2019  路  13Comments  路  Source: home-assistant/core

Home Assistant release with the issue:

0.91.3

Last working Home Assistant release (if known):
not known

Operating environment (Hass.io/Docker/Windows/etc.):

PyPi installation on Debian 9

Component/platform:

https://www.home-assistant.io/components/zwave/#cover

Description of problem:
See: https://github.com/OpenZWave/open-zwave/issues/1705

the state report of Fibaro FGR 223 of the blinds is not correct / not updated.
F.e. I moved the shutter to 25% via multi-state switch and it shows the old position f.e. 5%.

With the older version Fibaro FGR 222 everything is working well.

Issuer was being referred to: https://github.com/OpenZWave/open-zwave/issues/1705#issuecomment-473487861
Solution seems to be:

Enable SetChangeVerified on the ValueID in question (the level) [鈥

I am currently experiencing this problem too.

zwave stale

Most helpful comment

The delay issue is still present.

All 13 comments

Hey there @home-assistant/z-wave, mind taking a look at this issue as its been labeled with a integration (zwave) you are listed as a codeowner for? Thanks!

_This is a automatic comment generated by codeowners-mention to help ensure issues and pull requests are seen by the right people._

for me on position 100 the roller is completely up and on position 0 it is down. (and yes I did the calibration numerous times)
also there is a delay of about 5-10 seconds after changing directions in quick succession (it seems like the zwave stack is freezing bcs all other zwave devices also stop responding in this time)

bump

for me on position 100 the roller is completely up and on position 0 it is down. (and yes I did the calibration numerous times)
also there is a delay of about 5-10 seconds after changing directions in quick succession (it seems like the zwave stack is freezing bcs all other zwave devices also stop responding in this time)

This happens to me as well, any luck finding a solution/workaround?

This happens to me as well, any luck finding a solution/workaround?
unfortunately not. I use the roller for a cinema screen and I would actually like to disable the positioning all together

can someone from @homeassistant address this please?

@tofuSCHNITZEL there's a workaround for the positioning issue with 3 Automations => https://community.home-assistant.io/t/fibaro-roller-shutter-3-fgr-223-cannot-get-it-to-work-properly/97577/22

Have you found a fix/workaround for the 5-10 seconds of no responding?

Have you found a fix/workaround for the 5-10 seconds of no responding?
unfortunately not.

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 now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

The delay issue is still present.

For me it isn't working correctly either

same here, can this issue be reopened ?

Was this page helpful?
0 / 5 - 0 ratings