This repository has been archived by the owner on Mar 8, 2022. It is now read-only.
Replies: 2 comments
-
Oh yes ... and for me, setting up the testing environment was not entirely unlike this:
... which - gives me a chance of toying around with the code, updating it to the latest release, and ... always allowing me to get back to the "ground truth"-state of the repository ;) Again - this worked for me, your mileage may vary ;) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you for sharing !!! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I had some problems setting this up initially, and figured I might tell others "what went wrong"/"what I did wrong" and "how I got things working".
First and foremost; I was following the "Install for Testing" steps and... was somewhat perplexed by where exactly was the
custom_components
-folder supposed to be in. When I SSH'd to my box, I was in/root
-folder. And this was not where thecustom_components
-folder was supposed to be. In fact, when I rebooted my box, any changes I had made in that folder got reset; on my setup, the folder was not "persistent". (edit: I also tried having thecustom_components
-folder in the root of my setup - i.e./custom_components
... also not the correct place and not "persistent" over reboots)After a bit of head-scratching, googling and testing, Home Assistant documentation provided me with an answer; the
custom_components
-folder is supposed to be under the same folder that contains theconfiguration.yaml
-file. For me, this meant that the proper location was/config/custom_components
.Secondly*; I was still unable to add the devices to my
configuration.yaml
-file. Even though I followed the steps in "Install for Testing" ... when I tried to "Check Configuration" in Home Assistant UI, I received errors that "wiz_light" is not a recognised platform.It turned out that I needed to add a "dummy reference" to the domain before using that domain as a
platform
. In practice, what I needed to add to myconfiguration.yaml
was something not entirely unlike this:Hopefully this is of benefit for others. Naturally, your mileage may vary; e.g. after I had originally included the "dummy reference" to
wiz_light:
... it seems like it is no longer needed; if I drop it, now the "Check Configuration" passes without problems. Personally, I've decided to keep the dummy reference in there, because it doesn't hurt my setup and currently everything works as expected :)For me, there are still a few things I'm struggling with;
Hold Action
andDouble Tap Action
(but they work perfectly on my computer's browser UI) and...but I believe these are more a matter of the Home Assistant app rather than caused by this integration.
Personally; I love this :) My Wiz-RGB bulbs were the one thing I couldn't properly interact without a number of weird IFTTT setups in the past. But now I can ... and I'm a happy camper :)
Beta Was this translation helpful? Give feedback.
All reactions