Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set_cover_position does not workt correctly with Fibaro FGR-223 #23138

Closed
dilruacs opened this issue Apr 16, 2019 · 13 comments
Closed

set_cover_position does not workt correctly with Fibaro FGR-223 #23138

dilruacs opened this issue Apr 16, 2019 · 13 comments

Comments

@dilruacs
Copy link
Contributor

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: OpenZWave/open-zwave#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: OpenZWave/open-zwave#1705 (comment)
Solution seems to be:

Enable SetChangeVerified on the ValueID in question (the level) […]

I am currently experiencing this problem too.

@ghost
Copy link

ghost commented May 18, 2019

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.

@Plevuus
Copy link

Plevuus commented May 18, 2019

@tofuSCHNITZEL
Copy link
Contributor

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)

@lelikg
Copy link

lelikg commented May 27, 2019

bump

@lelikg
Copy link

lelikg commented May 29, 2019

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?

@tofuSCHNITZEL
Copy link
Contributor

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

@lelikg
Copy link

lelikg commented May 30, 2019

can someone from @homeassistant address this please?

@RickiestRick
Copy link

@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?

@tofuSCHNITZEL
Copy link
Contributor

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

@stale
Copy link

stale bot commented Sep 9, 2019

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.

@stale stale bot added the stale label Sep 9, 2019
@stale stale bot closed this as completed Sep 16, 2019
@tofuSCHNITZEL
Copy link
Contributor

The delay issue is still present.

@denniswham
Copy link

For me it isn't working correctly either

@HydrelioxGitHub
Copy link
Contributor

same here, can this issue be reopened ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants