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

Fibaro FGD-212 Dimmer 2 not working (correctly) #2325

Closed
alex3305 opened this issue Jul 24, 2020 · 3 comments
Closed

Fibaro FGD-212 Dimmer 2 not working (correctly) #2325

alex3305 opened this issue Jul 24, 2020 · 3 comments

Comments

@alex3305
Copy link

Environment

Recently I have migrated my Home Assistant environment to use OpenZWave Home Assistant Add-On (instead of built-in Z-Wave) which in turn is based on OpenZWave Admin.

All my devices seem to work fine and show up correctly, except my Fibaro FGD-212 Dimmer 2. It's acting very strange and to be honest I don't know what to do with it anymore.

The problem

  • Turning on an instance on the dimmer does work, but only after a delay of about 5 to 10 seconds. The lights will light up really, really dim. Changing brightness has no effect and I cannot turn it off remotely. The physical switch I've connected to the dimmer works and I can turn it off with that
  • Sometimes, after changing the brightness more than once it seems, the dimmer will go to the set brightness when flipping the physical switch. Flipping it again turns it off
  • Turning the light on with the physical switch results in the light turning on at 20% brightness. Which I cannot change.
  • Double tap seems to work correctly and I can change the brightness once after that
  • Refreshing the Node List results in the Node being displayed twice in the Node List
  • Reverting to the Home Assistant Z-Wave component solves the issues above

Note Communication from Home Assistant seems to work fine, thus I'm opening this issue in this repo and not in one of the Home Assistant repo's

Logfiles

I have attached two logfiles to a gist since they were a little large for posting here. The first log file is only with logging for the Node with this issue (Node 8), while the second should be a complete log file from the OpenZWave Docker container.

@Fishwaldo
Copy link
Member

Most Likely Related to this issue: home-assistant/core#38068 (comment)

When that fix lands in HA, Please retest

@alex3305
Copy link
Author

@Fishwaldo Thanks for the feedback.

I don't know if it is related, but just wanted to let you know that this behaviour also appears when I try to control the light from OZW Admin. I also noticed that the transition times were indeed quite high, but AFAIK I was unable to adjust those values within OZW Admin.

@alex3305
Copy link
Author

alex3305 commented Jul 27, 2020

I have some additional insights into this issue. Today I have tested OZW Admin without Home Assistant. Thus switching my device from OZW Admin and not with Home Assistant.

I found that the default Dimming Duration was quite high at 255. Which seems the max value, as indicated in home-assistant/core#38068. However I could easily bring that back down to something like 1. But refreshing the node reset the Dimming Duration to a ridiculous value of 15300:

image

However the light still responds instantly whenever I change the instance level. Perhaps this is a bug on its own?

Edit: Integrating OZW Beta within Home Assistant indeed resets the dimming duration to 255 when controlling the light and should be the issue you have linked.

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

No branches or pull requests

2 participants