Current State and Development Log #78
Replies: 38 comments 45 replies
-
Status 04/01/2021I'm currently working on the HASS core pull to push this integration into the base of Home Assistant.
The update poll for getting the current state of the bulb was decreased to 15 Seconds to detect a change from "others" like the WiZ app or a WiZ switch. Maybe I'll lower this to 5 Seconds in the future but ... lets see what can be done with the UDP broadcast listener from @jarpatus. The most time was consumed in developing the So the main point is, that I'm currently updating and working on the pull to HASS core. All or the most changes to the code will be reflected into this repo after a successful commit. After that this repo will be the developing and maybe "nonofficial" clone of the HASS core part. So we can test and have a playground with stuff like UDP Broadcast listener and others. Overall time consumption over the holidays:
= 31 hours overall (took these measurements form the Visual Studio Code 😉) I also wait for my second WiZ light to do more testing with two real lights. I bought (a really expensive 🤒 ) table light to get maybe better access to the ESP board to dump the FW. Hopefully the device will be not destroyed to do not waste 60€ ....... Stay tuned !!!!! And Thank you all for the support and feedback !!! May the Light be with you. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for all your hard work on this. I am excited to see this in HASS Core :-) |
Beta Was this translation helpful? Give feedback.
-
|
So grateful for all your hard work! I'm just starting to learn about all of this home automation, ESP stuff. Your project has been so incredibly helpful! Thank you! : - ) |
Beta Was this translation helpful? Give feedback.
-
Status 19/01/2021Hey, today I started my (long planed) reverse engendering of one of the WiZ bulb firmware. I try to figure out how and what functions are provided by the UDP API. Furthermore, I captured some traces between the app and the bulb. Another topic is the HASS pull request. This is now green (all checks are passed) and can now be merged into the core for the next release cycle. Hopefully this will happen in the next days. Stay tuned !!!!! And Thank you all for the support and feedback !!! May the Light be with you. Discovered UDP functionsSync functions:
Set functions:
Get functions
Error States and Returns
|
Beta Was this translation helpful? Give feedback.
-
|
Awesome!! Truly great work here! We would be in the dark if it weren't for you and everyone else who has contributed to this. |
Beta Was this translation helpful? Give feedback.
-
|
No function to update firmware? |
Beta Was this translation helpful? Give feedback.
-
Status 26/01/2021After some days "off" I've a disscussion and short Q&A with a WiZconnect developer. He told me that it is currently not possible to change the transition time between state changes via UDP API. This can only be changed in the app. In that case the But overall it is great to see that WiZ is interested in the Open Source Community and supports us to bring the "best light experience" to our homes. One bad news on the other hand - the pull request for the HASS core is still "on hold/open" because of "other important" topics like the security issues with other custom integrations (like the HACS). One side note: This integration has no vulnerability (so far) 😉 For now I'll push some other project and have a 👁️ on the pull for possible feedback and reviews. I'll also bring all changes form the pull to this repo to have a full sync and give you all the new features like ConfigFlow etc. May the Light be with you. Cheers |
Beta Was this translation helpful? Give feedback.
-
|
Excellent job. I have been waiting in anticipation for this ever since I
decided to use Home Assistant instead of the individual apps. This will
check yet other checkbox off my list of things left to integrate. Thank
you for your perseverance. It is greatly appreciated.
Sincerely,
Steveo
…On Tue, Jan 26, 2021, 3:26 PM Stephan Traub ***@***.***> wrote:
*Status 26/01/2021*
After some days "off" I've a disscussion and short Q&A with a WiZconnect
developer. He told me that it is currently not possible to change the
transition time between state changes via UDP API. This can only be changed
in the app. In that case the setUserConfig will not take this parameters.
The reason is loosely speaking the "fear" of power spikes in the bulb. But
maybe there will come something in the future 😄 ... The complete
discussion can be found here --> sbidy/pywizlight#40
<sbidy/pywizlight#40>
But overall it is great to see that WiZ is interested in the Open Source
Community and supports us to bring the "best light experience" to our homes.
One bad news on the other hand - the pull request
<home-assistant/core#44779> for the HASS core is
still "on hold/open" because of "other important" topics like the security
issues with other custom integrations (like the HACS). One side note: This
integration has no vulnerability (so far) 😉
I try to trigger some one from the core team to have a look into the pull
because all checkpoints are done (ConfigFlow, Translations, Tests etc.) and
all tests are 🟢 . Maybe I've to ask @fabaff <https://github.com/fabaff>
for help nicely 😸.
For now I'll push some other project and have a 👁️ on the pull for
possible feedback and reviews. I'll also bring all changes form the pull to
this repo to have a full sync and give you all the new features like
ConfigFlow etc.
I'll also try to solve some of the open issues but I think currently there
are no "big" points to dig in.
*May the Light be with you.*
Cheers
Stephan
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#78 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHYXSWM27GCC77OSOUL6VQ3S346RNANCNFSM4VTMVNYQ>
.
|
Beta Was this translation helpful? Give feedback.
-
Status 01/02/2021Version 0.3 now out! This version represents the current pull from HASS core with some additional improvements.
Please drop some issues 😆 ... May the Light be with you. Cheers |
Beta Was this translation helpful? Give feedback.
-
Status 08/02/2021Quick Update: I'll reach out to you because I need some testers for the different bulb types. I don't have any bulb type available for testing because they are to expensive for that. May the Light be with you. Cheers |
Beta Was this translation helpful? Give feedback.
-
Status 25/02/2021First of all a BIG THANK YOU to @vodovozovge and the whole WiZ connected Team!! 💙 Now I have created a "test environment" and looking forward to fix some outstanding issues. I defined the following "roadmap":
One point which is still open in the backend lib is the implementation of a registering feature to avoid a pulling of new states. The dimmer and WiZ Plug integration will also a point on the "long term ToDo". Hopefully I found sufficient time in the next time to dig into that 😞 May the Light be with you. Cheers |
Beta Was this translation helpful? Give feedback.
-
|
Now that is for sure the kind of support that will get me to buy more Wiz products |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your work! Its fantastic! There are not so many bulbs in Norwegian market that are same time filament, Wi-Fi and high CRI valued. So this is on high demand for sure. |
Beta Was this translation helpful? Give feedback.
-
|
As a noob in HA and Wiz, this project made me dive all in to HA! |
Beta Was this translation helpful? Give feedback.
-
Status 29/03/2021Some days later .... sorry for the delay. But ... I'm highly disappointed and frustrated about the documentation and the HASS developer community. There are some many "developer" in the discord and forum but you don't get really useful input from them. I also invest tonnes of hours into the "auto discovery" feature to provide a easier way to add multiple bulbs. But currently I struggled with the documentation of HASS. The "official" answer to my question where to find the documentation for the "discovery feature" was to go into a "good" existing integration and do some reverse engineering. Great starting point ... the question what a "good" integration is, is still not answered from the HASS dev. The other open point whit the "offline" bulbs after reboot is also a relay annoying issue. From the HASS dev team can nobody answer the question why the device will remain offline and ignore the `available = true' what the integration is reporting to the HASS core. I'm not a core developer of HASS and it is really hard to debug such an issue without deep knowledge of the state-machine and without a detailed documentation about that. So I decided to reduce my time investment into that project for some weeks. Ah - I don't want to "hate" against anyone of the HASS dev team. They also do an amazing job but from a "integrator" perspective it is a little bit disappointing 😞 . Stay tuned!! Cheers |
Beta Was this translation helpful? Give feedback.
-
|
Hi Stefan, I also would say thank you for your hard work. As a software developer I know how frustrating it could be to never get or find the needed information. For some reasons I have decided to take another route with my WizLights. But I will follow the discussions for WizLight integration. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Me too, I want to add my huge thanks for you work! I've been running ~20 WiZ bulbs for months utilizing your v0.1 integration and there has not been a single problem. That is huge and without your integration I probably would have no smart lights as I've been experimenting with zigbee lights every now and then and been always disappointed how unrealiable they are. Not a single problem with wiz_light. Yes later relases have problems stemming from lack of documentation you mention and I totally feel you. I took me ages to do even most trivial modifications to some home assistant integrations (namely hass) since there were virtually no documentation at all. I guess it's way too common with open source projects since documentation is boring part for some (it really should not be, it should be part of the fun) :( But in any case v0.1 is good, does not matter at all if we do not have discovery or config flow or what not. Anyways, take a good break, you really deserve it! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @sbidy , its been my experience that merging into large umbrella projects is often a really really hard problem for both integrators and feature devs..... probably this means that nobody on the core side even knows what the process is to approve haha. So sorry, I really appreciate the work you've done here! Your code turns my lights on and off every day 🙏🏽 |
Beta Was this translation helpful? Give feedback.
-
|
I still need to give it a try, in any case already big thumbs up for all the effort. I was about to give up on the whole HA setup, first the issue with mu HS110 plugs from TP-LINK and then almost 0 support for Wiz lights (until I found this repo). |
Beta Was this translation helpful? Give feedback.
-
|
Thanks again @sbidy for keeping this development moving forward. A quick note for people with a lot of lights who haven't updated because they do not want to migrate from the configuration.yaml setup. I found it really easy. I copied my bulb names and IP addresses from the configuration.yaml to notepad, commented them out of the file, upgraded (with a system restart), and then added each of them from the UI. As I added each back to the UI, they came back on-line in the HA system. I never changed the default IDs so the HA knew about them and just needed them added back in. In other words, smooth and easy. Thanks again, @sbidy ! |
Beta Was this translation helpful? Give feedback.
-
|
Stephan,
Thank you so much for all your work on this and the others as well. I’m merely an end user myself and don’t know really how or what to contribute but if there is one thing I can, it’s to say what an amazing job you have done with this, from the ground up really. Without you we would still be in wiz darkness with HASS.
I don’t know who we need to beg, beat or bribe over on the dev side to get you some support but I’ll be more than happy to start writing emails and making phone calls. I realize the HASS project as a whole is all volunteers and grateful we all are for the genius behind the platform, but surely someone on the dev side has wiz lights or at least played with them and can lend some assistance. I know I would if I knew how haha.
Cheers to a nice break from the project, sometimes that is all we need to come back and see the answer in front of us.
Thanks again for all your hard work.
Chris
From: Stephan Traub ***@***.***>
Sent: Monday, March 29, 2021 4:04 PM
To: sbidy/wiz_light ***@***.***>
Cc: chrisbl01 ***@***.***>; Comment ***@***.***>
Subject: Re: [sbidy/wiz_light] Current State and Development Log (#78)
Status 29/03/2021
Some days later .... sorry for the delay. But ... I'm highly disappointed and frustrated about the documentation and the HASS developer community. There are some many "developer" in the discord and forum but you don't get really use full input from them.
I was investing so much time into this project and created a pull request to the hass core - months ago. After asking the "core developer" of a review of the integration I only get the feedback that the pull is really "new" and I have to wait. Months later sill no feedback.
Maybe I have to wait until the end of the year? I don't know. It is really frustrating if you put so much affort into the project and don't see a progress on that topic. BUT THANK YOU ALL here in the "wiz_light community" for all the feedback and issues!! 💙 You are amazing - everyone who contributes makes this project better!
I also invest tonnes of hours into the "auto discovery" feature to provide a easier way to add multiple bulbs. But currently I struggled with the documentation of HASS. The "official" answer to my question where to find the documentation for the "discovery feature" was to go into a "good" existing integration and do some reverse engineering. Great starting point ... the question what a "good" integration is was still not answered.
So please if you have multiple bulbs please use the configuration.yaml to made a bulk add.
The other open point whit the "offline" bulbs after reboot is also a relay annoying issue. From the HASS dev team can nobody answer the question why the device will remain offline and ignore the `available = true' what the integration is reporting to the HASS core. I'm not a core developer of HASS and it is really hard to debug such an issue without deep knowledge of the state-machine and without a detailed documentation about that.
So I decided to reduce my time investment into that project for some weeks.
Maybe I find a solution for this issues after I have gain some distance 😉
Stay tuned!!
Cheers
Stephan
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#78 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQD4UI2EF32F2RPP4ZON3W3TGDTLPANCNFSM4VTMVNYQ>.
|
Beta Was this translation helpful? Give feedback.
-
|
Sorry to hear your struggles Stephan! Thank you so much for all of your hard work. As has been said already, what you have done so far is working really well! I'm extremely grateful as your code and the Wiz Lights was my introduction to IoT and home assistant. This has led to a rabbit hole of other projects. You have helped many people and really started a community around this hardware, I hope that it continues to develop. I will try to contribute how I can by sharing my experiences in the forums more and maybe even write some documentation. Thanks again! Cheers! |
Beta Was this translation helpful? Give feedback.
-
|
You have done an amazing job. I was worried there for a bit that you had
stopped progress but then you picked it back up and have kept it going. I
know you are ready to have it be incorporated into the system. I have been
waiting for this to happen ever since I started using HA and Wiz bulbs.
They are the ONLY smart bulb I have in my home.
That being said although I have no power over the core developers it is
interesting what an army of ants, or end-users in this case, can do to make
something happen. I make no promises but I will do whatever I need to to
make this become a reality and soon.
…On Mon, Mar 29, 2021, 1:03 PM Stephan Traub ***@***.***> wrote:
*Status 29/03/2021*
Some days later .... sorry for the delay. But ... I'm highly disappointed
and frustrated about the documentation and the HASS developer community.
There are some many "developer" in the discord and forum but you don't get
really use full input from them.
I was investing so much time into this project and created a pull request
to the hass core - months ago. After asking the "core developer" of a
review of the integration I only get the feedback that the pull is really
"new" and I have to wait. Months later sill no feedback.
Maybe I have to wait until the end of the year? I don't know. It is really
frustrating if you put so much affort into the project and don't see a
progress on that topic. BUT THANK YOU ALL here in the "wiz_light community"
for all the feedback and issues!! 💙 *You are amazing* - everyone who
contributes makes this project better!
I also invest tonnes of hours into the "auto discovery" feature to provide
a easier way to add multiple bulbs. But currently I struggled with the
documentation of HASS. The "official" answer to my question where to find
the documentation for the "discovery feature" was to go into a "good"
existing integration and do some reverse engineering. Great starting point
... the question what a "good" integration is was still not answered.
So please if you have multiple bulbs please use the configuration.yaml to
made a bulk add.
The other open point whit the "offline" bulbs after reboot is also a relay
annoying issue. From the HASS dev team can nobody answer the question why
the device will remain offline and ignore the `available = true' what the
integration is reporting to the HASS core. I'm not a core developer of HASS
and it is really hard to debug such an issue without deep knowledge of the
state-machine and without a detailed documentation about that.
So I decided to reduce my time investment into that project for some weeks.
Maybe I find a solution for this issues after I have gain some distance 😉
Stay tuned!!
Cheers
Stephan
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#78 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHYXSWPSVJZUAVE3LK3QLO3TGDTLPANCNFSM4VTMVNYQ>
.
|
Beta Was this translation helpful? Give feedback.
-
|
TY Stephan for the recent release; it resolved an issue I had (related to array out of bounds). I was about to move on from Wiz but glad I don't have to now. I appreciate that you're continuing to support this project. I look forward to the day when this is an official HASS integration. |
Beta Was this translation helpful? Give feedback.
-
|
After upgrading to Home Assistant 2021.4 several of my Wiz lights would no longer connect. I even upgraded to 2021.4.2, but the issue persisted with Wiz 0.4.1. Good news, I updated to the new Wiz version 0.4.2, and everything is working again! Additionally, I was having the issue where my white color changing bulbs wouldn't connect to HA on reboot unless they were turned on. (Power to the bulb was not enough, it had to lit) I can confirm that all bulbs are now connecting as long as they have power. For reference, I have the following bulb models: 23004 (A19 White only color changing), 23007 (A19 Full color), and B23065 (A19 Full color) I'm happy to help with any testing or troubleshooting in the future, thanks for the great work! |
Beta Was this translation helpful? Give feedback.
-
|
I've installed those via HACS and its working great. I noticed that there is no 'device' created for these, only the entities. e.g. I have some Hue bulbs that show up as devices with their associated entities. Wiz lights only seem to have the entity. A blueprint I'm looking to use requires the bulb be entered as a device so I was wondering if that is possible? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Great Job @sbidy . I haven't been very active but I've been watching the project. I've just cloned a copy of 0.4.5 into my Home Assistant 2021.11.5 install and it's working great. I'm happy that going from Yaml to GUI wasn't terrible, I just chose the same names and my automations all worked. I look forward to seeing this being accepted into Core! |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys, new to pretty much everything here... Thanks to Stephan for bothering with this! Just got HA up and running, and found this add-on, after a couple of days finding out that i needed HACS and how to do that i finally got the Wiz integration up, problem is that when i try to connect my wiz-plug i just get "Unknown error occured". I have tried IP and mac both full and last 6-digits with and without the wiz- prefics. Any ideas? |
Beta Was this translation helpful? Give feedback.
-
|
same for me |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Stephan for making this integration! It was easy to setup and is working great for me =) Maybe I'm missing something obvious but I couldn't figure out how to change the light color from a homeassistant script. Does anyone know how to do this? |
Beta Was this translation helpful? Give feedback.
-
|
I use the “call service” action, and “light.turn_on”. The GUI does not seem to be showing the color change options (no color picker, no call service options), but it is available from the developer tools if you are comfortable using them (you can copy the YAML from there...).
The option is working from my homekit automations, but I don't know if the lack of correct options in the visual editor is a wiz_light integration problem or a HASS problem.
(I'm not perfectly certain of my understanding of HASS's internals, so take this with a grain of salt) Looking at the entity registry, my bulbs don't have RGB in the supported color modes, could this be a factor? Color Temperature isn't showing up in HASS script interface either.
"supported_color_modes": [
"color_temp",
"hs"
]
I tried manually adding "rgb" to this list, but it had no affect. I'm running HASS 2021.12.4 (latest) in a container. HASS has been hyper flakey of late, so it wouldn't surprise me at all if this is their problem. I'll ask on the Discord.
|
Beta Was this translation helpful? Give feedback.
-
|
Maybe there's a new requirement that the integration reports color_mode as well as supported_color_modes. OK, my confusion - the interface does return color_mode if the light is operating in a color mode. When it is on, and already colored (by some other interface), lovelace will show the color picker. If it's just on, the color picker will not show and you have no way to bring it up. The Visual Editor for scripts and automations does not, however, give the color choices regardless of the light state. If you use the developer tools to create a service call, you can copy that into the YAML of the script or automation and that works. Somebody at HASS has made this way more complicated than it should be, I think. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks brettonw! Building a call using Developer Tools in hass and then copying the YAML code over to a script is working for me. service: light.turn_on
target:
device_id: XXXXXXXXXXXXXXX
data:
brightness_pct: 25
color_name: blue |
Beta Was this translation helpful? Give feedback.
-
|
Another option is to select "call service" -> "light.turn_on" as the action in the script builder. It brings up a gui with lots of options. |
Beta Was this translation helpful? Give feedback.
-
|
When you do that, are the color setting options shown? They are not shown for me, brightness is the only option unless I edit in yaml first, and then it shows my color setting in the visual editor. |
Beta Was this translation helpful? Give feedback.
-
|
Several color settings show up for me: RGB-color: RGBW-color: RGBWW-color: Color name: Hue/Sat color: XY-color: Color temperature (mireds): Color temperature (Kelvin): |
Beta Was this translation helpful? Give feedback.
-
|
I'm new to HA. I just installed it the first time yesterday. My main focus is the vast amount of WIZ lights that I have in my house. Basically all my lights are WIZ lights. So far I controlled them with self made PIs with a touch screen, which run scripts that I wrote all by myself after sniffing out the easy to understand plain text UDP protocol of the bulbs. So, in HA I have installed HACS, Mosquitto broker, Terminal, a File Editor, Samba Share, Studio Code Server and SSH & Web Terminal. HACS took a full day to get over Git's Ratelimit. But it seems to be up and running now. I've installed wiz_light 0.4.5b according to the "Install for testing" instructions. "WIZ Light" showed up in the Integrations list while HACS was still in its Ratelimit phase. After the Ratelimit was resolved and HACS got all of its repositories, "Wiz Light" does not show up in the Integrations list anymore. So, I can't add and consequently not use it. What happened? Can someone help? |
Beta Was this translation helpful? Give feedback.
-
|
You don’t need to use HACS, but I am confused why it would be rate-limiting you if you’ve already installed the integration.
You sound technically inclined, so I’d suggest just doing the custom_components route and putting the bulbs in your configuration.yaml file. Otherwise you’ll be adding your bulbs through the ui one at a time. I have just 12 bulbs and don’t want to do that again…
… On Jan 3, 2022, at 7:14 PM, chvchv ***@***.***> wrote:
I'm new to HA. I just installed it the first time yesterday. My main focus is the vast amount of WIZ lights that I have in my house. Basically all my lights are WIZ lights. So far I controlled them with self made PIs with a touch screen, which run scripts that I wrote all by myself after sniffing out the easy to understand plain text UDP protocol of the bulbs.
So, in HA I have installed HACS, Mosquitto broker, Terminal, a File Editor, Samba Share, Studio Code Server and SSH & Web Terminal.
HACS took a full day to get over Git's Ratelimit. But it seems to be up and running now.
I've installed wiz_light 0.4.5b according to the "Install for testing" instructions. "WIZ Light" showed up in the Integrations list while HACS was still in its Ratelimit phase. After the Ratelimit was resolved and HACS got all of its repositories, "Wiz Light" does not show up in the Integrations list anymore. So, I can't add and consequently not use it.
What happened? Can someone help?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
|
So, HACS is not necessary for the WIZ Light Integration? The webpage "https://github.com/sbidy/wiz_light" mentions the installation of HACS. So I thought it is necessary. (As I said, I'm new to HA and don't know yet which Add-Ons and Integrations depend on each other.) Still, my problem persists. Wiz Light is installed according to the installation guide (3 Terminal commands and a reboot of HA). That's easy enough. WIZ Light does however not show up anywhere. Neither in the list of installed integrations, nor anywhere else. I've already tried to reinstall WIZ Light by deleting the folder wiz_light from config/custom_components and then reinstalling it. This however also did not help. Also: |
Beta Was this translation helpful? Give feedback.
-
|
Presumably you found your answer at this point, @chvchv, but this feature has been added to the mainstream HA core. AKA, you don't need a custom component anymore. As indicated, you go to your config section of standard HA, add an integration, and select Wiz light. from there, you can specify the IP address (preferably assigned statically by your router), and an entity name. After that, you should be ready to rock and roll. |
Beta Was this translation helpful? Give feedback.
-
|
At the bottom of the WizLight GitHub page, there is a set of instructions for "Install for testing". Probably the part you are missing after rebooting the server is clearing your web cache (I activate the developer tools on the browser to do this selectively). I don't want to hijack too much of sbidy's dev log here, so I will point you at the wizlight discussion board (https://github.com/sbidy/wiz_light/discussions), the HA docs (https://www.home-assistant.io/docs/), and the HA community (https://community.home-assistant.io/). There is also a discord server, but I don't think you'll get much from them until you learn more about HA itself. |
Beta Was this translation helpful? Give feedback.
-
|
I've got 25+ wiz lights mostly br30 and some a19 and a22 and so far this integration is working amazingly! I'm coming from Smartthings and now having everything local is so fast with my zwave switches. It's very impressive. I'd like to contribute to time hard work, I there a way to do so? |
Beta Was this translation helpful? Give feedback.
-
|
What is a differentiation of the smartplug compared to the Bulb, the basic application does it, google home also allows it, currently only your integration does not allow it and I do not understand the reason at the moment. |
Beta Was this translation helpful? Give feedback.
-
Status 06/02/2022 🚀 🥳IT IS DONE!! The PR was now merged to the HASS core. I'm not sure what the next steps are, but the WiZ should show up as a new integration in the next release of HASS. So please keep in mind if you update your HASS to the next upcoming stable release, please remove this integration from Unfortunately, I was not that active in the past week because of some life-changing events 😄... Sorry for that .... I want to say thank you to !!YOU!! as contributes, testers, issue submitters and sponsors! THANK YOU!!! But some features, issues and changes are still open (as @Mick51 mentioned) - I'm optimistic to get these things done in the next weeks. If you want to contribute, you can have a look into the issues in the HASS repository (Link to the Issue Tracker) and help with support if you can. 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 🚀 Here is the link to the initial PR to the HASS core for more information: |
Beta Was this translation helpful? Give feedback.
-
|
Bravo! 👏🏼👏🏼👏🏼 This is awesome! Thank you!!! I swapped out every light in my home (minus two) with Wiz bulbs and use their circadian rhythm as the on setting for a two button control that replaced every light switch. People in my home have no idea that it's a smart home. They get the on/off functionality for each room that they expect and I get advanced, behind-the-scenes functionality, and full color options via Home Assistant. I've lived with this for just over a year thanks to Home Assistant and this integration. So happy with how well these all work with that solution! |
Beta Was this translation helpful? Give feedback.
-
|
@weberjam007 can you suggest a switch for Wiz devices? |
Beta Was this translation helpful? Give feedback.
-
|
Excited to see this move into core, been using the HACS version for 5 months with a few bulbs and it's worked great. This integration was a huge part of the reason I went with wiz bulbs for my needs. Thanks sbidy, wiz, and everyone else! |
Beta Was this translation helpful? Give feedback.
-
Sorry for the delay. There two ways to do this. The right way and the way I did it 🤣 The preferred way is to use a puck behind a standard mechanical switch. These pucks can watch the mechanical switch and send an event to Home Assistant when someone flips the switch up or down. You also connect the lighting load to the puck as well (different terminals) but program the puck to keep your Wi-Fi lights powered constantly. From there you can program Home Assistant to control the constantly powered WiZ bulbs (send On when someone flips the light switch up and off when they switch it down). The puck keeps the load powered constantly unless you need to change a lightbulb. In that event you can go into Home Assistant and tell the puck to cut the power while you change the bulb (or make an automation for bulb changing start and stop to control these pucks). I say this is the preferred way because you retain individual control over each set of light bulbs. I think Sonoff and Shelly make pucks that can do this. I would ask for advice on which puck to use to achieve this as I have not tested this setup myself. The way I did it was the similar. I keep my WiZ bulbs powered constantly by rewiring the loads to stay hot in the back box (I use the breaker to shut off the loads if a bulb ever needs changed). I then integrate with a Lutron Caseta Smart Bridge and the Pico keypads for that system. I use a mounting adapter (PICO-WBX-ADAPT) to safely mount a Lutron Caseta Pico over the spot where I remove the old mechanical switch. Personally, I use 2 button Picos (PJ2-2B-GWH-L01) because everyone understands On and Off and it saves me from answering questions. I program the Pico On button to call up the circadian rhythm that the WiZ bulbs use (the Off button does the obvious thing, but could be programmed to leave a nightlight on for a kid's room or a hallway). Now the WiZ bulbs are constantly powered, everyone can use them without instruction, and I have access to all the advanced features and color changing capabilities through the UIs I created in Home Assistant. |
Beta Was this translation helpful? Give feedback.
-
Ignore the terrible, and temporary, labels. I only use those in the Office which doubles as the guest bedroom. There used to be two mechanical switches here. Both have been completely eliminated and the power goes directly to the fixture. Then I cover them with Pico controls. The On/Off Pico controls the whole room as mentioned before (through Home Assistant automation). The Audio Pico controls the Sonos in each room (again through Home Assistant automation): Here I am leaning one of the Picos out to show the plastic mounting bracket that allows you to cover the opening and mount Picos: |
Beta Was this translation helpful? Give feedback.
-
|
I have my first WiZ light installed and was just waiting for the native integration to pull into HA. I'm now upgrade to 2022.2.6. I think I'm not doing something right. I go to Configuration > Integrations > Add Integration. I search for WiZ and nothing is listed. Is this what I should be doing? If so is there a reason it may be missing? I have cleared my browser cache and that good stuff. Thanks for the help! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Ok...great. I'll wait a little longer. This is an exciting project. Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
if you are eager, and running docker, you can switch to ghcr.io/home-assistant/home-assistant:dev if you are ok with the possibility of things breaking in general... And on that note, is it possible to migrate the 20 or so bulbs I have configured in my system via the custom integration to the new Official integration, without re-configuring everything from scratch? That is, take the existing entities, and just swtich them to using the new integration, instead of deleting and re-adding and re-configuring (and re-configuring and re-configuring) for all the various scenes, dashboards, etc where they are used? That could save me hours of work. |
Beta Was this translation helpful? Give feedback.
-
|
The domain of the integration has changed so you'll need to delete and re-add |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Are there any instructions on how the migration will be. Will we have to remove the HACS and re add everything or is there a more automated process? Thanks! Joaquin |
Beta Was this translation helpful? Give feedback.
-
|
Here was my process and it went smooth as 🧈:
Because Home Assistant is awesome and I kept the automatic entity IDs that HA created based on my WiZ bulb names, after step 4 everything worked exactly as before. Best of all (one of the main benefits of adding devices via the UI instead of the YAML file) is that as I added each light back in via the UI, it came right online and all automation worked without a reboot (BTW, I keep saying reboot, but I mean a restart of the HA server needed when changing the YAML file). |
Beta Was this translation helpful? Give feedback.
-
|
@sbidy and everyone, I'm a pickled old developer (aka I'm a manager now and not actively developing). Is there a good place on the repository to write up these notes and post them where they can easily be found? Or is this forum and this post the right place. I'm still learning what GitHub usage etiquette calls for. |
Beta Was this translation helpful? Give feedback.
-
|
When using the core integration you should see all the devices discovered right away on the integrations screen. You might want to remove the HACS version before adding them so you don't have conflicting entity ids in case you want to rename them. If you don't see them right away it means your network doesn't support dhcp discovery and adding a single device via add integration will start wiz discovery and find the rest of them. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the clarification, I must have updated before auto-discovery. That would have made step 4 even easier! |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Congratulations on this achievement! I have been using the custom component, and I have been very happy with it. I like the Wiz bulbs and recently bought two Wiz strip lights as bias lighting for my TVs. HA allows me to automate them to turn on and off with the TV. Super convenient! |
Beta Was this translation helpful? Give feedback.
-
|
A quick question, if I may - I keep seeing talk of the existing installations performed via HACS. I had manually added the custom component. Will there be special instructions made available for this case? Is it sufficient to just comment out the YAML, or should we remove the custom component as well? |
Beta Was this translation helpful? Give feedback.
-
You should do both. |
Beta Was this translation helpful? Give feedback.
-
|
Can you shed some light on why YAML isn't an option anymore? Adding 15+ lights in UI is very cumbersome and inconvenient. |
Beta Was this translation helpful? Give feedback.
-
|
We have auto discovery, automatic ip updating, and automatic retry when the device is offline or updating firmware all built in now (that doesn't work with YAML). You don't have to do anything but click Also YAML configuration is no longer allowed for this type of integration per https://github.com/home-assistant/architecture/blob/master/adr/0010-integration-configuration.md |
Beta Was this translation helpful? Give feedback.
-
|
Wow, it never ceases to amaze me how well documented and thought out decisions are for the Home Assistant project! @bdraco, thanks for sharing. @AjaxOdessa, I feel your pain as I have 40+ devices that I had to do this for. But there is hope, @sbidy noted an auto-discovery feature which should make this a non-issue for you if you wait to upgrade (the waiting is the downside I guess we would have to accept). |
Beta Was this translation helpful? Give feedback.
-
|
Oops, @bdraco, already pointed out the auto-discovery. I didn't read carefully 😇 |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Should be available in Home Assistant 2022.3 beta in the next hour https://rc.home-assistant.io/blog/2022/02/23/release-20223/ Be sure to join the |
Beta Was this translation helpful? Give feedback.
and others
-
Hey folks....
I try to create a kind of Development Log to trace changes/decissions and made the current overall development status transparent to you!!
Projects, Repos and Info:
Beta Was this translation helpful? Give feedback.
All reactions